Hey Girish, 2009/9/18 Girish Sheshadri <[email protected]>: > Hello Koen, > > > > First of all you have pulled off a fantabulous job with Witty. > > I think Witty brings C++ closest to a real web development platform as > compared any C++ hack or framework I have seen up until today.
Thanks! And we are always open to suggestions, even if we do not always agree :-) > · Use Regular Make vs CMake > You can see in the Witty Interest group how many people are struggling with > CMake, mind you most of them are not new to open source or building from > source. > When I say Make I mean regular run of the mill > ./configure > make > make install > (And make sure it works J) > The product is fantastic but seriously the building from source process is a > pain. I try out several products every now and then, Witty is really hard to > build for a seasoned hacker. You will have more adoption too. At some point we did you use autoconf (it was contributed by one of our users). But at the same time we wanted also to support Microsoft Visual Studio, and so that clearly did not work. Having said that, I also find that Wt is too hard too install. I wish it was as easy as: $ mkdir build $ cd build $ cmake ../ $ make $ make install That sequence might actually work, sometimes, but usually fails. I fear the culprit is however the boost libraries that are notoriously complex to build with a wide variety of names for their binaries, which then makes it very hard for CMake to find them. But surely our strategy to find and detect what kind of boost libraries are available surely could improve. Could you be more specific about what failed for you, or was it mostly that you are not familiar with cmake ? > · Reconsider the licensing LGPL vs BSD vs GPL > Something as good as Witty should be under more friendlier licensing than > GPL, Mind you I am a great supporter of open source (real open source, BSD > Style) but a less restrictive license like LGPL will help you a lot take > Witty to a whole new level. Chosing a license is hard, and we have considered lots of different options. For now we are committed to the GPL open source + commercial license strategy. It makes our business run and motivates us to make Wt absolutely the best toolkit. I understand that a less restricted license would result in a larger community (but quantity versus quality :-) ). > FYI: Licenses will not help you pay your rent, EMWEB services will. Says you? Regards, koen ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
