From: Daan L. <daa...@xs...> - 2004-01-31 02:16:18
|
Dear Eiffel folks, I am the creator of wxHaskell, the Haskell binding to wxWindows that is based c-code written for the Eiffel ewxw binding. As people here seem to discuss the relevance of the ewxw library and wxWindows, I thought that I might throw in my 2cents :-) Given my experience with wxWindows, I would say that it would be a mistake to abandon the ewxw libary and move on to other things like FLTK or Fox or whatever. If one rationally considers the options, the wxWindows library is the best choice for a community based on volunteers. Why? well there are many reasons, but the most important are: wxwindows has a very active community, many contributors, and industrial backup (=> supported and maintained), it has very good ports to windows, unix (gtk) and macosx, it has a very extensive API, and it has native widgets. Compared to other libraries, this is all very good news. Better yet, the Eiffel community has an (almost) working Eiffel binding to wxWindows, so all the hard work is done! Don't give this all up for newest trend, dreams of beautiful designs or "lean-and-mean" libraries! wxWindows is surely not perfect, but is writing a portable gui library yourself, or writing another binding making things better? Automatically generating bindings is nice when you start, but now that the ewxw library is already there, one just need to fix changes which is not that much work. If I were in your position, I would concentrate on making installation of the ewxw library easy, and on nice Eiffel abstractions on top of the basic wxWindows layer. Well, I hope that you all can find a common focus and make this all work without Uwe. In the meantime, maybe you can enjoy some of the Haskell samples and screenshots at <http://wxhaskell.sourceforge.net> which is all based on the work and efforts of the people that worked on the Eiffel ewxw library, and I want to thank you all for your time and commitment! All the best, Daan. On Thu, 22 Jan 2004 14:02:48 +0100, Pascal Poncin <Pas...@t-...> wrote: > it is a pity to read that everyone on the SmartEiffel list seems to > agree that ewxw is a dead project. owever, I think it has produced > interesting results which could be reycled in other and maybe smaller > projects. My interest in this stuff is not yet zero since it offers > many possibilities. Also there even exists a project derived from > ewxw for Haskell led by Daan Leijen: > http://sourceforge.net/projects/wxhaskell/ > I think there exists even a (Haskell specific) Mac port of wx. > However I do not know what the status of the wxHaskell prject is and > whether they still need ewxw to continue work but there So I can > image that ewxw is not entirely worthless and rescuing some parts > worth doing it. A possible way to continue could be to modify the c > layer so that it could automaticall be wrapped using ewg in order to > minimise work amount. > What is unclear about the ELJ stuff is its unclear license status: > There is lots of stuff involving different types of Licenses and I > wouldn't know whether it would be admissible to change the licenses > (e.g. to the current Eiffel Forum Freeware License) in order to make > this issue more transparent for use and reuse. > > Regards > Pascal > > > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > elj-devel mailing list > elj...@li... > https://lists.sourceforge.net/lists/listinfo/elj-devel > |