Slashdot Mirror


Apple Releases Safari 1.2 and Java 1.4.2

smithk writes "Apple has released Safari 1.2 and Java 1.4.2. Panther owners only. Some new features of Safari include full keyboard access for navigation, download resume, support for LiveConnect, and support for personal certificate authentication. Also, web site compatibility has been improved." Available, as usual, via Software Update.

13 of 273 comments (clear)

  1. resumable downloads and liveconnect!!! by johnjosephbachir · · Score: 5, Informative

    these two features have been annoyingly absent from safari since it came out and now they are finally here.

    i wonder if/when the liveconnect code will trickle back up to konqueror (or is that where it came from in the first place? does konqueror have liveconnect now?)

    1. Re:resumable downloads and liveconnect!!! by johnjosephbachir · · Score: 5, Informative

      this is LiveConnect I'm actually not totally familiar with its history but i know it's used by the Flash plugin to be able to talk to browser windows. Does anyone have any good examples of where it is useful for Java applets or anywhere else?

  2. Re:once again by Trillan · · Score: 5, Interesting

    They don't really have that much choice in this case. There were a lot of fixes to Core Graphics and other frameworks of Panther (little things like text not rendering properly). I don't think it's at all realistic for Apple to back-port those fixes to Jaguar. And without them, Safari 1.1 and 1.2 would look terrible.

  3. Re:once again by Anonymous Coward · · Score: 5, Insightful

    Yeah, but I won't pay $130 to update it.

    Then you don't get the free web browser that Apple graciously supplies for users of their current operating system.

    It's simple. If you don't want to pay for what they're offering, that's your call. But you can't complain that you don't get the perks.

    Where does your sense of entitlement come from?

  4. User stylesheets by weeeeed · · Score: 5, Informative
    Well, since you are already hacking around in some files, why not just create a user style sheet? No "...series of hacks on top of Apple's WebKit framework...", just pure CSS.

    Create a css file somewhere with a text editor, put following inside (Not made by me, just found it somewhere and made some additions):
    /*
    * This file can be used to apply a style to all web pages you view
    * Rules without !important are overruled by author rules if the
    * author sets any. Rules with !important overrule author rules.
    */

    /*
    * turns off "blink" element blinking
    */
    blink { text-decoration: none ! important; }

    /*
    * hides many ads by preventing display of images that are inside
    * links when the link HREF contans certain substrings.
    */

    A:link[HREF*="ad."] IMG { display: none ! important }
    A:link[HREF*="ads."] IMG { display: none ! important }
    A:link[HREF*="/ad"] IMG { display: none ! important }
    A:link[HREF*="/A="] IMG { display: none ! important }
    A:link[HREF*="/click"] IMG { display: none ! important }
    A:link[HREF*="?click"] IMG { display: none ! important }
    A:link[HREF*="?banner"] IMG { display: none ! important }
    A:link[HREF*="=click"] IMG { display: none ! important }
    A:link[HREF*="/ar.atwo"] IMG { display: none ! important }
    A:link[HREF*="spinbox."] IMG { display: none ! important }
    A:link[HREF*="transfer.go"] IMG { display: none ! important }
    A:link[HREF*="adfarm"] IMG { display: none ! important }
    A:link[HREF*="bluestreak"] IMG { display: none ! important }
    A:link[HREF*="doubleclick"] IMG { display: none ! important }

    /* disable ad iframes */
    IFRAME[SRC*="ad."] { display: none ! important }
    IFRAME[SRC*="ads."] { display: none ! important }
    IFRAME[SRC*="/ad"] { display: none ! important }
    IFRAME[SRC*="/A="] { display: none ! important }
    IFRAME[SRC*="/click"] { display: none ! important }
    IFRAME[SRC*="?click"] { display: none ! important }
    IFRAME[SRC*="?banner"] { display: none ! important }
    IFRAME[SRC*="=click"] { display: none ! important }
    IFRAME[SRC*="/ar.atwo"] { display: none ! important }
    IFRAME[SRC*="spinbox."] { display: none ! important }
    IFRAME[SRC*="transfer.go"] { display: none ! important }
    IFRAME[SRC*="adfarm"] { display: none ! important }
    IFRAME[SRC*="bluestreak"] { display: none ! important }
    IFRAME[SRC*="doubleclick"] { display: none ! important }

    xIMG[usemap] { display: none ! important }

    /* turning some false positives back off */

    A:link[HREF*="download."] IMG { display: inline ! important }
    A:link[HREF*="click.mp3"] IMG { display: inline ! important }

    /*
    * For more examples see http://www.mozilla.org/unix/customizing.html
    */
    Add this file as your Stylesheet in safari: Preferences/Advanced/Style Sheet.... there you go...

    Most tips for the Mozilla userContent.css file work also with Safari, so search on google for userContent.css for more examples.
  5. Safari 1.2 improves image downloading a lot by GrahamCox · · Score: 5, Informative

    Apart from the fact that downloads can now be resumed, image downloads are much better. Previously, if you dragged an image from the browser to the desktop (or wherever), it would download it AGAIN. Now it simply copies the image from the cache, if it's up to date. Halve your bandwidth overnight! Also, image icons with a download in progress are no longer broken - the icon shows an animated progress bar (!) until the d/l is complete, then the proper icon shows up. The only thing missing is that the image file doesn't store a preview, so you still get the generic icon browsing downloaded images in the Open dialog.

    Still to be fixed: The annoying jumping around that happens when reloading a previously scrolled page. It should stop trying to remember the old scroll position if it receives a new scroll event for that page in the meantime.

  6. Still no navigation via contexual menu by calstraycat · · Score: 5, Interesting

    Everybody's got their favorite pet peeve and this one is mine. It's obvious now that the Grand Puba in charge of features has decided that thou shalt only only navigate via the toolbar. This omission remains despite the fact that every other browser on earth provides this feature and it is used by a majority of web surfers. My wife won't use it due to this inexplicable omission. She just gives me an incredulous look and exclaims "what do you mean there's no back and forward when I click? This thing sucks". Safari is my main browser and I like it a lot, but this is a major shortcoming in my book.

    When it comes to application features, I'm often able to understand the reasoning behind a particular implementation even if I don't personally like it. But, for the life of me, I can't think of one good reason to leave this feature out.

    Can anyone enlighten me on the advantages of always having to mouse to the upper left-hand corner to go to the previous page? Am I missing something? I know I can do it from the keyboard, but I often like to kick back and just use the mouse.

    BTW, the update is nice. Faster. Renders some sites that previously were unreadable and/or unusable. I love the minimum font size feature and being able to tab through page items.

  7. No concurrent http connection limit by joni · · Score: 5, Informative

    The most notable change for me was the removal of the stupid four concurrent http connections limit. If you had four files downloading all you web browsing would just stop until one of the downloads finished.

    Now that limit is gone. I just tried adding huge list of files for download and opened multiple tabs and everything worked beautifully. Also it's great to be able to resume failed downloads, no need for third party download managers anymore.

  8. Re:changes to KHTML? by Meowing · · Score: 5, Informative

    Yes, they're sticking to their promises. You can get the source to WebCore v125 from this page.

  9. Damnit. When will we get ... by torpor · · Score: 5, Insightful

    ... 'session save' capabilities? Or, can we already do this with Safari, and I'm just clueless?

    What I'm talking about is that when you close Safari, it remembers all your current tabs, all your windows, all your sites, and then when you re-launch it, it restores the whole 'session' to the way it was ... I can't freakin' believe that browsers don't have this as a standard feature, but oh well.

    Guess I should just dl the source and whack it in there myself... trouble is, I'm not sure I haven't overlooked how to do this yet ...

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  10. Re:once again by Anonymous Coward · · Score: 5, Informative

    The wrapping of ObjC to Carbon and vice versa is analogous to the Java Bridge between ObjC and Java NeXT developed during the WebObjects transition from ObjC to Java.
    Cocoa and Carbon both sit on top of CoreFoundation and ApplicationServices. They are not wrapped to each other, they just use the same frameworks.

    The decision to focus ObjC on the desktop and not on the AppServer has been one that bit Apple in the ass and they know it.
    What?

    The advantages were removed from their products.
    Like... ??? At best it took Carbon a while to support services. Apple directly says not to use PDO; to use Apple Events or sockets instead.

    MVC Paradigm is at the very core of OS X. Linking to MachO was necessary because the OS was slow when all the Carbon/BlueBox/Classic layers were added.
    Eh? Mach supports host OSes. BSD is one of them; Mac OS 9 is another. Carbon is just an API, not a layer. MVC is a development style, not something core to Cocoa.

    Over time you will see OS X improve due to more Cocoa integration (new Finder being one example) and moreso. The latest Dev examples should show you how much the underpinnings of Cocoa are in Carbon now.
    Now you're talking out of your ass. The new Finder is not new, it's just got a stupid textured window. It's still written in PowerPlant. It is not linked to Cocoa at all.

    % otool -L /System/Library/CoreServices/Finder.app/Contents/M acOS/Finder | grep /Cocoa.framework
    % otool -L /System/Library/CoreServices/Finder.app/Contents/M acOS/Finder | grep /AppKit.framework
    % otool -L /System/Library/CoreServices/Finder.app/Contents/M acOS/Finder | grep /Foundation.framework
    % otool -L /System/Library/CoreServices/Finder.app/Contents/M acOS/Finder | grep /PowerPlant.framework
    /System/Library/PrivateFrameworks/PowerPlant.frame work/Versions/A/PowerPlant (compatibility version 1.0.0, current version 76.0.0)
    % otool -L /System/Library/CoreServices/Finder.app/Contents/M acOS/Finder | grep Carbon.framework
    /System/Library/Frameworks/Carbon.framework/Versio ns/A/Carbon (compatibility version 2.0.0, current version 128.0.0)
    % otool -L

    Carbon's an API from the original Mac OS that was first modernized to be re-entrant. Then Apple started adding features to an API that the old management team declared dead since Taligent began, and continued with OpenDoc/ODF.

    POSIX Compliance is necessary if one wants to work within the Federal Markets. And that's smart since the Feds have deep pocketbooks.
    No, POSIX is necessary because no one is going to use your non-Unix if it isn't compatible with POSIX (non-POSIX == not Unix). Even Linux implements POSIX. BSD 4.4 Lite and NeXT did not. NeXT didn't support it because they didn't have the money or the time. Hell, it had cthreads instead of pthreads, which every other OS implements. Do you expect anyone to write custom threading code for Mac OS X?

    There are now two major OSes on the planent. Win32 and POSIX. It would be stupid for Apple to not implement POSIX.

    The corporations who whined won back in 1998--Adobe, Microsoft, Quark, Macromedia and a few others demanded Carbon.
    No, Carbon (a procedural API) wasn't part of Rhapsody because Gill Amelio was an idiot. Porting from one object oriented framework (say, MFC) to another (say, Java or Cocoa) is, as Steve Jobs described it, like climbing down one 10 story building and climbing up another for everything you need to implement. Porting from one OOP framework and implementing it on another platform requires implementing the backend of the framework on the other OS (sa

  11. Re:once again by tyrione · · Score: 5, Interesting

    By the way, NeXT did support POSIX, but that required a specific support contract, so no it did not support POSIX, out-of-the-box but for Fed clients who demanded it we put it in.

    I was there at Apple when the decisions were made.

    Steve was asked by Fred Anderson what would it take to have you come back as CEO, because Gil is ignoring your advice and we are afraid with only 3 months of money left the company will fold?

    Steve wanted an interim title and the opportunity to build a new board of directors.

    He then made a decision to settle the Microsoft dispute and bury the hatchet, once and for all. That came down to private meetings.

    Avie, Bertrand Serlet and others were holding high level meetings with third party developers as I've hinted at to convince them to use Cocoa and they informed them that would set them back years and there had to be a better way.

    Back to Engineering and several weeks of brainstorming the teams decided to take the massive amounts of Procedural APIs and wittle it down to a reasonble number that they could then leverage the bulk of the legacy support and mesh them, over time with the future direction of Application Development grounded in Objective-C's Foundation and AppKit APIs.

    CoreFoundation was born along with countless other APIs for cross pollination.

    Gil Amelio saw the power of Cocoa and like anyone who hasn't developed much just thought it could Presto! change everything overnight. He was more than happy to dump the past and launch into the future with a new set of APIs that had nearly a decade of development already invested in them--Openstep.

    No one at NeXT was thrilled with Java--they got it almost right is what the usual comments were up to "If only Sun would ever 'get' objects."

    Java tries to be the best of both C++ and ObjC and misses on both but gee like any language if you don't get broad adoption it is perceived as being an inferior choice.

    No one from the NeXT encampment has ever "wanted" to port Apps using Procedural APIs, unless you count the Quartz group which wrote Quartz and they wrote WindowServer.app in C. Just ask Andrew Barnes or Peter Graffanino how many lines of C are in Quartz or how many were in Openstep's WindowServer.app.

    The languages used within OS X are chosen when it makes the most sense both technically and politically.

    BeOS died because its founder's arrogance was greater than the technologies the company could offer Apple. The man wanted > $100Million and a top spot back at Apple. He was concerned about himself, first and foremost. The cost of NeXT exactly paid off the debts NeXT owed to Canon and other investors. Steve made nothing out of the deal and was reluctant to even come onboard, hence his original role as a consultant. He was concerned that the 300 plus NeXT employees were still gainfully employed and that our stock options would be honored, which they were.

    The best day I remember was when Steve cancelled Sabbaticals and all those that were hanging around for their 3 month Sabbaticals all quit and stated the only reason they were here was for the 3 free months of pay. As I stated earlier Apple only had 3 months of money and paying for 1/3 of the Corporate Staff to sit on their rears and have a long vacation just wasn't gonna cut it.

    Smart Politics, Outstanding Vision, Compassion for the Company as a whole and other attributes is what makes Steven P. Jobs the best person and only person that could have and has save Apple Computer Inc, from oblivion.

    Fred Anderson is right up there, in my book, as one of the most able and intelligent executives I as a peon got to talk with and work for.

    Apple just keeps getting stronger and stronger and if I recall thats what we want from Her.
  12. OmniWeb 5.0 Public Beta by jjc2222 · · Score: 5, Informative

    For people interested in an alternative to Safari, the Omni Group just released the first public beta of OmniWeb 5.0. It has some cool new features including a particularly nice tabs implementation, a (IMHO) more flexible interpretation of Apple's SnapBack, and site-specific preferences.

    I don't mean to sound like an advertisement, and to be sure, OmniWeb has its quirks, but I thought I'd throw it out there.

    Here is a link.