[Schevo-devel] Re: [NAVIGATOR] - Basic Development Documentation

[Patrick K. O'Brien]

Matthew Scott wrote:
> Ilias Lazaridis wrote:
>> I am not sure about at this point, but following the existent structure,
>> SchevoGtk should contain the bindings to Gtk, and an additional
>> "SchevoNavigator" should containt the navigator related code.
>>
>> Keep this in mind for now.
>>
>> I will go deeper into this after finishing with the command-line.
> 
> Devil's advocate time:   :)
> 
> Will SchevoNavigator be dependent solely on SchevoGtk, thus deprecating
> any other navigators (such as the one in SchevoQt), or is the idea
> behind SchevoNavigator to make it agnostic, so that SchevoNavigator
> would be useful across SchevoGtk, SchevoQt, and other UI toolkits
> including any web toolkits, etc?

Good questions.  I'll give you my thoughts, which are open to debate...

The way I see it the navigator itself should be a pretty thin layer that
simply pulls together the building blocks provided by the "binding
layer" (I'm not sure that is the best word to describe how we will
support a GUI toolkit).  So 80% of the functionality should end up in
SchevoGtk, and only 20% in the navigator (or a custom UI for a custom
application).  Because of this, I don't see a need to immediately
separate the two, though that may be a good idea once the first version
is in place.

I also think it makes sense to have a navigator for each GUI or Web
toolkit that we intend to support.  So I don't necessarily see this new
GTK-based navigator replacing the Qt-based one.  It is simply the focus
of my current efforts.

I'm not sure how easy it would be to make a navigator that was agnostic.
 I'm having a hard time picturing something like that.

-- 
Patrick K. O'Brien
Orbtech       http://www.orbtech.com
Schevo        http://www.schevo.org
Louie         http://www.pylouie.org