RE: [FR-devel] Editor API?

[Curt Hibbs]

Laurent Julliard wrote:
>
> Well actually we do have a sort of an embryo editor API. We currently
> use the Scintilla widget as an editor. The low level binding stuff is
> in plugins/System_GuiRenderFox/fxscintilla/scintilla_wrapper.rb and
> must not be touched.
>
> Beside that there is
> plugins/System_GuiRenderFox/fxscintilla/scintilla.rb in which Rich
> started to put some higher level stuff and I continued to add thing in
> there myself for the debugger,... I think this is acceptable to put
> all the editor level thing in there for the moment. At least we know
> it's in there and it will be easy to relocate the code in another file
>   when need be.

Hal,

Laurent, Rich, and I are in the process of hashing out a fairly aggressive
gameplan for getting an initial version of FreeRIDE released. Regardless of
the details of the gameplan (which we will post shortly), I see you as
playing a key role.

You mission, should you decide to accept it, is to self-destruct in 30
seconds and disavow any knowledge of... [oops, wrong venue :-)]

Seriously, when we roll out the first version of FreeRIDE I anticipate
(hope?) that we will generate some excitement among our fellow Ruby
developers. Some of them, I hope, would be sufficiently intrigued to want to
try their hand at writing some FreeRIDE plugins to privately implement their
own pet features, and some of those might be captivated enough to officially
sign on to help us with the further development of FreeRIDE.

But in order for that to happen, we need to make it easy for them to learn
how write FreeRIDE plugins (we don't want them to give up in frustration).
Without going overboard, I think we can accomplish this with two documents
on the wiki:

- A Developer HowTo: a document on the wiki that shows the interested
developer's how to create, debug, and use a FreeRIDE plugin.

- A brief internal editor api quick-reference.

If you could codify the essential parts of internal editor api (enhancing it
as needed,
per Laurent's suggestions) and create a simple api reference doc on the
wiki, we'll be half way there (well, probably 75% there).

Is this something you'd be interested in doing?

Curt