GEdit OPI plugin

[Yves Jaradin]

> Dear Yves and Trosten, 
>
>   
>> Yves, how realistic do you reckon is it to aim for a IDE which will  
>> actually replace the OPI? Perhaps it would instead also be a useful  
>> goal for the new gedit-plugin to provide something which makes it  
>> more easy for new users to get into Mozart. Later, they may switch to  
>> the Emacs-OPI if necessary...
>>     
> In short term, our goal is not to implement a replacement plugin for
> Oz/Emacs, even if needed. 
> I think we do not have time, resource and skill to do it.
Don't underestimate the power of the community.
"I'm doing a (free) operating system (just a hobby, won't be big and
professional like gnu) for 386(486) AT clones."[Linus Torvalds 1991/8/25]

>  Our goal is
> clearly to develop a plugin for gedit which is, in terms of
> functionalities, between Emacs plugin and "Labo Interactif". 
>
>   
>> For now, it's unrealistic to expect the gedit plugin to replace the
>> Emacs OPI becuase gedit is too Linux-specific. 
>>     
> Yes, it is ! and we do not want to do a cross-plateform replacement IDE
> for Emacs. 
>
>   
>> But, we need some replacement for Emacs at least as a mid-term goal.
>> That's the reason I insist on at least the Oz part of the gedit plugin
>> to be portable and generic enough to support (almost) any plugin on any
>> system for any editor. The experience ecquired with gedit could then be
>> useful to build this replacement, whatever it will be.
>>     
> Yes perhaps but produce a code that will be usable on every plateform
> or arch will conduct to more complex code. Again, it is not the goal we
> want to reach.
>   
Writing completely portable code might be somewhat difficult but at least,
the non-portable parts must be easy to find and replace with a portable equivalent.

>   
>> Yes, that's what I would like but maybe that's too much having this as a
>> starting goal. On the need for another Browser, actually we need, again
>> as a mid-term or long-term goal, a replacement for Tcl/Tk which is
>> getting old and ugly, particularly in recent desktop environments. I see
>> this gedit-specific Browser as a good occasion to decouple the Browser
>> core functionality (dynamically describing values) from the Tk specific
>> stuff.
>>     
> Yes, I'm according with you on that point. We will try to make our code
> undependent of the toolkit used. So if you want to move from gtk to
> cocoa, it will be possible. But may be it is just a dream for the moment.
>   
This should be quite easy. I suppose that the GUI code will be Python/PyGtk running in gedit
while the reflection code will be in Oz. The Python part can be as specific as you want.
The Oz part should naturally not depend on anything GUI related.

> Thanks for all your answers, it is really amazing to see the interest
> you have for the plugin.
>   
Well, I don't really like emacs that much.

> Antoine C. 
>
>   
Yves