John Labenski wrote: > Ok, lets make a wxluaedit module with the two files wxledit.h/cpp in it. Thanks a lot! When the module is there, i will fix the wxluacan sample to use it, what more can i do :-( What can we do with the files in the art directory? > I would not want to maintain two copies of the same > thing > Just stick to wxstedit, if its not available, don't compile the module. Is that actually possible with bakefiles/makefiles? > 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?) > Notebook is not needed. > File open/save > Run scripts > Debug them? > That very much. > Scripts are run in main thread? I think for general use this is good enough. > Safety issues? > Don't know what you mean by this? > Want toobar and menubar? > Nice to have but for a simple version control nothing fancy would be needed > Need output window for errors > Yes, that is a needed. And especially a step mode for debugging. And i don't know what wxLuaIDE can do, but making breakpoints would be real cool. If possible, i think we can add a modeless version of wxLuaIDE in the module, people can use that without much trouble. One more request :-) A way to set the default place to open scripts files. Very likely already there? > >> 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? > Right, i think a dummy wxTextCtrl when wxStedit is not available would be ideal. > > 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. :) > I was like that, but now that i know it is just going to /usr/local/ i feel more save. But i agree it is risky. Normally there is also an install prefix option in configure. I used that a lot at work on solaris, where becoming root to "install what i think might be oke" is out of the question :-) So you can always test using the install scripts being non root. > > 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. > Now that would be handy indeed.
Klaas ------------------------------------------------------------------------- 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
