Re: [FR-devel] Editor API?

[Laurent Julliard]

Hal E. Fulton wrote:
> ----- Original Message -----
> From: "Curt Hibbs" <address@hidden>
> To: <address@hidden>
> Sent: Wednesday, September 04, 2002 3:14 PM
> Subject: RE: [FR-devel] Editor API?
>
>
>
> > The docs on the scintilla site are probably your best bet.
>
>
> I'm on it. Will take some digesting. I hope Rich and Laurent
> can answer questions.
>
> Hmm, should the Scintilla people be told that it's been
> wrapped for Ruby? Is the support fairly complete, and would
> they be interested in this (which as I see it is a Scintilla-
> FXRuby bridge)?

The scintilla_wrapper.rb file that we have in FR is up to date. it is 
our own version and contains some enhancement compared to the file in 
FXRuby.

My personal opinion is that Scintilla has a very nice and handy API. 
So my advice is that you look at scintilla_wrapper.rb and have their 
documentation page open at the same time. Go thorugh the code and see 
what kind of functionality is available.

From there, honestly, I don;t known where you should go. Write 
another abstraction layer in between FR and FXScintilla. Why not? My 
problem with this is that a) we haven't used the Editor API much and 
we don;t know how the ideal API should look like and b) would the 
abstraction layer be better than the Scintilla API and why not assume 
that our abstraction layer is the Scintilla APi and if we ever need to 
use another editor one day then you'll write an adapter so that this 
new editor shows an Scintilla like API.

As I said to Rich a few days ago and I re-iterate my view here (And 
Curt is ok with me) we need to implement the source code browser 
plugin and I'm not sure anybody is working on it. Not only is it an 
interesting part of the project bu it will also allow you to 
experiment with the current Scintilla API and then you can decide if 
another layer must be added on top of it and what it should look like.

I *really* want to see a first working release of FR soon. Then we can 
throw the first version away and start a cleaner one if need one. but 
let's get our feet wet first. This is exactly what I'm doing with the 
debugger, learning a lot about incompatibilities between Linux and 
Windows at the Ruby level and if you take the same approach for the 
class/method browser you'll learn a lot as well.

Laurent