Slashdot Mirror


GNUstep 0.6.5 freeze

teferi writes " The GNUstep project, a GPL'ed implementation of the OpenStep environment, has gone into a code freeze for the 0.6.5 release. The base library is 94% done, and the various parts, including the DPS/DGS graphics backend are coming along well. "

95 comments

  1. wmaker? by lubricated · · Score: 1

    is the gnustep project just window maker or is it more? Can anyone enlighten me on what else the gnustep project has done.

    --
    It has been statistically shown that helmets increase the risk of head injury.
    1. Re:wmaker? by jcr · · Score: 4

      GnuSTEP aims to re-implement the entire OpenStep spec under GPL. When this is done, you can expect about 200 NeXT apps to suddenly appear on Linux, FreeBSD, etc.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    2. Re:wmaker? by Anonymous Coward · · Score: 1

      GNUStep is not a window manager at all. GNUStep is like Java, it's a core fully Object Oriented language plus a complete set of foundation classes. Only in the case of GNUStep, the core langauge (Objective-C) kicks but (not that java isn't cool, but Obj-C rules) and the foundation classes actually make sense. It's by far the best development environment on the market today.

  2. That's great... by Mr.+Piccolo · · Score: 2

    but where are the applications?

    There's like maybe two that have been released. Having the library is great, but if there's no real use for it, no one will care.

    I don't know if there are very many open-source NeXTSTEP apps out there either.

    --
    Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
    1. Re:That's great... by QuMa · · Score: 2

      I think afterstep uses it. It puts it's preferences in ~/GNUstep, so...


      BTW, if you don't use afterstep: It's real nice, try it!

    2. Re:That's great... by Anonymous Coward · · Score: 2
      Well, no.

      Afterstep is a window manager. it could put its prefs in ~/Windows98, but that wouldn't make linux a microsoft product.

      Windowmaker is the official GNUStep Window Manager (and also the official GNU Window Manager), and has a look/feel more reminiscent of NeXTs.

    3. Re:That's great... by Anonymous Coward · · Score: 3

      Where are the applications?

      Very simple.. Once GNUstep is 100% done, it should
      require little effort to port tons of NeXTSTEP/OPENSTEP/MacOS X
      apps to GNUstep... The process is already on its way to port
      some of those.

      Not to mention the fact that ProjectCenter.app, once completed, will
      provide a really nice environment to create new GNUstep apps with
      a minimum of effort. (kinda like Steve Jobs demonstrating how to
      create a word processor in 5 minutes using NeXSTEP's ProjectBuilder.app).

      The final word is that the applications are just around the corner...

      Cheers.

      This is AC of Borg.
      Accounts are futile;
      Trolls are irrelevant.
      You will be slashdotted.

    4. Re:That's great... by smart2000 · · Score: 1
      but where are the applications?
      Isn't that what people used to (and still) say about Linux? The fact is that it's a great API, and as it get's better more and more people will release it.

      There's like maybe two that have been released. Having the library is great, but if there's no real use for it, no one will care.
      There is a real use for it. We use it internally to deploy apps that were originally written for OpenStep. Most current OpenStep developers are survivors of the great MCCA purge, and as a result, commercial apps aren't their highest priority or best focus. I

      I don't know if there are very many open-source NeXTSTEP apps out there either.
      Many NeXT apps were released as OpenSource before the term was invented. You can find some of the latest and greatest on StepWise, or on ftp.peak.org.

      --
      To purchase it is not like spending money but rather it is an investment in the future in a blow against the empire
    5. Re:That's great... by lintux · · Score: 1

      > Windowmaker is the official GNUStep Window Manager

      What? Shouldn't that be Enlightenment? Since that's the official GNOME (GNU Network Object Model Environment) window manager?

    6. Re:That's great... by asullivan · · Score: 1

      No. AfterStep is an X window manager. The GNUstep/* hierarchy is part of the specification of GNUstep, so AfterStep aims at conforming to that standard. AS has not been officially accepted as a GNUstep window manager. There was some attempt during the 1.6.x releases to get authorization as a GNUstep window manager; I have not heard any reports of success.

    7. Re:That's great... by Mr.+Piccolo · · Score: 1

      You can find some of the latest and greatest on StepWise, or on ftp.peak.org.

      So _that's_ where they've been hiding all the time! ;-)

      I wish the GNUStep page had a link there.

      Also, peanuts.org seems to have a decent selection...

      --
      Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
    8. Re:That's great... by Ian+Bicking · · Score: 2
      Ironically, while Window Maker is part of GNUStep, it doesn't use any of the GNUStep functionality, being written entirely in C (not Objective C). I guess this was done because the author (Alfred Kojima, I think) wanted to make it functional apart from GNUStep, and before GNUStep -- both of which have been accomplished.

      But as a result, it's only a matter of policy that Window Maker is part of GNUStep, while I imagine the rest of GNUStep will be connected at more of an architectural level, being based on Objective C, the Foundation libraries, and all that.

    9. Re:That's great... by Ian+Bicking · · Score: 1
      Well, Enlightenment isn't actually the official GNOME windowmanager -- it was the de facto standard for a while, but even that has changed as (it seems) Raster has been moving away from GNOME and in his own direction.

      But, those things aside, GNOME and GNUStep aren't really related, even though they are both sponsered by GNU. GNOME was a reaction to KDE/Qt, and demanded much shorter-term success. GNUStep, because it was ambitious and a little monolithic, took a long time to get to a usable point. It actually preceded GNOME by several years, but development languished while the core developers worked on the basic functionality -- essentially writing the standard library for Objective C.

    10. Re:That's great... by Anonymous Coward · · Score: 0

      AfterStep (AS) tries to emulate some of the looks of NeXT while GNUstep want's to do a lot more. Afterstep is mainly an improved version of FVWM so many old-fashioned people prefer AS to WindowMaker.

    11. Re:That's great... by QuMa · · Score: 1

      It *could* put the prefs in ~/windows98, but it doesn't. Because it would be illogical. And since most of the rest of AS is logical, I'd assume this part is too.

    12. Re:That's great... by hoss10 · · Score: 1

      If someone wants an app, they should write it themselves. That's the point of the GosPeL surely!

  3. NEXTSTEP / Mac OS X relationship? by Erich · · Score: 3

    What is the relationship between NEXTSTEP and the new MacOS X? If the OpenSTEP project is successful in making a NEXTSTEP-compatable system, would it be trivial to compile the new MacOS stuff to run under it?

    --

    -- Erich

    Slashdot reader since 1997

    1. Re:NEXTSTEP / Mac OS X relationship? by Anonymous Coward · · Score: 1
      Yes, the Cocoa level is basically OpenStep. MacOS X still supports a subset (99% or so) of the original Mac toolbox (API), so only Cocoa (OpenStep) apps could easily be ported/recompiled for GNUStep. As always, it may involve some work, depending on what assumptions the programmers made, etc.

      MacOS X Server looks very much like a NeXT with more macish controls, though, if you;ve ever seen screeenshots of it.

    2. Re:NEXTSTEP / Mac OS X relationship? by smart2000 · · Score: 5
      Mac OS X has several programming interfaces, one of which is called Cocoa. Depending on what you combine with it, this is also similar to OS X Server, Rhapsody, Yellow Box, OpenStep and NeXTSTEP.

      NeXTSTEP (an operating system) was first, and had a damn good programming model, but originally only ran on NeXT's hardware.(which was pretty sweet, but also pretty expensive) (and also one version on RS/6000, running on AIX, again fast, sweet and expensive.).

      NeXT then began making moves to dump hardware and make NeXTSTEP available on Intel hardware.

      Right around that time, they also started development on OpenStep, which has a very similar object hierarchy to NeXTSTEP, but uses a better object allocation model, and has renamed many methods to make the API "cleaner".

      To move an application from NeXTSTEP to OpenStep, you ran a series of scripts that would convert to the new API.

      OpenStep was made to run on several OS's including Solaris, Mach (from NeXT), HP/UX and Windows. OpenStep meant two things at the time, both the API and the NeXT delivered operating system as a whole. One was called OpenStep, and the other was OPENSTEP. You guess which was which.

      Any ways, Apple bought NeXT so that the NeXT management team could take over Apple, and now all that API is part of OSX Server and soon OSX.

      It is easy to move a program from NeXTSTEP to OpenStep or OSX Server. I moved Xox, an arcade style shooter with a few days of work.

      It is trivial to move the average program from OpenStep or OSX Server to GNUstep. In many cases the same code compiles on both.

      We moved our entire development over to GNUstep, and haven't looked back yet. We found the Foundation kit to be more stable than Apple's and easier to explore.

      --
      To purchase it is not like spending money but rather it is an investment in the future in a blow against the empire
    3. Re:NEXTSTEP / Mac OS X relationship? by um...+Lucas · · Score: 1

      Nope. Anything with a GUI will need to at least have that reworked. NextStep used Display PostScript, I assume that GNUStep is using GhostScript, and MacOS X is using... damn! I forgot it's fun name. But while *Step is postscript based, MacOS X's display is PDF based. That plus NextStep and OpenStep have basically been abandoned for the past few years in favor of OS X, which means that there's lots of enhancements out there that aren't even on the list to be reimplemented.

      What'd be nice is if Apple realized that as soon as OS-X consumer is out, NextStep and OpenStep are basically completely dead products. Even if they didn't release all the source (which wouldn't be happen because of license from Adobe, Pantone and others), it'd still be nice if they shipped the OS CD's at a neglible cost so people could have the option of installing OpenStep on their windows machines and at least see what the fuss used to be about.

    4. Re:NEXTSTEP / Mac OS X relationship? by pli · · Score: 1

      "[...]OpenStep, which has a very similar object hierarchy to NeXTSTEP, but uses a better object allocation model[...]"

      better object allocation model? would you care to explain that a bit further? I would be interested in hearing more about that.

  4. D'oh by Erich · · Score: 2

    I mean GNUStep, not OpenSTEP. OpenSTEP == NEXTSTEP. I knew that. Sorry.

    --

    -- Erich

    Slashdot reader since 1997

  5. Hooray! by Anonymous Coward · · Score: 2
    This is great news. IMO, GNUStep is (will be) more important than KDE or GNOME, even though they get more attention. OpenStep is a well designed spec. Programming for it is great. The only thing that matches it could possibly be BeOS (both are object oriented and similar in many respects, though BeOS is multi-threaded to the max).

    Plus, OpenStep has a better look & feel than KDE or GNOME*
    (Yeah, I know, OpenStep is a spec, not an implementation. It still looks nice).

    1. Re:Hooray! by Anonymous Coward · · Score: 0

      > more important than KDE or GNOME That's what I'm inclined to think -- Question: are any of the big vendors supporting the GNUStep effort (a la RedHat/GNOME)? If not, why not? Unless I'm blinded by hype, there aren't enough superlatives to describe how good (and, important...) a completed GNUStep could be. So, if there isn't some "big gun" support right now, what's the reason? Do the fellas in the community with all the lucre know something that the 'Step enthusiasts don't? Or is it simply that the project's just been too "low-visibility"?

    2. Re:Hooray! by aeonek · · Score: 1

      This is great news. IMO, GNUStep is (will be) more important than KDE or GNOME, even though they get more attention. OpenStep is a well designed spec. Programming for it is great. The only thing that matches it could possibly be BeOS (both are object oriented and similar in many respects, though BeOS is multi-threaded to the max).
      I would say OPENSTEP is nicer, much because of the language (Objective-C).
      If you look closely at the BeOS API and then the OPENSTEP API, you notice that BeOS have borrowed a lot from NeXT. Did you know that BeOS originally didn't have a desktop (Just like NeXT), and instead a dock? (Just like NeXT)

      There are other similarities too:
      NeXT was started by a former Apple Executive.
      Be was started by a former Apple Executive.

      NeXT was originally making a computer and an OS.
      Be was originally making a computer and an OS.

      NeXT had to leave the hardware bussines. Instead, they made an Intel version of their OS and became a pure software company.
      Be had to leave the hardware bussines. Instead, they made an Intel version of their OS and became a pure software company.

      When Apple realised they couldn't make a modern OS by themselves, they decided that they would by an OS vendor. They choice was between NeXT and Be.

      --
      "Bernoulli was wrong. X proves that you can fill a vacuum, yet still it sucks." - Dennis Ritchie
  6. Good use for "FREE" Solaris by Anonymous Coward · · Score: 1
    "Free" Solaris comes with SunX, which has licensed Display Postscript, which kicks the shit out of that nasty hack display ghostscript.

    Interestingly enough, the OpenStep spec was from Sun & NeXT, and if you look hard enough, you can find an unfinished OpenStep implementation for Solaris. Unfortunately, Sun let it die in favor of Java (smooth move, dickwads), and the binaries are for SPARC only.

    I'm glad to see GNUStep is progressing though. I tried it back in the 0.5.0 era, but it was, well, in the development stage :-)

    1. Re:Good use for "FREE" Solaris by IntlHarvester · · Score: 1

      So, the obvious question: Is there any way to get the Solaris DPS libraries running under Linux? Or is ghostscript good enough that it's not worth it?

      I know about ibcs (?), but had trouble getting it to do anything with Solaris x86 apps.

      (Yup, solaris stuff is not free software, but on the otherhand, the licence from Sun for personal solaris is cheeep, and it would be nice to make use of the software I paid for.)
      --

      --
      Business. Numbers. Money. People. Computer World.
    2. Re:Good use for "FREE" Solaris by aeonek · · Score: 1

      "Free" Solaris comes with SunX, which has licensed Display Postscript, which kicks the shit out of that nasty hack display ghostscript.

      Of course. SunX has DPS as an X extension, whereas Display Ghostscript is a DPS/NX agent, which means that it talks to the X server through the usual X protocol. It doesn't require a DPS extension at the server, so it can use any X display. Of course, this is much slower than having DPS integrated with the display server.

      There is a free DPS/X extension under development, but it's in a very early stage. When it's ready, i'll change my sig.

      --
      "Bernoulli was wrong. X proves that you can fill a vacuum, yet still it sucks." - Dennis Ritchie
  7. DPS vs DPDF by Straker+Skunk · · Score: 1

    Incidentally, what would the difference(s) be between OpenStep's Display Postscript and OSX's Display PDF (Quartz) tech? Anyone know the relative pros/cons, how either one stacks up against the other, etc.?

    Methinks the xdps component may see a surge of interest, with all these tantalizing reports of what OSX can do with dynamic scaling and alpha-channelling....

    --
    iSKUNK!
    1. Re:DPS vs DPDF by be-fan · · Score: 1

      The difference between Quartz and DPS is that Quartz is based on PDF while DPS is based on PostScript. I believe PDF is more powerful, and I think is an evolution of Postscript. PDF can do anything Postscript can do except it has more constant color handling, and more features. You can check the MacOS X article a while ago to see what Quartz is about.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:DPS vs DPDF by jgrr · · Score: 1

      I wondered about this also, because I've been thinking that a word processor that used pdf as a native format might be really nice. Most people can read pdf files, so it's more portable than ms word, or even PS. Why not have a program that works a little like lyx, but just draws pdf to the screen?

      I thought of this because when I'm writing in (La)TeX, I usually have a gv window displaying the file I'm editing. It seems like it ought to be a small step to move from having three windows (emacs, gv, xterm to run for file; do latex $i; dvips $i;done). What's to prevent mixing the emacs part and the gv part.

      Rendering the document would be free, since pdf viewing code exists already, and dps is supposed to just let you put ps on a screen. So all that you need is a way to enter text in the file in a WYSIWYG way, and process it easily into PDF or PS.

      The processing could be through a tex backend, or something, so you just need to be able to enter the text. How easy would it be to tweak gv to make entering text possible, as a sort of proof of concept?

    3. Re:DPS vs DPDF by Straker+Skunk · · Score: 1

      Interesting idea, but it would probably just be more efficient to combine the editor with xdvi (the engine, not the interface!) rather than gv... that way, you get rid of the PS/PDF stage, which (in your example) is an intermediate between the editor and the screen anyway.

      --
      iSKUNK!
  8. Yes! by Anonymous Coward · · Score: 0

    This is the desktop that should have been THE GNU Desktop all along. Just one look at the screenshots and you can tell this is by professionals.

    1. Re:Yes! by rm+-rf+/etc/* · · Score: 1


      GNUStep isn't a desktop, you're thinking of window maker...

  9. they are there, just... by Anonymous Coward · · Score: 3

    waiting to run. The problem is that GNUStep hasn't reached a point where GUI OpenStep apps can just be compiled. There are too many inconsistencies and too much not done yet in the AppKit Foundation. But once it's done, in theory any openstep app should be able to be run on linux. They also run on MacOSX, and Windows. OpenStep is the cross platform app development environment that Java wishes it was. A JVM is stupid, it slows things down to much especially considering what a hog swing is, and you have to use swing to do decent interfaces. OpenStep got it right. The basic philosophy of OpenStep is write once, compile anywhere as opposed to Java's compile once, run anywhere...

    1. Re:they are there, just... by smart2000 · · Score: 2
      The problem is that GNUStep hasn't reached a point where GUI OpenStep apps can just be compiled

      We find most command line stuff "just builds". We type make, and it's off to the races. The GUI stuff is a bit harder. It compiles, but the interface format used by NeXT / Apple is un-documented, so you have to convert the interfaces. The GUI apps compile, they just run a bit funky.

      --
      To purchase it is not like spending money but rather it is an investment in the future in a blow against the empire
    2. Re:they are there, just... by mistabobdobalina · · Score: 1

      isnt the philosophy of Unix write once compile anywhere as well?

      --
      -- your knees hurt, don't they?
  10. Ah yes! by Yarn · · Score: 3

    I remember lusting after NeXT boxes when I was like 12 after we got our 1st 386, they looked so sweet, and the UI was so *smart*. Consistancy is something that almost everyone agrees is a problem with X, but plans to make is nice always seem to fall over. CDE is/was hell (imo), gnome and kde are diverging and converging at the same time, and I'm getting confused. SAVE ME GNUSTEP :)

    --
    -Yarn - Rio Karma: Excellent
    1. Re:Ah yes! by Surak · · Score: 2

      Believe it or not, CDE is still in wide spread use. The engineering workstations at GM all use CDE (they run Solaris and HP-UX) and I have to agree its GARBAGE.

      KDE and GNOME are good steps in the right direction.

      I don't think GNUStep/OpenStep/NeXTStep whatever is really going to ever be any sort of standard, IMHO. Nice interface, nice technology, but too far from mainstream interfaces.


    2. Re:Ah yes! by scrytch · · Score: 3

      Sun, of course, also uses CDE. It's also pretty much universally hated there. It does do some things well that KDE still doesn't quite manage, and gnome doesn't even try for. But overall it's ugly, klunky, and unfriendly. The file manager is a joke (except when you want to set ACL's, there it's the best interface going). The mail client is primitive (except it does IMAP perfectly, something free email clients are always lagging on). And it uses the classic motif look, which can only be described as "boxy but good" if only it were good.

      All that said, CDE does some things right. Like a web browser icon on the panel that runs sdtwebclient, which acts as the equivalent of the netscape-wrapper script for netscape or hotjava. The panel isn't very flexible, but it's far more intuitive and easy to navigate than any START button or knockoff thereof.

      I'd love KDE on Solaris if it were actually as functional as CDE. Give it a year or two and it'll probably get there, faster than CDE, for sure.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    3. Re:Ah yes! by Ian+Bicking · · Score: 2
      I don't think GNUStep/OpenStep/NeXTStep whatever is really going to ever be any sort of standard, IMHO. Nice interface, nice technology, but too far from mainstream interfaces.
      I don't think the interfaces are a problem at all. NeXTStep isn't really all that novel in its interface -- basically a polishing of the Mac interface. Windows looks more like NeXT than Macs.

      But that won't be the problem -- the biggest issue is, IMHO, Objective C. Now, I'm not saying anything bad about Objective C, but it's a new language to most people, and people get weird about that sort of thing. It doesn't have the hype behind it that Java does, the history and maturity of C, or the mainstream acceptance of C++. Too bad, it's better than all of them.

    4. Re:Ah yes! by Zurk · · Score: 1

      you can use AfterStep on solaris - the first thing i did was to wipe CDE off my box, whack AfterStep on and voila - instant NeXT desktop with around twice the performance of CDE and 16 virtual desktops. BTW, you gotta start the session with safemode barebones X to run AfterStep. didnt figure that out for a while.

    5. Re:Ah yes! by Anonymous Coward · · Score: 0

      And we can all see how much the hype helped java... -AX

    6. Re:Ah yes! by Surak · · Score: 2

      I fail to see how KDE is less functional than CDE. I use both on quite a regular basis and I am always saying that CDE is not as functional as KDE.

      KDE's panel is very similar to CDE's (this is not by mistake). CDE *does* have the ability to customize it a bit better by hacking scripts (you can have multiple rows of icons and customize their size, for instance), but overall, KDE offers more "point-and-click" functionality right out of the box.



    7. Re:Ah yes! by scrytch · · Score: 2

      > KDE's panel is very similar to CDE's (this is not by mistake).

      Not where it matters, namely the drawers. All of the CDE panel's icons have arrows for the drawers above them, with the ability to add new items to the drawer via drag and drop, and the ability to put one of the drawer items on the main panel. It's extremely intuitive, and KDE isn't quite the same (possibly no worse, but I didn't feel it was as straightforward). Secondly, unless they've changed this recently, every time I click on the netscape icon in KDE, it attempts to launch a new netscape process (and whines about lockfiles, etc). To say nothing of detecting preferred browsers or launching an alternate one. Sound simply didn't work at all in Solaris KDE.

      The most damning thing of all is that KDE does not understand multiheading. Getting it going on the second monitor tended to make it conflict with itself and do very ugly things.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    8. Re:Ah yes! by John+Allsup · · Score: 1

      KDE and GNOME are good steps in the right direction.
      Sorry, but the first step to consistency HAS to be dropping X. The various UI components that everybody uses 101 and more UI toolkits to generate need to reside in the display, as does most of the UI. Only the non-trivial aspects of the application should even need to be handled by the application's code (the only library it should need to link to is the one which allows it to communicate with the display server (-lc and -lm excepted of course)).

      I don't think GNUStep/OpenStep/NeXTStep whatever is really going to ever be any sort of standard, IMHO. Nice interface, nice technology, but too far from mainstream interfaces.
      The only thing currently mainstream that stands any chance of being a standard s Windows. This has been reiterated time and time again. If you believe in what you stated above, you should really be working with the WINE people, whose task is to implement the most mainstream of application interfaces.
      John
      --
      John_Chalisque
  11. Re:Another (L)GPLed project that will never finish by smart2000 · · Score: 4
    Anyone who would devote any time to GNUstep is an idiot.

    Please, tell us what you really think. I devote time to GNUstep because it allows me to quickly write cool software that we need and distribute it on commodity hardware that runs an operating system that supports the cards and features we need. I make money doing this. How does this make me an idiot?

    It is possible to work with GPLed software for the wrong, and wasteful reasons. But just choosing GNUstep over the competition doesn't make one an idiot.

    This project will clearly never finish.

    Probably so. Like most free software it will continue to live and improve each day. However they have met several important goals, and they stuff the code as it stands is useful TODAY.

    GNUstep is in the same hopeless position as projects such as GNU Classpath, forever trying to catch up to an evolving standard.

    At the time GNUstep started, OpenStep was supposed to become a certified standard. Since then Apple bought NeXT (who saw it coming?) and is trying to take their existing code base and justify the purchase. Whether they actually ship it is another question.

    .. snip.. The bizarre GNUstep mission page claims that the project will accomodate both commercial and free software. How's that supposed to happen with GPLed libraries?

    The libraries are LPGL, not GPL. There is nothing in the GPL that prevents commercial projects from using the source. There is nothing that requires them to distribute the source unless they distribute binaries. For MCCA users, there is no conflict

    --
    To purchase it is not like spending money but rather it is an investment in the future in a blow against the empire
  12. Yawn. Another Whiner that will never finish by Anonymous Coward · · Score: 1
    Boy, you sure get emotional about software that you won't ever use!

    Yes, like its fellow GNU brothers--GCC, Emacs, Gnome, Bash, SmallEiffel and so on--GNUstep probably never will be finished. Wink ;^) -- it will continually keep getting better.

  13. About the *step interface... by extrasolar · · Score: 2

    My knowledge of the *step interface is based on WindowMaker. I read somewhere that much of the design of the *step interface was based on large computers with large monitors. That was why they have root menus instead of a global menu. Is this true?

    1. Re:About the *step interface... by Ian+Bicking · · Score: 1
      As I remember it, the original NeXT interface didn't have any root menus, just the wharf.

      I wouldn't be surprised that NeXT was forward-thinking when it came to hardware, since the hardware itself was always top-of-the-line (perhaps to a fault). The icons where pretty big (64x64, I think). The original screens were 4-color (black, white, two shades of gray) so that would explain the original color scheme (very grey). But they were big and fairly high resolution.

    2. Re:About the *step interface... by Matthew+Weigel · · Score: 1

      NeXTSTEP has no root menu. What is the root menu in WindowMaker is the Application menu in NeXTSTEP, in a standard installation it is in the upper right hand corner (it can be moved around, and made to pop up wherever the RMB is clicked, like an application-specific root menu).

      According to folklore, NeXTSTEP has that menu system because they were afraid of simply wholesale copying the application menu in MacOS (the one across the top). I can't think of any other reason they'd waste the space with an "always on top" object that can grow both vertically (more options) and horizontally (long words).

      And yes, NeXTSTEP originally ran on 17" monitors minimum. The Color NeXTs could come with 17" and 21" monitors, and a NeXTDimension system (NeXTCube with NeXTDimension board) could come with a 17" monochrome and a 21" color monitor, dual-head.

      The 64x64 icons seemed quite reasonable on screens of that size, and even the annoying application menu isn't too annoying there. NeXTSTEP for intel suffered in that many people (myself included) stuck it on a system with a 15" monitor, which it was never designed for.

      Since the smallest display Apple currently offers is a 15" flat panel (and the smallest CRT is 17"), I suspect that current complaints about the size of Aqua icons (variable, apparently, from 32x32 to 128x128) will be rendered "not too relevant."

      --
      --Matthew
    3. Re:About the *step interface... by rangek · · Score: 2

      I read somewhere that much of the design of the *step interface was based on large computers with large monitors.

      I can believe this. I started using X under Solaris and CDE (and I didn't think it was too bad. Yeah the file manager sucked, but I never really use a file manager... (am I missing something?)). Then I used a customized fvwm2 set up under RH5.x. I liked that well enough, since I constantly twiddled with it over the course of a year or so.

      Then I installed RH6.0 and dealt with GNOME for a while. It is great for newbies, most every one in my lab uses it. It is just point and click configurable enough for them to make life livable for themselves. They are all used to fvwm-95 or whatever that default config was under RH5.x (YUCK!), so GNOME/E is just peachy as far as they know.

      I soon got sick of GNOME though. It just wasn't configurable enough. Granted, I didn't spend a lot of time figuring it out, but shit, I have work to do man. I can't just fuck around with my WM all day.

      So I looked around and decided to try GNUstep (WindowMaker). It is awesome on my machine at work (1600x1200 on a 21" monitor). But when I installed it at home (1024x768 on a 17") I really wanted smaller icons. You can change the icon size, but then you have to use pictures on those icons that are the right size. So I know it is possible to do, but once again, too much effort. WindowMaker should be smart enough to use a 32x32 set of xpm's or whatever if I tell it I want 32x32 icons.

      I still like WindowMaker and GNUStep. But I think it would be pretty impossible to use on a system Now maybe we are all complaining about something that is easily fixed but we just don't know about. Any WindowMaker/GNUStep guru's know something we don't?

    4. Re:About the *step interface... by Anonymous Coward · · Score: 0
      is in the upper right hand corner

      Make that upper left

      According to folklore, NeXTSTEP has that menu system because they were afraid of simply wholesale copying the application menu in MacOS (the one across the top). I can't think of any other reason they'd waste the space with an "always on top" object that can grow both vertically (more options) and horizontally (long words).

      NS has this kind of menus because this structure offers better usage then the orginal menu bar idea *if* your screen is large enough. These vertically stacked menus do not waste space anymore than a standard menu bar do. Being able to move then around makes them *very* convenient. I prefer them even today over every menu bar/start menu crap.

      The 64x64 icons seemed quite reasonable on screens of that size...[17']

      Make that 48x48, that's at least big enought to make some nice icons - where 32x32 is way to small.

    5. Re:About the *step interface... by extrasolar · · Score: 2

      NS has this kind of menus because this structure offers better usage then the orginal menu bar idea *if* your screen is large enough. These vertically stacked menus do not waste space anymore than a standard menu bar do. Being able to move then around makes them *very* convenient. I prefer them even today over every menu bar/start menu crap.

      That is a very good point. It is probably a reason why WindowMaker has the Root Menu able to be dragged around, most users don't have that much screen space.

      This NextStep way of the user interface is interesting to me. I only now realize how much of a mess our interfaces are that try to *hide* the information from the user.

    6. Re:About the *step interface... by Anonymous Coward · · Score: 0

      I have been using WindowMaker since 1998 on a laptop with a 800x600 screen, with 32x32 icon size. As far as I can determine, WindowMaker scales the icons that are really user-assigned icon files to 32x32 pixels, but shows only the upper left 32x32 pixels of icons that are provided by the application via the X server.

    7. Re:About the *step interface... by Anonymous Coward · · Score: 2
      NS has this kind of menus because this structure offers better usage then the orginal menu bar idea *if* your screen is large enough. These vertically stacked menus do not waste space anymore than a standard menu bar do. Being able to move then around makes them *very* convenient. I prefer them even today over every menu bar/start menu crap.

      Like many NeXTSTEP idiosyncracies (scrollbars on the left, close box on the top right, 17" minimum screen, black hole / recycler icon instead of trash can, etc.) the NeXT menu is touted for its "benefits" -- but was actually not designed for that reason but instead to avoid lawsuits from Apple. As part of his severance agreement, Steve Jobs agreed to a number stipulations from Apple about the then-unnamed NeXT computer. One was, humorously enough, that the NeXT cube had to be more powerful than any of Apple's present offerings (which it was, with a 25 MHz 68030 processor, soon changed to 68040).

      Although there are lots of nice features about the NeXT menu bar design, and I personally love it, it nonetheless has three flaws which override all of its niceties and make it distinctly inferior to the Mac menu bar.

      1. It violates Fitt's Law. (If you do not know what this is, don't respond to this message until you look it up on the web; you'll just look foolish otherwise.) The single most serindipidous feature of the Mac menu bar (Apple lucked out) is that it is very easy to hit with the mouse, because the menus are backstopped by the top of the screen. While NeXT (and Windows, and XWindows) users generally choose menus by carefully and precisely moving the mouse to the menu button and pressing, Mac users generally choose menus by slamming the mouse up to the top of the screen, then dragging down, all in a very crude, hit-the-barn-door fashion. They can get away with this because it is impossible to overshoot Mac menu options -- it's as if they have infinite height. Published studies generally show that experienced Mac users choose menus at almost five times the speed of Windows (or NeXT) users for the same accuracy.
      2. Apple's submenu-dragging algorithm is vastly superior to XWindows, Windows or NeXTSTEP. On the NeXT, in order to drag onto a submenu, you must move your mouse carefully to the right, out of the submenu parent's menu area. Don't move the mouse too far up or down! Or you'll have chosen another parent menu option and the submenu will disappear. This is also the case for Windows and for nearly every XWindows application with submenus. On the Mac, if a submenu is up, you can move at a significant angle to hit the submenu, even crossing over other menu choices for short periods of time, to reach the submenu. This is a real problem for NeXT users because nearly everything is in a submenu in the NeXT GUI.
      3. The NeXT's menu design might seem to take up "less space" than the Mac menu design, but in reality it is significantly more obstructive. Like most GUIs, the NeXT GUI is built around large rectangular windows. On the Mac, the menu leaves a workspace below which is still rectangular, whereas the NeXT menu leaves a workspace in the shape of Utah (horizontally flipped). As a result most NeXT users tend to leave the entire desktop area directly below the menu unused. One occasional hack is to move NeXT "inspector windows" (information-modification dialogs) over there, though inspectors are rarely thinner than the menu width so this isn't a great solution. Usually the space, about 15% of the screen, is just left wasted.

      Many NeXT users, like Windows users, avoid problem #2 by chosing menus click-by-click, rather than dragging through the menu tree. Mac users are not, of course, forced to do this. The catch-22 for the NeXT GUI is, however, that most experienced NeXT users avoid problems #1 and #3 by moving the menu nearly off the screen and using the right mouse button to pop up the menu at the mouse position -- the problem with this is that when using the popped-up menu, you must drag to choose menu items, hence problem #2 rears its devastating head again. Right-mouse-menu-choosing is very slow.

      As a longtime NeXTSTEP developer and experienced GUI hacker, I love the NeXT interface. But let's call a duck a duck: the NeXT menu really really sucks in some places.

    8. Re:About the *step interface... by Anonymous Coward · · Score: 1

      Shame on you - as a NeXTstep user, you should know better ...

      > 1. It violates Fitt's Law
      Nope - it lets the user violate Fitt's law if they want to. The standard positioning of the menu in the top-left corner of the screen gives the menu the same advantages as the mac menu-bar

      > 2. Apple's submenu-dragging algorithm is vastly
      > superior to XWindows, Windows or NeXTSTEP. On
      > the NeXT, in order to drag onto a submenu, you
      > must move your mouse carefully to the right, out
      > of the submenu parent's menu area. Don't move
      > the mouse too far up or down! Or you'll have
      > chosen another parent menu option and the
      > submenu will disappear.

      Nope - this is untrue - you can click and drag directly to the submenu item you want. Another parent menu option is chosen only if you stop on it!

      > 3. The NeXT's menu design might seem to take up
      > "less space" than the Mac menu design, but in
      > reality it is significantly more obstructive.
      > Like most GUIs, the NeXT GUI is built around
      > large rectangular windows. On the Mac, the menu
      > leaves a workspace below which is still
      > rectangular, whereas the NeXT menu leaves
      > a workspace in the shape of Utah (horizontally
      > flipped). As a result most NeXT users tend to
      > leave the entire desktop area directly below the
      > menu unused.

      Nope - most NeXT users fill the area under the top-level menu with panels, torn-off submenus or windows. Perhaps if people were using 14 inch displays then the space under the top-level menu would be inconveniently small - but NeXT users work with 17 inch and upwards and a decent resolution.

      In short - the MacOS menu-bar is a design for small, low-res (old) displays, the NeXT menu system is a design for larger higher resolution (current/future) displays.

    9. Re:About the *step interface... by Anonymous Coward · · Score: 0
      Nope - it lets the user violate Fitt's law if they want to.

      From this I take it you literally have *no* idea what you're talking about.

      Nope - this is untrue - you can click and drag directly to the submenu item you want. Another parent menu option is chosen only if you stop on it!

      Open Edit.app. Click on the "E" in the "Edit" menu. Hold it there. Now, ready, set, go: drag DIAGONALLY straight to the "Select All" menu choice. Can't do it, can you? Format menu pops up, huh? This is because NeXT went with a time-delay model and didn't get it right. It's a classic example of bad algorithm choice. MacOSX's menus are supposed to fix this.

      Nope - most NeXT users fill the area under the top-level menu with panels, torn-off submenus or windows.

      Having taught and managed hundreds of NeXT users, I think I can safely say that most NeXT users, even experienced developers, leave the area blank.

      In short - the MacOS menu-bar is a design for small, low-res (old) displays, the NeXT menu system is a design for larger higher resolution (current/future) displays.

      I'm all for tear-off menus. But other than this, NeXT's menus have no advantage in a large screen. It might be better said that the NeXT menu system is only acceptable for larger displays. It is NeXTSTEP's single worst feature. We should be nonfanatical enough to admit that.

    10. Re:About the *step interface... by Matthew+Weigel · · Score: 1
      Make that upper left
      Oops. I'm bad that way.
      NS has this kind of menus because this structure offers better usage then the orginal menu bar idea *if* your screen is large enough. These vertically stacked menus do not waste space anymore than a standard menu bar do.
      Nope. It renders the screen space available to users into a shape that doesn't fit the shape of the windows. Since the menu height is variable, there's no set distance down I can put a window so that it doesn't get run over. And don't forget getting the right menu selection takes more time than in MacOS.

      And further, the decision to do the menu like that was most certainly not a willing design decision based on the assumption that the way they were doing it was better.
      Being able to move then around makes them *very* convenient.
      True, but irrelevant to the poor design of the rectangular menu bar.

      Just for grins I've compiled a quick look at other operating systems that use something like this:
      • OS/2 -- LaunchPad / Toolbar. Its shape is definitely annoying. ObjectDesktop unfortunately copies this in some of its tools, but not all (thank God!). At least with version 4, you can elect to use the WarpCenter rather than (or in addition to) the Toolbar; the WarpCenter takes up the entire top or bottom 15 pixels or so, and provides access to a list of running processes (closer to the Macintosh Application menu than the Windows Taskbar, except it lists each process or window seperately), all objects on the desktop, and user-defined trays that hold any objects you damn well please.
      • BeOS -- is a curious cross between MacOS and Windows. Each window will have its own menu bar, but windows are listed by application in the MacOS-Application-menu-like system menu. This menu increases in size with the number of applications running, but it can be made to run across the top or bottom of the screen and get out of the way.
      --
      --Matthew
    11. Re:About the *step interface... by Anonymous Coward · · Score: 0

      >>Nope - it lets the user violate Fitt's law if
      >> they want to.
      >From this I take it you literally have *no* idea
      >what you're talking about.
      From this comment I take it you suffer basic
      comprehension difficulties - so I'll restate ...
      The standard positioning does not not violate
      Fitt's law (which is merely a rough guide): the
      menu is an easy target at the edge of the screen.
      However, the user is free to move the menu to a
      position where it is not such an easy target.

      >>Nope - this is untrue - you can click and drag
      >>directly to the submenu item you want. Another
      >>parent menu option is chosen only if you stop
      >>on it!

      >Open Edit.app. Click on the "E" in the "Edit"
      >menu. Hold it there. Now, ready, set, go: drag
      >DIAGONALLY straight to the "Select All" menu
      >choice. Can't do it, can you? Format menu pops
      >up, huh? This is because NeXT went with a
      >time-delay model and didn't get it right.

      That's a special case of highly abnormal use.
      agree that the algorithm is imperfect, but in
      practice people don't click, then deliberately
      pause. In normal use, your description of how
      you lose submenus is simply WRONG and the time
      delay algorithm works fine.

      >>Nope - most NeXT users fill the area under the
      >>top-level menu with panels, torn-off submenus
      >>or windows.
      >Having taught and managed hundreds of NeXT
      >users, I think I can safely say that most NeXT
      >users, even experienced developers, leave the
      >area blank.

      Well - if you teach them to use the GUI badly,
      I'm not surprised that you find that that is what
      they do.
      My experience is only with tens of users, but
      those people who are just left to learn for
      themselves seem to have no trouble using the
      screen real-estate.

      >I'm all for tear-off menus. But other than this,
      >NeXT's menus have no advantage in a large
      >screen
      Well - vertical arrangement makes it easier to
      find menu items visually since we are used to
      lists arranged line by line. Aside from that
      and the flexibility of being able to move the
      menu and pop it up under the mouse, there's
      really little difference now that MacOS has
      added support for NeXT-style submenus that stay
      up when you click and release on the parent menu
      item.

  14. CNN story by Anonymous Coward · · Score: 0

    CNN Entertainment has full coverage. Thank you.

    1. Re:CNN story by Anonymous Coward · · Score: 0

      scum. its a troll. anyway, please join me in mailing www@dorsai.org and CC the following message:
      Dear Sir,
      One of your users has been spamming a news site at slashdot.org. The URL he posts is : http://www.dorsai.org/~delchi/cnn.htm
      We request you to delete and cancel his web access.
      Thank you.
      -name-

  15. Re:Ah yes!-Walk this way. by Anonymous Coward · · Score: 1

    Am I the only one who finds the comment about non-acceptance a bit ironic in light of the previous slashdot story concerning Linux's achilles heel and the comments generated?
    GNUStep/OpenStep/NeXTStep represent a viable solution to the comments generated *but* is shot down because it isn't mainstream (read not Windows/Mac). Ahh the price we will pay for our "conformist" ways.



  16. idiot by Anonymous Coward · · Score: 0

    how do you know the page owner is even doing the posting? besides, some of us think this is funny!

  17. Mama!!! by Anonymous Coward · · Score: 0

    (crying) Mama, he mentioned a web page I don't like! Make him stop!

    1. Re:Mama!!! by Anonymous Coward · · Score: 0

      mama : sure honey, let me mail the webmaster.
      webmaster: delete spammers account.
      spammer: wah!!

  18. Nextstep Hype by Anonymous Coward · · Score: 0

    What a bunch of crap. Everyone extolls the holy virtues of nextstep, but no one really can give real world reasons why it is so great.

    As someone who used and programmed nextstep apps, I can say the hype is unbelievable. I guess Jobs is good at that though.

    1. Re:Nextstep Hype by rm+-rf+/etc/* · · Score: 2


      Have you asked anyone who has used it? Everyone I know who has done Openstep development would be happy to share with you. My list? I wrote a TextEditor with search and replace, multiple undos/redos, selectable font size and style, spell checking, cut and paste, and drag and drop integration with 7 lines of code in under 4 minutes.

      Show me somewhere else I can do that.

    2. Re:Nextstep Hype by Vryl · · Score: 1
      as a matter of interest (I have never programmed in openstep), would you say you 'wrote' that or 'assembled' it.

      It seems that there must be massive pre-fabbed components to be able to do your TextEditor in only 7 lines of code.

    3. Re:Nextstep Hype by Anonymous Coward · · Score: 1

      It's not hype.
      Which NeXTstep apps did you use?
      Ever take advantage of DisplayPostScript to extend in real time a drawing application? I do this all the time, and it makes my 10 year old NeXT Cube a much nicer tool for graphic design, typography and page layout than the G4 I have at work.
      Or, how about adding a new language's spell-checking to every application by installing one library? Or .PDF support by installing a single app (pstill.app from www.this.net/~frank)
      Ever pause to look up a word or quotation in Webster.app or Oxford.app?
      Ever hear of a game called ``Doom''? It was written in NeXTstep and then ported to DOS.
      Or what about the ``world wide web''? The first point and click web browser was worldwideweb.app for NeXTstep, on which platform the web and http were created.
      NeXTstep is great because it's elegant, consistent, harnesses Unix for mere mortals, and makes using a computer a pleasure and not a chor.
      William, willadams@aol.com whose slashdot login isn't working at the moment.

    4. Re:Nextstep Hype by Anonymous Coward · · Score: 1

      Disclaimer: I am only a 6-year SysAdmin, not a developer.

      On my first real post-collegiate job, I was fortunate enough to inherit and expand a mixed SunOS/NEXTSTEP network. As I have progressed through small, medium, and large enterprise networks, the lessons and elegance of managing NEXTSTEP hosts and servers have never left me.

      Call me a bigot if you will, but I and most of those who have ever used NS intimately (and I don't mean slathered in baby oil) tend to use superlitives when referring to what NeXT wrought. Best, most beautiful, seamless, brilliant.

      Object inheritance, extensibility, and network tranparence added so much functionality. Appls like CREATE!, Tailor, NeXtMail.app, and the Lighthouse apps had functionality and interpplication communication like nothing you have ever seen elsewhere. Services were available to all apps, and new services were immediately modifiable for an individual of a 5000-node domain.

      Use NetInfo in a 4-tier hierarchical nertwork of 6000 hosts across three continents in realtime and then try to manage a hierarchical NIS+ network. Case closed. I have drag-and-dropped entire mid-level subdomains, readdressed in bulk all of the hosts, shipped the machines, and the all worked when plugged in and powered up. Servers, replicas, hosts, NFS volumes, printers, services, and cute little NeXTMail user.tiffs. I may or may not do SysAdmin for a very large entity that invented many open protocols that we all use, and I assert that NetInfo and it's related apps & tools were the pinnacle of Systems Administration. Oh, yeah, it can serve Samba and YP for the rest of your network, too.

      It is truly a case of "don't knock it 'till you've tried it." UNIX purists will sneer at mach as "not a true UN*X kernel," but the nuts & bolts implementation says, as all NeXTies know, "it just works."

      I have OpenStep 4.2 running on SPARC, M68K, and i386 at home. I can't wait for GnuStep to be ready! Good job to all in the Project. Show the world what truths we have known since 1988.

      Mike

    5. Re:Nextstep Hype by John+Allsup · · Score: 1

      You could just say 'prouced'. The basic point is the same -- RAD. Application developers shouldn't have to do intricate component development (i.e. going through code with a fine toothcomb, removing wasted instructions etc.). When was the last time you heard someone complain that 'mending a car' wasn't really mending since 'you don't have to do all the complicated bits').
      John

      --
      John_Chalisque
  19. MPAA is at it again! by Anonymous Coward · · Score: 0

    The MPAA is at it again! Yet another injunction has been filed against 2600 on 26, Jan. 2000. This time to stop LINKING to sites with DeCSS.

  20. GNUstep clarification: Support GNUstep! by RevAaron · · Score: 3

    People seem to be kind of confused about what GNUstep is and implies, I'll try to clarify:

    GNUstep is: an implementation of the OpenStep API. The OpenStep API makes it quite easy to develop programs for it, as the developer doesn't have to worry about the little things, and spend their time innovating and writing great code . It's cross-platform (between Windows w/ the YellowBox, anything running GNUstep, Mac OS X/Cocoa). It's a dream to develop with, and the Objective-C language, to me, is much nicer to use than C++ (although I think there's wrappers for Java, and perhaps C/C++).

    GNUstep will: Allow for easy ports to platforms running GNUstep from source written under OpenStep, Rhapsody, or Mac OS X (using Cocoa/YellowBox). This encourages cross-platform development, and hopefully will help bring many apps to Mac OS X/Cocoa, as well as Linux/FreeBSD/etc.

    GNUstep is not: a window manager or a desktop environment. Desktop environments can (and quite easily) built with GNUstep. In fact, someone is working on a NeXT-like file manager right now, which is working and developed under OpenStep, and easily recompiled on a FreeBSD box using GNUstep.



    For more information, see the GNUstep website or the unofficial GNUstep website, both of which have plenty of information on the OpenStep spec, and where GNUstep is going.

    In short-- definately check it out!

    Aaron

    --

    Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
    1. Re:GNUstep clarification: Support GNUstep! by uid8472 · · Score: 1

      It's a dream to develop with, and the Objective-C language, to me, is much nicer to use than C++ (although I think there's wrappers for Java, and perhaps C/C++).

      I sort of doubt there'd be a wrapper for C or C++, since Objective-C uses class objects (factories) and message-passing semantics for method calls; C++'s RTTI and virtual member functions can't emulate some features that I know *Step uses.

    2. Re:GNUstep clarification: Support GNUstep! by ph43drus · · Score: 1
      GNUstep is not: a window manager or a desktop environment.

      IIRC, the GNUstep team has endorced a very pretty and functional window manager as their ``Official Window Manager,'' WindowMaker.

      Jeff

  21. fag by Anonymous Coward · · Score: 0

    waaaaaahhhhhh look what a crybaby fag i am, i don't like that web page WWWWWWWWWWWAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

  22. Tools will pop up VERY SOON by Anonymous Coward · · Score: 2

    My colleagues and I wrote some OPENSTEP tools that are Interface Builder and Project Builder workalikes.

    They are running right now on Intel and NeXT machines running OPENSTEP. As soon as GNUstep can host the code base, these tools will be released.

    Linux is about ready to get the best application development environment on any platform--and it'll all be open source.

    Interface Builder is a GUI-building tool that works something like VisualAge in that it allows you to (a) visually build connections between GUI controls and methods and instance variables in objects and (b) create new instances of non-UI objects.

    Finished UIs in Interface Builder do not contain code. Instead the connections and controls are archived into "NIBs." This allows you to create and maintain UIs without having to write a single line of code. If you've ever written a Java Swing application, you know what a pain in the ass it is to write GUIs by hand.
    However, the tool does generate stubs for the custom, non-UI-related objects you create. This allows you to visually create a new object, connect up its stub methods to your controls visually, then "fill in the blank" to generate the core logic of your object's methods.

    Project Builder is similar to a Smalltalk code browser, with a Miller column view of your class hierarchy and an integrated editor window that displays source code and documentation depending on the currently browsed object. If you've used JBuilder, Visual Cafe, or VisualAge, you already know how this kind of thing works.

    1. Re:Tools will pop up VERY SOON by bentwookie · · Score: 1

      I started checking out the GNUStep pages a few weeks ago and saw your site. It was really eeri! I work on the "other" InterfaceBuilder. It's pretty cool (to me at least) that there's this parallel universe going on.

      Scott.

    2. Re:Tools will pop up VERY SOON by JasonAsbahr · · Score: 1

      I'd like to start hacking with these on NeXT hardware. Are they available?

      Thanks!

    3. Re:Tools will pop up VERY SOON by CyberELF · · Score: 1

      They are still for sale at Black Hole Inc.

  23. cool by mnf999 · · Score: 1

    I just love wm

    marc

    --
    The real mnf999 always posts as anonymous coward
  24. sort've by / · · Score: 2

    The philosophy of unix is "write once, compile on all conforming platforms" (ie, other unices, as long as you don't use any platform-specific code). What openstep/gnustep buys you is "write once, compile anywhere, including all the silly proprietary have-their-thumbs-where-the-sun-doesn't-shine platforms (ie, Windows et al). The latter is a godsend for programmers everywhere.

    --
    "If one is really a superior person, the fact is likely to leak out without too much assistance" -- John Andrew Holmes
  25. Interface feel by Julian+Morrison · · Score: 2

    I've used a proper OpenStep derived OS (Apple's Rhapsody betas) and I've used the current front runner linux UIs, Gnome and KDE. OpenStep is a lot nicer. Why is OpenStep nicer? Because it's integrated. Because it has things like color wells you can drag out of onto things, document proxy icons in the window manager you can drag to the filer, app bundles that contain an app and all it's global config in a single unit, system services that dynamically detect what you have selected and offer relevant options to tweak it.

    Gnome and KDE can be snazzified with themes and config and whatnot, but in the end it's mostly just chrome. They are struggling to retrofit the same degree of dynamism and integration that OpenStep had from the get-go.

  26. Wrong by Julian+Morrison · · Score: 1

    PDF is "good" specifically because it's weaker. Postscript is a fully fledged interpreted stack based language, and the only way to get the output is to run the program. PDF is more like HTML - a page description language which looks very similar to PS and shares its imaging model, but without the Turing-completeness. Basically this means less processor churn at the expense of flexibility and nifty hacks (eg: defining PS subroutines for your graphical elements and just calling them later).

    OpenStep used to use a full PS interpreter to drive the GUI. Apple's new system just allocates a chunk of screen real estate, and the program links against the "Quartz" libraries that use PDF to draw into it. One annoying consequence is you can no longer in MacOS X use "NSHosting" - basically, sending the PS stream from a remote machine to display locally, similar to how X works.

  27. Objective C by Christopher+B.+Brown · · Score: 2
    Part of the big deal comes from the Smalltalk-like structuring of Objective C.

    Note that there is an Objective C binding for GTK...

    --
    If you're not part of the solution, you're part of the precipitate.
  28. Re:Another (L)GPLed project that will never finish by exoduz · · Score: 1

    >At the time GNUstep started, OpenStep was >supposed to become a certified standard.
    >Since then Apple bought NeXT (who saw it coming?) >and is trying to take their existing
    >code base and justify the purchase. Whether they >actually ship it is another question

    Does this mean that openstep and objective-C was going through the process of standardization(standards committee) and all that when Apple bought Next and is now trying to milk openstep's proprietory old code for all its worth? thus killing the standards process?

    IF the GNUstep guys are trying to reverse engineer Openstep... wouldn't they be in the same boat as the WINE ppl and never quite be able to get there? I dont know much about the state of openstep and its documentation but if it were standardized and had all the specs available then i guess it would be possible.

    was thinking of learning objective-c (objective-c==openstep?) but if i gotta buy some devkit from apple to get the full functionality and only be able to run stuff on OSX then i guess i wouldn't be bothered...

    --

    --

    # I have no brain
  29. Re:Another (L)GPLed project that will never finish by Anonymous Coward · · Score: 0
    Does this mean that openstep and objective-C was going through the process of standardization(standards committee)

    The OpenStep spec was publicly made available, and at one point NeXT indicated that a GNU implementation that met the spec could be certied as OpenStep compliant. This was around the time of Sun/NeXT, pre java. When Sun went Java, NeXT eventually abandonded the standards process.

    IF the GNUstep guys are trying to reverse engineer Openstep... wouldn't they be in the same boat as the WINE ppl

    It's not reverse enginnering. There is an API, and they are writing the implementation to match that API.

    More importantly, I think 2000 will be the year that we see more programs available for GNUstep then were ever avaailable for NeXTSTEP/OpenStep. GNUstep will eventually hold the crown for Objective-C implementations. It's only a matter of time.

  30. You misunderstand. by SeanNi · · Score: 1

    You misunderstand. I/we (I'm not the poster you responded to) have nothing against the website itself. It's his/her prerogative to create it. And it's fine if some people find it funny. What sucks, is the fact that he's spammed Slashdot over and over and over and over and over... again. In the last week, I personally have seen him spam /. with this link at least 100 times. No, I am not exaggerating. 100 times, easily. And I only read at most 1/4 of the articles, and even then only about 1/3 to 1/2 the posts under those articles (unless it's something I'm really interested in).

    This person has put up a web-page. That is fine. However, he is also spamming it (under false pretenses, too... he disguises the link as being relevant to the discussion). That is not fine. It is spam, plain and simple. And we are responding to him as we would to any spammer, to any person that abuses their internet accounts. By reporting them to their ISP and hoping that their detrimental activities are stopped.

    It's a fine line between trolling and karma-whoring... and I think you just crossed it.
    --
    - Sean

    --
    It's a fine line between trolling and karma-whoring... and I think I just crossed it.
    - Sean
    1. Re:You misunderstand. by Anonymous Coward · · Score: 0

      So what say I go out, find some random webpage, spam it to /. for 3 weeks straight.. Think it'll get taken offline? Good revenge tactic.

    2. Re:You misunderstand. by Anonymous Coward · · Score: 0

      You don't know that the page owner is spamming Slashdot, so you probably won't get it taken offline for that. But the site is a copyrighted CNN page, and I doubt they have permission to mirror it.

  31. The apps are at Stepwise.com. by jcr · · Score: 2

    There are about 200 apps for NeXTSTEP that will show up on Linux as soon as GnuSTEP is able to support them.

    GnuSTEP isn't done yet, but when it is, hold on to your hat.

    For a sample of the apps you'll see, check out next-ftp.peak.org, and www.stepwise.com/softrak/

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  32. WindowMaker makes a Great Thin Client Interface! by orichter · · Score: 1

    I know this may be a bit off topic, but I just thought I would chime in and say that I have done a fair amount of work using VNC (http://www.uk.research.att.com/vnc/)
    for thin client computing. While I really like KDE and to a lesser degree GNOME on my local desktop, I have found that they seem to be quite slow over anything slower than the highest speed network. WindowMaker, on the other hand seems snappy even under a 56K connection. The only WM I have found to be any faster is twm (which I use to export individual applications to a web browser when I don't need any window manager.) Can anyone tell me why WindowMaker is so fast over a low bandwidth connection. Is it just the simple color scheme, or is there something more to it.

  33. Re:Another (L)GPLed project that will never finish by Le+douanier · · Score: 2

    was thinking of learning objective-c (objective-c==openstep?) but if i gotta buy some devkit from apple to get the full functionality and only be able to run stuff on OSX then i guess i wouldn't be bothered...

    Objective C != OpenStep.

    Objective C is a programming language that adds OO style programming to C but with a philosophy closer to Smalltalk than to C++ (i.e. Java also has a Smalltalk-like philosophy but with C++ syntax), thus Objective C has got great merits on its own.

    OpenStep use Objective C, so it integrates well with OpenStep, but you can use it without OpenStep.

    By the way, Next made the Objective C front end for GCC, and first tried to release it in binary only (they thought that releasing the .o binary was compliant with the GPL), RMS contacted them to tell them it was in violation and they re-released it under the GPL.

    I have also heard that Apple has got a compiler in which you can mix Objective C and C++, must be pretty cool.

    I haven't used it personally so it is things I have heard about it in various tutorials/explanations/... When I get the time I definitively must check it (I'm checking Guile right now).

    Anyway, for more informations see this.

    --
    "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  34. TeX implementations (was Re:DPS vs DPDF) by WillAdams · · Score: 1

    Actually, one of the nicest of TeX implementations was done for NeXTstep, TeXView.app (provided as an example in /NextDeveloper/Demos in NeXTstep) along with InstantTeX (originally by Dmitri Linde, later expanded upon by various individuals).

    Alan Hoenig, author of _TeX Unbound_ speaks highly of NeXTstep and the power of Display PostScript in his book and in articles in TugBoat (newsletter of the TeX User's Group, www.tug.org)

    The problem with the .pdf implementation is that it takes away ones ability to effortlessly extend (for example) a drawing application with (arbitrary) PostScript code and have said code render on-screen.

    Hopefully, InstantTeX or some successor to it and TeXView will be available for GNUstep and will then make it trivial to provide .pdfs for the unwashed masses. LyX, www.lyx.org looks very promishing for this sort of thing as well---though I hope someone 'stepifies the app---I want my vertical menus! support for services! etc.


    William

    --
    Sphinx of black quartz, judge my vow.