Menu
▾
▴
Re: [Wxdevide-devs] discussing wxDevIDE publicly
|
From: Nuklear Z. <nuk...@gm...> - 2009-07-26 02:59:33
|
I think that waiting a little is a good idea. we should decide what we will say when we make the announcement. i think that we should let people know that wxDev-C++ will be the current "stable use" version for a while. maybe we could report our findings of using wine? yes we defenatly need to talk about wxDevIDE. i took a look at the code and then i felt overwhelmed and kinda quit. some of the delphi stuff is duplicated over an already exsisting C++ solution. Tstringlist could be replaced with wxArrayString, unless there is a viable reason we need to keep the other one or that the wx version is too unstable. i have not seen that it is. also in keeping the interface the same it will mean configuration dialogs too. most generally for the compiler this is easy from what i have seen, but the editor is a different matter. we can't make it a clone, but that is not the point. we have an issue with the [editor dialog]&[editor] combo. do we just MAKE the dialog as Devish as possible and pass it to the ide or do we make a template class and have the plugin fill it out. obviously if we don't use a plugin for this there is no problem, but, planning for the future makes things a lot easier. I am strongly leaning toword building two editor plugins side by side. one uses XSTC, the other wxRTF. initially the calltips and autocompletion will be stubs in the rtf version. it will not color syntax either. but the scintilla lexing code can be reused and the coloring code can be revamped. the calltips and autocompletion will need to be created, but that won't be a big issue right away. my biggest concern is keeping the plugin flexible to manage with another editor realistically. we can put an extended configuration dialog in the editor dialog for more control over the specific behavior of a plugin editor. (like home() and homext()) the rtf editor will not have the second version. also the menu bar can set some of the functionality. basically the rtf version will become a light plugin and the XSTC one a fully featured one. This is primarily an effort to keep the editor plugin api realistic and reasonable. what xml library are we going to use? i have used TinyXML in the past because it is small and light weight, but expat is distributed with wxWidgets. i also know of exceres and libxml. there is a wx wrapper for both tinyxml and libxml on wxcode. i looked at expat and felt that it was straing to use but i wasn't too prepared to directly handle a c library at the time. i know there is a wx xml api too, i don't know anything about it, does it use expat? in wx2.6 the docs had an unstable api warning, is it still the same? we need to remember the form designer in this too. is it going to be xml driven, do we need to use xpath? does anyone know whats up with wxWidgets adding wxScintilla to their trunk? i know the name makes a lot more sense than wxStyledTextCtrl, but they are the same thing. i use wxScintilla and keep it up-to-date with the current verison of scintilla. i hack the inclusions and recursive prevention header macros so it will build in dev and CB and add the newest languages to wxscintilla.h. there was a little hack i needed to put into wxScintilla.cpp or Scintillawx.cpp to make the newer scintilla's work. unless someone else is keeping up with it too, which i haven't seen any evidence for, i have the most current version. so i use it instead of STC for everything. (and keep XSTC up with it.) which do we use? it looks like either will work with wxWidgets soon. Those are my conserns right now. more debate has yet to come of course. i am still doing some housekeeping. i got fedora11 installed and fought with mp3 playback. i finally figured out how to make it work in xine. i am back to working on a text editor i started last time i was using linux because i need something more powerful than gedit and it is the perfect excuse to drive XSTC. dual booting is the best way i know of to keep the cross platform code working as it should on both platforms and keeping the system related case sensitivity in linux compliant. also what about the website. i can built it if someone can design the interface, but i am no graphic designer. do we copy the wxDev-C++ one or? i now have a server on bluehost, we could put it on there, is that a good idea? it gives us full control over the backend, i have a linux server with apache 2.2 and php5 running. we could use ruby-on-rails, ruby gems, mod_python over just php and there is an sql database too. is any of that stuff necessary for what we need to put on the website? the current one has been neglected for a year, so its probably time to think about it. i have not needed to work with a database, so that would be a learning experience for me, but that is partly why i put up a website of my own. That covers what's on my mind, hope i didn't bore anyone too much. Nuklear On Sat, Jul 25, 2009 at 6:14 PM, Tony Reina <tb...@gm...> wrote: > Yes, I've had the exact same thoughts. > > I suppose my preference would be to wait until a week or so after we > release 7.0 to make any announcement about wxDevIDE. My thought is that we > shouldn't steal 7.0's thunder. Also, I'm not sure if people will be hesitant > to upgrade if they think there is a forthcoming new IDE. > > In reality, when Nuklear and I tested wxDev-C++ with Wine under Linux, it > performed quite well. The biggest problem we had was that the makefiles > weren't properly written (since the libs and compilers were different on > Linux). However, it is possible to manually alter the makefile and get the > projects to compile and run just fine. So Wine is a viable (albeit not > ideal) alternative for the present time. > > Finally, since Nuklear is the lead on wxDevIDE, I wanted to give him a > chance to do the formal announcement (unless he wishes to defer to one of > us). > > Nuklear? Any thoughts? > > -Tony > > > > On Sat, Jul 25, 2009 at 4:56 PM, Esteban Aguilar B. <nab...@ya...>wrote: > >> I said that I may not be that much involved with wxDevIDE, but I'm not >> sure of this yet; as wxDeCpp 7 is getting closer, I'm actually feeling a >> little more entusiastic about wxDevIDE again. >> >> That said, would it be a good idea to start discussing this project more >> publicly? As always, people ask ( >> http://wxforum.shadonet.com/viewtopic.php?t=24962) about wxDevCpp not >> being multiplatform and its kind of bad not giving any answers to them. >> >> Or, would it be better to wait for the final 7.0 relase of wxDevCpp to >> make the announcement? >> >> >> >> ____________________________________________________________________________________ >> ¡Obtén la mejor experiencia en la web! >> Descarga gratis el nuevo Internet Explorer 8. >> http://downloads.yahoo.com/ieak8/?l=e1 >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Wxdevide-devs mailing list >> Wxd...@li... >> https://lists.sourceforge.net/lists/listinfo/wxdevide-devs >> > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Wxdevide-devs mailing list > Wxd...@li... > https://lists.sourceforge.net/lists/listinfo/wxdevide-devs > > |
