Re: [Xswt-developer] extensions

[<ha...@id...>]

> -----Original Message-----
> Subject: Re: [Xswt-developer] Thanks and regression testing
> Cc: xsw...@li...
> Message-ID: <449...@co...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Without seeing your code I can't comment in detail, but is 
> there a way to not use static fields?  Designers tend to view 
> static fields as evil and in the context of Eclipse, this is 
> magnified.
> ...
> Maybe this situation doesn't apply to what you did (I can't 
> tell without seeing the code), but I wanted to make sure we 
> discussed it.

When a plugin contributes an extension, it will affect the extended plugin
"globally", similar to changing a static field. In this case, it adds
objects to a list, which the receiver uses for some purpose. There are three
contributions: IDataParser, imports to ClassBuilder and ScriptingEngines. I
think we should decide case by case if the technique is OK. I don't have any
strong feeling about this, there are two requirements: ensuring XSWT can run
without the XswtPlugin and support these extensions.

> 1) The Great Renaming that we discussed.  (Making all plugins 
> and packages start with net.sf.xswt.)

I'll leave this one to you. It's better done without too many people
involved.

> 2) The XSWT style sheet proposal / implementation.

I'll take a look at your suggested syntax, and see if I get some inspiration
:-) I think my last thought on this was that it would be a lot easier if we
had an element tree, instead of doing pull parsing (my own framework
supported copying/inserting/transforming nodes from other parts of the
tree).
 
> 3) Start coming up to speed on the XSWT editor code base.

With only two weeks left before my vacation, I think I'll have to wait.

> 4) Documentation.

Are you thinking of a separate document or as javadoc?

> > I have hacked together a pnuts extension module, based on XOM (XML 
> > parsing) + TagSoup (converts ugly HTML to XHTML), ... it supports
> > simple UIs for fetching and displaying data from GET-based web services.
> >   
> This would make an awesome screencast!  :-)

I'll try to think of a good example, to inspire people.

Hallvard