On Tuesday 02 June 2009 13.59.59 Peder Hedlund wrote:
Quoting Nick Copeland
<nickycopeland(a)hotmail.com>om>:
David Horvath has put together a front end to the
bristol
emulations. It is written in C# using Mono and GTK:
No disrespect for his work (and it looks really nice), but with the
slight controversy and overhead of Mono I would've liked a pure GTK or
QT solution.
I even hacked up a crude Xdialog app
(
http://www2.park.se/~peder/files/Bristol) for AVlinux that probably
could be improved by someone better than me.
This is no attack on you, just some general OT toughs that made me think about
toolkits and other geeky words: :-)
IMHO, toolkit issues are one of the really big problems when talking about
"Linux on the desktop" and making people try it. I wonder how many times I see
text like this when developers and fans describes applications to the public
(IE. home pages): "Myapp is a GTK/Gnome/FLTK application that...", or
"...application written in C++ with the Qt4 framework..." in the first
meaning.
What do a musician coming from Windows or Mac think when they see stuff like
this? Perhaps "GTK, is that a new communication standard?, or maybe "is
framework a plugin standard?"
When I try to convince people to use Linux stuff, they often say that "I don't
want to learn new systems" after looking at the apps, not realizing that one
for example use File/Open and so on in almost every app no matter OS. No
wonder that they think things are scary when Gtk, Gnome, KDE, QT, C/C++ and
other non usage related stuff shows up early in the description of the
programs - it's like begging that the app should continue to be used only in
the Linux Geek Club.
Look at "http://www.ardour.org/", that's the way to do it. The whole front
page is dedicated to the people that are supposed to use the program, not
geeks and other hard core computer nerds. When Windows and Mac people see that
page, then they can relate to the information.
Jostein