BeanBox is the JavaBeans container provided in the Beans Developer Kit
from Sun. In it, you can throw around Beans in a (minimalist) visual
component editor, and it was intended as a prototype / example to help
people make tools that used JavaBeans components.
Everything WOBuilder does (html rendering notwithstanding) is pretty
easy (not fast, but not hard) to do in a run-time changeable way. It
just takes some infrastructure work to make the application useable, and
ideally wysiwyg.
Cg.
-----Original Message-----
From: Anjo Krank [mailto:anjo.kran..-online.de]
Sent: Friday, December 13, 2002 6:43 PM
To: Christian Gruber
Cc: 'Anjo Krank'; 'Anders Peterson'; 'Ulrich Köster'; 'Euan Maxwell';
woproject-de..bjectstyle.org
Subject: Re: WOBuilder replacement.
Am Freitag, 13.12.02, um 23:31 Uhr (Europe/Berlin) schrieb Christian
Gruber:
> It doesn't have to be WYSIWYG, it just has to manage all the resources
> of a component nicely. It can be a bean-box app, for all I care, if
> you
> create a JavaBean that wrapps and "stands-in" for the WO. In that
case
> you do have a visual paradigm, but obviously not rendered. All
> Design-time stuff. It's still nice.
I don´t really know what a "bean-box" app is, but once you have the
.api files, you should be able to make a list like the WOBuilder
component inspector. This may well be the reason for the .api files in
the first place.
And the column-list at the bottom should also be do-able with a bit of
introspection. But you certainly won't get the kind of integration you
get with WOBuilder. And certainly not without recompilation...
Cheers, Anjo
This archive was generated by hypermail 2.0.0 : Fri Dec 13 2002 - 19:13:30 EST