On Wed, Nov 4, 2009 at 5:13 PM, Koen Deforche <[email protected]> wrote:
> Hey all,
>
> We are very pleased to announce the release of Wt and JWt 3.0.0 !
>
> You can download it from the usual place.
>
> Wt 3.0.0 does not differ in too much from Wt 2.99.5, except for
> several bug fixes. JWt 3.0.0 profits from the same bug fixes and we
> have worked on improving its documentation to bring it to the same
> level as Wt's. As always, we owe you for the bug reports, test cases,
> and in several cases also bug fixes.
>
> Read the post (on our brand new blog) for more details on what is new
> in Wt 3.0.0, and also what to expect from us in the near future:
>
> http://www.webtoolkit.eu/wt/blog/2009/11/04/wt_and_jwt_3

Great news!

Will you include the blog webapp as an example, or as a separate
download in the future?

Regarding the Debian packaging, do you have a release plan for the
future? I. e. is it "new versions of Wt will be released every 3
months", or "new versions of Wt will be released when we feel we have
something valuable, be it next week or in 6 months". Not that I care
about numbers (3.0, 3.1, 3.2.87, etc) but about binary compatibility:
Wt usually breaks binary compatibility with each release, which makes
it quite unfit for packaging as a shared library (and I really dislike
libraries packaged as static libraries).

> With that out of the way, we can finally play with Pau's wtdesktop!

Cool.

My code is available at gitorious (
http://gitorious.org/wtdesktop/wtdesktop ). Will you hack publicly (i.
e. at gitorious or in the public master branch at webtoolkit.eu), or
will you do further development in private? If you'd ratherhack in
your private repo, then suprise us with something awesome, it's OK by
me, but please tell me now. My spare time is very scarce and I'd hate
to use it to develop something for Wt, then find you were doing the
same thing, or it won't be useful because of some changes in Wt.

The latest code at gitorious tried to implement automatic port
selection (by requesting a new http server on port 0, as Wim
suggested) but it does not work. Due to the async'ness of Qt, the
WebKit browser starts before the WServer is availaable, therefore I
had to use signals and slots Unfortunately, I was unable to get Boost
signals and slots communicate with Qt signals and slots, and I've been
very busy since then. The error might be obvious.

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to