Post by Meinrad RecheisPost by Meinrad RecheisPost by Laurent JulliardMeinrad,
As a matter of fact I had the same thought a while ago when I read the
foxGuib announcement on ruby-talk and I said to myself "wouldn't be nice
if we had this as a plugin in FXRuby".
I think it is a very nice idea and would definitely give FreeRIDE an
advantage compared to the Ruby IDE. I'll take a look at foxGuib myself
and I suggest that you take a look at the FR sources and see how we have
integrated the RDOC browser (see plugins/rubyide_tools_fox_ri/) or the
FXIRB (see plugins/rubyide_tools_fox_irb/). Those were initially
standalone programs that we managed to visually integrate in FreeRIDE.
i will have a look at them.
Post by Laurent JulliardI think you should also tell us how you envisage the integration between
the two from an end-user perspective. That would help us translate this
in terms of technical requirements.
ok. let me have a close look at freeride and the available plugins
first. then i will be able to talk about that.
1) foxGUIb is not a single window application. so it will not
integrate into the FreeRIDE GUI as nicely as fxri for instance. Also
the foxGUIb mainwindow needs much screenspace. The only way that makes
sense is launching foxGUIb as a free floating window. foxGUIb is able
to open up some sub windows like the event editor or its built in Ruby
console.
2) foxGUIb's GUI is very individually styled. would you force me to
change the GUI to conform to FreeRIDE's look and feel?
I'd suggest to start foxGUIb as it is from FreeRIDE. Any code that is
generated by foxguib could be opened by the freeride editor
immediately.
* light integration: freeride just start and stops foxguib and
immediately opens generated source code.
* heavy integration: some parts of foxGUIb become freeride components
such as the event editor and the ruby console.
i'd prefer the light one ;)
what do you think?
I fully agree with you that we should do the light integration. I
doesn't make much sense to embed the windows or panels of foxGUIb in FR.
As to the look and feel it doesn't matter so much for a start. I would
even argue that FR could adopt the foxGUIb look and feel in the long run.
So if foxGUIb is launched as an independent binary programm it is just a
matter of writing a small plugin to start and stop it and establish a
communication mechanism for foxGUIb to give instructions to FR (open a
file, refresh a file,...). Does FR need to give feedback to foxGUIb?
(e.g when pointing to a specific widget variable can we also highlght it
in foxGUIb?
We would also integrate FR in the installers so that the users has
everything in one piece.
Laurent