On 12/17/06, Francesco Montorsi <[EMAIL PROTECTED]> wrote:
> klaas.holwerda ha scritto:
> >> What about just adding the path $(WXLUA) to your include path and then
> >> include this in the header
> >> #include "apps/wxluaedit/src/wxledit.h"
> >> and this in the cpp file
> >> #include "apps/wxluaedit/src/wxledit.cpp"
> >>
> > In that case better copy, since how will users understand such things.
> > Currently i do already set WXLUA (after installing), just to get to the
> > script for generating the bindings.
> > This is part of the Cmake files. But not needed, if using a released
> > distribution, so acceptable.
> > But asking users to have wxLua installed, and the wxLua source to get to
> > the two wxledit files, is a bit to much.
> I agree.
Ok, lets make a wxluaedit module with the two files wxledit.h/cpp in it.
> I also think that having a stock dialog for running wxLua scripts and
> maybe debug them would be very nice. Unfortunately I don't really know
> much about wxLua internals and wxStEdit, so here it is my dumb question:
> do such things need wxStEdit? wouldn't it be possible to add such things
> to "wxlua" module _without_ making it depending on wxStEdit?
The wxStEdit lib provides all the nice wxStyledTextCtrl functionality
that is needed to actually make it work. There's a lot of code to keep
menu/toolbar items updated and I'd hate to have to duplicate it.
Find/Replace is another bit of non trivial code, splitting is also
nice and you have to create your own splitter to get it to work by
refing the editor, the wxNotebook doesn't send enough events so again
wxStEdit has it's own subclassed wxNotebook to make sure menu/tool
items are updated. I would not want to maintain two copies of the same
thing
We could make a dumb wxTextCtrl based editor. I'm still not sure how
much and what functionality is wanted though.
An editor to edit the scripts (notebook too?)
File open/save
Run scripts
Debug them?
Scripts are run in main thread? Safety issues?
Want toobar and menubar?
Need output window for errors
> If it's really required, maybe we could still add it to wxlua module and
> then use wxDynamicLibrary stuff to open wxstedit.dll at runtime, if present.
Wouldn't we still need the #include stedit stuff making wxStEdit a
compile time dependency? Can you subclass classes in DLLs?
> >> It's a little unconventional, but will easily work. The only thing is
> >> that it won't work if you install wxlua to a system directory? Do you
> >> do that?
> >>
> > Yes, that i always do.
> I always do that, too ;)
Ok, I never do, had a really bad experience with an install script
messing up my system years ago and have been afraid of them since. :)
> > You should have a look at krusader, almost the same as windows commander
> > on windows.
> > I use it for almost anything (edit, search, pack, browse dirs.).
> I'm now get used to KATE. It's great I think.
I like Kate too, the one thing I miss is not being able to click in
the output window during a compile to go to the line of an error or
warning easily, I don't think it can do that.
Regards,
John Labenski
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
