D
David Brown
Guest
DJ Delorie wrote:
(except that the Xaw screenshot and information should be moved out of
the limelight - it's fine to make a plainer gui for slower PC's, but
it's poor advertising to have it first in the list!). It's clear there
is a lot more going on with gEDA development than is apparent from the
web site. I still don't think it is likely to be a realistic choice for
my use at the moment, but it's a lot closer than I thought, and appears
to be getting much more usable. It is perhaps the web site and
information that is most in need of updating, rather than the software
itself. Thanks for your time and information, and all your work on gEDA
(even if I don't use it myself, I still think it is an important
project). I'll be looking in at it again in the future.
mvh.,
David
I don't think I can come up with any sensible counter-arguments hereDavid Brown <david@westcontrol.removethisbit.com> writes:
I'm basing this on the single screenshot from the geda website, by
the way
The Gtk GUI still looks mostly like that. The new Motif HID looks more
like this: http://www.delorie.com/pcb/screenshot.png (although the
status line has more in it now).
The Motif HID is new so I haven't had much time to play with
look-n-feel. I kept it minimalist on purpose.
why on earth is the Xaw screenshot still there?
The Xaw GUI is, for some people, significanly faster than the Gtk one
on older hardware. We kept a branch for it so those users could still
use it.
I'd expect a set of toolbars with configurable buttons
Good suggestion.
(with a nicer button label font, if you want labels on the buttons at
all),
Gtk fonts are configurable on a user-level basis, just like Windows.
The Motif HID uses standard .Xdefaults, so you can set the fonts to
whatever you want (even a different font for each button).
Is there any reason for having several GUIs, instead of a single good
cross-platform gui?
A couple. First, lock-in. We already went through the pain of
changing the GUI layer once. Part of the goals behind the HID project
was to *hide* the GUI from the core, as the old gui code polluted the
core a lot, which made it harder to work on the core code. By
isolating the gui code behind an application-specific API, core
development is easier and GUI development stays "clean" of the core.
Second, we actually have eight HIDs at the moment, only two of which
are GUIs. Having two GUI hids proves that the API is properly
designed. We use the same API to handle exporting, printing,
importing, wizards, extensions, etc.
Third, we've discovered that not everyone LIKES the same layout.
Windows users shouldn't be burdened with the Unix conventions. Motif
users shouldn't be burdened by the Gtk style guides. Etc. Some users
want lots of buttons and knobs in the main window (like your toolbar).
Some users want as much screen space dedicated to their board as
possible. HID lets us support different *styles* of GUIs, not just
different toolkits.
Fourth, there's no such thing as a "single good cross-platform gui".
There are acceptable cross-platform guis, but they all result in some
compromise. With HID, you can always take advantage of whatever
extras your native toolkit offers, without having to dumb down to the
least common denominator.
At best, you are going to end up with a lot of
duplication of effort,
There's some duplicated effort, yes. We try to keep the duplicated
parts in the core, if they can be made gui-independent.
and at worst you'll get GUIs that look completely different on
different platforms, with significantly different functionality.
Well, that's one possiblility we consider a bonus
Imagine being able to plug in a pads-compatibility HID if you're a
pads house, or an orcad compatiblity HID if you're an orcad house.
(except that the Xaw screenshot and information should be moved out of
the limelight - it's fine to make a plainer gui for slower PC's, but
it's poor advertising to have it first in the list!). It's clear there
is a lot more going on with gEDA development than is apparent from the
web site. I still don't think it is likely to be a realistic choice for
my use at the moment, but it's a lot closer than I thought, and appears
to be getting much more usable. It is perhaps the web site and
information that is most in need of updating, rather than the software
itself. Thanks for your time and information, and all your work on gEDA
(even if I don't use it myself, I still think it is an important
project). I'll be looking in at it again in the future.
mvh.,
David