Slashdot Mirror


Etoile Project Releases Mac-Like Environment

pschmied writes "Today the Étoilé Project released v0.2 of its Desktop Environment. Not only does Étoilé share user interface similarities with Mac OS X, Étoilé enjoys some source-level compatibility with Mac OS X as well. Many here undoubtedly remember NeXT, the revolutionary computer / development environment that gave rise to the first Web browser and later became the foundation of Mac OS X. Étoilé uses the FSF's own implementation of the NeXT development environment, GNUstep, making this a close technological relative of OS X. Screenshots and a source tarball are available."

311 comments

  1. Oblig. by Aetuneo · · Score: 1, Funny

    I, for one, welcome our new Mac-like overlords.

    --
    Everything is subjective.
    1. Re:Oblig. by Anonymous Coward · · Score: 0, Flamebait

      you like, all of the other slashdotters that post stupid drivel like this, are an idiot.

    2. Re:Oblig. by Anonymous Coward · · Score: 0

      That's it, you're first to the sugar caves.

    3. Re:Oblig. by SpaceballsTheUserNam · · Score: 0

      "you like, all of the other slashdotters that post stupid drivel like this, are an idiot." Perhaps it is just your own unique leet writing style, in which case its all good, but I think you meant to have placed the comma after "you," not after "like." Otherwise it can be quite confusing.

      --
      \.
    4. Re:Oblig. by ubrgeek · · Score: 2, Funny

      "... built from the ground up on highly modular and light components with project and document orientation in mind, in order to allow users to create their own workflow by reshaping or recombining provided Services (aka Applications), Components etc. Flexibility and modularity on both User Interface and code level should allow us to scale from PDA to computer environment."

      All that's missing from that description is "synergy" and "paradigm." Throw those in there and the VC money will start flowing in ;)

      --
      Bark less. Wag more.
    5. Re:Oblig. by Anonymous Coward · · Score: 0

      I had to read it twice to understand what his message with that comma in the wrong spot.

    6. Re:Oblig. by jrjarrett · · Score: 1

      All that's missing from that description is "synergy" and "paradigm." Throw those in there and the VC money will start flowing in ;)

      Or you can yell, "BINGO!"

    7. Re:Oblig. by Anonymous Coward · · Score: 0

      While I second your assertion regarding the grandparent's intelligence, such banality is often the extent of the average slashdotter's intellectual capacity - or merely the easiest means to karma whore.

      Btw, I propose forming an Anonymous Coward "You are an idiot" squad (if such does not already exist).

    8. Re:Oblig. by Charles+W+Griswold · · Score: 1

      you like, all of the other slashdotters that post stupid drivel like this, are an idiot.

      I snicker at the irony of your statement. :-P

      --
      "Those who are too smart to engage in politics are punished by being governed by those who are dumber" -- Plato
    9. Re:Oblig. by jedidiah · · Score: 1

      I remember back when this project started (GNUStep). Since NextStep seemed cool at the time it seemed like a very cool thing. This was back before GNOME or KDE got started. So something like this was woefully needed. Unfortnately, development seemed to be progressing much like it was for Hurd at the time.

      GNUstep was what originally prompted me to switch from Slackware to Redhat... all of those dang little dependencies. Trying to build gnustep myself was a b*tch and a half. That's saying a lot since my BS tolerance was a lot higher back then. ...hadn't been spoiled by Mandrake or Ubuntu yet.

      So now this stuff is finally seeing the light of day after all of this time...

      --
      A Pirate and a Puritan look the same on a balance sheet.
    10. Re:Oblig. by Charles+W+Griswold · · Score: 1

      "... built from the ground up on highly modular and light components with project and document orientation in mind, in order to allow users to create their own workflow by reshaping or recombining provided Services (aka Applications), Components etc. Flexibility and modularity on both User Interface and code level should allow us to scale from PDA to computer environment."

      All that's missing from that description is "synergy" and "paradigm." Throw those in there and the VC money will start flowing in ;)

      "... built from the ground up on highly modular and light components with project and document orientation in mind, in order to allow users to create their own synergy paradigm by reshaping or recombining provided Services (aka Applications), Components etc..."

      4) Profit!

      --
      "Those who are too smart to engage in politics are punished by being governed by those who are dumber" -- Plato
  2. Way to confuse NEXT with Mach and BSD by Anonymous Coward · · Score: 0

    Oh but it uses objective-C it must be NEXT!

    1. Re:Way to confuse NEXT with Mach and BSD by HeroreV · · Score: 4, Informative
      You are confused (or trolling). Here's a history lesson:
      1. NeXT creates the NextStep/NeXTstep/NeXTSTEP/NEXTSTEP operating system
      2. NeXT releases a specification for some of their API as OpenStep
      3. NeXT makes NEXTSTEP conform with the OpenStep spec and rebrands NEXTSTEP as OPENSTEP
      4. Apple buys OPENSTEP and uses it to produce Mac OS X
      5. GNU implements the OpenStep API as GNUstep
      6. the Étoilé desktop environment is built on GNUstep

      Mac OS X's Cocoa API is based on the OpenStep API, so Étoilé and GNUstep are related to Mac OS X through the OpenStep API. If you really love the Cocoa API and you want to make an app for Linux, you should take a look at GNUstep.
    2. Re:Way to confuse NEXT with Mach and BSD by Anonymous Coward · · Score: 2, Informative

      Way to show that you know nothing about NeXT, and can't even read the summary of an article, let alone the article itself.

      Here are some facts which might spur you to actually find something out about NeXT so you don't make a fool of yourself the next time you try to say something about this...

      Etoile is based on GNUstep, which is based on the Openstep Specification published by NeXT.

      Mac OS X is based on Rhapsody which was based on Openstep which was based on Nextstep which is the basis of the Openstep Specification.

      Mach and BSD4.3 were a basis for Nextstep, but by no means were they necessary. The Openstep environment has run on top of Solaris, HP-UX and even Windows.

      The intention of NeXT was, for a large part of their existence to make the underlying hardware and OS irrelevant, something that you have seen playing into Apple's favour of late with the Intel transition and iPhone OS.

      You insult both NeXT's work and Gnustep by insinuating that they need Mach or BSD to be "NEXT".

    3. Re:Way to confuse NEXT with Mach and BSD by jrumney · · Score: 3, Informative

      4. Apple buys OPENSTEP and uses it to produce Mac OS X
      5. GNU implements the OpenStep API as GNUstep

      I think you have these two the wrong way around. GNUstep dates back to at least 1995, while Apple did not buy NeXT until December 1996.

    4. Re:Way to confuse NEXT with Mach and BSD by blankaBrew · · Score: 2, Interesting

      You are absolutely correct. In fact, NeXT was positioning OPENSTEP as what Java later turned out to be; write once, run anywhere. Actually, Sun was very interested in NeXT and included it in Solaris. However, a funny thing happened. About a year or two after Sun became involved in OPENSTEP, they dropped it and came out with their own environment called Java. Amazing to think how history might have changed if they stayed the course with OPENSTEP, rather than coming out with their own Java.

      So, OPENSTEP/NeXTSTEP/Cocoa/GNUstep are in no way tied to their BSD underpinnings, and have actually been implemented over other OSes.

    5. Re:Way to confuse NEXT with Mach and BSD by HeroreV · · Score: 1

      That's correct, and Wikipedia says GNUstep also came before NeXT rebranded NEXTSTEP as OPENSTEP. I just wasn't sure at the time and I wasn't as concerned about the order as I was about the actions.

  3. Mac OSX? by Daengbo · · Score: 2, Insightful

    Except for the fact that it has a top panel and a launcher, I don't see the similarity to Mac OSX (Not that I really use either of them -- just seen screenshots). Honestly, it reminds me more of WindowMaker using GnuStep apps. I think GnuStep is a great platform, though, and am glad that someone is finally puuting together a DM for it from the ground up, instead of using WindowMaker or similar. With the ease of development GnuStep gives, I guess the project could develop quickly if enough people get on board.

    1. Re:Mac OSX? by marcello_dl · · Score: 3, Informative

      In fact if I got TFA it has similarities with what the mac could have been if Apple didn't practically kill hypercard and left the newton and opendoc to wither. The monolithic app is what commercial software vendors want, while a document or object centric environment is very exciting from the power user point of view. In fact is kinda translating the unix philosophy of making specialized tools work together for complex tasks in a GUI and OO.

      If it can be done and they also find ways to integrate the now ubiquitous web applications' data, database, and other languages in that environment we could end up, for example, having a set of remote EJBs and Rails's active record objects, a couple local database rows and some emails being processed by a filter written in c that once belonged to openoffice calc, ending up in a nice graph.

      Anyway, Gnome's bonobo, netbeans and probably lots of other projects wanted to achieve something like this as a primary or secondary goal, maybe people don't want such a paradigm shift.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    2. Re:Mac OSX? by Daengbo · · Score: 0, Redundant

      (This is a bitch about moderation -- sorry):
      Overrated? WTF? No karma bonus. Standard score. I actually read the article before posting. Geez! If there were more of these hitting me today, I'd assumed I god mod-bombed. As it is, I think someone is just in a bad mood.

    3. Re:Mac OSX? by Ilgaz · · Score: 2, Interesting

      I am saying something for 3-4 years since I switched to OS X as ex Slackware/WindowMaker user.

      If people supported WindowMaker/OpenStep as they really seem to get impressed with OS X Desktop, things could really change in Linux Desktop scene. Especially those guys who spend hard time trying to make OS X work flawless on white box PCs via binary hacks.

      Thanks to Fink project I checked WindowMaker again on OS X and I easily recommend it to Mac only people wanting a "real" fullscreen X11 since it is very close to OS X Desktop. In fact I made it my default X11 windowmanager easily. It has some features which lacks from OS X as it would confuse average end user (in Apple eyes) which are there on Next.

      If Apple releases Cocoa etc. stuff for open source systems one day, I am sure they will first check WindowMaker and AfterStep.

      It is either the submissions choice of words/headline or some Linux distro known for its fanatics but the discussion under this story is completely off topic. I think it is a waste.

    4. Re:Mac OSX? by metamatic · · Score: 1

      I imagine you got downmodded because you said you didn't see any similarity between it and OS X, when even a cursory reading of the discussion would reveal that the similarity is in both OSs being descendants of OpenStep.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    5. Re:Mac OSX? by Anonymous Coward · · Score: 0

      I agree it looks like Gnome with a dockbar. It doesn't look or have any similiarity to Mac OS X other than the existence of a dockbar.

    6. Re:Mac OSX? by Daengbo · · Score: 1

      Since I made the third comment in the discussion, it's safe to assume I read the entire thread before posting.

  4. Menus at the top! by kinabrew · · Score: 5, Insightful

    Finally, an open-source desktop environment whose developers understand that menus at the top are infinite targets and always in the same place and therefore are easier to hit.

    1. Re:Menus at the top! by aichpvee · · Score: 0, Troll

      Why not just make the screen one big button? Can't miss that and it takes less movement of the eye and won't confuse anyone as to what app the button belongs to because it obviously belongs to the only one taking up the whole screen.

      --
      The Farewell Tour II
    2. Re:Menus at the top! by gilesjuk · · Score: 2, Interesting

      It's a pain when you have dual screens though. With OSX you have to choose which screen gets the menubar.

      There's hacks to work around it of course.

    3. Re:Menus at the top! by Chilled+urine. · · Score: 0, Offtopic

      Finalee aye kan take a piss in an etoilet!

    4. Re:Menus at the top! by Anonymous Coward · · Score: 0

      Yeah, I mean it's not as if KDE has had that option for years and years!

      And the captcha I get is "nonsense," how fitting.

    5. Re:Menus at the top! by kinabrew · · Score: 2, Interesting

      A simple solution to that is to have menu bars appear on both screens if there are applications on both screens.

      Just show the menu bar on both screens with the menus of whatever is the front application on that particular screen.

    6. Re:Menus at the top! by Tangent128 · · Score: 0

      If it's open source, can't one just add an "on all screens" setting?

    7. Re:Menus at the top! by kinabrew · · Score: 2, Informative

      Actually, while KDE has long had the option to put the menu bar at the top of the screen, the last time I used KDE, if you move your mouse to the very top of the screen, you would still click above the menu, not activating it.

      You can't click above a Mac menu. Being against the edge of the screen makes it an infinite target, making it easier to hit. Just zip your mouse straight up to the top of the screen, and click.

      It's another example of programmers copying the way things look rather than the way they work.

    8. Re:Menus at the top! by dltaylor · · Score: 1

      I dislike giving up screen real estate for a menu or task bar, and I resent the additional mouse movement to reach it. As near as I can tell, no one has improved on Sawfish/Sawmill in ease of use, since I could get a menu and task list at any point on the root window, allowing me to minimize mouse travel, and the task bar wasn't cluttering up the lower or upper edge of the display.

      On a Mac, the best compromise I have found is to move the task bar to the right edge to free up that space (and what's with the "only put a resize gadget in one corner?), but the menu bar is still a pain.

    9. Re:Menus at the top! by Anonymous Coward · · Score: 2, Informative

      How long ago was this? As it is now, you're just spreading FUD, you can't click above the KDE top-menu as there is nothing above it, and it's been like this for a long time.

    10. Re:Menus at the top! by chroma · · Score: 1
      Actually, while KDE has long had the option to put the menu bar at the top of the screen, the last time I used KDE, if you move your mouse to the very top of the screen, you would still click above the menu, not activating it.

      Must have been a long while ago, as the KDE menu bar works exactly how you want it, with an infinitely tall target.

      --

      Your design to a real part online: Big Blue Saw
    11. Re:Menus at the top! by goarilla · · Score: 1

      please explain what the hell are you complaining about? please stop using the word infinite

    12. Re:Menus at the top! by chill · · Score: 3, Informative

      I believe this was fixed in 3.2. In any case, with the most recent version of KDE (3.5.6) I can't click above the menu bar.

      --
      Learning HOW to think is more important than learning WHAT to think.
    13. Re:Menus at the top! by kinabrew · · Score: 5, Insightful

      You're not giving up real estate by having the menu bar at the top. If each program has its own menu bar inside its window, that uses several times as much real estate.

      For example, I have six windows open right now in OS X. Were I using an environment where each window had its own menu bar, that would use six times as much screen real estate.

      If menus are hidden and only activated by right-click, many people wouldn't realize the options that are available to them. That is admittedly easy for some people, but it's better not to require most people to memorize a whole bunch of stuff. Using a computer shouldn't be frustrating even for someone just sitting down for the first time. A luddite isn't going to know that they need to right-click to see menus.

      As for the dock(not actually called a taskbar), that can be hidden. I suppose it would be beneficial to let people decide whether to display menus in-window or outside, and do I agree that all commands should be accessible through contextual menus, but by default, I believe strongly that controls should be placed to waste as little screen real estate as possible, and to be very easy to hit, regardless of movement.

    14. Re:Menus at the top! by kinabrew · · Score: 1

      I'm glad to hear that. I'd been bitching about it for a long time and had actually quit using KDE because of that.

      If I was wrong, please accept my sincere apology.

    15. Re:Menus at the top! by dltaylor · · Score: 2, Interesting

      The task bars, docks, whatever you call them, cost me real estate; the "menu at the top" costs me mouse movement, unless I put every application at the very top of the screen. Since I multitask, I would have a lot of hidden windows, which then costs me work to sort through (without a task bar). I end up trading real estate (taskbar) for mouse, or keyboard, actions (sorting through active windows).

      With Sawfish, I have neither of those downsides. The only thing that now bothers me with Sawfish is that is seems to have lost the ability to focus a window, without bringing it "front", which is common with other recent window managers/desktops. Again, since I multitask, it takes me longer to "copy and paste" from, for example, a log window in a corner of the screen to an email.

    16. Re:Menus at the top! by warrigal · · Score: 1

      The widow controls are still at the top-right. Very Win/Linux. Not all that Mac-like. You have to wonder if the designers have read the Human Interface Guidelines. Not everybody follows them, I know (especially Apple), but a passing familiarity would give better results.

    17. Re:Menus at the top! by grahamd0 · · Score: 1

      I'm going to have to go ahead and disagree with you on that one.

      I find that it's much more helpful to have the menu attached to the window to which it applies, establishing a context for those commands. I can't tell you how many times a day MacOS fails to properly or completely give an app focus when I click on it's window, or how often the OS fails to unambiguously demonstrate which app currently has the focus (granted, the former is clearly a bug in the OS or the app, not a flaw in the UI design). The latter being a big problem because though the correct app's name may show up in the corner, the gist of your point is (I believe) that the clarity and consistency of putting the menu bar on top allow you to use the OS with less conscious decision-making. This is negated if I have to double check whether the menu says "Photoshop" or "Firefox" or "Eclipse".

      A bigger concern for me personally is that on a high-res monitor [If don't have a need for a high-res monitor, why are you using a Mac?] it takes noticeably longer to reach the menu bar on a Mac than it should.

      DISCLAIMER: I'm not a Windows fanboy. I was introduced to computers via the Mac as a youngling, and I use one every day at work. I've owned several Windows PCs (I'm typing this one of them now), and I'm speaking as someone who has a great deal of practical experience using both platforms for fun and profit.

      PS [AND FLAMEBAIT]: Of all the OS UIs I've used, KDE is best.

      -Graham

    18. Re:Menus at the top! by Space+cowboy · · Score: 5, Informative

      I'm not sure I understand your comment. I think you don't get the usual Mac workflow.

      (a) The dock (which sort of doubles as a taskbar) is hideable. No screen real-estate need be sacrificed.

      (b) The mouse-movement that the menu costs you is a lot easier than the mouse movement for menus attached to windows - that's the point of putting the menus at the top of the screen.

      (c) If I'm using multiple applications on the same screen (and I'm not using a virtual-desktop, which to be fair I usually do), then I use Exposé to switch between them. It's bound to my 5th mouse button so it works anywhere and it's very quick.

      (d) There are other ways the Mac tries to speed workflow, but to be fair, other systems have extras too, so I'll stick to what you identified...

      You don't have to like the Mac way of doing things, but you ought to try it with a fair mind before criticising it...

      Simon.

      --
      Physicists get Hadrons!
    19. Re:Menus at the top! by Anonymous Coward · · Score: 0

      Why not just make the screen one big button? Because that would reduce functionality, unlike putting the menus the the top. I would've though that was obvious, are you sure you've used a computer before?
    20. Re:Menus at the top! by p0tat03 · · Score: 1

      I wish OS X would put the menu bar on both screens. It's really not too hard to do.

      That said, I think Windows is a worse violator, or maybe it's just the drivers... The task bar only goes on the secondary display. When I hook my laptop up to my big monitor, the task bar simply refuses to budge! But at home, with the big LCD, I only use my laptop screen as a tools palette for apps like Photoshop and 3dsmax. This is very annoying. I can't even get games to run on the big monitor, since the display panel would not allow me to switch the external monitor to "primary". Argh.

    21. Re:Menus at the top! by Anonymous Coward · · Score: 0

      Sure you can, I have the same setup.
      You can have your desktop on the external monitor and your laptop as a "secondary" display, simply use the notebook's hardware keys to have only the external display (ie the notebook's display is off), at that point go to settings and select the native monitor and click on "extend my display to this monitor" (or something like that, sorry i'm on my Mac at home right now).

      Even with that setup you can move your start menu to be on the native monitor while the external monitor is still primary.

    22. Re:Menus at the top! by kevorkian · · Score: 2, Informative

      in regards to the task bar that wont budge .. there is a setting called "lock the taskbar" when unlocked you can move it where ever you want .. even the 'other' display

      Also as for the second monitor that wont play the games. You can simply disable the internal monitor of the laptop. Either via the hardware 'Fn' on a old IBM thinkpad or in the settings screen.

    23. Re:Menus at the top! by QuantumG · · Score: 0, Troll

      You outline all the good things about the Mac UI but don't outline the bad things. In fact, I bet you can't even name any bad things and just think it is perfect. Which is total bullocks. You're just repressing them.

      One thing I hate is the mentality of "it just works". Which is great, if it does, but when it doesn't, well, you're shit out of luck because we didn't even bother putting any UI components in to help you diagnose what the problem is, because there's not supposed to be any problems!

      --
      How we know is more important than what we know.
    24. Re:Menus at the top! by Space+cowboy · · Score: 2, Insightful

      So, as I *stated* in the post, I was responding to the points raised by the poster. If you want to raise your own, go right ahead - pulling "all the bad things" out as a catch-all isn't a good argument though.

      As for "... didn't even bother putting any UI components in to help you diagnose what the problem is", again I don't really see your point. It's UNIX. It has logs. Use them. If you want pretty UI-based logs, then open up the console application, and you can see all the logs in a nice pretty format. Personally I prefer grep.

      Not to mention all the pretty UI-based help available using the 'help' key; or the drop-down 'help' menu available on all apps...

      Simon.

      --
      Physicists get Hadrons!
    25. Re:Menus at the top! by aichpvee · · Score: 1

      Putting the menu on the top neither increases or decreases functionality. It does however reduce usability and disrupts work flow.

      --
      The Farewell Tour II
    26. Re:Menus at the top! by Anonymous Coward · · Score: 0

      Finally, an open-source desktop environment whose developers understand that menus at the top are infinite targets and always in the same place and therefore are easier to hit.

      Er, KDE has had that option since version 2, seven years ago, although it wasn't the default. And in more recent versions, when you first log in, it asks you whether you want a Windows, UNIX, or Mac-like environment, and if you answer Mac, it puts the application menus at the top. In fact, come to think of it, doesn't GNOME have a menu at the top as well?

    27. Re:Menus at the top! by tepples · · Score: 1

      Putting the menu on the top neither increases or decreases functionality. It does however reduce usability Citation needed for this assertion on a single-monitor system.
    28. Re:Menus at the top! by rainman_bc · · Score: 1

      If you care, there's a cool mod for XP that'll stretch the bar across both displays called ultramon

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    29. Re:Menus at the top! by Ohreally_factor · · Score: 1

      Widow controls? What about the orphan controls? =)

      Take a gander at this screenshot of NeXtstep to see where it's coming from. Very early 90s. Yes, the window controls are not Mac-like, but on the whole it's not all that different in feel from System 7 or OS 8. As I said, a very 90s feel to it.

      --
      It's not offtopic, dumbass. It's orthogonal.
    30. Re:Menus at the top! by Asphalt · · Score: 1
      Is there a reason that Apple won't release OSX for generic X86 Platforms?

      I know it's just a really nice Window Manager on top of BSD (for the most part), but I think they would really have a market among the people who want to get away from Windows, but just aren't ready to make the leap to Linux.

      Is it really just a device driver issue where they don't want to support 1,000,000 combinations of hardware?

    31. Re:Menus at the top! by Ohreally_factor · · Score: 1

      I'm a fucking idiot. That screenshot is to a Windows skin. Here's a screenshot from WP, and even better, here's GUIdebook so you can compare GUIs to your heart's content.

      --
      It's not offtopic, dumbass. It's orthogonal.
    32. Re:Menus at the top! by Daengbo · · Score: 1

      An Application menu, but not the application's menu. hmmm.

    33. Re:Menus at the top! by ZachMG · · Score: 1, Funny

      do you people really have that much trouble aiming the mouse as to worry about "hitting" a menu? I might have impressive skillzorz but i never just run to the top of the screen and i have no problem hitting what im aiming for.

      --
      There is hopeful symbolism in the fact that flags do not wave in a vacuum. --Arthur C. Clarke
    34. Re:Menus at the top! by Millenniumman · · Score: 2, Funny

      Well, there is that thing about them wanting to make money.

      --
      Stupidity is like nuclear power, it can be used for good or evil. And you don't want to get any on you.
    35. Re:Menus at the top! by Anonymous Coward · · Score: 2, Interesting

      Here's one: Me.

      I can't tell you how much I hate tooling around to the top of the screen when I have several applications open on a large monitor. It's bad enough that I have my mousepad sideways (long-axis vertical), because that's the direction that requires the most unnecessary movement:

      (1) Click on a button in the application.
      (2) Motor the fuck all the way up to the top of the screen, click a menu option.
      (3) Voyage the mouse all the way back down to the bottom of the screen where the application window is. Click something.
      (4) Trundle the motherfucking mouse all the way back up to the top of the screen. This is getting old.

      It also makes multimonitor so much of a pain that it's not worth it for anything but graphics programs (where you can have a fullscreen, non-interactive preview on the 2nd monitor - and you never mouse over there).

      The "we don't need stinking maximize" argument for the "zoom" button is exposed as the bullshit it is with this argument for the menus at the top of the screen, isn't it? (the Mactard argument for zoom is that monitors are huge, nobody wants maximized windows - the Mactard argument for menus being at the top of the screen is that monitors are tiny and menus are a waste of valuable space).

      I really do like almost every aspect of OSX (typing this on my Mac right now) - except for the menu placement and that the dock doesn't behave more like the Windows taskbar (which is not so good for starting programs - but is infinitely superior for managing programs and windows that are open).

    36. Re:Menus at the top! by und0 · · Score: 1

      With Sawfish, I have neither of those downsides. The only thing that now bothers me with Sawfish is that is seems to have lost the ability to focus a window, without bringing it "front", which is common with other recent window managers/desktops. Again, since I multitask, it takes me longer to "copy and paste" from, for example, a log window in a corner of the screen to an email.
      I think the option is still present, buried somewhere. If i'm wrong, maybe you can file a suggestion or provide a patch if you can, now that Sawfish is active again: http://sawfish.wikia.com/
    37. Re:Menus at the top! by dltaylor · · Score: 2, Interesting

      > (a) The dock (which sort of doubles as a taskbar) is hideable. No screen real-estate need be sacrificed.

      Except that I now have to move the pointer farther to get to it. Like I said, I trade real estate for motion.

      > b) The mouse-movement that the menu costs you is a lot easier than the mouse movement for menus attached to windows - that's the point of putting the menus at the top of the screen.

      That's just nonsense, unless ALL windows are opened immediately below the menu bar, and, even then, the per-application menu might be more compact horizontally than the top-of-screen menu. Any window that opens mid-display still has to have its menu accessed at the top of the screen. On a 640x480 Amiga, that was too far, and it's still too far on an 1024x768, or larger, Mac or Linux box.

      > (c) If I'm using multiple applications on the same screen (and I'm not using a virtual-desktop, which to be fair I usually do), then I use Exposé to switch between them. It's bound to my 5th mouse button so it works anywhere and it's very quick.

      Haven't tried that (have to use the middle of a three-button, I suppose), but if Expose pops up close the current pointer, it would help.

      > (d) There are other ways the Mac tries to speed workflow, but to be fair, other systems have extras too, so I'll stick to what you identified...

      Could be, but I unless (c) helps, I can't find them.

      > You don't have to like the Mac way of doing things, but you ought to try it with a fair mind before criticising it...

      We have three in current use (all PPC: two iBooks, since Linux laptop support didn't used to be as good as it is now, and a Mini below the home theater monitor, for casual web browsing and streaming media), so I have tried them. I cannot get a Mac to multitask even as well as the Amiga used to, since the Amiga had fast paging through applications screens, and I cannot find that on the Mac, and it had a "lower window" feature on the windows that made togging through stacks faster since there was not even the need to move from the mouse to the keyboard. I'm not saying you can't do it, but that it takes more mouse or keyboard work to accomplish it. Could be worse, though.

    38. Re:Menus at the top! by LKM · · Score: 1

      One thing I hate is the mentality of "it just works". Which is great, if it does, but when it doesn't, well, you're shit out of luck because we didn't even bother putting any UI components in to help you diagnose what the problem is, because there's not supposed to be any problems!

      I think it's kind of funny that many Windows users seem to think that you can't "debug" Macs. I attribute this misconception to a lack of experience with Macs. Obviously, you can diagnose problems with Mac OS X, and in my experience, it's a lot easier to do than with Windows. I don't know a lot of Mac users who routinely reinstall Mac OS X, but I know a lot of Windows users who routinely reinstall Windows - despite the fact that reinstalling Mac OS X is really simple and can even be done while keeping all of your data (select the "Archive and Install" option while installing).

      So no, you're wrong. Diagnosing a problem in Mac OS X is really simple using the logs all applications and system components write.

    39. Re:Menus at the top! by LKM · · Score: 1

      The task bars, docks, whatever you call them, cost me real estate;

      Which is why a lot of people just hide the Dock.

      the "menu at the top" costs me mouse movement

      Well, it may indeed cost you "mouse movement," but on the other hand, you gain time. Fitt's law, look it up.

      More mouse movement does not equal more time used.

    40. Re:Menus at the top! by theKinkyRabbit · · Score: 1

      (1) Click on a button in the application.
      (2) Motor the fuck all the way up to the top of the screen, click a menu option.
      (3) Voyage the mouse all the way back down to the bottom of the screen where the application window is. Click something.
      (4) Trundle the motherfucking mouse all the way back up to the top of the screen. This is getting old.

      Have you tried using Command-Tab for switching between apps ?

      --
      Life isn't a bitch. Life is a virgin. A bitch is easy.
    41. Re:Menus at the top! by Onan · · Score: 2, Interesting

      The mouse-movement that the menu costs you is a lot easier than the mouse movement for menus attached to windows - that's the point of putting the menus at the top of the screen.
      That's just nonsense, unless ALL windows are opened immediately below the menu bar, and, even then, the per-application menu might be more compact horizontally than the top-of-screen menu. Any window that opens mid-display still has to have its menu accessed at the top of the screen. On a 640x480 Amiga, that was too far, and it's still too far on an 1024x768, or larger, Mac or Linux box.

      He didn't say it was closer, he said it was easier. And the two are generally not the same thing.

      He's referring to Fitt's Law, and one of its interesting corollaries. The relevant bit of the law is that the time it takes to point at a target is related to the size of that target. The interesting corollary is that targets at the edge of a display are infinitely large (given that you can overshoot them endlessly without missing them), and therefore vastly faster and easier to point at than any targets not at the edge of the display.

      Moving to a mid-screen menubar requires far more precision, and is therefore much slower, even though it's a shorter distance to move.

      ...the Amiga had fast paging through applications screens, and I cannot find that on the Mac...
      You mean just switching easily between the various windows of one application? How is that not covered by expose or command-` ?
    42. Re:Menus at the top! by BobPaul · · Score: 1, Insightful

      You're an idiot. While I've always owned PCs, I did a lot of work on OS7.5-OS9 way back before OSX came out. I never had any trouble diagnosing hardware. No, I could pop into the local computer shop and buy replacement hardware, but fortunately Apple was always willing to sell us extras of what wasn't standard. Now a days, the only thing non-standard in a Mac is the mobo, which requires a special TCM or the OS won't run.

      But I digress. The fact that you didn't know how to diagnose software problems isn't my fault. If you didn't know what Mac bomb code 92 was, well, you must have thrown out the manual. It was different, for sure, and I didn't prefer it for a number of reasons, but that's it. Different.

      OSX is unix, and if you can't handle that then it's obvious why you had problems with OS =9. Windows power users are used to windows. You've spent years transforming from noob to where you are now. Mac power users did the same thing. To be certain, noobs on any system can't troubleshoot shit, just ask your parents/grandparents/whoever.

      I'm sorry your such a Mac noob.

    43. Re:Menus at the top! by QuantumG · · Score: 2, Insightful

      Thanks you my rude friend.

      The point I was trying to make was simply that the assumption that something will "just work" often is used as justification for poor control over such actions being placed in the UI. For example, if it is assumed that the wireless subsystem will automatically pick the best access point, why bother putting an access point preference selector in the wireless device configuration UI? The idea that someone should have to go dig through logs to find out why the lesser favourite access point was selected is all well and good, but it doesn't help solve the immediate problem that the automatic selection of access points isn't working. Whereas, if the assumption is that things that "just work" might not "just work" now and then, the developer is more likely to provide the user with the tools they need to get the job done themselves.

      Now, kindly, fuck off.

      --
      How we know is more important than what we know.
    44. Re:Menus at the top! by HeroreV · · Score: 1

      Too bad non-KDE apps completely ignore it, so that it just ends up wasting space. I wish it would only appear when a program that actually uses it has focus.

    45. Re:Menus at the top! by belg4mit · · Score: 1

      Multimon is better, it gives a start button and clock on the supplementary taskbar too
      (although, unfortunately, you cannot right clock this clock for the date)

      --
      Were that I say, pancakes?
    46. Re:Menus at the top! by steeviant · · Score: 3, Informative

      Here's a tip... tune your mouse acceleration settings so that the mouse goes completely to the left and right (or top and bottom if your monitor is in portrait orientation) in one sweep of the mouse, then you'll find you can reach any point on your screen in just one sweep of the mouse. This works not only for menus, but for taskbars and Docks as well.

      If you're seriously having to use more than one movement of the mouse to get from say, the top-left of your monitor to the bottom-right of your monitor and don't know how to fix it then you should have your geek card revoked.

      Hitting a unified menubar or taskbar is exactly the same process, "slam" the mouse to the bottom of the screen and you're there no "voyaging" involved. There's a lot of well established ergonomic research to suggest that screen edges are good places for commonly used objects because they are effectively infinitely large in a certain direction, and that research has been heeded by ALL major OS vendors in one way or another.

      Interestingly, research suggests that the time to acquire objects like menu bars is purely a function of their size and their distance from where your hands (or pointer on a computer) spend most of their time. Once you are "up to speed" with an interface, those are the only factors that matter in acquiring a target, the training of the user is irrelevant.

      That suggests that both attached and detached menu bars are a good idea, attached menu bars by virtue of being close at hand to the content that you're manipulating, and detached menu bars by virtue of being effectively enormous in size. I'm certain, as would be anyone with common-sense that all users can acquire a menu bar at the top of the screen more quickly than one in the middle of the screen.

      However, as you state above unless the user is quitting the application they probably have to return to the application window, this is still a much larger target than a menu bar, but leaves you much further from the content than the attached menu bar would.

      I don't think there actually is a consensus on which type of menu bar is best, but there is a lot of agreement that no-one should have trouble navigating to a detached menu bar, because it's infinitely large, so either you're exaggerating, stupid, or have such unbelievably awful hand-eye coordination that you can't even hit a side of the screen.

      Speaking as a Linux, OS X and Windows user with a 24" 1920x1200 monitor.

    47. Re:Menus at the top! by Anonymous Coward · · Score: 0

      > It's bound to my 5th mouse button

      First they give you ONE button and argue that ONE button is enough.

      Then I all of sudden hear that some macs have FIVE buttons.

      Wow. Apple's evolving.

    48. Re:Menus at the top! by ickoonite · · Score: 1

      I know it's just a really nice Window Manager on top of BSD (for the most part)...

      Not even close.

      Is it really just a device driver issue where they don't want to support 1,000,000 combinations of hardware?

      In a word: yes. If you ever have the misfortune to have to use a 3rd party driver for, say, a networking device on Mac OS X - whether on a real Mac or because you need it to run Mac OS X on your generic x86 box - you will come to understand quite quickly the difference in quality between Apple's efforts and those of basically everyone else.

      iqu :|

    49. Re:Menus at the top! by Weedlekin · · Score: 1

      Every geek knows they could make piles of money taking Microsoft on in the commodity x86 OS space by being more stable, and having compelling features, just like other successful operating systems such as OS/2 and BeOS.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    50. Re:Menus at the top! by logixoul · · Score: 1

      Actually KDE understood that years ago. The problem I personally have with it, though, is that it's there all the time, regardless if my current app has a menu... and I tend to hide the menus of all simple utility apps like Amarok and KGet. That's why I returned to in-window menubars in my KDE.

    51. Re:Menus at the top! by Chilled+urine. · · Score: 0

      But Macs have a wireless access point selector right on the menu bar, so your argument doesn't even make any sense.

    52. Re:Menus at the top! by Chilled+urine. · · Score: 0

      D00d, ya fuckin' raped me wit da "Offtopic" mod!

    53. Re:Menus at the top! by Curien · · Score: 4, Insightful

      [T]argets at the edge of a display are infinitely large (given that you can overshoot them endlessly without missing them)

      They are NOT "infinitely large". If they were infinitely large, then you wouldn't have to move the mouse *at all* to click on them. Calling them "infinitely large" just confuses people who know what the words "infinite" and "large" mean.

      He's referring to Fitt's Law, and one of its interesting corollaries. The relevant bit of the law is that the time it takes to point at a target is related to the size of that target.

      Fitts' law, according to that Wikipedia article, states that the time it takes to complete a movement is proportional to the binary logarithm of the ratio between the distance to the center of the target and the width of the target in the direction of motion.

      Note that Fitts' law does not say anything about how "easy" the task is -- just how much time it takes.

      Now, the argument you and others seem to be making is that, for the purposes of Fitts' law, an object at the edge of the mousing area can be considered to have infinite width; the amount of time it takes to complete the action is therefore minimized.

      However, you are neglecting the other parameter: if the width of the target is infinite, then the distance to its center is also infinite, and the ratio between the two converges to 1/2. But it's still not even that good: the 1/2 ratio between the "center" and the width doesn't hold in this case. Rather than being infinite, the width of the edge in a given instance is however much farther past the edge of the screen the user chooses to travel. The "center" is therefore effectively wherever the user clicks, and the ratio between the width and the center converges to 1 (it converges more quickly for narrower hotspots, so a menu bar would have a ratio very nearly 1). So Fitts' law gives T = a + (.58)b.

      On my monitor, each application takes up roughly 1/4 of the screen, so while performing a sequence of actions, the menu bar is, on average, only 1/8 of a monitor width away from the location of the next action. The menu bar is 1/40 screen tall, so my average D/W ratio 5. So by Fitts' law, that gives T = a + (2.58)b.

      So the log-factor ratio is 4.4, in favor of edge menus.

      What this neglects is the time it then takes to perfor your NEXT action. On small monitors, the distance from the edge to any other point on the screen is small, so the cost of moving back to the location of interest isn't prohibitively large. With large monitors, however, the edge advantage actually becomes an edge disadvantage, as you have to move farther back.

      For edge menus, the average distance is half the monitor size, so Fitts' law says the time is proportional to lg (1/(2w) + 1). For my screen, with the menu bar at the top of the app, the average distance is only 1/8 of the screen. So it's proportional to lg(1/(8w) + 1).

      The ratio between the two is -1.415 - lg w. (Where the units for w are in terms of the size of the screen). So to click on a large item, edge menus still have the advantage. But for me, most things are button-sized (again, 1/40 the screen size in the vertical direction). In that case, the ratio comes out to about 3.9 in favor of app-menus. The ratio will favor app-menus more as the size of the target becomes smaller and less as the size becomes larger.

      So not only does Fitts' law show that users with my usage pattern (roughly, as monitor size increases, window sizes remain contstant), there is no clear winner between app-menus and edge menus. But app-windows are getting more advantageous as monitor sizes increase, while edge-menus are becoming less advantageous.

      If someone sees a fault in my math or reasoning, please point it out to me.

      --
      It's always a long day... 86400 doesn't fit into a short.
    54. Re:Menus at the top! by Anonymous Coward · · Score: 0
    55. Re:Menus at the top! by Goth+Biker+Babe · · Score: 1

      Is there a reason that Apple won't release OSX for generic X86 Platforms?

      Yes! Scalability. M$ is somewhat bigger than Apple. At the moment Apple write everything OS, drivers, Apps and have a limited subset of hardware to test it on. That means they can exhaustively test. The moment you have generic hardware where Joe Public can stick any old thing in to the machine you have to support drivers for those things. Either Apple has to write them or the hardware vendor has to write them. Many of the issues with Windows come from badly written drivers from third party hardware suppliers. It's just easier to keep the quality by ensuring you're only targeting a limited selection of hardware...

    56. Re:Menus at the top! by leonem · · Score: 1

      The following is not quite an apples-to-apples comparison as you are talking about OS X and I'm talking about OS, er, 7 or 8 I think (well, technically it's an Apple-to-Apple comparison, but anyway):

      When Apple licensed the OS last time, it nearly took the company under. A lot of people (obviously) thought it was a good idea and it did benefit the end user. We got cheaper top-end Macs from third parties. The kicker was that Apple made most of their money from the high-end hardware, and so this ostensibly beneficial result nearly took them to the wall. Ironically, putting the user first could have destroyed exactly what the user wanted.

      An interesting example of the way capitalism functions. I think most people would agree it was positive, although if Apple had collapsed, MS might have been split up, which could have been better in the long term.

    57. Re:Menus at the top! by Anonymous Coward · · Score: 0

      menus at the top are infinite targets Except that that's not true anymore if you're (like me) using an absolute-positioning graphics tablet, and more and more people are. Then, top menus are just one more rectangular region, and a far away, narrow one. Auto-hidden panels work even less well - you have to position the stylus at the exact edge (i.e. less than or equal to one pixel) of the tablet, which totally sucks.

    58. Re:Menus at the top! by BobPaul · · Score: 1

      For example, if it is assumed that the wireless subsystem will automatically pick the best access point, why bother putting an access point preference selector in the wireless device configuration UI? It's nice that you found an example that doesn't exist. There is an access point selector...
    59. Re:Menus at the top! by leonem · · Score: 1

      I think he was talking about setting an order-of-preference list automatically, rather than choosing manually. However, I think you can drag the order of access points in the Network control panel to determine this (on work PC right now so can't test), so you may still be right that the GP hasn't looked very hard.

    60. Re:Menus at the top! by Anonymous Coward · · Score: 0

      (c) If I'm using multiple applications on the same screen (and I'm not using a virtual-desktop, which to be fair I usually do), then I use Exposé to switch between them. It's bound to my 5th mouse button so it works anywhere and it's very quick.

      Personally, I find Expose to be too slow. I prefer to just click on the app in the dock I want to use, or use Window-Tab or Window-` to select the app or window I want to get to.

      As a side note, I almost always use hide instead of minimize, unless its something I want to get out of my way to work on later. It's amazing how many Mac users don't know about hide.

    61. Re:Menus at the top! by someone300 · · Score: 3, Interesting

      That's strange. The main aspects I like about my Mac are the menu placement and the way the dock+expose manages applications and windows.

      The Mac argument for zoom is that noone wants maximised windows... which is true when you really think about it. Most Windows or indeed Linux converts (that includes me) I see are always struggling to maximise their windows until it hits them - they never really wanted it maximised in the first place. Why would they want to maximise Word on a 36" monitor?

      I'm not sure why we maximise windows. I think I had two reasons:
      - It was hard to tell which window was what. I have quite a bit of difficulty distinguishing between windows without decent shadows behind them, which neither Windows or Linux at the time provided.
      - I always used to use the top of the screen as a sort of mouse reflection point. I knew that if I threw the mouse up there from any point on the screen, it's stop and I could be more precise and lower it carefully to select a menu button... it was easier because the top of the screen was a sort of infinite height target.

      The small screen argument has been irrelevant for a few years, I think.

      I think the problem you're having is that your mouse settings are crap. Macs are really optimised towards high precision mice optimised so that you can cover the entire screen in a short sweep as well as having good precision when you move slowly. This means quite high acceleration. I can cover over 1000 pixels in about 4cm when I move my mouse sharply, but if I move slowly I can almost move the mouse with 1:1 distance correspondence between mouse distance and screen distance... about 40px/cm.

      Plus, try using cmd+tab (and other shortcuts or expose once in a while, though expose is also optimised for decent mouse settings. You do have a point about dual monitor, but I think even mac fanboys tend to accept that it's a PITA for dual monitor. What applications are you using that require menu interaction that frequently? CS3 suite or something? If so, do yourself a favour and learn the shortcuts. It's damn near impossible to use a program with that much menu interaction without learning shortcuts... Windows, Linux or OS X.

    62. Re:Menus at the top! by G+Morgan · · Score: 1

      What he means is not that the bar is infinite (which is just confusing) but that you can move the mouse a theoretically infinite amount and it still won't go pass that point. It's really just a hard limit where a floating menu can be overshot. Then again I don't think I've ever missed a menu item.

      Personally I've had situations where I've used multiple menus at once (depending on your window focus model it can be done without even bring a window to the front). If you cascade your windows then you can click on a menu without first switching to its window. If you only have one app open then it's slightly better though.

    63. Re:Menus at the top! by Paradise+Pete · · Score: 1
      If someone sees a fault in my math or reasoning, please point it out to me.

      Cursor speed is not constant. You can just throw it towards the menu bar. This works because it's impossible to overshoot the target. With a local menu you have to carefully move to it.

    64. Re:Menus at the top! by Kickasso · · Score: 1

      For example, I have six windows open right now in OS X. Were I using an environment where each window had its own menu bar, that would use six times as much screen real estate.

      Perhaps you should learn the concept of "overlapping windows" then.

    65. Re:Menus at the top! by Curien · · Score: 1

      I already took that into account. That's why my Fitts' law evaluation of edge-menus gave them a D/W ratio of 1. Otherwise it would have been 1/(2w), where w is the width of the menu; in my case where menus are 1/40 of screen size, the ratio would have been 20 on average.

      --
      It's always a long day... 86400 doesn't fit into a short.
    66. Re:Menus at the top! by Weedlekin · · Score: 1

      I think you missed the sarcasm in my post, which should have been evident from the phrase "just like other successful operating systems such as OS/2 and BeOS", because neither of them was at all successful at gaining any notable share of the commodity desktop OS market (although OS/2 had a niche corporate desktop market, and was also used as an embedded OS for ATMs and EPOS systems for several years).

      "When Apple licensed the OS last time, it nearly took the company under."

      While I agree that Apple would be silly to sell OS X for machines other than Macs, I think that their many other problems at the time they did licence MacOS were what was destroying the company, and the legal clones merely served to highlight these existing problems rather than being the cause of new ones. In the mid 1990s Apple had a confusing product line, an OS that was starting to look very old and limited compared with Windows, and a growing history of ambitious software projects that ended up being abandoned before they were completed, often after various third party developers had spent considerable amounts of time and effort designing products around them. This resulted in a contracting market where new Macs were only selling to people who were already committed to Macs, while the rest of the world (including some Apple users) went with Windows, which was now a 32-bit OS with pre-emptive multitasking that, despite stability problems in its consumer versions, actually crashed less than Apple's offering, so even some of the Mac faithful started to balk at paying a lot more money for something that was actually worse in practice than a cheap commodity PC.

      If one's overall market is static or contracting, then it's obvious that any company's gains will be another company's losses, and this is the situation Apple found themselves in when they licensed MacOS to others during a period when their market was shrinking rather than growing. Things would however have been very different if they'd licensed MacOS to others during the early 1980s, when it effectively had no competition, and would therefore have stood an excellent chance of putting Apple where MS are today (even Bill Gates believed that this would happen at that time).

      --
      I'm not going to change your sheets again, Mr. Hastings.
    67. Re:Menus at the top! by aichpvee · · Score: 1

      Is that supposed to be some kind of troll or something? Or are there really so few people using that crap these days that you have to spam links just to get some attention?

      --
      The Farewell Tour II
    68. Re:Menus at the top! by leonem · · Score: 1

      Oh good grief, yes I did miss that completely. The apples-to-apples joke came to me half way through reading your post and I clearly didn't digest the rest!

      Your other points about Apple's strategy are very good, and I agree that licensing was far from being Apple's sole error. My point (irrelevant as it may have been!) would be better cast as: even now, in a position of strength, it still would not make sense for Apple to license the OS. As you say, last time it revealed weakness, and at the moment there is strength, but cross-subsidising from the iPod or suchlike is exactly the sort of financial pollution in diversified companies that often kills innovation, IMO, regardless of how well they are doing overall.

      My apologies again.

    69. Re:Menus at the top! by ThousandStars · · Score: 1

      If only Apple would learn the same is true of windows and let us specify whether we want windows to open to full size by default, and thus not play the "drag the edge" and "find the scroll bar" games.

    70. Re:Menus at the top! by dfghjk · · Score: 1

      Of course, because the world's most intuitive environment designed from the beginning to use a mouse must use keyboard shortcuts in order to get things done.

    71. Re:Menus at the top! by dfghjk · · Score: 1

      "For example, I have six windows open right now in OS X. Were I using an environment where each window had its own menu bar, that would use six times as much screen real estate."

      No it wouldn't. Perhaps you ought to think about that some more.

      "If menus are hidden and only activated by right-click, many people wouldn't realize the options that are available to them. That is admittedly easy for some people, but it's better not to require most people to memorize a whole bunch of stuff."

      How did this suddenly switch to a discussion of context menus, and are you now going to be the only one to argue against them now that Apple implements them as well?

      "Using a computer shouldn't be frustrating even for someone just sitting down for the first time. A luddite isn't going to know that they need to right-click to see menus."

      Agreed, and disassociating menus with applications like an OS written in the early 80's for a 9" monochrome monitor is about the most obvious, frustrating anacronism there is. I can see how you might confuse mac users and luddites, but every user except the most hardcore mac ones know what the right mouse button is. Apple lost that argument long ago.

      "I suppose it would be beneficial to let people decide whether to display menus in-window or outside, and do I agree that all commands should be accessible through contextual menus, but by default, I believe strongly that controls should be placed to waste as little screen real estate as possible, and to be very easy to hit, regardless of movement."

      Menus inside apps do not waste real estate. In fact, when menu hiding is available, the mac approach wastes real estate because the menu space is always lost. As for being easy to hit, "Fitt's law", which was never a law to begin with, ceased being valid in any way when screen resolutions became too large for mouse movements to comfortably cover the entire surface. The mac menu bar is something OS X is stuck with, it is not a usability improvement.

    72. Re:Menus at the top! by Peganthyrus · · Score: 1

      Since OSX, the Mac is almost as responsive as the Amiga used to be, in my experience.

      apple-tab (plus apple-` once you've brought up the task flipper) mostly does what amiga-m,n did: flips through your running apps. Once 10.5 comes out you'll have multiple desktops, so you could run some apps on their own desktop, for a similar experience to the Amiga's 'screens'.

      And I find that Exposé solves the window-sorting problem. If you use a lot of console windows it might not be for you, but I find it pretty easy to hit (fn-)f9 and locate the window I want. Or you could use a screen corner as the trigger, for a no-keyboard experience: whip the mouse until you hit the lower left corner (or whichever one you choose), then click on the huge target of a window. Or if you're feeling geeky you could probably use Quicksilver to wire a mouse gesture to activating Exposé...

      --
      egypt urnash minimal art.
    73. Re:Menus at the top! by dfghjk · · Score: 1

      "I think you don't get the usual Mac workflow."

      I don't think you know what "workflow" means.

      "(b) The mouse-movement that the menu costs you is a lot easier than the mouse movement for menus attached to windows..."

      No it's not, and anyone who uses a modern mac with a large monitor can see that immediately. It's a shame people repeat the same old tired arguments rather than think for themselves.

      "...that's the point of putting the menus at the top of the screen."

      It was 25 years ago when all apps took up the entire screen and switching the menu and title bars made sense. Now it's just legacy garbage that Apple couldn't get rid of without a great deal of pain a huge blow to their ego.

      "(c) If I'm using multiple applications on the same screen (and I'm not using a virtual-desktop, which to be fair I usually do), then I use Exposé to switch between them. It's bound to my 5th mouse button so it works anywhere and it's very quick."

      "(d) There are other ways the Mac tries to speed workflow, but to be fair, other systems have extras too, so I'll stick to what you identified..."

      Wow, the wonders of a mac "workflow" copied from other systems. Mac was last to get such a mechanism yet it is dissentors that don't understand the mac "workflow".

      "You don't have to like the Mac way of doing things, but you ought to try it with a fair mind before criticising it..."

      And you ought to try other platforms before making such qualitative judgements.

      As a converted mac user, my criticisms are the same as his. The top menu bar is the number one abomination to OS X usability. It wastes space, is awkward and non-intuitive, and it slows the user down. The dock does not serve as an effective task bar and it isn't a suitable launcher until you make it contain too many items. It's default location, like the menu bar, wastes the most precious screen real estate and auto-hiding is a poor solution just like it is on other desktops. It's sad that mac defenders regurgitate the same, tired arguments and blame others for failing to understand the one, true way.

    74. Re:Menus at the top! by dfghjk · · Score: 1

      So he's wrong because reinstalling OS X is easier and is needed less frequently than Windows?

      Thanks for all the detail.

    75. Re:Menus at the top! by dfghjk · · Score: 1

      I didn't realize that macs required such a learning curve. I thought they were the computer for everyone else. I thought they "just worked". Who knew?

      I realized mac users were elitist but I had no idea they were just juvenile nerd-pricks with more money. Thanks for setting the record straight.

    76. Re:Menus at the top! by dfghjk · · Score: 1

      You can't increase cursor speed beyond a setting that is comfortable in overall use and cursor acceleration is useless when returning to an app after travelling cross-country to get to the menu bar. It's only impossible to overshoot the target half the time in the mac system. With a local menu bar you have to carefully move it but the shorter distance enables you to use more controllable cursor speeds.

      The sad thing is that mac users continue to argue this in the presence of overwhelming usability evidence to the contrary. Try a mac on a 30" monitor; it's ridiculous. I know, I have one, and it's a source of constant errors and frustration. It is possible to miss the menu, by the way, and the penalty for that is particuarly severe. You have to travel back to the app in order to get the menu to reappear. What a great usability feature ;-)

    77. Re:Menus at the top! by Anonymous Coward · · Score: 0

      I think you don't get the usual Mac workflow. ... then I use Exposé to switch between them. It's bound to my 5th mouse button so it works anywhere and it's very quick.
      No sir, it is you who "don't get" it. 5th mouse button!? Gadzooks! How can users be expected to understand 5 separate buttons when our HCI studies (from 1978) clearly show that people cannot understand the difference between a left and right mouse click? Macs are all about simplifying the computing experience. Making it accessible to the lowest common denominator. Clearly you've forgotten that in your post.
    78. Re:Menus at the top! by LKM · · Score: 1

      No. Are you intentionally trying to misunderstand me? I'll make this easy.

      He: "[Apple] didn't even bother putting any UI components in to help you diagnose what the problem is"
      Me: "Diagnosing a problem in Mac OS X is really simple using the logs all applications and system components write."

      All clear?

    79. Re:Menus at the top! by namekuseijin · · Score: 1

      "It's bound to my 5th mouse button"

      Steve Jobs will sue you for that blasphemy against Mac tech. I believe he thinks even 1 button mouse is too much!

      --
      I don't feel like it...
    80. Re:Menus at the top! by Weedlekin · · Score: 1

      "even now, in a position of strength, it still would not make sense for Apple to license the OS"

      Agreed, especially as they aren't in a position of strength compared to Microsoft in computer operating systems. What makes OS X special is the synergy with Apple's hardware: take away OS X, and their machines are now nothing more than a pricey of Wintel computers; sell the OS without a Mac, and they lose one of the key things that distinguishes them from every other PC vendor. Either situation would result in Apple losing their currently almost unique ability to sell significant numbers of desktop and laptop computers for a price that includes a decent profit margin, without which there would be no reason for them to carry on making Macs when they can get better margins from consumer electronics.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    81. Re:Menus at the top! by Jorophose · · Score: 0

      I never really understood how having the menubars at the top is logical...

      Not trolling, I'd just like to know "Why?". Maybe I'm just used to the "Windows-way" (Though I'm using Xubuntu now) but I'd think having all your menu bars attached to the windows they belong to would help; constantly reaching for the top of the screen doesn't look very fun...

    82. Re:Menus at the top! by Anonymous Coward · · Score: 0

      X Window System users interested in Fitts' Law would do well to look at windowlab. It uses some interesting tricks to make application launching and task switching with the mouse faster than anything else I've come across.

    83. Re:Menus at the top! by jedidiah · · Score: 1

      36" monitors are nice in theory but in practice seem to be
      even more rare than dual-headed configurations.

      Cost is certainly a factor there...

      Not everyone is made of money. Even those that do will probably
      want to use all of that real estate in some program. It might
      even be msword.

      In Unix, virtual desktops blunt the impact of maximizing an app.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    84. Re:Menus at the top! by BobPaul · · Score: 1

      Read my post again. I'm not a Mac user. I am and always have been a PC user. In fact, for the past couple of years I've been strictly a GNU/Linux user. Supporting Macs was just one of the tasks I had at a previous employer.

      And, yes, power-users are often pricks and becoming one requires you spend more than 10 minutes to learn how the operating system works. Stating "Apple sucks cause they don't give you any room to fix things on your own" is, simply put, ignorant. I'm sorry I offended some people, but Mac problems really are no more difficult to fix than Windows or *nix problems. The best thing you can do is pretend you haven't used Windows before and stop trying to attacking the problem with the assumption that you know how it works because you know how Windows works. They are completely different animals.

    85. Re:Menus at the top! by Anonymous Coward · · Score: 0
      The sad thing is that mac users continue to argue this in the presence of overwhelming usability evidence to the contrary.

      What contrary evidence? Don't worry about the "overwhelming" part, I'll settle for scant. Good luck finding a single actual study that supports your contention. I also have a 30" monitor, have the mouse set to a reasonable speed, and yet can reach the menu bar with a flick of the mouse. If you're dragging the cursor up there, then sure, it will take some time. But don't do that. Make a short fast movement towards it.

    86. Re:Menus at the top! by theKinkyRabbit · · Score: 1

      No, you must not use keyboard shortcuts, you can. And in situations where you need to quickly access the menus of two different apps, which is what I understood the AC wanted, you should. It's always better than whining, anyway.

      --
      Life isn't a bitch. Life is a virgin. A bitch is easy.
    87. Re:Menus at the top! by Ohreally_factor · · Score: 1

      I think he was talking about setting an order-of-preference list automatically, rather than choosing manually. However, I think you can drag the order of access points in the Network control panel to determine this (on work PC right now so can't test), so you may still be right that the GP hasn't looked very hard. What you're thinking of is dragging the type of connection (wifi, ethernet, bluetooth, modem) in network system prefs, not which wireless network with which to connect. You can set which network it will attempt to connect with first, however. Then it will automatically look for your most recent networks. The options you can set for that if no recent networks are found are to join without a prompt, to get a prompt before joining, or to keep looking for recent networks. There are a number of other options you can set in network prefs as well.

      However, perhaps you are referring to this (from a tip at Macworld:

      Get back preferred networks
      When you open the Network preference pane, select AirPort from the Show pop-up menu, and then click on the Join pop-up menu, you should see two options: Automatic and Preferred Networks. The latter option, new in Tiger, lets you add, delete, or edit the names and passwords of networks you use often. If you don't see a Preferred Networks option, something went wrong when you upgraded to Tiger. The other thing is that, if you're 1) old school, and 2) knowledgeable, you can edit pretty much any preferences in the terminal (or in any text editor, really, but what's the point?). Most prefs are stored in XML format in a .plist file. There's also a property list editor that gets installed with Xcode. I don't have Xcode installed on this laptop, so I don't have details on that at the moment. Anyway, there's an excellent tutorial on pref files at MacFixIt.

      All that being said, Quantum is nitpicking to make a point. His point is that closed proprietary systems are bad. The truth of the matter is that OS X is not as closed as he'd like to believe, it's just that some of the more grungy and potentially dangerous stuff is hidden from the non-power user. Anyone that wants to more deeply hack their OS X install can figure it out or do 5 or 10 minutes of research and learn how. What this is really about is Quantum's prejudice against proprietary software and his need to make up shortcomings to support his FSF supplied talking points. He has little, if any, knowledge of Mac OS X and is just trolling. Trolling for freeeeeeeeeedom. Trolling for Staaaaaaalman. For people like him, facts are irrelevant and religious ideology is everything.

      --
      It's not offtopic, dumbass. It's orthogonal.
    88. Re:Menus at the top! by Ohreally_factor · · Score: 1

      I'm surprised you didn't bring up Zeno's Paradox in your little discussion about finding the center of an infinitely tall menu bar. If finding the center was even relevant, then it would take an infinite amount of time to find it (knowing where one edge is). There, you win your non-applicable argument.

      Here's the truth: You've not spent more than five or ten minutes at a time on OS X, if that. You didn't know what expose is (and I hope you've looked it up now): "Haven't tried that (have to use the middle of a three-button, I suppose), but if Expose pops up close the current pointer, it would help," is what you wrote.

      I think you just like to argue. You're comfortable with your current way of doing things, you've adapted to whatever system you're using, and that's fine. If some other system is developed with features compelling enough to get you to switch, you'll adapt to that, too, I imagine.

      Fitt's Law has been supported (many times over) in usability studies. Such studies determine what is easiest for the greatest number of people, not for everyone. You might be on the toe of the curve because of how you've adapted to windowed menu bars. If you had to relearn, or were learning for the first time, you might not be on the toe.

      As for the size of the monitor, this is easily overcome with hot keys to bring your cursor back to the focused window. Check the keyboard/mouse prefs in OS X system prefs next time you have the opportunity.

      Seriously, I'm not claiming that OS X is better for everyone, nor even that Fitt's Law trumps your learned behavior. You've got a system that works for you and you're happy, and I wouldn't of trying to convert you to another system. If you're happy and productive that's all that matters, and screw the dicks that want you to change. So, ultimately (and beyond my own predilection for arguing for the sake of argument), you don't need to argue what works for you and why. It is enough to say that you're happy with it.

      --
      It's not offtopic, dumbass. It's orthogonal.
    89. Re:Menus at the top! by Ohreally_factor · · Score: 1

      I don't like to brag about my inventions, but I hold a patent for an infinitely tall urinal, for those that do have a problem aiming.

      --
      It's not offtopic, dumbass. It's orthogonal.
    90. Re:Menus at the top! by 3choTh1s · · Score: 1

      I see the argument of high acceleration being put all over this discussion. I'll have to point out a few things. Whenever you increase the acceleration you reduce the precision of the entire mouse system period. Okay you can get to the menu in one sweep of the mouse on a very high resolution monitor. But then what? You select what you want from the menu and then you'll have to do something that probably isn't close to the edge of the monitor(ie, get back to where you were). This is especially bad if you work in non-maximized windows which most OS X apps I've seen are like. If you try to get back to where you were(or to a dialog box that opened up) quickly you'll just bounce off the other side of the screen. High acceleration has downfalls just as much as edge menus.

    91. Re:Menus at the top! by radish · · Score: 1

      I can only blindly throw the cursor to a corner. To hit an actual menu item I have two dimensions to worry about, and whilst one may be constrained (by the top of the screen) the other certainly isn't. And again, as a previous poster correctly pointed out, having made my selection I now have to get back to where I was and (probably) hit a button or something. Only now I have to do it over a much bigger distance, hence it's slower. I've used large- and small-screen Macs, and it matters much less (i.e. not at all) on something like a laptop. With a 30" display (or even worse, multiple screens) it drives me crazy.

      The way I like to use a computer is to have multiple apps open, side by side and self contained. The Mac-style menu bar stops me working the way I want to, and no number of HCI experts telling me I'm wrong will change that :)

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    92. Re:Menus at the top! by Anonymous Coward · · Score: 0

      To be clear: KDE puts the application's menu at the top. For instance, if you were running Firefox, Firefox's menu would be at the very top of the screen.

    93. Re:Menus at the top! by Anonymous Coward · · Score: 0

      Only now I have to do it over a much bigger distance, hence it's slower.

      Only if the rate of travel is constant in both situations. It isn't. That's the point.

    94. Re:Menus at the top! by Paradise+Pete · · Score: 1
      To hit an actual menu item I have two dimensions to worry about, and whilst one may be constrained (by the top of the screen) the other certainly isn't.

      That's true. But you still have the top of the screen to act like a railing, allowing you to click anywhere and then just slide left or right to the correct menu, and without requiring a precise movement. And because it's a single menu bar not constrained to its window the menu names themselves can be larger. Bigger targets are easier to hit.

      Those are the ideas behind the 'universal' menu bar, and were borne out in studies. Another interesting aspect of the studies was that many people thought that in-window menus were faster, despite the actual measurement showing the opposite.

    95. Re:Menus at the top! by Anonymous Coward · · Score: 2, Interesting
      You obviously haven't touched a Mac, or at least haven't done any experimenting with mouse control.

      Acceleration on OS X is nothing like Windows. It actually works.

      As in, I can move the mouse gently within just the range that my fingers reach and only move about a total of an onscreen inch. That's great for precision work.
      If I move the mouse the same distance, but quickly, I can reach any side of the screen or corner.

      Clearer now?

      Whenever you increase the acceleration you reduce the precision of the entire mouse system period.

      INCORRECT.
    96. Re:Menus at the top! by Anonymous Coward · · Score: 0

      I'm not going to bother correcting the math (Mostly because I don't want to bother figuring out the math.), however, you did make a couple mistakes early on.

      Firstly, "if the width of the target is infinite, then the distance to its center is also infinite, and the ratio between the two converges to 1/2."--The problem with that reasoning is that it's a perceived finite, and a practical infinite, as the target has a fixed size on the screen. In turn, the width is infinite and the center is not (Because the reason the center is important is because we're looking at the amount of time it takes for the person to mentally get to a satisfactory location).

      Secondly, you're using an equation built for single-dimensional applications and applying it to multi-dimensional ones.

    97. Re:Menus at the top! by Anonymous Coward · · Score: 0

      I use maximize all the time.

      But I use multiple monitors.

      VMware? Maximize!

      NNTP reader? Maximize!

      E-mail reader? Maximize!

      Visual Studio? Maximize!

      I maximize all those things and more because you just can't fit everything you want on the screen no matter how high resolution it is.

    98. Re:Menus at the top! by leonem · · Score: 1

      Yup, I'm on my Mac now and I meant the second one. Didn't realise it was new as I upgraded OS at the same time I got wireless. The property list editor is okay - I've never found an OSX XML editor I felt improved my workflow beyond a good text editor plus grep. There's a few Java based ones but I didn't like them.

      I thought there might be some trolling going on, but I tend to give people the benefit of the doubt, plus I was concerned that someone else might read it and believe him!

    99. Re:Menus at the top! by Curien · · Score: 1

      Umm... I think you have me confused with someone else. I entered the discussion late, and I haven't commented on OS X at all.

      Zeno's "paradox" is not applicable. First because we have tools to deal with limits of infinite ratios, and second because there really isn't anything infinite in the case of edge-menus. Calling it so is a mathematical misnomer.

      I didn't disagree with Fitts' law at all. Quite the contrary, I took it as given and /used/ it to draw my conclusions. My evaluation even supported your position that edge-menus are currently and have in the past been a usability boon.

      It doesn't appear that you read my post very carefully. Perhaps you should peruse it again.

      --
      It's always a long day... 86400 doesn't fit into a short.
    100. Re:Menus at the top! by Curien · · Score: 1

      My answer to mojoNYC above mostly addresses your objections, but you're wrong about one thing.

      it's a perceived finite, and a practical infinite, as the target has a fixed size on the screen

      It doesn't matter how large the size is on the screen. All that matters is the "size" of the hotspot, where "size" means the difference between the minimum and maximum movements which allow the pointer to touch it.

      Fitts' law is evaluates the *mechanics* of motion. That's why all the people talking about how it shows that edge-menus are "easier" are all wrong. Fitts' law says nothing about ease-of-use. It only evaluates the time it takes to flick your wrist.

      I didn't bother with a two-dimensional analysis because I didn't think it was useful. The horizontal axis for edge-menus and app-menus are nearly identical.

      --
      It's always a long day... 86400 doesn't fit into a short.
    101. Re:Menus at the top! by Curien · · Score: 1

      From the site: "[Windowlab] has a click-to-focus but not raise-on-focus policy..."

      Holy cow, I was wishing for that just yesterday! Thanks for the link.

      --
      It's always a long day... 86400 doesn't fit into a short.
    102. Re:Menus at the top! by Anonymous Coward · · Score: 0

      They are NOT "infinitely large". If they were infinitely large, then you wouldn't have to move the mouse *at all* to click on them. Calling them "infinitely large" just confuses people who know what the words "infinite" and "large" mean.

      You seem to be having trouble yourself, so I'll help you out.

      The set of integers greater than 100 is infinite, and covers an infinite range. If I'm at the number 5, I still have to add 95 to get to the closest number in this infinite set.

      Just because it doesn't include every possible value, doesn't make it any less infinite. There are the same number of rationals as integers.

    103. Re:Menus at the top! by Anonymous Coward · · Score: 0
      First of all, nobody is using less than a 17" monitor on the desktop, or less than 13-15" on a laptop. It has nothing to do with money. We're not on 9-inch screens anymore.

      In Unix, virtual desktops blunt the impact of maximizing an app

      Huh. That's funny, it sounds like you don't actually switch between apps, but leave every app maximized and switch desktops. (1 program per desktop) If that is the case, you're making far more work for yourself than you need to, and using up resources that could be better spent elsewhere.

      What's the difference between your method and using Alt-Tab? Seems like no difference, except you're having to run another app to manage the virtual desktops.

      Again, anyone who maximizes every app they run is a fucking nimrod and shouldn't be allowed near a computer.
    104. Re:Menus at the top! by yoasif · · Score: 1
    105. Re:Menus at the top! by radish · · Score: 1

      Those are the ideas behind the 'universal' menu bar, and were borne out in studies. Another interesting aspect of the studies was that many people thought that in-window menus were faster, despite the actual measurement showing the opposite.
      A good point, one must never underestimate the power of self denial - "I swear I didn't change a thing in that code, it just suddenly stopped working!" ;)

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    106. Re:Menus at the top! by kinabrew · · Score: 1

      On Macs, if you click directly in either top right corner, you will hit the actual menu that is closest to that corner. You can throw the cursor blindly to hit those two menus. I just thought I'd point that out.

    107. Re:Menus at the top! by aichpvee · · Score: 1

      I never use alt-tab. Focus follows mouse, auto-raise, and window functions do the job a whole lot better. Virtual desktops are useful for organizing the apps you're using, but that has nothing to do with maximizing, which is really kind of a nuisance.

      Of course none of this is practical on windows or mac where the window managers both suck.

      --
      The Farewell Tour II
    108. Re:Menus at the top! by Anonymous Coward · · Score: 0
      Oh please. Either say why you think your setup is better, or stfu.

      My opinion is that the things you can do on OS X for window management are a whole lot better than anything else out there.

      OS X can have virtual desktops (Virtue), focus-follows-mouse (ctvd), and window functions (tons of different apps) that offer a hell of a lot more options and don't look like ass.

      So yeah, when are we going to see a font that actually doesn't burn the eyes in a *nix setup?

      I want to see Helvetica, Futura, Optima, or Lucidia Grande.

      Of course none of this is practical on windows or mac where the window managers both suck.

      Perhaps for the workflow that you're stuck in, but I'm damn fast with mine. Ever consider trying something new? Not just poking at it for a few minutes, actually learning how to use something new to its fullest?

      Methinks there are a ton of *nix geeks that have bought Macs since OS X came out that would disagree with you.
    109. Re:Menus at the top! by Paradise+Pete · · Score: 1
      "I swear I didn't change a thing in that code, it just suddenly stopped working!"

      That's one I happen to agree with ;-)

    110. Re:Menus at the top! by Curien · · Score: 1

      Good point. I retract my position on the inappropriateness of calling it "infinite". That doesn't change any of my analysis though.

      --
      It's always a long day... 86400 doesn't fit into a short.
    111. Re:Menus at the top! by entgod · · Score: 1

      If you really dislike giving up screen real estate you should try Ion3, wmii or some other tiling wm. After some time of getting used to windows not floating around the screen(s) it's really great.

    112. Re:Menus at the top! by 1110110001 · · Score: 1

      [T]argets at the edge of a display are infinitely large (given that you can overshoot them endlessly without missing them)

      They are NOT "infinitely large". If they were infinitely large, then you wouldn't have to move the mouse *at all* to click on them. Calling them "infinitely large" just confuses people who know what the words "infinite" and "large" mean. So you are arguing they are infinite - the screen height or width? IIRC infinite - x = infinite.

      If someone sees a fault in my math [...]
    113. Re:Menus at the top! by Curien · · Score: 1

      http://slashdot.org/comments.pl?sid=257335&cid=200 53441

      That was posted something like five hours before your comment. Thanks for the feedback, though.

      --
      It's always a long day... 86400 doesn't fit into a short.
    114. Re:Menus at the top! by aichpvee · · Score: 1

      So yeah, when are we going to see a font that actually doesn't burn the eyes in a *nix setup?

      Whenever you want? When are we going to see fonts on a mac that aren't all blurry, a window theme that isn't ugly as shit, and not have to install third party addons (usually commercial) just to make it work properly?

      Oh yeah, never.

      There are tons of "*nix geeks" who disagree with me. I fucking hate gnome, sysv-style init scripts, and package managers that handle dependencies. You do realize that not everything is like your cult of mac where you all agree with each other on everything because you all follow the steve blindly, right?

      Please, from now on just keep your mouth shut and your hands off your silly-looking mac keyboard.

      --
      The Farewell Tour II
    115. Re:Menus at the top! by Asphalt · · Score: 1
      Well, there is that thing about them wanting to make money.

      I don't think I ever suggested that the OS be released for free did I?

      Let me re-read my post. No, no I dind't.

      $300 for Vista Ultimate, or $150 for OSX ... I would probably shell out the cash for the latter.

      Wouldn't they make more money selling the OS to the 97% of the people who don't own Macs, instead of just selling it to the 3% who do?

      I'm not an economist, but it just seems like they would make a pretty good amount of money with it.

      Most of their iPod sales are to non-Mac users. Let a few of their gadgets work on a variety of hardware is what took their stock price from $14 to $140.

      You think they would have made more money if they only sold iPods to Mac users?

    116. Re:Menus at the top! by Anonymous Coward · · Score: 0

      make it work properly

      Very subjective. 'Proper' to you is not the same as proper to me. Why should I have to touch a command line, after this many years of computer development? That's just thinking backwards, and smacks of the elitist thinking that Mac users are so often accused of. It's not the 70s any more, learn to take advantage of the technology that's available to you.

      Focus-follow-mouse is annoying as hell (unbelievably so on Windows), and I can't imagine why anyone would use it over keyboard shortcuts to navigate.

      You do realize that not everything is like your cult of mac

      Yes, and because I've used other systems, I can't understand why anyone would subject themselves to that kind of painful experience, when there is a system that will make just about anyone (with half a brain) much more productive available. On the other hand, perhaps people like you don't want to be productive. You want to believe that you're in control of your system, while fighting with dependancy bullshit and engaging in vi vs emacs wars. Let me know when you guys actually have some decent programs available that don't require typing in arcane command line commands to force them to operate at even half the level of quality of experience that a typical OS X app does.

      fonts on a mac that aren't all blurry

      If you'd take the time to educate yourself a bit, you'd learn that OS X shows fonts the way they will look when printed. That behavior makes using the machine much easier on the eyes, and (to me) looks a thousand times better than seeing bitmapped chunky text on the screen. Don't like the font smoothing? Turn it off. Oh right, you wouldn't know about that option, since you're too small- and closed-minded to explore what's available.

      you all agree with each other on everything

      There is quite a bit that Mac users disagree on, including design decisions and choices that Apple makes. I've never met anyone who 'follows the steve blindly', as you so childishly put it.

      sysv-style init scripts, and package managers that handle dependencies

      Again, why should anyone have to even think about crap like that? What a waste of a person's time.

      have to install third party addons

      Really, you're saying you don't install third-party add-ons to your *nix system? I don't believe you, since everything except the main OS for *nix systems is a third-party add-on.

      Clear enough? You need to do a bit more research before shooting your mouth off.
    117. Re:Menus at the top! by Asphalt · · Score: 1
      Agreed, especially as they aren't in a position of strength compared to Microsoft in computer operating systems. What makes OS X special is the synergy with Apple's hardware

      The only issue with that is that the specs of Apple's hardware can now be easily spec'ed in a white box. It is no longer a mysterious liquid-cooled Power PC.

      Want a high-end Mac Pro? Get a couple of Xeon's (the speed of your choice), throw a somewhat dated 7300GT graphics card in there, a couple gigs of ECC Memory, and the Sata Hard Drive of your choosing.

      There, you have a Mac Pro.

      I can get a Mac machine from just about anywhere.

      What I cannot get is the OS to run on said machine because of some proprietary things thrown into the Macs that would not allow it to run.

      But I suppose all of this is what Linux is for ...

    118. Re:Menus at the top! by Asphalt · · Score: 1
      Not even close.

      Okay, okay, I forget the pixie dust and pink elephant droppings. Other than that it's pretty close. For fuck's sake, Apples even says that their machines are based on BSD, and the window manager is not that terribly hard to emulate in *nix.

      Application compatibility is another issue.

      In a word: yes. If you ever have the misfortune to have to use a 3rd party driver for, say, a networking device on Mac OS X - whether on a real Mac or because you need it to run Mac OS X on your generic x86 box - you will come to understand quite quickly the difference in quality between Apple's efforts and those of basically everyone else.

      I don't disagree. Fairly static hardware is infinitely easier to support and perfect that a hodgepodge of differing hardware.

      Still, I have some 12 year old PC's that are still chugging along doing inane things like firewalling, etc. My 7 year old P3 Laptop still runs like the day I bought it ... using Firefox instead of IE.

      Quality, bulletproof, non-Mac computers can and are made. Maybe Macs are 98% satisfactory and PC's are 85% satisfactory, but the overwhelming majority of computers will pretty much hum along forever unless you stick them in the microwave or something.

    119. Re:Menus at the top! by quanticle · · Score: 1

      One thing I hate is the mentality of "it just works". Which is great, if it does, but when it doesn't, well, you're shit out of luck because we didn't even bother putting any UI components in to help you diagnose what the problem is, because there's not supposed to be any problems!

      I recently encountered this on my iPod Nano. The sensitivity of the touch-wheel is non-tuneable. Now, I know that the touch-wheel is made by Synaptics, who also makes the touchpad on my laptop. My laptop touchpad can adjust its sensitivity. Why can't I do the same for my iPod? Its really annoying, because I find the iPod touch wheel to be too sensitive, especially when I'm going running.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    120. Re:Menus at the top! by aichpvee · · Score: 1

      As to "proper" I was referring to the GP's comment about virtual desktops and focus follows mouse. Since you've started off your little rant so poorly by a) whining about things you haven't read and b) being an idiot I'm not going to bother with the rest. Next time start by reading and follow it with thinking. But the reading first since it comes first and seems like it'll be the easier option for you.

      --
      The Farewell Tour II
    121. Re:Menus at the top! by Anonymous Coward · · Score: 0

      I am the GP, dipshit. I was referring to your misuse of the word 'proper'.

      Virtual Desktops and focus-follows-mouse aren't 'proper' for everyone. Regardless, I gave you examples of such that are available for OS X.

      Still no answer to my other points, it seems.

    122. Re:Menus at the top! by Weedlekin · · Score: 1

      "Want a high-end Mac Pro? Get a couple of Xeon's (the speed of your choice), throw a somewhat dated 7300GT graphics card in there, a couple gigs of ECC Memory, and the Sata Hard Drive of your choosing.

      There, you have a Mac Pro."

      What you actually have is a no-name box with the same CPU and graphics card as a Mac Pro, which, as a subsequent comment of your own proves, isn't a Mac Pro:

      "What I cannot get is the OS to run on said machine because of some proprietary things thrown into the Macs that would not allow it to run."

      The distinguishing feature of a (modern) Mac is its ability to run a non-hacked version of MacOS X, and software written for MacOS X, so any system that can''t do this isn't a Mac, irrespective of what its owner may say. It isn't a HP or Dell either, so it won't run one of their special registration-free versions of Windows that ship with their systems, and use proprietary BIOS ID information to ensure that they can't be installed on computers made by someone else.

      "But I suppose all of this is what Linux is for ..."

      Linux is not OS X, or even a reasonable facsimile thereof, because it cannot run software written specifically for OS X. An arbitrary white box with Linux is not therefore a Mac, irrespective of whether its has the same CPU and graphics card some Macs.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    123. Re:Menus at the top! by Asphalt · · Score: 1
      What you actually have is a no-name box with the same CPU and graphics card as a Mac Pro, which, as a subsequent comment of your own proves, isn't a Mac Pro:

      But you have the same hardware. The point is the Apple doesn't create this mystery hardware out of magic purple elephant poop. It's pretty standard stuff. One can have the hardware that Apple uses (or better) at will. And you and I both know that people can get OSX to run on it, but given that they try to proprietarily lock the software to the hardware, I doubt I will ever use it like that.

      The distinguishing feature of a (modern) Mac is its ability to run a non-hacked version of MacOS X, and software written for MacOS X, so any system that can''t do this isn't a Mac, irrespective of what its owner may say. It isn't a HP or Dell either, so it won't run one of their special registration-free versions of Windows that ship with their systems, and use proprietary BIOS ID information to ensure that they can't be installed on computers made by someone else.

      True, but is the hardware of any higher or lower quality? That is debatable. Most of the hardware used by all of these folks are obtained from the same or similar vendors. One may get a headstart on the other here or there, but for the most part it's all the same, save for locking out people who may want to use a project on a machine they built themselves.

      Of course the magic pixie dust and butterfly tears are hard for the average consumer to come by, but I know this Mexican guy that lives in an underpass in Los Angeles who sells the stuff pretty cheap. Just go to Los Angeles and ask for "Jose'". Everyone will know who you are talking about, and he will hook you up. But whatever you do, don't buy the bottle of Unicorn flatulence that he will try to push on you. I can confirm that it does not double RAM capacity. As the saying goes ... screw me once it's your fault Jose', but screw me twice ... I won't get fooled again.

      Linux is not OS X, or even a reasonable facsimile thereof, because it cannot run software written specifically for OS X. An arbitrary white box with Linux is not therefore a Mac, irrespective of whether its has the same CPU and graphics card some Macs.

      Take that unwashed masses of Linux users! I spit on your NextStep-like window managers! Posers!

      Quite a bit of Linux stuff doesn't run on the Mac either, so I guess it's pretty much a wash.

      Seriously, the differences in what you are able to do between the different OS's, IMHO, are getting slimmer as time goes on. Do you REALLY think that some of these folks on ./ can't make OSX run on that whitebox? If they do, is it a true "Mac"? If it isn't, does it matter? What if they use superior 8800 cards instead of the somewhat dated 7300 cards that Apple uses? What if they get RAID working? Can the argument be made that they have a better "Mac" than Apple makes?

      Mac hardware as some kind of machine that is superior to all others simply because it has the pixie dust to run a specific OS is somewhat specious reasoning to me. Is OS X nice? Hell yes it's nice.

      Then again, so is Ubuntu running Beryl. It makes both Mac and Windows look terribly dated. And it will do it on consumer hardware that you can buy at Newegg for reasonable prices, and the hardware will probably chug along for 20 years given reasonable assembly.

      A computer is what you make it. And most people can make it pretty much whatever they want to.

      I still think it would make sense for Apple to sell OSX to the filthy riff-raff, like they sell the iPod to the filthy riff-raff, as long as they state what hardware will and won't work.

      But it's not my call, and it probably won't happen. Nobody will blow their brains out over it. Life goes on.

    124. Re:Menus at the top! by Weedlekin · · Score: 1

      "But you have the same hardware."

      You have the same CPU and graphics card, which are part of the hardware, not all of it. You won't for example have the same motherboard, hence the fact that the machine won't run an unmodified OS X, and motherboards are hardware.

      "The point is the Apple doesn't create this mystery hardware out of magic purple elephant poop. It's pretty standard stuff."

      It's always been pretty standard stuff. The original Mac used a 68000, and other 68000-based computers such as the Atari ST and Amiga equipped with a little box with sockets for Apple ROMs could run MacOS and any software written for it. PowerPC is made by IBM and Freescale, not Apple, and various companies make PPC-based motherboards that use standard PC cases and components, e.g. PagasosPC and Terra Soft, while IBM manufacture a wide variety of complete PPC systems. However, as is the case with the Intel-based computer you're talking about, these are not Macs, and cannot therefore run OS X and software written for it.

      "True, but is the hardware of any higher or lower quality? That is debatable. Most of the hardware used by all of these folks are obtained from the same or similar vendors. One may get a headstart on the other here or there, but for the most part it's all the same"

      Some things are the same, others differ, most notably motherboards and the sorts of chips / firmware they have. It's difficult to say whether one obtains a better system by building it or buying one from a name vendor, because hardware can fail or perform badly no matter where one gets it from, even when one avoids the cheap crap end of the price spectrum.

      "Take that unwashed masses of Linux users! I spit on your NextStep-like window managers! Posers!"

      You seem to have some notable bitterness issues, because my entirely factual statement about Linux not being able to run software that's written for OS X, ergo a PC running Linux isn't a Mac, did not either state or imply that this means Linux is an inferior OS.

      "Quite a bit of Linux stuff doesn't run on the Mac either, so I guess it's pretty much a wash."

      It's not a wash for somebody wants to run software written for OS X, just like it isn't a wash for people who want or need to run Windows software that doesn't work properly (or at all) under Wine, Crossover Office, etc. There are far more of both categories than people who want to run something which is Linux-specific on another OS, especially with Macs, which have UNIX underpinnings, ship with XWindows on their installation disks, and use GNU compilers and base libraries.

      "Mac hardware as some kind of machine that is superior to all others simply because it has the pixie dust to run a specific OS is somewhat specious reasoning to me."

      It's specious to me as well, hence the fact that I didn't say anything of the sort. Incompatible != inferior; Amigas were incompatible with Sinclair Spectrum and Apple-II software, but most would agree that they significantly better than either of those 8 bit machines.

      "Seriously, the differences in what you are able to do between the different OS's, IMHO, are getting slimmer as time goes on."

      The differences in capabilities of computer operating systems have been dictated by the realities of the hardware they must run on, and what people want to do with it, for nearly half a century. Just about everything we expect from a modern OS had been implemented in the 1960s, but things like mice, GUIs, hypertext, and video conferencing had no real application in a world where most computers spent their time batch-processing punched cards containing financial and scientific data. Personal computers have consistently been a couple of decades behind top dollar "big iron" used by large companies and well-funded research facilities, so it tends to take a little over a decade for those concepts to appear on high-end business PCs, and another decade or so for it to become common on home PCs. A current example is virtualisation, which has been around in th

      --
      I'm not going to change your sheets again, Mr. Hastings.
  5. First web browser by HighPerformanceCoder · · Score: 2, Interesting

    What is the historical basis for claiming that NeXT gave rise to the Web browser? Was NCSA Mosaic developed on a NeXT? Or are you referring to an earlier browser?

    1. Re:First web browser by Anonymous Coward · · Score: 3, Informative

      The very first web browser (called WorldWideWeb) was developed on a NeXT by Tim Berners-Lee.

    2. Re:First web browser by Anonymous Coward · · Score: 0

      Quick Wikipedia look-up shows that Tim Berners-Lee hacked the HTML/HTTP server/browser on Next Cube. Though, the first widely-used graphical web browser was the NCSA one, I think. Well, that's the one I first come across. Not sure if Lynx came before.

    3. Re:First web browser by Strepsil · · Score: 2, Insightful

      And, of course, so was the world's first web server, without which the browser wouldn't have been very useful. :)

    4. Re:First web browser by Stormwatch · · Score: 4, Informative

      What is the historical basis for claiming that NeXT gave rise to the Web browser? Was NCSA Mosaic developed on a NeXT? Or are you referring to an earlier browser?
      WorldWideWeb was the world's first web browser and WYSIWYG HTML editor and was introduced on February 26, 1991 by Tim Berners-Lee and ran on the NeXTSTEP platform.
    5. Re:First web browser by bomanbot · · Score: 1

      The reference is to WorldWideWeb, the first web browser that Tim Berners-Lee actually made for NeXTSTEP, not NCSA Mosaic, which came later.
      Wikipedia has an entry about WorldWideWeb: http://en.wikipedia.org/wiki/WorldWideWeb

    6. Re:First web browser by Anonymous Coward · · Score: 0

      They mean WorldWideWeb, the first web browser. Written on a NEXT machine, along with the first web server. Both MacOS X and GNUStep are modelled after the NEXT environment.

    7. Re:First web browser by marcello_dl · · Score: 3, Funny

      Well if berners lee developed on windows he'd have to integrate his browser into the OS. If he developed on mac, users who surfed with http would have had their sexual orientation questioned. If he developed on unix nobody would have left telnet and gopher for http, unless it had either perl or remote exploits. That leaves the amiga and the next.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
    8. Re:First web browser by pschmied · · Score: 1

      Quite right! I suppose Tim Berners-Lee wouldn't have been doing much hypertext transport with out some sort of a hypertext transport protocol. ;-)

    9. Re:First web browser by Jorophose · · Score: 0

      Sir TBL developped HTML on a NeXT Cube. So I'm assuming he had a reader to go with it.

    10. Re:First web browser by Nazlfrag · · Score: 1

      So it's not 'Here's the tubes pipe'?

    11. Re:First web browser by belg4mit · · Score: 1

      Not at all. Browsers are still useful without servers, as long as they support something like file://

      --
      Were that I say, pancakes?
    12. Re:First web browser by 5of0 · · Score: 1

      I'm sorry, I'm going to have to take your geek card. As many others have said, the first web browser was WorldWideWeb, clearly on a NeXT system. Not NCSA Mosaic. But good try.

      --
      You all have Oo.o and Firefox, so get World Wind.
    13. Re:First web browser by dfghjk · · Score: 1

      That didn't answer the question though. In what way did NeXT "give rise" to the Web browser? Being the application platform used means nothing.

  6. The want to avoid the GPL by bomanbot · · Score: 3, Interesting

    Interestingly, the Etoile developers seem to want to avoid the GPL and prefer the BSD License (as seen on their about page here: http://www.etoile-project.org/etoile/mediawiki/ind ex.php?title=EtoileWiki:About/), which I find a bit odd...

    1. Re:The want to avoid the GPL by Microlith · · Score: 2, Insightful

      It's not odd, it's just not what -you- would have done I imagine.

      Some people feel it's more important to create something that gets used whether in open or closed source form than something be bound by an ideology.

    2. Re:The want to avoid the GPL by bomanbot · · Score: 1
    3. Re:The want to avoid the GPL by bomanbot · · Score: 1

      I think it is odd because Etoile is build upon and heavily relies on GNUstep, which is licensed under the LGPL (I think).

      This has nothing to do with any sort of ideology (as I personally hate ideologic zealotry), but I think maybe it could be impractical in the future to use a different license as there may be legal ramifications they (and especially me) may not be aware of.

      It certainly would be easier if Etoile and GNUstep would use the same license because you do not have different licenses with different legal aspects and issues that may even be interacting with each other. It does not mean that the BSD license is inherently better or worse than the (L)GPL.

    4. Re:The want to avoid the GPL by larry+bagina · · Score: 2, Insightful

      The GNUStep libraries are LGPL. Anything can link to them. the LGPL is not supposed to be viral. Let's keep it that way.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    5. Re:The want to avoid the GPL by Ohreally_factor · · Score: 1

      It's due to the component architecture of the system and having the ability to mix modules. I'm curious as to how this affects the GNU userland. Or does it replace it?

      --
      It's not offtopic, dumbass. It's orthogonal.
    6. Re:The want to avoid the GPL by Actually,+I+do+RTFA · · Score: 1

      Why do you find it odd? The GPL has a fairly viral nature, which they find does not works with their component based system.

      They actually have very strong reasoning.

      --
      Your ad here. Ask me how!
    7. Re:The want to avoid the GPL by TheRaven64 · · Score: 2, Informative
      Hi, I wrote the document you linked to (although the other core devs agree with the reasoning and conclusions). The LGPL affects GNUstep code, and GNUstep code only. The only requirement it places on other code is that it should be possible for the end user to re-link it with their own version of GNUstep. This is not a problem for us (we distribute source code). If people want to distribute binary-only components for Étoilé, I probably wouldn't use them, but they can if they don't statically link to GNUstep.

      We're not trying to fork GNUstep. I, and several other developers, have signed a Free Software Foundation copyright assignment form for GNUstep, so any bug fixes or changes we make can be pushed upstream. Being based on Objective-C, GNUstep can be patched at runtime easily with categories (which can replace methods in existing classes). You may see a few of these in various places fixing bugs in GNUstep, but these are always pushed upstream for inclusion in the next release. The categories are just there so people don't have to install GNUstep from SVN.

      The choice to avoid the GPL comes from two things. The first is that we want to achieve very tight integration between components. This would mean that any license which controls linking as well as derived works would spread over the whole tree, and to third party components. We want to give people the choice to use more permissive licenses, and several of us prefer to use them for our own code.

      It certainly would be easier if Etoile and GNUstep would use the same license because you do not have different licenses with different legal aspects and issues that may even be interacting with each other We do have a few LGPL'd components in the core system, and none of us have a problem with the LGPL as a license. Every other license we use is more permissive. If what you are doing is allowed under the LGPL, then it will be allowed. For some components, you may have more rights. Some parts are MIT-licensed, so you can do pretty much anything with them. Most new code is 3-clause BSD-licensed. The one exception currently is PopplerKit which, being based on Poppler, which is based on xpdf, inherits the GPL. If you know of an LGPL, BSDL, MITL or PD library for parsing and displaying PDFs, I'd love to hear about it.

      One of the nice things about the BSDL and MITL is that you don't need to be a lawyer to understand them. They're one or two very short clauses with an absolute minimum of legalese. The LGPL is a lot more complicated. If you have read and understood the LGPL, then you should have no problems with any other licenses we use.

      --
      I am TheRaven on Soylent News
  7. Huh? by JimDaGeek · · Score: 2, Interesting

    This isn't even close to OS X. Seriously. This is like making some really crappy "OS" and then saying, hey, we are close to MS Windows 95. I looked at this site, screen shots and other stuff. They just don't come close to the current Mac OS X OS.

    --
    General, you are listening to a machine! Do the world a favor and don't act like one.
    1. Re:Huh? by istewart · · Score: 1

      Look at it this way: of course it'll never be close to OS X in terms of interface design or polish, but if a GNUstep-based desktop solution gains traction, that can only be a good thing for the Mac as well as open-source platforms. More robust open-source Objective-C frameworks mean that Mac developers can potentially deploy their programs on many more computers, and that will in turn attract more developers to the NeXT-derivative frameworks.

      On the other hand, these Étoilé guys seem to be writing as many of their own frameworks as they are contributing code back to the base GNUstep frameworks. That may be a wise decision, since the GNUstep project isn't focused on creating a desktop environment, but at the same time, I hope it isn't symptomatic of NIH syndrome. I would hate it if cross-developing for OS X and GNUstep systems wound up involving a bunch of compatibility shims and poser classes; that would wreck the whole effort.

    2. Re:Huh? by mr_matticus · · Score: 3, Insightful

      Parent is not a troll.

      Ubuntu is more Mac-like than this. This is the perfect example of just plain not getting it. Copying a general layout isn't good enough. Approximations of a user experience defined by close attention to detail and sound design principles are simply bound to failure. Just look at the screenshots. This UI has the exact same deficiencies as nearly every other window manager for Linux--poor typefaces, rendered poorly and positioned poorly. Manipulation elements that lack refinement. You've got flat icons on a flat background shoehorned into a plain rectangular space.

      The "About" screen shows it all. The background image is unbalanced. That's fine. But the shadowbox on top of it is precisely centered. Those are clashing elements. The corners on that shadowbox are too rounded to appear crisp and too confined to appear smooth or blended. The "let your environment grow" text looks goofy and childish, and it doesn't seem related to anything. It should be superimposed on the image, above the gradient bar, or it should be boxed into a separate branding box somewhere. Right now, it's superfluous text, and it's a typical, ugly Linux text experience to boot.

      I don't mean to be an art snob or to demean the people who doubtlessly worked hard on this. I certainly don't mean to imply that Linux's goals should be as heavily slanted toward the aesthetic as, say, OS X. But if you put *yourself* in the big kids' pool, be prepared to take it. This is amateur, uninspired, and completely misses the boat.

    3. Re:Huh? by pschmied · · Score: 4, Insightful

      I think some times that the Linux community can be too concerned with window dressing and not enough by substance. What make this Mac like isn't a skin deep sort of thing. It's about being able to write a program and have it run on both.

      Now, there is such a thing as not having enough of an eye for Window dressing as well. That's one of the historic complaints about GNUStep. People complain that it looks too much like the Old School NeXT. That's probably a valid complaint. These guys are making progress. I'd rather have the UI look pretty in 0.3 or 0.4 than the development libs suck into perpetuity. On that front, GNUStep is reasonably Cocoa-compatible--to the point of being able to share .Nibs (user interface files) with the Mac.

      -Peter

    4. Re:Huh? by JimDaGeek · · Score: 0, Flamebait

      Huh? WTF are you talking about? What "backwards" scrollbars? I know from your stupid comments that you have never used OS X for more than a few minutes. Buy a Mac and use it over a few weeks (2-3 weeks) and you will be converted. End of story.

      So, you are a stupid, idiot that likes to lick balls!

      --
      General, you are listening to a machine! Do the world a favor and don't act like one.
    5. Re:Huh? by chuckymonkey · · Score: 1

      Please don't kill him!!!! He didn't mean anything by it!

      --
      "Some books contain the machinery required to create and sustain universes."-Tycho
    6. Re:Huh? by mr_matticus · · Score: 4, Interesting

      But the problem exists on that level as well. I confined my comments to the visual layer because that's what parent started with this thread. But these people seem to writing themselves into a corner and it's pretty easy to see how their frameworks are going to have to be wedged in with electronic equivalents of shims and compatibility layers to come back into the fold. They're writing a lot of their own stuff and making it, just like on the surface layer, an approximation of true interoperability.

      GNUStep is reasonably compatible with NextStep which is reasonably compatible with Cocoa. They branched from a common ancestor and happen to be reasonably similar now. All the extra frameworks tossed in to this project looks to be a third fork more than a bridge between the two.

    7. Re:Huh? by forkazoo · · Score: 4, Insightful

      Ubuntu is more Mac-like than this. This is the perfect example of just plain not getting it. Copying a general layout isn't good enough.


      "Mac-Like" in this context refers chiefly to the fact that programming for this is very similar to Cocoa development on Mac OS X. The guts are quite Mac-like compared to writing for Qt/KDE or GTK/Gnome.

      OTOH, I expect that your criticism is quite valid. You may want to consider contributing some art to the project, or submitting patches to make it more aesthetic. Personally, the way it looks doesn't bother me, but don't let my bland tastes stop you from scratching your itch! :)
    8. Re:Huh? by mr_matticus · · Score: 4, Insightful

      Wouldn't it still be more accurate to say that this project is GNUstep-like? Or GNUstep-based?

      Its similarity to OS X is purely by virtue of it using GNUstep, which is Cocoa-like. Credit for "Mac-like" would therefore go to the GNUstep project, at least in my book. I certainly agree with your assessment of the context of the summary, and I think that I simply glossed over the underpinnings. Perhaps my definition of similarity is too strict. I simply assumed that everyone knew GNUstep was Cocoa-like and that these people were making the claim based on their UI. It hadn't occurred to me that they would just take the "Mac-like" title from their GNUstep underpinnings.

    9. Re:Huh? by originalnih · · Score: 0

      We're talking about Etoile, not OS X. You fail. Try to read the article next time, slashbot.

    10. Re:Huh? by dircha · · Score: 0, Flamebait

      "I don't mean to be an art snob or to demean the people who doubtlessly worked hard on this," and yet you very much did demean their hard work, work for which they were not paid, did not ask your blessing, nor did they need it. It's the very essence of snobbery to suppose that your personal taste is the yardstick by which others judge success and failure.

      How do you say... oh, FUCK OFF?

      Seriously. What is your problem?

    11. Re:Huh? by yoshi3 · · Score: 1

      Agrees! Apart from the menu bar, dock and rip offs of a few utilities that come bundled with osx the ui is nothing like it. It does look like a promising project though, I'll be sure to keep an eye on it!

    12. Re:Huh? by Orange+Crush · · Score: 3, Funny

      It looked more Mac-like before the name change, but Apple threatened to sue if they called it iToil.

    13. Re:Huh? by iminplaya · · Score: 1

      I thought the same thing. It looked like a trip back to 1998. For a Mac lookalike, I use Baghira and rearranged the window buttons. This is their screenshot. Now that looks like a Mac!

      --
      What?
    14. Re:Huh? by theurge14 · · Score: 1

      The didn't even have the decency to not directly copy the volume icon from OS X. Sigh. It's hard to criticize Microsoft for no innovation when much of the open source world does nothing but directly copy other work.

    15. Re:Huh? by Improv · · Score: 1

      If it really looked like NeXTStep, there'd be a lot less to complain about. GNUStep generally looks like "NeXTStep-but-ugly" - part of what defined NeXTStep was that the interface was so polished.

      --
      For every problem, there is at least one solution that is simple, neat, and wrong.
    16. Re:Huh? by guardiangod · · Score: 1

      Hard work always give you result, but the result may not be the reward you are looking for.

    17. Re:Huh? by mr_matticus · · Score: 3, Insightful

      Perhaps you should ask yourself what your problem is. You're the blustery, vitriol-spitting pig that makes Slashdot infamous as a hive of morons and assholes.

      Needing or asking for a blessing is irrelevant. This is a discussion site, in case you hadn't noticed. The summary makes a proposition. People disagree with that proposition. I'm one of them. The idea that people should get a free pass because they're not paid to do it is likewise absurd. These developers are not children. They don't get a writeoff for failing to capture the essence and for missing the point. If they want to invite comparisons to other products and want to put something in the public eye, then they can accept the consequences that result, which includes criticism. It's not an arbitrary, empty, personal assault, much unlike your comment.

      "My personal taste" is not a factor in this assessment. They're called basic design principles and are sorely misunderstood and violated by people at large. That's why not everyone is an architect or a designer or a sculptor. It's an art of subtlety, but as you clearly personify, there's no one more dense than an angry Slashdotter. "My personal taste" would be to avoid purple and flowers. "My personal taste" would involve a more dynamic menu bar that goes beyond the Mac metaphor. But you see, these aren't the issues with the project from a design standpoint. Part of a fair critique is looking at what it purports itself to be and seeing how well-realized that is. I don't like Gothic architecture, but I can certainly admire the success of a great Gothic revival piece.

      The "yardstick," further, is clear: they (be they /. editors or developers) threw down the gauntlet and said "Mac-like" while coughing up a poor approximation. Success and failure are determined by their ability to capture the theme. It's abundantly clear that this is sorely lacking. If you disagree, then be a rational adult and do it. I've outlined a few of the many ways they fail to measure up. Demonstrate how they ARE Mac-like if you can. The summary put itself in with the big kids and it can't hold its weight. You can't seem to divorce yourself from your rabid feelings and don't seem to know anything about space and weight, to say nothing of design in general, so I won't hold my breath for an intelligent response.

      While you're at it, cook up some rationale as to how thoughtful criticism is demeaning.

    18. Re:Huh? by Onan · · Score: 1

      It looks vaguely like a mac (though eesh, invest in some antialiasing), but the static looks of an interface are a relatively small part of what matters. I'd bet cash money that it doesn't work like a mac.

      Sorry, I don't mean to disparage your choice of window dressing or imply that it doesn't work well for you. I'm just frustrated by the decades of people willing to steal the very simple superficial parts of another known-good system and declare, "okay, user interface problem solved!"

    19. Re:Huh? by Anonymous Coward · · Score: 0

      You Sir are an Idiot. Have you perhaps noticed the 0.2 version number? Every and all the things you mention are not *critical* to software development, just things that will round up the *finished* product.
      Talking about vitriol spitting pigs...
      I have had enough with the design pseudo-elite. And don't make me start talking about this "infinite target" thing. Pure idiocy.

    20. Re:Huh? by KugelKurt · · Score: 1

      This is amateur, uninspired, and completely misses the boat. God.... this is version 0.2 -- the second Étoilé release ever. It's targeted towards developers, not the general public.
      It's like saying that KDE 4 is crap, because the current Alpha 2 release is not polished.
    21. Re:Huh? by MysteriousPreacher · · Score: 1

      There are two problems with your argument.

      "work for which they were not paid, did not ask your blessing, nor did they need it"

      It doesn't matter why someone is doing something, it's the end result that counts. Even if someone is doing volunteer work for a charity, if they do a bad job then something needs to be done. Best intentions are not an excuse. That said, in a project like this it's up to the developers to decide what they want to achieve. As users, we can only hope that our interests are the same as theirs.

      "It's the very essence of snobbery to suppose that your personal taste is the yardstick by which others judge success and "

      The best thing about open source projects is that they can be very responsive with regard to feedback. Without this feedback, they will stagnate or find it difficult to find a userbase outside the development group. Projects vary a great deal, for example OpenBSD is primarily developed to satisfy the needs and scratch the itches of its developers. MySQL is developed to meet the needs of its users. Either way, projects grow stronger through feedback and suggestions. Most suggestions are unworkable or undesirable but some are good enough to advance the project.

      I'd suggest you take Mr Matticus' feedback as it was intended. A constructive critique of the project, backed up with advice on how to resolve his concerns. Two things you managed to totally avoid doing in your 'omg stfu!!1!' response.

      --
      -- Using the preview button since 2005
    22. Re:Huh? by Anonymous Coward · · Score: 0

      That defense is not reasonable. That's like saying "don't point out the problems with the Wright brothers' flyer because there are lots of changes and room to grow."

      Feedback is a critical part of how changes are made and it's a foolish notion to say there's ever a point where informed critique is inappropriate.

    23. Re:Huh? by bogomipz · · Score: 1

      Many people here seem to be under the impression that it's the Étoilé project that compares themselves with OS X. It's not, at least not in the context of this specific release. The only place the official release note mentions Mac OS is here;

      This release includes improvements to the Camaelon theme engine, providing a clean and modern appearance to GNUstep-based applications. This is combined with the Étoilé Menu Server, providing a horizontal menu bar similar to that found in Mac OS, and making this the first Étoilé release with enough features in place to be usable on a daily basis.

      Of course, the fact that Étoilé is pushing a horizontal global menu means /. has to come up with an sensational headline like this.

    24. Re:Huh? by KugelKurt · · Score: 1

      That was not feedback. Feedback is targetted at the developers. That was just a bashing /. comment. And "You're amateurish." is not a good feedback anyway.

    25. Re:Huh? by MrHanky · · Score: 1

      Assholes, certainily, but the morons are mostly Apple fanboys.

    26. Re:Huh? by Nicolas+Roard · · Score: 2, Informative
      The idea that people should get a free pass because they're not paid to do it is likewise absurd. These developers are not children. They don't get a writeoff for failing to capture the essence and for missing the point. If they want to invite comparisons to other products and want to put something in the public eye, then they can accept the consequences that result, which includes criticism.

      In general, I would agree with you. But if you had taken two minutes reading OUR website and not the misleading /. summary, you'd have realized that we DO NOT MAKE ANY CLAIM to be a MacOS-like environment (As in fact, we actually don't want MacOS X, we want something else.). Now, we do gladly accept criticism, and you are more than welcome to discuss UI issues on our mailing list : we actually are very UI focused, and I assure you that we think it's important. But as others said, this is only a 0.2 release, and many things will improve, we know that very well...

      The "yardstick," further, is clear: they (be they /. editors or developers) threw down the gauntlet and said "Mac-like" while coughing up a poor approximation. Success and failure are determined by their ability to capture the theme. It's abundantly clear that this is sorely lacking. If you disagree, then be a rational adult and do it. I've outlined a few of the many ways they fail to measure up. Demonstrate how they ARE Mac-like if you can. The summary put itself in with the big kids and it can't hold its weight. You can't seem to divorce yourself from your rabid feelings and don't seem to know anything about space and weight, to say nothing of design in general, so I won't hold my breath for an intelligent response.

      Well, you can't really hold on to us that the /. post is misleading ? Your whole premise is that we claimed that, and then you proceed to detail where we fail in that goal. And I totally agree ! Contrary to what you think, we are not claiming to be an OSX clone, we don't want to be one, and we are FAR from saying that we provide here a perfect thing: there are lots of things to do, to fix, to clean up, be it in the code or on the UI. And people are welcolme to provide constructive critiscism and give us a hand ;-) but at the same time you should also understand that it's "just" a 0.2 release and we are perfectly aware that we have a lot to do...
      Sigh.. what happened to the whole premise "Release Early, Release Often" :-P [and we're far to that too...]

    27. Re:Huh? by Nicolas+Roard · · Score: 1

      Err... can you point me to that ? Because I'm pretty sure we don't :)

    28. Re:Huh? by Anonymous Coward · · Score: 0

      This could have been a great reply, if it hadn't been delivered with immaturity and more personal attacks than the original post it replied to.

      I'm sure the OP doesn't want (or need) a lesson in what you and perhaps even many others consider 'basic design principles'. If, as you claim, 'people at large' violate these principles consistently, perhaps it is dogmatic adherence to a supposedly 'basic' set of principles that is at fault, and not the people at large.

    29. Re:Huh? by iminplaya · · Score: 1

      You are right, though, remember that pic is a jpeg. And it's very tweakable. Using it looks a lot better, but it's no substitute by a long shot. My PC is fairly tricked out with lots of RAM, two drives, etc., but it's still a PC. Even with the Linux, I still prefer my office Mac mini. There's nothing like the real thing (baby), and it has Unix, too. Can't beat that with a stick. I just took a cheap shot at the pictures. Hell, it's just out! Obviously it deserves every chance. And I'm more than willing to jump in and learn a little about interface design. Right now it looks very Gnome like. A little lip stick, some eye shadow, and who knows? Maybe I can make this inflatable feel a bit more like a RealDoll :-)

      Sorry, I don't mean to disparage your choice of window dressing...

      No problem. I recognize that it just that, window dressing, but I gotta be able to pretend a little. It helps me stay in touch with my "inner Mac". And in many ways, I do like Linux file management way better than Apple's, which is where my real complaints are.

      --
      What?
    30. Re:Huh? by Anonymous Coward · · Score: 0

      Anyone who uses a phrase like "text experience" needs to die in a fire.

    31. Re:Huh? by blankaBrew · · Score: 1

      You are completely missing the point. Their efforts are not to create a MacOS X skin, but rather an OS compatible with cocoa. From the developers perspective, if they can achieve near parity with the cocoa libraries (they already had a great start since they had OpenStep), then you can just recompile a MacOS X application to run on this GNUStep based OS. In my opinion, this represents a quantum leap in the opensource movement. Stop trying to copy the knuckleheads in Redmond, and start copying the guys in Cupertino.
       
      If this project catches on, it could fuel development into the GNUStep libraries and be a huge boon to linux developers (that want a high-end and highly object oriented development environment), the Mac Community (because there would be more developers knowledgable about cocoa), Mac developers (because it could mean a painless port of their Mac app to linux) and all Mac and Linux users (because it could mean a more developed and application rich environment).
       
        Let's hope this project gets embraced by the opensource community.

    32. Re:Huh? by Nicolas+Roard · · Score: 1
      GNUStep is reasonably compatible with NextStep which is reasonably compatible with Cocoa. They branched from a common ancestor and happen to be reasonably similar now. All the extra frameworks tossed in to this project looks to be a third fork more than a bridge between the two.

      Uh... we aren't forking GNUstep at all. Many of the Etoile developers are also GNUstep developers... :)

      What we do provide and will continue to provide are additional frameworks. Those are obviously free software as well, and anybody is welcome to compile them on OSX; as a matter of fact, many of them already works on OSX, as quite a few devs program on OSX. But anyway... it's just a side effect of beeing based on GNUstep/OpenStep, we don't especially want to be compatible with OSX -- I repeat myself, but we aren't doing an OSX clone and that was never our goal.

    33. Re:Huh? by Nicolas+Roard · · Score: 1
      Their efforts are not to create a MacOS X skin, but rather an OS compatible with cocoa. From the developers perspective, if they can achieve near parity with the cocoa libraries (they already had a great start since they had OpenStep), then you can just recompile a MacOS X application to run on this GNUStep based OS. In my opinion, this represents a quantum leap in the opensource movement. Stop trying to copy the knuckleheads in Redmond, and start copying the guys in Cupertino.

      Actually... we aren't particularly aiming at an OS compatible with Cocoa. We are compatible, indeed, but it's a (nice) side effect of beeing based on GNUstep, it's a bonus, but not our primary goal. We are not particularly aimed at copying OSX either; it's just that OSX happend to be really good (mostly) and we want to use some of its ideas. Similarly we are influenced by NeXTSTEP, by Smalltalk, NewtonOS, etc.

      That beeing said, as we are using the GNUstep libraries, it is relatively easy to port a Cocoa application to Etoile, simply because it's also pretty straightforward to port a Cococa application to GNUstep in the first place... So we have a certain source compatibility with Cocoa, to the extent that GNUstep has it. But our main goal is not to produce an OSX clone.

      We want to create a good, component/document oriented desktop environment. It's a lot of work and we are just at the beginning. It's also rather likely that we'll always be a "small" desktop, as what we want is not exactly what current popular desktop environment are aiming for, and maybe we are also completely mistaken in thinking that our approach will be much better. Note also that the current 0.2 release is still rather close to a normal desktop, but we are planning quite different things for the future (much closer to NewtonOS or a Smalltalk system than to Windows...) : widespread use of CoreObject, Assistant tech, etc.

      So in the end it just amount to the fact that we are kinda bored with the current desktop approach and we prefer to work on our free time on something that isn't afraid to try really different approach than working on cloning Windows (gasp!) or even MacOS X. Current Linux Desktop provides a good enough solution for that.

      (ps: as an aside I totally agree though that Etoile could help GNUstep gains some traction and nothing would please me more)

    34. Re:Huh? by theurge14 · · Score: 1

      Here's Mac OS X 10.4

      And here's a screenshot from Étoilé

      The volume icon on the titlebar is the same, the rounded corners are the same and even the shading from white to gray of the titlebar is the same.

      I'm not saying using a titlebar like that is bad thing, I'm just saying if you're going to use the idea at least come up with one that is unique looking.

    35. Re:Huh? by Nicolas+Roard · · Score: 1

      We didn't copy the image, jesse recreated something that was close.. yes it does look similar, perhaps too much (though there's so many thing you can do if you want a plain looking icon for a speaker!) but we certainly didn't just copy the image. The rounded corners are indeed an obvious nod to apple -- there's no denying that Etoile is somehow inspired by OSX graphically, and many of us use OSX regularly.

    36. Re:Huh? by mr_matticus · · Score: 1

      I understand that your website does not make that claim. I also indicated that the source of this could easily be the Slashdot editors. However, the top menu bar and inclusion of a dock is begging for someone to make that comparison, and coupled with the GNUstep use, it's something you must expect. The fact is that Slashdot is just as much about the ideas proposed by the summaries as it is about the material they link.

      Being "just" a 0.2 release is meaningless, though. People do all sorts of things with version numbers these days. If you release a product to the public at any stage, criticism should be expected of that product as it exists. Anything and everything else promised or hinted by developers or on the website is vaporware until it's done. It also doesn't appear as though the site indicates a list of "known issues" or "future development plans." Moreover, the idea that the developers are aware of every issue is something that we all know is false.

      I'm glad that you guys are trying your hand at something new. The UI basics you've chosen certainly are functional and familiar. But to expect that you know what you have to do already (particularly from a UI standpoint) is unrealistic, historically speaking. If you're serious about UI, I would suggest creating a separate visual layer mailing list and trying to get good interface designers and artists onboard as early as possible. Putting it on the "we'll get to it at the 'polish' stage" is perhaps the biggest reason FOSS UIs tend to suck so much. It needs to be part of the process from the very beginning, and it needs just as much time and attention as any other component. The "it's just a 0.2 release" excuse just doesn't fly. Good UI basics should be in place from the very first release just like good programming basics need to be in place.

    37. Re:Huh? by Anonymous Coward · · Score: 0

      Okay, but when are we going to get some half-decent-looking fonts for Linux?

      I want Helvetica and Lucidia Grande. Only then will I be able to stand looking at the interface.

    38. Re:Huh? by jesseross · · Score: 1

      As the artist working on Etoile, I totally agree with you. We're not there yet. There are a lot of issues I'd love to see resolved: the font issue is a major one for me (I have someone working on a new system font as I type this), and the lack of polish on the widgets and titlebars requires changes to happen in GNUstep proper in order for Etoile to take advantage of them. I'm in a discussion with the maintainer of GNUstep about that right now too. The About screen is ugly--point taken--and I need to fix that. I consider ugly UI elements bugs, and by all means, feel free to file bug reports against them. If I can do something about them, I will. This is one of the recent mockups I've been working on to try to target towards for our 0.3 release -- again, don't expect OS X, but hopefully it gives you some hope that we're not clueless, and that we actually do care about the UI.

      On the project, we've long said that comparing ourselves to Apple and OS X would only lead people to disappointment. We don't have the resources of Apple -- there is no way we could ever compete. All we hope to do is provide something different, something that we who work on the project would enjoy using. Getting more people contributing would make that happen faster.

    39. Re:Huh? by mr_matticus · · Score: 1

      That mockup is a wholesale ripoff. You keep saying you're not going after OS X and you don't want to invite comparisons, but then you do something like this.

      Why do you have the rounded top corners in the menubar? It's mildly inconsistent in OS X, but it's 100% out of place in your mockup. What function does it serve? Unlike OS X, none of your windows have rounded edges. The audio icon, like another poster stated, is a complete recreation. You can't honestly say that there's no other way to convey an audio control or even a visual representation of a speaker. Why the black silhouettes for all the icons? Simplicity and contrast is a good idea to take away, but it can be accomplished in many other ways. What is the icon to the right of the clock? Presumably a search function. The buttons in the foreground window are nice, but shouldn't they embrace the same sharp lines as the windows and interface in general? The sidebar layout is the exact tree topography used by Apple, which can be improved (use horizontal sorting to prevent scrolling, to give one example).

      If you want to provide something different, provide something different. There's not a single original idea in the mockup. The mockup is an improvement, but it's begging for even more OS X comparison because all of the improvements consist of taking more ideas from OS X (though in many cases more successfully than the current version).

    40. Re:Huh? by jesseross · · Score: 1

      This was just to show you that we do have the desire and the ability to do something more polished. Obviously we're not going to do exactly this, and this is really rough and not completely thought out (I made it in one afternoon after a quick chat with another developer). I respect the feedback though, and I'll continue to push it a different direction.

    41. Re:Huh? by jesseross · · Score: 1

      If you're up for it, I'd be interested in talking with you further and hearing more about your suggestions, such as what you had in mind with the horizontal sorting. Ideally, we'd like this to be a collaborative project, and good ideas definitely come from everywhere.

      If you're interested in discussing what else you'd like to see in the project, you can get a hold of me via the Contact page on my site.

    42. Re:Huh? by Lproven · · Score: 1

      I think your priorities are all to cock.

      For one, your objections to the "about" box are /subjective,/ These things may not appeal /to you/ but that is /your/ personal taste; the points you raise are not universal rules, they are your take on it. The single one I personally feel has /any/ shred of validity whatsoever is the placement of the motto beneath the image rather than in or on it. I am not an artist, but I do magazine design and layout and am regularly published. My opinion is just as valid as yours.

      What makes Etoile MAc-like is the class libraries and programming languages and interfaces. It could look like AmigaOS 1 or a Psion 3, that has no relevance to its Mac-like nature.

      When a system is in early development, the aesthetics really are not particularly important.

      I suggest you take your finely-honed sensibilities and apply them to a mature project which needs a facelift, like, say, KDE, which I find such a visual dog's dinner that it actually puts me right off using it. KDE is plug ugly and the previews of KDE4 are every bit as bad. There's a GUI which desperately needs some cleaning and prettifying.

      --
      Liam P. ~ "Intelligence is a lethal mutation." (me)
    43. Re:Huh? by Anonymous Coward · · Score: 0

      "Your work is amateur" != "you're amateurish"

      Every bit of his comment is directed squarely at the developers.

    44. Re:Huh? by mr_matticus · · Score: 1

      I would be happy to lend a hand where I can. My schedule is a bit erratic for the next few months as I switch gears and take on some new cases, but I'll get in touch.

      As to the horizontal sort, it's really quite simple. Arrange the field headers in a row (like Firefox's bookmark bar, for example) with individual options in drop-down menus. For flexibility, include a collapsible side "drawer" which contains the options of the chosen sort mode. I'd be happy to provide some rough visual examples if this description is unclear.

    45. Re:Huh? by jesseross · · Score: 1

      Ah, yeah -- very smart. With the Tag section that could be a bit messy, as I anticipate the user will end up having a large list, which when using a drop-down becomes ever more impractical as the list grows . But for the Date and Type sections, which will have relatively few options, drop-downs should work very well. Thanks for the idea and feel free to get in touch again when your schedule clears up!

  8. Trying to get this up and running by Deliveranc3 · · Score: 1

    In Ubuntu Feisty (using 2.6.16 kernel, don't ask)...

    It's not a window manager like my enlightenment or blackbox and I'm not sure where to start it. Seems to have installed fine.

    Can I configure it to be an option in my login or do I need to command line it?

    1. Re:Trying to get this up and running by pschmied · · Score: 4, Informative

      No, it's not a window manager. It's more analogous to something like GNOME or KDE with their associated libraries.

      Here's a rough step-by-step:

      1. Install the dependencies listed here: http://gnustep.blogspot.com/2006/10/gnustep-on-ubu ntuppc-610.html

      2. Use the GNUStep "Startup" package (you need a newer version of GNUStep than what is bundled with Ubuntu): http://www.gnustep.org/experience/Startup.html

      3. Compile Etoile per the instructions in the tarball.

      It's a bit different procedure than your average configure, make, make install. My hope is that someone will start packaging current versions for Ubuntu. Maybe I'll get off my duff and start doing that.

      Cheers,
      Peter

    2. Re:Trying to get this up and running by pschmied · · Score: 1

      If you are on Intel rather than PPC you may want "libffi-dev" instead of "libffcall-dev"

      Cheers,
      Peter

    3. Re:Trying to get this up and running by Deliveranc3 · · Score: 1

      Thanks so much peter, unfortunately I think we miscommunicated. I have installed the tarball, however I don't know how to change my windows manager or desktop environment. I don't know how to get back into the standard.

      As well as not being able to choose my desktop environment I'm having trouble choosing between the "theme" option I've chosen and what's available through gdmsetup.

      Basically there are several desktop configuration menus, and none seem to allow me to choose a desktop environment.

    4. Re:Trying to get this up and running by TheRaven64 · · Score: 1

      It's not a Window Manager, but it does include one. It should work fine under Ubuntu, since that's what our LiveCD uses. If you run the setup.sh script, then it will install a .desktop file that GDM can use to define a login environment. Please be aware though, that this really is a 0.2 release. We don't expect people to use it as their primary environment yet; it's still mainly for developers.

      --
      I am TheRaven on Soylent News
    5. Re:Trying to get this up and running by pschmied · · Score: 1

      Sorry I missed your message earlier. In the tarball, check out the INSTALL file. Short answer: run the setup.sh. It will ensure that the .desktop file gets added to the list of session types in gdm.

  9. Strategic importance of Etoile by pschmied · · Score: 5, Interesting

    Etoile may be in its relative infancy, but I believe it has great strategic potential for the FOSS movement. Etoile / GNUStep is building some great infrastructure, uniting the Mac and FOSS communities, and is building on some very interesting ideas.

    If you haven't already done so, I urge you to check out David's Core Object posting. There is some exciting stuff there. Smalltalkers will find it particularly interesting.

    Props to the Etoile team! This is even more reason for me to grow my Objective C / Cocoa / GNUStep skills.

    -Peter

    1. Re:Strategic importance of Etoile by TheRaven64 · · Score: 1
      IF you're following CoreObject, I committed code yesterday that turns the experimental pile of cruft into a framework. Serialising invocations (messages and their arguments, that's method calls to any C++/Java people) and then re-loading them and playing them back now works for my test case. This week I'll tidy up and document the code and then start working on the higher levels. Quentin's already done some work from the top down while I've been working bottom-up, so we should meet in the middle soon, and have something relatively usable for 0.3.

      By the way, I'm not a huge fan of describing Étoilé as 'Mac-like.' OS X does some things very well, and we have no hesitation in copying them. NeXT also did some things very well, and we also have no hesitation in copying them either. Both did a lot of things wrong, however. We are not trying to copy either. We're trying to build a first-rate user environment. In doing this, there is no surprise that we will have some similarities with the best of the existing environments.

      --
      I am TheRaven on Soylent News
  10. Editors? by pete-classic · · Score: 1, Troll

    Once again, the "editors" have failed us. The linked news item doesn't mention Mac anywhere. Neither does the project "about" page. And the screenshots don't look particularly like a Mac. (The title bar icons are on the opposite side from MacOS!)

    So, the submitter is out of phase with our collective reality, and the "editor" went ahead and posted it to the front page :(

    -Peter

    1. Re:Editors? by Swampash · · Score: 1

      Remind me never to read another article posted by kdawson that mentions OS X. The guy appears to not have any idea what it is.

  11. Mac OS? by Anonymous Coward · · Score: 0

    This looks like Gnome with a Mac-like skin (I do realize that it's more than that). Although it does bear some similarities to Mac OS, I wouldn't say it was entirely similar...

  12. Oh good, another IP-ripoff. by Anonymous Coward · · Score: 0

    Just what the movement needed, more copying and unoriginality.

  13. NEXTSTEP = OS X by Anonymous Coward · · Score: 2, Informative

    Read some history, Apple bought NEXTSTEP and based OS X on it. Etoile uses some NEXTSTEP.

    1. Re:NEXTSTEP = OS X by heinousjay · · Score: 1

      The relationship is kinda like eToile's dad's stepbrother's kid is OS X.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    2. Re:NEXTSTEP = OS X by pete-classic · · Score: 1

      Thanks for the back, but you really should resist the urge to feed the trolls. I imagine that this AC knows perfectly well that what he's saying doesn't make sense. For example, Etoile is based on GNUstep, not NeXTStep, which he must know, since he reads some history.

      -Peter

  14. Obligatory comment by Anonymous Coward · · Score: 0

    Yes, but does linux run it?

  15. Hail to windowmaker by Anonymous Coward · · Score: 0

    I've always loved the dockapps in windowmaker (the way you can just drag them on side and they stick).
    I also loved some other features of windowmaker (its fast, small, integrated configuration utility, etc, etc)

    However, I think they should add some sane functionality in windowmaker, like a file manager that makes sense, and the file choosing dialogs that are not crazy.

    Really, someone should just recode the Windowmaker in a sane way so it makes sense, recode it in something like Qt/C++ so people easily can add features etc.

    I really think that instead of just following one way of doing stuff (e.g. it has to look like osx, or it has to look like windows), developers should just pick the best features from all the environments (think of it as mistakes we can learn from) and then redo this in a better way, only taking features that are sweet.

    Anyone up for it?

    1. Re:Hail to windowmaker by Anonymous Coward · · Score: 0

      Anybody who thinks Windowmaker should be redone in QT/C++
      A. Does not get it
      B. Needs to be shot.

      One of the REASONS Windowmaker wasn't written in C++ was because there wasn't an objective c++ compiler available for non-mac OSes at the time.

      Another thing is that WindowMaker as it stands is extremely low resource, maybe not as low as fluxbox or something, but it's been running on my systems constantly since the Double Digit pentium era. What features it does include do what's needed and little else (Although I agree with issues regarding the dockbar, and the menus, but neither of those will be fixed by some uneducated twit going at it with QT and C++ and making everything a class because they're a l33t h4x0r.

      My 2 creds.

    2. Re:Hail to windowmaker by Anonymous Coward · · Score: 0

      So it wasn't written in C++ because of a constraint that no longer exists. That's no argument against rewriting it. And the current version is easy on the resources. That's fine, but again no reason to write something more featureful that isn't constrained by the low resouce requirements. You're free to continue using the current WindowMaker.

    3. Re:Hail to windowmaker by Anonymous Coward · · Score: 0

      Windowmaker is very good, but there are bunch of stupid little things that annoy me. Mostly because it follows the "it has to be like NeXT" ways.

      The reason why I think it should be rewritten is because one should take all the best things from GNUStep (or NeXT) and all the best things from other environments and come up with a desktop environment that has docks, but all the weird things and quirks of Windowmaker should be avoided. Also, a nice and simple file manager should be integrated (one that has no resemblance to NeXT/Mac on because those are so screwy in my opinion).

      And as for the C++, I said that it should be rewritten. That means that you can still use Windowmaker for years to come. But someone else should rewrite the thing and call it something else. And as for the speed, the fastest environment ever was BeOS and it was also written in C++. The advantage of using C++ (and Qt for that matter) is the fact that it is much simpler and logical to develop in.

      IMHO, C makes a lot of sense for certain applications (low level OS stuff, drivers, etc), but when it comes to GUI, C++ (or any other OO language) makes helluva lot more sense.

      So, anyone up to writing a small, fast, windowmaker-like-with-dock-ctrlpanel-and-file-mana ger desktop environment that makes sense and that is not just another step clone?
      I'm thinking more like good wm features + good mac features + good windows features + good kde features + good gnome features + good enlightenment features...

  16. So does the FSF for GNUStep by pschmied · · Score: 4, Insightful

    The reasoning is actually pretty good. They are building a services based desktop that also has a lot of components for which they want broad reuse to be possible. The FSF actually releases most of GNUStep under the LGPL. Given the age and status as an FSF project, I wonder if LGPL wasn't in part to address the requirements of GNUStep.

  17. Looks like WindowMaker! by Anonymous Coward · · Score: 0

    http://www.windowmaker.info/

    Why couldn't the Etoile guys just enhance WindowMaker instead? It seems a bit like they are reinventing the wheel.

    1. Re:Looks like WindowMaker! by belg4mit · · Score: 0, Troll

      No, WindowMaker has a Wharf/Dock a la NeXT. Etoile has auseless dock" a la OS X.
      One allows for nice cascading graphical menus, the other allows for candy clutter.

      --
      Were that I say, pancakes?
  18. not so closely related anymore by BorgCopyeditor · · Score: 1

    Close technological relative? Close? Like the bird and the dinosaur?

    --
    Shop as usual. And avoid panic buying.
  19. Yawn by Anonymous Coward · · Score: 0

    *Yawn*. Nothing new here. It looks like every other windowed environment I've ever seen ever since Microsoft invented the windowed computer with Windows 95.

    (mod funny, yo)

  20. Not OSX by Anonymous Coward · · Score: 0

    It looks as much like OSX as KDE looks like windows.

  21. Fun fact by feijai · · Score: 1

    The tags and attributes in HTML 1.0 were largely based on what Tim Berners-Lee could display using NeXT's Text class.

  22. Iffy work on next-gen-file-abstraction by Craig+Ringer · · Score: 2, Interesting

    The discussion of a replacement for the "file" abstraction seems a bit iffy. We've seen this before, many times, and it hasn't worked:

    1. Files are a low level SHARED abstraction agreed upon by ALL major plaforms in use. Like the use of the C interface to communicate between components in an executable (no matter what language(s) they're written in) it's going to stay dominant unless you can convince everybody to change to your new one.
    2. Because of (1), cross-platform data sharing will be much harder, and apps will have to support a conventional file format too. Especially for a niche platform that lacks the market power to force the new approach down everybody's throats.
    3. It's very much like the Apple Resouce Fork - a quite nice (if imperfectly implemented and historically limited) approach to enhancing files. ResEdit was amazing. Unfortunately, the resource fork is fading from use because it was always a royal PITA for cross platform work, and because portable apps can't rely on it.
    4. This is different to, say, Java's object serialization how?

    In short: it seems they're improving object serialization. Nice, but hardly revolutionary, and likely to introduce fun problems when interoperating with software relying on it.

    1. Re:Iffy work on next-gen-file-abstraction by PCM2 · · Score: 1

      # It's very much like the Apple Resouce Fork - a quite nice (if imperfectly implemented and historically limited) approach to enhancing files. ResEdit was amazing. Unfortunately, the resource fork is fading from use because it was always a royal PITA for cross platform work, and because portable apps can't rely on it.

      A little offtopic, but I never really understood people's love for the resource fork idea. Yes, separating out resources and metadata was a good thing and Apple was right to encourage that. But did doing so really require a filesystem that was completely alien to pretty much everything else on the market? Why couldn't Apple have just proposed a file format that packaged all that metadata at the end of the code or something? You could still have ResEdit; it would just read its data from the end of the file, instead of from a different place in the filesystem. All cross-platform problems would have been eliminated. Because after all, it's all just data on a hard drive anyway. Apple seemed to want you to think of resource forks as existing somewhere in Dimension X, instead of sitting right there next to your other data, which just seemed silly and needlessly complicating.

      --
      Breakfast served all day!
    2. Re:Iffy work on next-gen-file-abstraction by Craig+Ringer · · Score: 1

      The resource fork wasn't that out there - some UNIX file systems had supported streams for ages. That said, as a desktop OS concept it was pretty damn weird.

      I agree that it would've worked much better if it'd been implemented without relying on a file system level forked file concept. The same is true of the Mac file metadata (type/creator codes, etc), since both they and resource forks required quite a bit of annoyance to preserve across standard networks.

      Not all cross platform issues would've been eliminated, though. Do you see Apple publishing a portable C/C++ "resource fork" library and/or full specs and keeping it up to date? Me neither.

  23. GPL isn't the only game in town by cjwl · · Score: 1

    The Cocotron (cocotron.org) project aims to implement Cocoa in a cross-platform fashion and is under the MIT license.

  24. Urgh! by NoMaster · · Score: 2, Informative

    Urgh! Looks like an ugly version of a Gnome-ified WindowMaker/GNUstep. Granted, with GNUstep the underpinnings should be sufficiently NeXT / OS X like - but the 'G' part of the 'GUI' is fugly as sin and hardly Mac-like (with the exception of the 'taskbar at the top'), which doesn't bode well for the 'UI' part of the equation.

    (Note to developers: you should actually use and think about the UI you're trying to emulate. Even broad concepts, like level of menu depth and placement of functions/actions appropriate to their complexity, can make all the difference in the world. Not that Apple themselves aren't adverse to ignoring their own guidelines on these matters when it suits them...)

    --
    What part of "a well regulated militia" do you not understand?
    1. Re:Urgh! by antic · · Score: 1

      I'm with you, but wasn't sure if we were meant to be discussing the aesthetics or whether this was only a new project?

      Checked out the screenshots and it looks really ugly. Surely this is what an interface designer comes up with on their first, embarrassing attempt?

      --
      'Thats they exact same thing a banana wrench monkey.'
  25. It's like OpenStep by OrangeTide · · Score: 2, Informative

    The GNUStep project has been around for a very long time (been available since around 1991). Internally it is more like MacOS X or OpenStep, and therefor theoretically easier to port applications to this environment (or port GNUStep apps to OSX).

    I think what GNUStep needs is a lot more artists to draw some pretty icons and some people who are concerned with the front-end appearance rather than back-end compatibility and framework APIs.

    You mention "it's a typical, ugly Linux text experience to boot." .. but it's older than Linux kernel.

    --
    “Common sense is not so common.” — Voltaire
  26. Oh sure... by clang_jangle · · Score: 1

    ...but does it run Expose?

    --
    Caveat Utilitor
  27. Wow! by Caspian · · Score: 2, Funny

    It's like a Mac, but minus all the cool!

    *dodges Linux fanboys* Aieee!

    --
    With spending like this, exactly what are "conservatives" conserving?
    1. Re:Wow! by Joe+Tie. · · Score: 1

      5/5 for the "Mac-like" marketing etoile often gets, 0/5 for their not capitalizing on it by actually getting some artists on board. Keeping everything so square and gray will continue to ensure that few people will use it. Dislike for the look is one of the few things I've ever seen both kde and gnome folks agree about when it comes to aesthetics.

      --
      Everything will be taken away from you.
  28. not a good direction for Linux by oohshiny · · Score: 1

    Objective C is 1980's technology: it's a clever and useful extension of C, and its dynamic binding and typing are still convenient, but it's lacking garbage collection and runtime safety. Apple is addressing the garbage collection issue in Leopard, but there is still no runtime safety.

    Why does runtime safety matter? It matters because it makes software more robust and more secure. Without it, an error in a plugin or application can cause not only a crash, but also silent data corruption or data loss. Mac, Windows, and Linux achieve reasonable robustness only through extensive and costly testing, and crashes and data corruption still occur regularly on all three platforms.

    Of course, everybody still uses a lot of unsafe libraries, but Windows and Linux are moving away from it. On Linux, new code is increasingly written in languages like Python and Mono. In particular, a combo like Python with C extensions gives you an Objective-C-like object system (from Python) with C performance for compute intensive code, plus garbage collection and runtime safety.

    1. Re:not a good direction for Linux by tyrione · · Score: 1

      I suppose you don't know jack about Objective-C 2.0. Do yourself a favor and download the docs when OS X 10.5 is released. Or better yet, get a ADC Select license and study it.

    2. Re:not a good direction for Linux by Anonymous Coward · · Score: 0

      The early reputation of objective c of being slow was result of his support/use of the first garbage collectors that where at that time indeed very slow... not sure whats your take of that

      (object system + runtime safety + garbage collection) its the essence of Java. Mono? sure! supposedly... but, Python with C extensions (for compute intensive code)? Its in another very different league, probably Squeak or Oberon 2 are closer to fulfill the (object system + runtime safety + garbage collection) than Python + C

    3. Re:not a good direction for Linux by oohshiny · · Score: 1

      I suppose you don't know jack about Objective-C 2.0

      Only what has been publicly released, which indicates that Objective C 2.0 includes garbage collection but remains backwards compatible; that would make it an unsafe language.

      If Objective C 2.0 turns out to be a safe language and if someone creates an open source implementation, then it's a reasonable consideration. But if Objective C 2.0 turns out to be a safe language, then Etoile and Cocoa would have to be reengineered from the ground up to take advantage of that.

      I do hope Apple will fix Objective C and make it a safe language, because then we'd really have a decent alternative to C and C++. However, I wouldn't hold my breath.

      Do yourself a favor and download the docs when OS X 10.5 is released. Or better yet, get a ADC Select license and study it.

      Of course, I will look at it when OS X 10.5 comes out; however, as long as Objective C 2.0 remains a proprietary language that only exists on Macintosh, that's more of an academic exercise.

    4. Re:not a good direction for Linux by oohshiny · · Score: 1

      One more thing: Apple has explained what the enhancements for Objective C 2.0 are: modern garbage collection, syntax enhancements, runtime performance improvements, and 64-bit support. There is nothing in there about improving runtime safety. So, it's reasonable to assume that the only improvements to runtime safety that is in Objective C 2.0 are those related to garbage collection.

      If you have more information, maybe instead of name calling, you can share that with the rest of us.

    5. Re:not a good direction for Linux by oohshiny · · Score: 1

      The early reputation of objective c of being slow was result of his support/use of the first garbage collectors that where at that time indeed very slow... not sure whats your take of that

      Objective C has never used garbage collection until now, and Objective C has had one of the fastest method dispatches of any dynamic object-oriented language. The issue with Objective C has always been its lack of runtime safety, which is even worse than C. For example, nothing checks that the argument types for method calls are consistent across compilation units.

      but, Python with C extensions (for compute intensive code)? Its in another very different league

      Actually, Python with C extensions is not all that different from Objective C: it's a high level language (Python) integrated with a low-level language (C), just like Objective C is a high level language (Smalltalk subset) integrated with a low-level language (C). The main difference is that the high level language is more cleanly separated in Python/C than in Objective-C. (Python also gives you the option of closer integration with Pyrex.)

      probably Squeak or Oberon 2 are closer to fulfill the (object system + runtime safety + garbage collection) than Python + C

      Unfortunately, neither Squeak nor Oberon 2 are as practical or well-integrated. And I think Python is actually a nicer language and maturing technically (new object system, Pyrex, ctype, etc.).

    6. Re:not a good direction for Linux by iluvcapra · · Score: 1

      I find this matter tedious, but I feel compelled to defend the honor of the old girl Objective-C:

      • Objective-C will never be strictly typed, and while this lets people get into trouble at runtime, it allows you to build generics, like containers and arrays, as plain objects and avoids the C++ solution of using templates and macros. You can even load collection objects like arrays with objects of different classes.
      • I have walked past the end of an array/string in C, but never in Objective-C, since arrays and strings are objects and you are able to store things (like, say, the length) as ivars and you can use encapsulation to guard against de-referencing illegal subscripts. You occasionally still have to use old C-style arrays and strings, but rarely.
      • The problems we often cite with C and ObjC are really ergonomic; the language lets you do stupid things without waving a flag at you. Python, Ruby, Java will always be easier to program, but their "management" of the developer's experience (which is really all it is) will always cost cycles. As the CPUs get faster it matters less and less, though I doubt an embedded device like, say, an iPhone could efficiently use GUI apps written in Python.
      • Ditto any process that's watching the clock, like, say, audio. If you built an OS that mandated third party devs used Python or Java, that OS would never be able to support realtime audio processes written by third party devs (aside from what the OS vendor provides you, and why are THEY so much better at writing C than YOU?). This issue would go away if someone wrote an interpreted language that was realtime-savvy, but I've never seen it.

      For context: Mac OS X 10.5 will not feature a managed or "safe" ObjC, but XCode will support bindings into Cocoa for Python and Ruby. You can already develop using these using PyObjC and RubyCocoa. I personally think this whole "safe language" business is some sort of connector conspiracy to give the OS/runtime vendors ascendency over the CPU vendors ("Don't write for Wintel, write for CLR!"). Why don't we all just go back to LISP?

      --
      Don't blame me, I voted for Baltar.
    7. Re:not a good direction for Linux by blankaBrew · · Score: 1

      UNIX is 1960s technology.... so what does that mean? The year a software product began development is irrelevant. The quality and throught they put into building a rock solid foundation are what matter. OpenStep/Cocoa and Objective-C are as rock-solid as the UNIX that it runs upon. Things like garbage collection, which have been added to Objective-C 2.0, are not critical to a good development platform, are mostly there for noobs IMHO (with the exception that it can be useful for highly threaded apps), and can always be added at a later date. The critical part of a development environment which must be there from day one is the development model and philosophy of the platform. That is where Cocoa and Objective-C shine, and that is why every cocoa developer that I know loves it.

    8. Re:not a good direction for Linux by oohshiny · · Score: 1

      Objective-C will never be strictly typed, and while this lets people get into trouble at runtime,

      The issue is not that Objective C is dynamically typed, the issue is that it is an inherently unsafe language. Smalltalk, for example, is dynamically typed, yet Smalltalk is safe.

      The problems we often cite with C and ObjC are really ergonomic

      Yes, of course, that's all type systems are about: preventing stupid human mistakes. You know, the kinds of mistakes that cause most of the security holes, crashes, and data corruption that we experience day-to-day on our computers. If programmers were perfect, we wouldn't need type systems.

      If you built an OS that mandated third party devs

      I didn't say anything about "mandating". Objective C could be a safe language with an explicitly unsafe C subset that is there when you need it (kind of like Mono). Instead, Objective C is a language that is, quite unnecessarily, unsafe throughout.

      I personally think this whole "safe language" business is some sort of connector conspiracy

      No, it's a conspiracy by users who are tired of buffer overflows and crashes. I use a Macintosh and Apple's own applications crash and hang regularly. (The fact that Microsoft is attempting to use C# to dominate the industry is unrelated to the fact that C# is a well-designed, safe language.)

      Why don't we all just go back to LISP?

      Mostly because Lisp isn't widely used and doesn't fit well with what mainstream programmers know.

      The obvious choice for Apple would be to make an aggressive move to Smalltalk, which Objective C programmers should feel comfortable with and which easily integrates with existing Objective C libraries. It would also be a big improvement on XCode and AppleScript. They can probably pick up a Smalltalk vendor cheap.

      For context: Mac OS X 10.5 will not feature a managed or "safe" ObjC

      And that is precisely why Objective C and GNU Step are bad choices for Linux, which is what all of this is about.

    9. Re:not a good direction for Linux by oohshiny · · Score: 1

      Things like garbage collection, which have been added to Objective-C 2.0, are not critical to a good development platform, are mostly there for noobs IMHO

      I use a Mac, and I think I have managed to crash just about every piece of software Apple ships: the Finder, Dashboard, Keynote, Address Book, Mail, the kernel, System Preferences, Safari, etc. Evidently, Apple must be populated by noobs that simply can't produce software in Objective C that at least gracefully recovers from errors without data loss.

      Of course, I don't blame them: I can't either, and I frankly doubt you can.

      OpenStep/Cocoa and Objective-C are as rock-solid as the UNIX that it runs upon.

      You mean that unless you spend many man-years for testing each release, you get software that is full of buffer overflows, data corruption, and crashes? Yes, I quite agree.

      The critical part of a development environment which must be there from day one is the development model and philosophy of the platform.

      The philosophy of Objective C has been to provide a stripped down version of Smalltalk with easy interfacing to native code. It was a nice idea but a flawed execution, and it hasn't been updated or fixed in the last 20 years.

    10. Re:not a good direction for Linux by iluvcapra · · Score: 1

      We are talking about different things, but I think we can digress on this with some profit.

      I think you're saying "safe" languages are better for application programming, which is fair. However, I would say that safe languages, in the end, have the effect of keeping you, the developer, away from the hardware. If you code in a safe language, you are denying yourself access to the CPU instructions, registers and memory of your hardware platform, which is a good thing if you're ignorant of such things, but in the end can keep you from writing the most optimal or fastest code on the platform.

      You say there's no mandate of safe languages on platforms, or rather that you wouldn't argue for it, though I can't help but see such a thing as the end of the safe language argument. Microsoft already has people keywording blocks as "unsafe" in Managed C++, with the goal of requiring either a user authentication and/or code signing to allow these blocks to execute. If you can't write a program that can peek outside of its own allocation, how do you pick the lock on MS's private APIs, or write a debugger that actually tells you the state of your actual MACHINE, and not the virtual one the OS vendor has you running in? The answer is, you don't.

      "Safe languages" are about conferring the right of writing for the hardware to the runtime vendor, and restricting the application vendor to a walled garden of services. This is acceptable if your runtime is OSS, like Python or Mono (we'll just see how the legal stuff all pans out on that one), but not if you're writing for the other 98%.

      Those programmers who would trade a little bit of freedom for a little bit of safety deserve neither.

      --
      Don't blame me, I voted for Baltar.
    11. Re:not a good direction for Linux by oohshiny · · Score: 1

      However, I would say that safe languages, in the end, have the effect of keeping you, the developer, away from the hardware. If you code in a safe language, you are denying yourself access to the CPU instructions, registers and memory of your hardware platform,

      A safe language doesn't mean absence of unsafe features, it means that, unless the task actually requires it, you can stay entirely in the safe subset of the language, and that if you use unsafe features, their use is lexically apparent.

      which is a good thing if you're ignorant of such things, but in the end can keep you from writing the most optimal or fastest code on the platform.

      You are absolutely right that I am ignorant of such things: after 25 years of C and assembly language programming and lots and lots of benchmarking and optimization, I have no idea what kind of C code will actually run fast on a particular compiler/CPU combo anymore because it's pretty much impossible to predict given the wide variety of compilers and architectures that exist. People who think they can are too inexperienced to know better.

      That's why the correct strategy is to leave the low-level optimization to a compiler (preferably a JIT) and CPU-specific hand-crafted libraries, and to use a language that makes it easy to focus on high-level optimizations like good data structures.

      C is exactly the opposite: C compilers can't do many obvious optimizations due to C's semantics, and creating good data structures in C is a royal pain.

    12. Re:not a good direction for Linux by quanticle · · Score: 1

      However, I would say that safe languages, in the end, have the effect of keeping you, the developer, away from the hardware. If you code in a safe language, you are denying yourself access to the CPU instructions, registers and memory of your hardware platform, which is a good thing if you're ignorant of such things, but in the end can keep you from writing the most optimal or fastest code on the platform.

      Argh! I am so sick and tired of hearing this argument used to defend unsafe languages and programming practices. Face it: CPU instruction sets these days are not really optimized for you, the programmer. They're optimized for your compiler. Unless you're writing a compiler, you have very few reasons to be getting that close to the hardware.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
  29. NouveAUX by ChristTrekker · · Score: 1

    I've often wondered what it would take to write a generic library for placing X11 menu bars at the top of the window.

    1. Re:NouveAUX by Anonymous Coward · · Score: 0

      Probably not possible for all 'X11 menu bars' (no such thing, as far as I'm aware; dependant on the GUI toolkit), but such a feature has already been available in KDE for quite some time now. Unfortunately, it only works for applications using KDElibs; even applications written with plain Qt don't work with it.

      Now, if someone could extend that so it works with plain Qt apps and perhaps even GTK ones, then it might be viable for everyday use.

    2. Re:NouveAUX by Anonymous Coward · · Score: 0

      Pointless.

      KDE can do that, but it's pointless.

      The point of OS X's menuing is **not** that it in any particular location, but that it is **per application** not per **Window**. The menus could just as well be detached - as they were on NeXT - and that would probably be a better way of doing it on OS X with the size of some screens today (anything up to 30in).

      This gives some insight into why you would want menuing to be per application - and why that can't be done if your architecture doesn't permit it.

      The Target-Action Paradigm:

      http://rixstep.com/2/20050529,03.shtml

    3. Re:NouveAUX by Misagon · · Score: 1

      There is no such thing as an "X11 menu bar". Menus are implemented by various "tool kits" on top of X11, and only a few of them allow the menu bar to be there, each toolkit being incompatible with the other (of course).

      --
      "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
    4. Re:NouveAUX by ChristTrekker · · Score: 1

      I was imprecise, but I think most everyone understood what I was talking about.

      My question remains, how much work would it take to create a cross-toolkit API and library so that menuing could be (optionally) separated from the window? I am not a GUI developer. I don't know how much commonality there is to menuing in different toolkits, but I'd think there would be a lot.

  30. Can we get away from WIMP? by Stu22 · · Score: 1

    The WIMP model has served us well, but if you told me I would never have to deal with a window, menu, or a pointer again I would be the happiest person in the world.

    If open source wants to innovate, can we get away from little floaty things that you move around on the screen? Right now you're thinking "what else are we going to use?" Interfaces could have gone in a different direction, I don't completely know or understand what the other direction would be, but there HAS to be something better than these little floaty things.

    OLPC has done a good job with it, second and third world kids are going to have a leg up on us because their interfaces have done away with all the annoying crap we have to deal with. Can we please have something that doesn't "take advantage of" all the interface advancements from the 1980s that we deal with on a day to day basis?

    Am I asking too much? Maybe, but I want something better and I know you do too.

    Also, ponder this without trying to find a solution: Would you be elated to find out you never have to see another window again? I know I would, and I would be happy to not have to see another pointer again in my life. The solution is obviously not easy. It will require great minds and years of research.

  31. Maybe, but why? by Onan · · Score: 1


    You don't seem to have described any actual problems that you perceive with a windowing paradigm. You assert that there must be some other metaphor, but you don't say anything about the ways in which it would be beneficial for that metaphor to differ from this one. You assert that you want something "better", but don't say anything about what would be better about it or what is currently lacking.

    You can't find a solution without understanding what the problem is.

    1. Re:Maybe, but why? by ardor · · Score: 1

      There are certain problems with WIMP.

      First, overlapping windows are often undesirable, users either maximize the current window or tile them. An exception are dialogs, which obviously cannot be tiled. (Toolwindows CAN be tiled, however.)
      It matches the design principle of an application's GUI: there, no widgets overlap, they are tiled, and/or organized into tabbed groups.

      With the advent of large screens (and multi-monitor setups) tiling window managers like ion or wmii become more interesting. Now, something like a tiling KDE would be fine. (Exception to the tiling: dialog windows of course.) Automatically rearranging windows works well in ion, and would be a nice experiment in KDE's kwm.

      Then, there is the fact that GUI applications often rely too much on mouse input. The mouse should not be overused, as the user can enter input much faster via the keyboard. Its the input *volume* that often speaks against the keyboard (like, typing this 30-char-filename instead of simply clicking it). Also, the mouse is obviously the input method of choice for 2d input (drawing without the mouse?). But, observe this website for example. Try posting something without using the mouse, ever. It is doable, but easier with the mouse.

      Editors are a good example of where the mouse is often overused. Ideally, one never has to use the mouse for editing. vim and emacs shine here, but they have an awful learning curve, because it is hard to grasp all those commands at first. Editors like joe do it better for starters imo. In joe, the right upper corner contains the hint "press Ctrl-K H for help". You press that, and a quick summary appears. Perfect! One is not lost like in vim or emacs, yet the mouse is not necessary.

      --
      This sig does not contain any SCO code.
    2. Re:Maybe, but why? by TeknoHog · · Score: 1

      Good point. I've found that I don't have a problem with windowing systems per se, but with all the extraneous crap that goes with Windows-style GUIs. I think plain window managers like Fluxbox, with virtual desktops, are great for organizing work and managing multitasking. (I also use screen, the equivalent of VDs for the command line.)

      On the other hand, desktop icons, menus and panels are in the way of focusing on the actual work. I like to manage my files in the unix style, instead of thinking they are stored inside the monitor. I also find many graphical, windowed applications necessary, and while working with them, I don't want to see anything else on the screen but the relevant application windows. Depending on the work, I may want to use a few applications at once, so the basic idea of windowing is useful.

      The great thing with computers is that they help you manage enormous amounts of data, much more than you can visualize otherwise. The Windows way seems to be that, in order to be easy to use, all the data and applications must be visible all the time. It either becomes very messy, or very limited in function. Good user interfaces let you hide other things and focus on a few things at a time, and virtual desktops are one thing that helps.

      --
      Escher was the first MC and Giger invented the HR department.
    3. Re:Maybe, but why? by Anonymous Coward · · Score: 0
    4. Re:Maybe, but why? by spitzak · · Score: 1

      Have you ever been able to try a system where clicking in the window does not raise it? I believe this is the main reason "overlapping windows are not usable" as you say. Older X window managers did not raise the windows unless you clicked the title bar (see fvwm for example), and many programs were created that used many overlapping windows (FrameMaker and Gimp for instance). These were much more usable then than they are today, due to modern Linux systems insisting on copying Windows "click raises window" behavior.

      I agree that some new ideas need to be done, but they may not be as dramatic as you think. Primary "innovations" I would like to see are:

      1. Get rid of click-raises-window and let the application decide how to stack it's windows. This is easily done on X now, but as long as it is optional it is useless as no program can take advantage of it. (notice that on a click THE APPLICATION CAN RAISE ITSELF. It is NOT a change in user interface, only a change in implementation! Any arguments about whether this is user friendly or not are IRRELEVANT!)

      2. Get rid of titlebars and all other decoration on the windows. The application should be responsible for drawing every pixel in it's window and responding to all mouse clicks, including raising, moving, and resizing itself. This will stop the lock-in to current ideas about window manipulation and allow much more freedom in use of screen space.

    5. Re:Maybe, but why? by Stu22 · · Score: 1

      Those seem like small details of a larger problem to me. It's hard to realize the problems with the status quo until it has past.

      I would like to see a system with applications that fill the height of the screen and expand themselves horizontally to take up as much space as they need. You could then scroll your applications horizontally to switch between programs, reorder them and lock apps to the sides of the screen. Alt-tab would be great, it would just be a picture of all your apps.

    6. Re:Maybe, but why? by argent · · Score: 1

      First, overlapping windows are often undesirable, users either maximize the current window or tile them.

      I only typically find myself maximizing on small screens (less than 1024x768), or in UI environments that encourage tiling (Windows). On X11 or OSX I typically have a cluster of tiled Xterms, yes, but with other application windows overlapping all over the place. On X11, the window I'm working on often has other application's windows hovering over it, unfortunately Apple doesn't let you do that.

      It's a shame that Apple's unable to get away from the click-to-focus/raise-on-focus model. I much prefer focus-follows-mouse and explicit-raise. If someone would come up with a hack to make the menu bar just a place to dock menu extras, and attach menus to the title bar of the application (but not the way NeXT did it, keep it a *bar*) or make them come up under the mouse (Fitt's Law notwithstanding... the easiest place to move the mouse to is where it already is!)... then you could change the focus and raise behaviour...

      The other thing that I find useful is to make my windows slightly (maybe 10%) transparent, so I can see changes beneath them. So the window in the back with a download progress in it isn't actually hidden by the one in front. Extending this to real 3d is an obvious next step.

  32. No, this is oblig. :) by Anonymous Coward · · Score: 3, Funny


    Slashdot 29 July 2007: Sun Says Project Indiana is Not a Linux Copy - yeah right!

    Slashdot 30 July 2007: Etoile Project Releases Mac-Like Environment

    Slashdot 31 July 2007: Mac OS-X is the most copied OS on planet - copying is the highest form of flattery.

    So, Solaris copies Linux, Linux copies Mac OSX, but nobody is really interested in Vista.

    1. Re:No, this is oblig. :) by snoyberg · · Score: 1

      So does that have any bearing on BSD, seeing Darwin is just a fork on the OpenBSD kernel?

      --
      Thank God for evolution.
    2. Re:No, this is oblig. :) by FLAGGR · · Score: 1

      1. It's not a fork of the BSD kernel you tool, it's Mach + I/O Kit, with the BSD userland 2. OS X != Darwin

    3. Re:No, this is oblig. :) by snoyberg · · Score: 1

      So I was mistaken about Darwin, but my point remains: Max OS X is built around BSD (by your own admission, simply the "BSD userland" instead of the kernel). I'm simply pointing out the fact that Apple is also just "copying someone else." It's not like Apple is the master copy of all things computer and Linux and Friends are simply playing catch-up.

      --
      Thank God for evolution.
    4. Re:No, this is oblig. :) by jedidiah · · Score: 1

      You are incorrect.

      WE started "copying" OpenStep first.

      Apple just brought their clone of OpenStep to market sooner.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:No, this is oblig. :) by 4D6963 · · Score: 1

      Slashdot 29 July 2007: Sun Says Project Indiana is Not a Linux Copy - yeah right!

      Slashdot 30 July 2007: Etoile Project Releases Mac-Like Environment

      Slashdot 31 July 2007: Mac OS-X is the most copied OS on planet - copying is the highest form of flattery.

      Slashdot 32 July 2007: Netcraft confirms it: Apple is not dead.

      --
      You just got troll'd!
  33. UI customisation and preference by fadilnet · · Score: 1

    I've never used a MAC but have tried the various UI customisation packs available (for fun and because I was bored). I don't think that Etoile should be taken as a Mac-like Environment but more like a Mac UI customization package. Think of it this way - the new dock in KDE4 is supposed to be compatible with Mac Widgets. That's nice. See, I can run the Mac widgets on KDE. That's a plus. Can I edit the preferences of KDE to make it Mac-like? Sure! Why not let the user decide how the UI will be? Major distros may add Etoile amongst the myriad of other UI 'tools' - Metisse. As far as the UI menus, and way to fill the screen go, I prefer Windowmaker and GNUstep. I minimise my windows, stack them on top, have some apps docked, and xterm always open. It's clean. Some may prefer Mac-like UI or Windows-like UI. That's the beauty of opensource and Linux -> you've awesome projects going on, and you've the CHOICE of customising your UI. (ok, I may have repeated myself in the above statement. *going to try Etoile now*)

    --
    Do I require the c-sig package to have a signature?
  34. Console.app/Event Viewer by Savage-Rabbit · · Score: 1

    As for "... didn't even bother putting any UI components in to help you diagnose what the problem is", again I don't really see your point. It's UNIX. It has logs. Use them. If you want pretty UI-based logs, then open up the console application, and you can see all the logs in a nice pretty format. Personally I prefer grep. That's true, It's amazing how many people don't seem to know that the OS X log viewer exists. One can find it here: /Applications/Utilities/Console.app. To draw a parallel, the Console.app serves a roughly similar purpose as "Event Viewer" in Windows (Start->Control Panel->Administrative Tools->Event Viewer). Personally I feel the OS X logs are somewhat less cryptic than the ones in Windows but that's probably just because I don't have much experience with debugging Windows since I haven't used it seriously for almost a decade except occasionally having to work with Windows 2003 servers (at work). The Console.app gives you access to all, or at least most the OS X system logs although much of the time the console log and the syslog are enough to diagnose a problem.
    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
  35. Someone help me out: What's the point? by Qbertino · · Score: 1

    I don't get it. Mostly. I do get the one Font manager I'm seeing on one screenshot. Looks like it's using some *Step/*Maker/*Box WM toolkit. Anyone with more details on that? If this is their baby, then they desever big kudos for that alone. Font management still is underrepresented in the Linux world.

    However the rest just looks like an inconsistent WMaker/*Step theme with an XFCE bar at the left. Or is there more to it than meets the eye? Some underlying feature laden super framework that will make this WM the new fluxbox? The last WM hype I remember was fluxbox - it introduced some cool new features and effectively displayed that there is room for improvement in the WM space (and that WM project websites needn't look like a pile of shit). Thus Fluxbox is my prime choice for small-footprint WMs.

    What's with this one that could make it the new fluxbox? Maybe someone with the project could provide some insight on it?

    --
    We suffer more in our imagination than in reality. - Seneca
  36. +10^100 super-effin'-ultra-über insightfull!! by Qbertino · · Score: 1

    Well said indeed.

    (apart from the opening insults maybe - allthough they're understandable)

    --
    We suffer more in our imagination than in reality. - Seneca
  37. Uh No by CelticPirate · · Score: 0

    I have seen Gnome look more like any version of OSX than this.

  38. It's all about GNUStep by Tony · · Score: 2, Insightful

    A window manager is not a desktop environment; it is but one part of a desktop environment. GNUStep is an implementation of OpenStep, an open API that is based closely on the old NeXTStep environment from the old NeXT computers.

    GNUStep is a decent implementation, though it's slow in development. It is based on Objective-C, which is (in MNSHO) a much better OO language than C++, Java, or C#. The foundation libraries are a little primitive by modern standards, but pretty clean and powerful nonetheless.

    The window manager is the least of the operating environment.

    --
    Microsoft is to software what Budweiser is to beer.
  39. I don't want real state by Wooky_linuxer · · Score: 1

    When I have a 24" iMac. I want to know at a glance which commands are available for each of the apps that happen to be opened. Heck, I want to do that even in my 13,3" Macbook screen. I do understand that having an infinite width makes it easier to hit - but I am proficient enough in hitting my menus, thank you. Give me the option at least, some people who are power users will be happy, and the rest can use the easier default. I like my Apple machines, but I'd really love if Apple didn't oversimplify things all the times.

    --
    Where is that guy who'd die defending what I had to say when I need him?
  40. Re:OSS == copycats by Anonymous Coward · · Score: 0

    I haven't seen the compiz cube virtual desktops on a comercial offering.

  41. Just another by IwantToKeepAnon · · Score: 1

    Mac-like fanboy

    --
    "Happy families are all alike; every unhappy family is unhappy in its own way." -- Anna Karenina by Leo Tolstoy
  42. Tog sez... by mojoNYC · · Score: 1
    However, you are neglecting the other parameter: if the width of the target is infinite, then the distance to its center is also infinite

    semantical difference--'infinite' in this context means the far edge of the target, ie. the window/screen, so that when you 'throw' your mouse at it, it can only go so far. therefore, the idea of the 'distance to center' is a misnomer, imo. perhaps I didn't read closely enough?

    I'm surprised nobody's mentioned Bruce Tognazzini in this post, the orginal Apple Human Interface guru, and popularizer of Fitts' Law in the UI world: A Quiz Designed to Give You Fitts

    1. Re:Tog sez... by Curien · · Score: 1

      I'm no expert on Fitts' law (I only just heard about it from the guy I was responding to earlier), but the two key parameters are the distance from the starting point to the center of the destination object and the width of the destination object in the direction of motion. In particular, the important number is their *ratio*. This makes sense -- the farther away an object is, the longer it takes to get there, and the larger an object is, the less time you have to spend making precision adjustments.

      So the question becomes, "What do you do in the edge case of a border object?" (pun intended) My solution is that the ratio converges to 1 for the average case because (as I said earlier), thinking of the width as "infinite" is actually incorrect. Rather, no matter how far the pointer was "slung" past the edge, the time taken to sling it is equal to the amount of time it would have taken to reach an object as wide as the distance slung.

      --
      It's always a long day... 86400 doesn't fit into a short.
  43. It's about time! by argent · · Score: 2, Insightful

    Making something "cool" around GNUstep is something I've been hoping would happen for some time.

    Objective C is not the best OOPL, and NeXTstep is not the best class library, but the competition that's actually got wide use is so appallingly bad that they shine like costume jewelry in a pile of muck. Being able to write code that will compile and run natively on OS X and X11 polishes it up a treat.

    The looks and theme aren't the point. NeXTstep was awfully drab too but it developed a devoted following not because it looked cool, but because it worked well and consistently across all applications, and that was a result of the language and libraries as much as Steve Jobs' legendary attitude.

    1. Re:It's about time! by pschmied · · Score: 1

      You, sir, get the prize for possessing a clue. Well said. GNUStep suffers because nobody makes cool stuff with it. Everything else suffers because they are using lesser frameworks :-)

      I also agree with your assessment of ObjC / Cocoa as a technology. In terms of object orientation, Objective C isn't the best OOPL. Smalltalk, for one, seems like a marked improvement. Ruby and Python probably are too. But Objective C is still C. Interfacing C and C++ with ObjC / ObjC++ is much easier (and probably more elegant and robust) than many of the C-to-$FOO bridges that exist. So, in my estimation, ObjectiveC is nice because it combines a nice object model with the unbeatable compatibility of C. And the classes are a damn-sight better than the vast majority of the competition.

      Cheers,
      Peter

  44. That's exactly what it isn't. by argent · · Score: 1

    I've never used a MAC but have tried the various UI customisation packs available (for fun and because I was bored). I don't think that Etoile should be taken as a Mac-like Environment but more like a Mac UI customization package.

    In fact that's exactly what it isn't. Not only can you not get a "mac-like" environment by changing the details of the UI, you can't even really get a "windows-like" environment that way... despite both KDE and Gnome borrowing so much from Windows. To get a real NeXT/Mac environment you need your applications to use GNUstep, so they inherit everything from Services on down from it. And to do that, you need people using it so there's a demand for it, and for that, you need someone to package the whole thing up in a cool and friendly way.

    Which is where Etoile comes in.

  45. What I want to know is how flexible is WildMenus? by argent · · Score: 1

    The one thing that's always bugged me about the Mac and about NeXTstep is the way they make a fetish of making menus hard for the user.

    Apple sticks the menus up at the top of the screen like we were all still on 9" Compact Macs. On a 30" monitor, or with two monitors, it's frustrating.

    NeXTstep made the menus a vertical box that looked like another window and had all the charm of Apple's other bag-on-the-side-of-a-winow interface, the shelf.

    Neither is ideal. I'd like to either make them a context menu on the title bar, or something like a menu bar on the window edge (one that can be dragged to any edge).

  46. Can you say Garage Band? by bandmassa · · Score: 1

    When Audacity has the power of Garage Band (looping is still in the 1990s in Audacity), I'll make the jump to Linux and run it on a Medosin Celebrity ;-) Until then, sorry, Apple's got me by the balls.

    --
    "I hope you like Guinness, Sir. I find it a refreshing substitute for, er... food." Col. Jack O'Neil, SG-1
  47. A semiplane is infinite! by Nicolay77 · · Score: 1

    They are NOT "infinitely large". If they were infinitely large, then you wouldn't have to move the mouse *at all* to click on them. Calling them "infinitely large" just confuses people who know what the words "infinite" and "large" mean.

    A semi-plane is as infinitely large as a plane. It follows easily by relating Descartes and Cantor theories.

    If my mouse is outside that semi-plane I would have to move the mouse to click on it, and it would still be infinitely large.

    That's for illustrating the concept. Screen borders are more like infinite rectangles with three sides, and screen corners are like quadrants on a plane (not so sure on this). Still as infinite as a plane (you can make the Cantor-correspondence just as easily as with a semiplane).

    --
    We are Turing O-Machines. The Oracle is out there.
    1. Re:A semiplane is infinite! by Curien · · Score: 1

      Holy christ, do you even bother to read threads before you post in them? That was discussed and resolved DAYS ago. But thanks for trying.

      --
      It's always a long day... 86400 doesn't fit into a short.
    2. Re:A semiplane is infinite! by Nicolay77 · · Score: 1

      There were too many responses without a descriptive subject. Too many plus signs to choose. The first ones I read where about something else entirely.

      That's why I used a descriptive subject.

      --
      We are Turing O-Machines. The Oracle is out there.