O'Reilly Motif Books On-Line and Free 21
MightyMicro writes "According to the Motifdeveloper community site, the O'Reilly Motif Programming Manual and Reference Guide are now available for free download from Imperial Software's site. As Open Motif is also free for Linux (and xBSD), this looks like a valuable resource."
Why people don't use Motif (Score:3, Insightful)
Do you feel that NEdit has suffered from not using more popular libraries, and does it matter to you?
One thing that Motif was getting right... (Score:3, Informative)
Last time I used Motif (about 2 years ago, on Irix) was that it had a working and fairly powerful drag and drop. Granted, they changed the API right in the middle of things, which sucked, but I could (and did) write an application where any user could drag "film rolls" (an object in our system) onto the desktop, and then drag them from the desktop into other programs that knew something about "film rolls" and that program could process the film roll. Programs that didn't know anything about film roll object just got the file name where the film roll was stored, but applications that knew about film rolls got all sorts of other characteristics of the film roll in the drop message without opening the file.
I haven't figured out how to do similar dragging and dropping on the desktop or between applications with KDE or Gnome. I'm pretty sure it's there, but it doesn't seem as integrated as it did on Irix.
Re:Why people don't use Motif (Score:2, Interesting)
The main reason that Mosaic was the first mega successful Web browser was that it was the first to use a GUI toolkit that did not look like crap. It was not actually the first Motif browser but it was the first with Motif look and feel. The other browsers looked like science projects.
Ten years later it is quite possible that Motif's time has come and gone. The Motif look is somewhat dated and the OSF licensing model is certainly dated. Unless it was released as open source sometime I didn't notice you still have to pay for Motif which pretty much rules it out in the Linux world. I don't think that the chances of survival for the non-open source Unix world are very good these days.
What puzzles me is that these toolkits still need a rack of twenty manuals each of which is six inches thick. Its only a goddam menu system!
Re:Why people don't use Motif (Score:2, Informative)
You must have been asleep! It's available for free, but under conditions, and RMS doesn't like the licence...
http://www.opengroup.org/openmotif/license/
http://www.gnu.org/philosophy/motif.html
Re:Why people don't use Motif (Score:1)
Re:A valuable resource for whom? (Score:1, Insightful)
None of that is actually true though. Is there an anything in particular you think KDE does better than Motif?
Re:A valuable resource for whom? (Score:3, Informative)
However, there's no comparison between Motif and. KDE has a distributed object model, a solid foundation (Qt), and a rich set of widgets, including everything Qt provides (including collection classes, network support, and XML support), and KDEs add-ons. Because it's usable in OO languages, extending and adding widgets is a piece of cake.
Cheers,
Re:A valuable resource for whom? (Score:2, Interesting)
http://unix.oreilly.com/news/motif_0400.html
I think his point about legacy code and the fact the Motif is on every UNIX is dead on. You may not like Motif, but odds are your employer might.
Re:A valuable resource for whom? (Score:2)
That was an interesting article. I'm sure Motif won't die any time soon, because there is a lot of code out there that uses it. But tradition will only keep it alive for so long, and for new projects, it's likely to get dumped. Also, some of the comments about Qt are just dead wrong. Qt is not just used to write "software for programmers", in fact the KDE and QT APIs are designed to make it easy to write user friendly software. Qt is actually used for in-house Windows development, and that's how TT make some of their money. His "no documenation" comment is completely wrong. Every class and every method in Qt is documented, and there are also several tutorials and books. And there have been for years. I can see Motif championing legacy applications, but for new projects, Qt is a much more appealing product.
On internationalization, Qt supports Unicode, and GTK is more recently catching up on this.
Truth must be told. (Score:1, Informative)
I know this might sound like a troll, but you can't
expect a sane developer to ship a GUI on time, with
nothing but list boxes, dialogs, text fields, menues and labels.
Some might say that is all you will ever need, or that
you can assemble any other widgets from those basic
ones as needed, but why bother do that when other
toolkits give me property sheets, combo boxes, tabbed views, rich toolbars (dragable, detachable, with animated bitmaps, and even with support for other control embedding.)
rich text support, and entire grids for spread sheet
and database applications. Document/View architectures (aka. MVC)
and rich OO class hierchies.
Guys, the days of hand coding everything are over.
MFC gives me all I need on Win32, and Qt on Unix;
someone else might appreciate Motif, but thank you
very much, not me.
This offcourse goes against the longs standing
trend of clapping for everything new. As always,
O'Reilly gets my respect (I knew about the books
for two months, and I was one of the first volunteers to convert them to PDF from the troff
sources.)
I forgot to add. (Score:1)
along with other goodies.
Does anyone like Motif? (Score:2)
Re:Does anyone like Motif? (Score:1)
Re:Does anyone like Motif? (Score:2)
Legacy Applications (Score:1, Insightful)
Motif? (Score:4, Interesting)
Motif apps, like netscape 4.x, tend to support established X mechanisms for things - like the X resource database (a very good generalised application preferences database, somewhat akin to the windows registry, but less sucky and more human-readable) - they tend to support the editres protocol, they generally integrate better with the X window system Xt infrastructure. Qt and Gtk go off and implement their own half-assed preferences systems and ignore the solid work that exists in X (presumably because Qt and to some extent Gtk are intended to work well on non-X platforms)
It's almost as if the toolkit authors went off and started implementing their toolkits without bothering to study how X had already solved 3/4 of their problems...
If you still have ns 4.x or other motif applications around, fire it up, fire up editres, and have a play around - the end-user dynamic configuation abilities are more still more advanced than either Qt or Gtk, and the only other toolkit that I can think of that is comparably easily end-user configurable at runtime is amiga MUI (and xaw, but that starts out looking quite crappy.)