Friday Morning Release Party
usermilk writes "Apple has released an update for iMovie 3. It provides improved performance and stability, you can get it from the Software Update preference pane." Hopefully this resolves many of the complaints about what could be a really cool program. maxentius writes "The beta .7 version of
Camino has been released. Once Chimera, this tabbed browser and Apple's Safari might start a real browser war. Which one do you prefer?" And on that note, an anonymous user writes "Safari v64 is making the rounds according to macrumors. Safari v62 brought us Tabs, and this new version (v64) appears to provide increased stability, improved tab appearance, loading status for tabs, and enhanced autocomplete."
I haven't tried imovie3 yet, suprised though by the high sys req. Anyone with a G3 700 try it, how's it run? I must say I'm a little annoyed that any low end MAC can't run software made 6 months after you buy it. Apple always makes their new builds to the lowest MAC at the time. This is great if you have a high end mac, as the software stays cutting edge, but if you have a low end MAC you are doomed to keep it with the current software only. (I'm not fishing for flames here I have had low end macs for sometime and I love them they're great but it is a bit annoying)
Also I used camino exclusively and have switched to safari after the advent of tabs, anyone with me?
FIRST POST hahaha suckaz
I'm loving Safari, but I really want Apple to implement a feature that enables a user to have multiple homepages, which are displayed in different tabs at startup. I'm not sure if another browser has this feature, but I think it would be killer.
(Posting from Camino.)
.7 seems considerably more stable than Chimera .6 was. Chimera would crash pretty often if I had, say, three or four windows open, each with five or six tabs. I haven't been able to reproduce that with Camino.
... actually I'm not sure whether that works or not. It wastes space on the tab bar, that's for sure.
Both Safari v64 and Camino seem a bit faster, especially Camino. Also,
In Process Viewer, Camino seems a bit more memory efficient, particularly with several tabs open.
I prefer the mass-bookmark (tab group? favorite folder?) approach that Camino uses over Safari's implementation, which still seems pretty crude. I get where I need to be in fewer clicks with Camino. Not to say that Safari won't get better.
Rendering-wise, I think they look about the same, though I prefer the Camino widgets and layout, not to mention the tab metaphor logic. On the other hand, the Safari tabs each have their own close button, albeit a non-standard "x" in a circle
Now, what I want to see is the ability to make one's home page a tab group. That seems pretty obvious.
Imagine a Beowulf cluster of neurons.
Safari won't supplant Camino as my browser of choice until it gets Keychain integration like Camino has (it auto-fills user names and passwords on Web forms, not just on login dialogs and specially-coded forms).
One interesting tidbit is that they've announced that this will be the last Chimera/Camino release to be based on the 1.0 Mozilla branch. They'll finally be pulling up to the current Mozilla 1.3 branch, which should fix alot of bugs(Including one I find really annoying, which both Chimera and Safari share, the inability to copy/paste japanese text with most carbon apps, yay!), as well as provide some performance increase. This leaves only one big feature on my wishlist for Camino: Native text fields, with spell checking and all. Safari has spell checking, but it still has to be manually enabled for each field, which I consider a bug. Safari meanwhile is advancing at a breakneck pace. Beta62 had tabs, although there were some really annoying bugs (like the close tab command occasionally closing the whole window instead. DOH!). Hopefully today's b64 will fix that, in addition to adding tab support to bookmarks.
"The worst tyrannies were the ones where a governance required its own logic on every embedded node." - Vernor Vinge
when is MS going to update its IE for mac? it seems that they are falling behind even more every day. or is MS going to pull out of the mac browser market, which they previously had a large claim to. i cannot see that happening though, but i can see a MS browser on par with MS's flagship mac product, Office v.x. if IE played as nice as office on the mac, wed have a nice three way browser war, chim... err camino vs safari vs ie v.x. but seriously, ie for the mac is getting dusty its so outdated.
I want 2D games back.
No, they use the same key combos as Camino. Cmd-W closes a tab, or the window if there are no tabs, while Cmd-Shift-W closes the window if there are tabs (and oddly does nothing when no tabs are open, that's probably not optimum behavior).
They just hadn't finished implementing their custom menu/command keys in beta62.
In beta64, you can just open a tab and look in the file menu to see what I mean, the key combos are properly shown.
"The worst tyrannies were the ones where a governance required its own logic on every embedded node." - Vernor Vinge
In the release notes for Camino / Chimera, it mentions that they have added the functionality for proxy autoconfiguration (.PAC files). There is no preference pane for it, but I did find documentation about editing the user.js file in ~/Library/Application Support/ / though it still doesn't work.
Anyone else running an autoproxy and had better luck?
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
If you do have a presentation and want to keep people's attention, it really does work.
As for *why* it works, I actually think that it probably comes from our primitive past when we noticed motion as a possible preditor ready to attack us or possible prey ready to feed us. Our eyes and brain are trained to focus more on change than stasis.
I would point out though that a lot of people *don't* like the interface for Project Builder and do find it somewhat jarring compared to the rest of the OSX GUI. Still, I'm hard pressed to come up with a different way to do it functionally, beyond requiring a right click to a context menu. But that would then contradict Apple's desire to have a visual clue for action. (i.e. no "invisibile" UIs for necessary actions)
I should also point out that v64 fixes a bug that kept the tabs from looking right when you put an Aqua appearance to Safari instead of Brushed Metal. (It looks much better) For those who've not downloaded v64 for fear of stability issues, you can check it out along with a discussion at MacNN.
I'm one of those who hasn't downloaded the beta. I prefer stability at the moment and the public beta of Safari is very nice. (I think Apple just made references to these betas to get the tab fanatics out of their hair) One thing I hope that the Safari final has is the ability ala Adobe apps to drag tabs out of the window and automatically create a new window.
I switched back to Camino after printing several pages from Safari. Safari's notion of printing is actually worse than printing in Netscape 4 was, a hard act to follow.