wxdevide-devs

Re: [Wxdevide-devs] editor plugin

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

Actually I like the Notebook parent because I think it fits in with the
concept of a workspace or project space. We should make sure that the
notebook/workspace handler can accept editor objects and RAD designer
objects. So the handle to a notebook is the handle to all of the
files/objects for one user project.

-Tony


On Sun, Sep 27, 2009 at 3:36 PM, Nuklear Zelph <nuk...@gm...>wrote:

> this is a model i came up with today. supposing we decide to use the
> multi-document singe editor approach, we will want to have the notebook
> inside the editor plugin in order to keep trancparency for other editors. if
> we want it to be part of the main gui, then we should scrap the idea,
> because of the normal behavior of a notebook. as far as the notebook is
> conserned there is not much of a difference whether it is in the editor
> plugin or the gui. it has a small api for attaching and removing panels and
> that is not much of a big deal.
>
> with the one doc per editor approach will not be hindered either way we
> create it. the notebook will be in the same place one way or another, so it
> probably depends on what affects it might have on the plugin system
> bandwidth and such.
>
> i am working on the api's mentioned in the picture. the final decision of
> what needs to go where is a ways off right now, the api that any plugin
> would see is not going to change between the two approaches and niether will
> the base editor, but the resulting plugin can only do what it has been given
> resources for, so i am just wondering what we think is the best way to
> design this is.
>
> when i can log into sf.net i'll post the pic onto the editor api page.
>
> 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
>
>

[Wxdevide-devs] editor plugin

[Nuklear Z. <nuk...@gm...>]

my text editor project is now on sf.net
http://sourceforge.net/projects/nztexteditor/
Its inteded to show off XSTC and MultiBook (notebook component)
its also going to help me actaully get the editor/notebook module bult
finally.

the editor plugin based on Scintilla is going to use MultiBook and XSTC. I
am hoping to completely drop wxScintilla/STC support using ExtScintilla.
its a wrapper that takes a pointer to your instance of scintilla and lets
you talk to it via the wxScintilla api. that api will cover the editor api
for wxDevIDE.the purpose of building this api is simply put, STC and
wxScintilla are woefully slow at updating the Scintilla version. I havent
gotten to wxDevIDE yet to see if i can get it running in fedora the text
editor has taken my time. im also helping remodel a trailer house so i have
a bit less time than i would, although the cold wheather is making that
project slow as well. i am going to write a minimalist plugin based on
wxRichText to help stress test the basic plugin api. it will not be fancy,
but it will get the job done. its possible that could grow into a usable
alternative plugin that doesn't require any nonwxwidgets components but i
have no such plans at the moment.

the editor plugin will make use of ExtScintilla, MultiBook and XSTC. I have
to build the first two before it can be a reality, im 1 third of the way
there anyway. MultiBook is half written, the manager stuff is pretty much
done but i had some strange issues with the drawing code. I mostly kept
drawing code seperate from manager code and recently i did some research
into gtk3. and i got qt to build arora 11 on windows, when i realised it
would take very little extra effort to make MultiBook work on those
toolkits too. since i have not run across a notebook that will do any of
the things im trying to do except for the themeing, why not share it. im
probably going to do a gtk2 and 3 version but i have to finish the wx
version so the platform interface is finished.

I have almost got my editor codebase arranged how i want so i can commit to
svn and then i will take a look at the ide. im trying to keep up with my
progress on the blog. i didnt realize how nice those where untill now. im
hoping that the text editor project wont look dead like the ide has so far.

When i get to the ide ill write up a webpage to replace the current website
and possibly build a windows and linux binary for the file release system.
they wont do much but it will make my webpage more convincing.

Nuklear