dethmaShine
Apr 19, 02:37 PM
WRONG! They weren't invented at Apple's Cupertino HQ, they were invented back in Palo Alto (Xerox PARC).
Secondly, your source is a pro-Apple website. Thats a problem right there.
I'll give you a proper source, the NYTimes, which wrote an article on Xerox vs Apple back in 1989, untarnished, in its raw form. Your 'source' was cherry picking data.
Here is one excerpt.
Then Apple CEO John Sculley stated:
^^ thats a GLARING admission, by the CEO of Apple, don't you think? Nevertheless, Xerox ended up losing that lawsuit, with some saying that by the time they filed that lawsuit it was too late. The lawsuit wasn't thrown out because they didn't have a strong case against Apple, but because of how the lawsuit was presented as is at the time.
I'm not saying that Apple stole IP from Xerox, but what I am is that its quite disappointing to see Apple fanboys trying to distort the past into making it seem as though Apple created the first GUI, when that is CLEARLY not the case. The GUI had its roots in Xerox PARC. That, is a FACT.
Who said Apple created the first GUI.
Jobs himself credits Xerox for their GUI. :rolleyes:
Secondly, your source is a pro-Apple website. Thats a problem right there.
I'll give you a proper source, the NYTimes, which wrote an article on Xerox vs Apple back in 1989, untarnished, in its raw form. Your 'source' was cherry picking data.
Here is one excerpt.
Then Apple CEO John Sculley stated:
^^ thats a GLARING admission, by the CEO of Apple, don't you think? Nevertheless, Xerox ended up losing that lawsuit, with some saying that by the time they filed that lawsuit it was too late. The lawsuit wasn't thrown out because they didn't have a strong case against Apple, but because of how the lawsuit was presented as is at the time.
I'm not saying that Apple stole IP from Xerox, but what I am is that its quite disappointing to see Apple fanboys trying to distort the past into making it seem as though Apple created the first GUI, when that is CLEARLY not the case. The GUI had its roots in Xerox PARC. That, is a FACT.
Who said Apple created the first GUI.
Jobs himself credits Xerox for their GUI. :rolleyes:
Arcus
Apr 25, 03:46 PM
Sued for breaking what law?
Being sued and breaking the law are two different things. I can sue you for killing the tree between our yards. You didnt break any law, but I can still sue.
I kinda see where he is a bit right. If I turn off or say no to allowing the apps to use my location this might suggest to the user that it is not tracking and storing this data. I do not think that it is a stretch to make that connection.
I do agree this is way out of hand though.
Being sued and breaking the law are two different things. I can sue you for killing the tree between our yards. You didnt break any law, but I can still sue.
I kinda see where he is a bit right. If I turn off or say no to allowing the apps to use my location this might suggest to the user that it is not tracking and storing this data. I do not think that it is a stretch to make that connection.
I do agree this is way out of hand though.
R94N
Aug 18, 05:23 AM
A blue PS3 is a nice idea.
GQB
Mar 31, 05:10 PM
Good. I hope they take one of the last strengths of the iPad ecosystem away from it.
If you're going to spew nonsense, at least make it relevant to the thread.
If you're going to spew nonsense, at least make it relevant to the thread.
THX1139
Aug 21, 02:09 AM
I stopped by the Apple store tonight to play with a Macpro. I'm getting ready to buy and thought I'd get some hands on experience to see how it performed with Finalcut Pro. I was especially interested in how it handles playback of uncompressed footage.
The store had a 2.6 hooked up to a 30"ACD. Everything on the machine was stock. I launched FCP and it appeared with a project already loaded (about 5 seconds). The project was a simple 20-30 second 720x480 NTSC clip of hockey game footage. I selected the clip and copied it to a new layer and threw a blend mode on it AND changed the speed to 85%. Next I copied and made another layer and changed the speed and offset it and changed the transparency to 80%. 3 layers total with the top two manipulated. I hit the render and it finished in about 30 seconds. :)
I know, not very scientific, but I just wanted to get a feel for how fast the Macpro would render manipulated footage. Anyhow, next I changed the output in project settings to "uncompressed" and hit render again. Again, it took less than a minute to render and the CPU usage in console was maxing out at only 42% per core.
Once the render completed, I hit the play button to see how the stock Macpro would handle playback of the uncompressed footage. It played for about 4 seconds then threw an error saying that frames were being dropped during playback. Not good. I was hoping that the Macpro would be able to play uncompressed footage from the timeline without 3rd party acceleration or setting up a raid. The error message suggested turning off RT effects (of which I did, but still had dropped frames) or get a faster drive. There was a couple other things the error suggested, but I can't remember at the moment. I wonder if having the ATI card would have made a difference? Not sure if FCP uses the GPU for playback, but I would think that should make a difference. Ram would probably help too. Anyone know what might be going on? Am I expecting too much out of this machine?
Sorry for sort of getting off topic. I thought this might be an appropriate area to post this; I wasn't feeling up to starting a new thread.
The store had a 2.6 hooked up to a 30"ACD. Everything on the machine was stock. I launched FCP and it appeared with a project already loaded (about 5 seconds). The project was a simple 20-30 second 720x480 NTSC clip of hockey game footage. I selected the clip and copied it to a new layer and threw a blend mode on it AND changed the speed to 85%. Next I copied and made another layer and changed the speed and offset it and changed the transparency to 80%. 3 layers total with the top two manipulated. I hit the render and it finished in about 30 seconds. :)
I know, not very scientific, but I just wanted to get a feel for how fast the Macpro would render manipulated footage. Anyhow, next I changed the output in project settings to "uncompressed" and hit render again. Again, it took less than a minute to render and the CPU usage in console was maxing out at only 42% per core.
Once the render completed, I hit the play button to see how the stock Macpro would handle playback of the uncompressed footage. It played for about 4 seconds then threw an error saying that frames were being dropped during playback. Not good. I was hoping that the Macpro would be able to play uncompressed footage from the timeline without 3rd party acceleration or setting up a raid. The error message suggested turning off RT effects (of which I did, but still had dropped frames) or get a faster drive. There was a couple other things the error suggested, but I can't remember at the moment. I wonder if having the ATI card would have made a difference? Not sure if FCP uses the GPU for playback, but I would think that should make a difference. Ram would probably help too. Anyone know what might be going on? Am I expecting too much out of this machine?
Sorry for sort of getting off topic. I thought this might be an appropriate area to post this; I wasn't feeling up to starting a new thread.
nick123222
Mar 27, 03:59 AM
I use Spotlight, but Launchpad is terribly inefficient compared to stacks. You have to click on its icon to invoke it, hunt through potentially a bunch of different screens, click on a folder if you've organized your apps, and then click on your app. With stacks, I move my cursor down to the dock, click on the appropriate stack, and then click on my app. 2 clicks vs a button press, a bunch of swipes, hunting, and 2 more clicks.
Yes but, with stacks, I often have to do a lot of scrolling to find the app in my applications folder because I haven't spent the time to organise it all into folders. With launchpad, I would have every app in a folder (probably) so I would probably have only 1-3 pages. For me the number of clicks will be the same for the apps that I store in folders already, just with less scrolling:
Stacks: click the stack, scroll to the folder, click the folder, click the app.
Launchpad: click launchpad, swipe to the correct page (if necessary), click the folder, click the app.
I think it will be easier to find apps in launchpad because of the easy use of folders and the fact that it is fullscreen.
Yes but, with stacks, I often have to do a lot of scrolling to find the app in my applications folder because I haven't spent the time to organise it all into folders. With launchpad, I would have every app in a folder (probably) so I would probably have only 1-3 pages. For me the number of clicks will be the same for the apps that I store in folders already, just with less scrolling:
Stacks: click the stack, scroll to the folder, click the folder, click the app.
Launchpad: click launchpad, swipe to the correct page (if necessary), click the folder, click the app.
I think it will be easier to find apps in launchpad because of the easy use of folders and the fact that it is fullscreen.