Gerry Weaver wrote:
> I think Greg's video does an excellent job of illustrating what
> I'm talking about. It just needs to be a little more comfortable.
> To me, when using a tool like this, you shouldn't need or want
> to switch back to the command line.
Heh, the use of the command line in those videos probably more
reflects the preferences of the video's author than it does
shortcomings in fluid.
I'm something of a command line zealot, and it'll be a cold day
indeed that I switch from vi/make + shell prompts to a GUI/IDE.
I'm trying to avoid a rant on what I hate about IDEs, but I'll
just say using the CLI keeps me close to the compiler, which
as a programmer I feel is important to keep me close to what's
going on under the hood. I also try to avoid being lulled into
sexy GUIs that make things look pretty, while hiding all sorts
of ugly code and complexities that in the end can make a real
mess for porting.
You can use fluid without every having to see the CLI by using
its GUI text editor and using the hotkeys for invoking a predefined
makefile to build and run the app. You still have to manage the
Makefile by hand.
Fluid does what it does well; not aspiring to be a full on IDE,
but rather just a GUI layout program and modest code editor.
The video doesn't really make an effort to show how to avoid
the CLI, in fact rather, it tries underline integrating with it.
But that doesn't have to be the case, and many folks find their
own successful work flows with fluid.
I like that fluid won't try to take over project management,
won't mess up my code directories with little junk file droppings,
and won't meddle with my Makefiles or inject strange code into
my source files.
There are several open source IDEs that I believe some folks here
have integrated with FLTK -- I've seen mentioned here before
Eclipse, DevC, CodeBlocks and some others. I haven't tracked them,
and don't know to what extent they integrate.
Bit if you're looking to make a nice IDE for FLTK, best place
might be to look at what folks have done with the existing ones
to see if there's a fit somewhere, as I think open source IDEs
are trying to be more flexible in supporting multiple GUI toolkits.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
