optikz writes "Apple has just released Safari 1.0 and it is availlable via Software Update. This release is now out of the 'beta' stage. It is version 1.0 (v85)." Not much appears to have changed since the last beta. I just need to decide if it should replace Camino for me.
Seems faster
by
Llywelyn
·
· Score: 4, Informative
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
The default font has also changed to Times. Pages rendered look much more like IE now.
Re:Still a little buggy
by
babbage
·
· Score: 4, Informative
Don't tell us -- file a bug! If you had it active before, the "bug" icon may have gone away with the 1.0 upgrade, but it can be restored, and "Repot bugs to Apple..." is still the second item under the Safari menu.
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
Re:Some stuff still needs fixin'
by
bedouin
·
· Score: 4, Informative
http sites load okay, but https sites do not work at all.
Just curious, have you tried it recently? There was a bug in early builds of Safari where secure proxies simply didn't work; it's since been fixed.
Re:Cross-platform web design issue
by
thumperward
·
· Score: 4, Informative
Webcore renders in a similar way to Gecko. If you absolutely must know how it renders in Safari though, get a Knoppix CD and check with Konqueror.
- Chris
RAM Disk in OS X and how to move Safari's cache
by
SensitiveMale
·
· Score: 5, Informative
70% of this code isn't mine, but found I bits everywhere.
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs/dev/r" & myDevDisk as text
do shell script myShellCmd
do shell script "hdiutil mount/dev/" & myDevDisk
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Then delete the folder "your home/library/caches/safari"
Run this command -
ln -s "/Volumes/RAM Disk" ~/Library/Caches/Safari
That will create the link between the RAM disk and your safari cache folder.
That's it. Works perfectly and much much faster.
You will have to run the applescript at login.
You only have to run the terminal commands once.
Re:What was the default font before?
by
ProfKyne
·
· Score: 4, Informative
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
Slashdot Mirror
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
Integrate Keynote and LaTeX
The default font has also changed to Times. Pages rendered look much more like IE now.
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
DO NOT LEAVE IT IS NOT REAL
http sites load okay, but https sites do not work at all.
Just curious, have you tried it recently? There was a bug in early builds of Safari where secure proxies simply didn't work; it's since been fixed.
Webcore renders in a similar way to Gecko. If you absolutely must know how it renders in Safari though, get a Knoppix CD and check with Konqueror.
- Chris
70% of this code isn't mine, but found I bits everywhere.
/dev/r" & myDevDisk as text /dev/" & myDevDisk
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs
do shell script myShellCmd
do shell script "hdiutil mount
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Close Safari.
Open terminal.
Run this command -
ditto -rsrc ~/Library/Caches/Safari "/Volumes/RAM Disk/"
Then delete the folder "your home/library/caches/safari"
Run this command -
ln -s "/Volumes/RAM Disk" ~/Library/Caches/Safari
That will create the link between the RAM disk and your safari cache folder.
That's it. Works perfectly and much much faster.
You will have to run the applescript at login.
You only have to run the terminal commands once.
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
"First you gotta do the truffle shuffle."