Re: [Wxdevide-devs] scintilla multiple documents

[Tony R. <tb...@gm...>]

That sounds great. You may want to look at ScITE to get ideas of how they
handle Scintilla. Do you plan on still using your wx abstraction layer to
access Scintilla?

Also, do you want to handle the wxDevIDE announcement on the wxForum? It's
probably a good time to tell people what we've been up to. Might even
generate some help from other developers.

-Tony


On Thu, Sep 24, 2009 at 9:25 PM, Nuklear Zelph <nuk...@gm...>wrote:

> while i was looking through scintillas api and working on an editor plugin
> api i ran across an interesting functionality that scintilla has. i have
> seen it before, but not explored it any. so i decided to write a simple
> manager class to handle the slight complexity of using it.
>
> scintilla is seperated in a few ways. there is a gui layer, the backend and
> a document. having the document seperated form the rest of the editor allows
> for that same document to be viewed and edited by multiple scintilla
> instances at once. or simply to use one scintilla window to edit multiple
> buffers at once.  it uses reference counting to know when to destroy a
> document. scintilla gives you a void pointer to a document so you cannot
> destroy it yourself.
>
> the usage of the manager class is simple, create an instance, passing your
> scintilla window to it. then when you want to create, destroy or switch
> documents you make a simple function call. all reference counting and
> storage is handled for you. it does not handle multiple views, i don't think
> i want to make it that big. i attached it along with a test program. its not
> complete, i just figured it may be an option we could use with the ide, but
> that may make the editor part more dependant that we want it to be.
>
> the document in scintilla is more than just text, or it would be as easy as
> storing a string. lexers , markers, selected text, possibly more is stored
> in the document, so they are all per document information. possibly codepage
> and line ending and that sort of thing too. so using a multi-buffer single
> window editor approach, this simplifies swapping. just an idea at this early
> stage, we can still use the same basic idea with a different editor, it
> would just require us to manage more of the information ourselves, (or the
> editor plugin handles it anyway)
>
> Nuklear
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Wxdevide-devs mailing list
> Wxd...@li...
> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs
>
>