Don`t jump to too many conclusions. Things are up in the air. j.dll will still be the core engine and the overall architecture will remain. I suspect wd will also be around for some time to come. Lots more dteails in the new year.
On Mon, Dec 14, 2009 at 3:50 AM, Oleg Kobchenko <[email protected]> wrote: > A few comments. > > > > > From: Dan Bron <[email protected]> > > > > Bill Lam > > > Didn't Chris demonstrate how to do that? (I missed that event) > > > > For those who missed the event: > > > > * There will be one more version of J6 before J7 is released: J6.03 > > * J6.03 will have the new J7 engine (J.dll) but the current front > > ends (j.exe, j.jar etc) > > * In J7, the engine will be packaged as an executable rather than a > > DLL. > > I did not hear that part. It would be real bad not to be able to call j.dll > from other applications (including--but not so critical--COM). > > > * This executable will essentially be a combination of what j.dll > > and jconsole are today. > > * The current frontends are deprecated in J7. > > More specifically, WD is no more. Very sad and surprising, given that > in Chris' words, it is considered one of the best JSoftware desings. > Good news is that it may be re-implemented as an addon with clients > for different platforms, including web. > > > * The primary FE in J7 will be GTK-based. And it's VERY cool. > > * JHS will also be available in J7 > > * Some current functionality may not make it into J7, e.g. J COM > > servers. > > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
