From: Simon Strandgaard <neoneye@...>
Date: 2004-07-06T02:35:12+09:00
Subject: Re: [ANN] aeditor 1.0 released

On Monday 05 July 2004 19:07, Curt Hibbs wrote:
> Simon Strandgaard wrote:
> > > Can I ask you again to the exact reason why another fully evolved
> > > editor like SciTE will not do ?
> >
> > Im obsessed by ruby. I want to be able to write plugins in Ruby.
> > I want to be able to do changes in the editor core via plugins.
> > It is not possible with Scintilla to have so much freedom in the
> > plugins. What I want is maybe emacs ala ruby?
> >
> > At some point it could be interesting to integrate my editor widget into
> > freeride, and see what happens.
>
> It would, indeed, be interesting to see an aeditor freeride plugin. One of
> the goals of freeride is to be an IDE written in ruby. Obviously, aeditor
> fits right into that mold! If you decide to give it a go, we (the freeride
> developers) will be happy to answer your questions and provide whatever
> assistance we can.

I need to enhance the editor sligthly more, before I give it a shot.
Here is a very optimiztic plan, in no paticular order:
I will first experiment with supporting different encodings, such as
unicode, big5, sjis.. etc. 
I will port my old undo/redo/macro system to the new editor.
I will add line folding (my old editor had arbitary folding).


> You mentioned that you want to have editor plugins. Do you have this
> already? The reason I ask is because freeride is entirely plugin based. Its
> plugin management is handled by a completely independent piece of code we
> call FreeBASE (pun intended) which handles plug loading, dependencies, and
> inter-plugin communications.

no, I don't have any plugins yet.
I have looked at your plugin system earlier, and found it interesting.


> Someday we are going to make a separate RubyForge project for FreeBASE to
> make it more visible and accessible.

If I understand you correct, freebase is a standalone plugin architecture ?


> If you don't already have a plugin system, then you should consider
> FreeBASE. Doing so would not only save you a lot of time, but would make
> integration into FreeRIDE much easier.

I have considered it, but not come to any conclusion.

The kind of plugins I imagine, which will need to interact with the lower
layers of editor could be:
coverage/profiling.. will have to color each line, and keep track of 
profiling information per line.
cvs-annotate.. will have to keep track of version-numbers per line.
abstract-syntax-tree.. pointers between the model and the ast.
custom editing modes.. which has control of cursor movement.
These things have to dig deep into the model.

There are probably many more possible plugins.

--
Simon Strandgaard