Re: [Xweb-developers] Reactivating development

[murphee (W. Schuster) <wer...@ne...>]

>> Peter Becker wrote:
>> murphee wrote:
>>> Your bus described in the presentation -- is that a Bean InfoBus?
>> Nope, but it was influenced by it InfoBus (and jEdits EditBus);
>> Webbuilder was designed to be very extensible and something like
>> that was necessary for that;
> What was the reason not to go with an InfoBus? I am currently trying to
> understand the Bean world and I wonder if I should use some of the ideas
> in XWeb itself.

InfoBus is basically for connecting data sources; if I remember 
correctly, it was built by Lotus (for their e...-something Java office
suite) and then donated (or something like that) to Sun ... who 
immediateley started working hard on ignoring it... sometimes I really
don't understand what the people at Sun are thinking (same thing with
Jini, which, after the first months of press-brooha, was simply 
ignored...);

Well, anyway the Bus & Channel structure in Webbuilder is for
sending Events; the idea was basically stolen from jEdits EditBus;
One thing I changed was to allow for several channels; the reason
was to make the whole thing scaleable; if all Events are sent on one
bus, everyone gets every Event (as far as I understood EditBus); if
the application reaches a certain amount of traffic, that must be
limiting performance;



>> Generally updating input files, like regenerating them from DB
>>  sources, ...
> I don't see that as compelling, a little UNIX script would do the same.
> Of course being able to call XWeb from Ant is nice to create
> cross-platform solutions, but I don't see the need for a further
> integration.

hmmm... OK;


 > The Ant task as you described -- just called the main
> process from within Ant, seems quite appropriate. Maybe some extra
> options like configuring the baseURL or some parameters might be helpful.

yup; currently it can only set the previewFlag (I think);


>> Oh yeah... running JTidy before Xweb would be useful, if you want
>> to import non-XHTML input files (this would make XWeb more userfriendly,
> I defintely want JTidy support within XWeb, it seems to be too important
> to need extra tools. The XHTML requirement for things like the generic
> stylesheet coming with the distribution is a bit of a drawback.

Hmm... how do you want to integrate JTidy into XWeb? Simply call it 
before using an input file? Or if the XML Parser complains that the
file is not well formed;

> chance to be found than yet another SF project without any activity. But
> it's your choice of course. And there is the licensing issue, at the
> moment XWeb is still public domain. The thing with licenses is that I
> don't really want to care, but sometimes I feel I should :-)

er... when you say public domain, you mean GPL? (Can't remember what
XWebs license was...);


murphee
-- 
Werner Schuster (murphee)
Student of SoftwareEngineering and KnowledgeManagement
Maintainer of the OGO-JOGI Project @ http://ogo-jogi.sourceforge.net/