Mark Baker (
Fri, 5 Sep 1997 14:03:03 -0400 (EDT)

"Two-guys-in-a-loft" apparently got together and decided they weren't
going to wait for somebody to provide the next generation of Object/Web
middleware. WIDL, schmiddle.

Holy Cow. Beans, XML, swimming pools, movie stars.

>In summary, BamBam's competitive advantages are:
> The ability to create and configure sophisticated Java

Yeah, well I guess you *can* do applications if you're a masochist. But
what *else* can you do?

>solely through HTML-like text files (based on a
> standard XML-compliant syntax);
> Exceptional graphics designed for "glossy" branded interfaces:
>including irregular text justification, anti-aliased
> vector-graphics, region-based image compositing, etc;
> Unprecedented control over the layout and positioning of
>components within an interactive environment;
> An open, JavaBeans-oriented framework that allows developers to
>freely add new functionality;
> A dynamic, object-oriented data model that seamlessly integrates
>visual components, server-side data resources
> and client-side functionality;
> A streamable code base that allows fast, no-wait installations
>and proactive optimization of network bandwidth
> usage;
[big snip]

And, look ma, compound documents, drag-and-drop, Beans ...

>Without the multiple windows with which end-users are familiar, most
>HTML-based user-interfaces are clumsy and
> frustrating.

Uh huh.

>BamBam, on the other hand, supports multiple "child" windows. Each child
>window can be dragged, layered, brought
> forward, closed and minimized like traditional application windows.
>This facility allows BamBam applications to have the
> feel of traditional desktop applications even when operating within
>the confines of a Web browser.

It's about time. So the browser really *is* the desktop? Who'da thunk it?

>Drag-and-drop functionality is built into the BamBam framework; no
>additional code is necessary on the part of individual
> components. Any component within a BamBam application can be
>"draggeable". Any other component can be registered as
> a "drop" area. Draggeable components can be constrained to specified
>regions. Drop areas can be defined so as to accept
> or reject certain components based on simple or complex semantic rules.
>Drag-and-drop functionality can easily trigger
> complex application sequences: e.g. calculating total purchase prices
>and checking an inventory database based on items
> dragged into a user's "shopping basket".

This looks like it's shooting past the style-sheet fiasco. It's the
whole Bosak "XML gives Java something to do" thing - but I honestly hadn't
expected to see anything materialize along these lines anytime soon.

I'm in the process of trying to set up Internet Explorer 3.02, since
that's what it currently requires. I'll report back once I find some
time to sit down and have a serious look/play at/with it.


Mark Baker, Ottawa Ontario CANADA.               Java, CORBA, Agents, Beans   

Too many dinosaurs, too few meteors - Seyma Atik