Jeremie Pelletier Wrote: > Lutger wrote: > > Jeremie Pelletier wrote: > > > >> watching wrote: > >>> what a pityful sate d is in. this probably shows, that you can't use d > >>> for anything serious and by the time you guys are through discussing > >>> things, people will be using something different for good. too bad > >>> > >> I really don't think so, the very purpose of this IDE I'm developing is > >> to make D easier to use and develop large scale projects with. > >> > >> The only thing still in the way of using D with graphical applications > >> right now is the lack of proper bindings to cross-platform GUI toolkits > >> for D2. > > > > Out of curiosity, did you consider GtkD and QtD? > > > > Have you thought about how to do plugins / extensions already? Of all the > > best software I'm using it seems a large part comes from the extensions. > > > > I wish you all the best with this project, great to see something started > > again on this front. > > I did consider a gtk/gdk approach but not Qt since I never used that > API. However, wxWidgets abstracts both the entire native widgets and > drawing tookits and extends them quite a lot, especially with wxAUI, > that therefore seemed like the best road. > > I have a basic draft for plugins already. I made a base Component class > template to define abstract factories for the different component types > such as Language, Compiler, Linker, Librarian and Plugin which each > define a specific interface. > > It's a really simple API but it works great, components will be able to > register observers at different points in the IDE to implement their > functionalities. > > Jeremie
Well, QtD works well for D2, and I must say that Qt is a very easy API to learn.
