Re: XUL Tag Plugins

Hi Sam,

> I know about tagdef, and I have a DTD for Luxor-XUL,
> I don't know where 
> I got it, or if I made it myself.  I thought it came
> with Luxor-XUL.

  I put together a DTD for Luxor last December as far
as I remember and it's up on the luxor-contrib site.
However, it's only a snapshot and incomplete and it
also can't handle inline XHTML.
 
> The problem with tagdef is that verifying it can be
> a problem.  If it 
> were something closer to:
> 
> <tagdef class=net.sf.something.PhoneField"
> name="phone"/>
> <tag type="phone" id="phone1" color="red" />
> 
> , then you could verify it much easier.
> 
> In any case, since Luxor-XUL is open source, I'm
> betting in a lot of 
> cases, like the phoneField, most people would
> benefit from extending and 
> sharing, but there is always going to be some
> component that only you 
> need, and no one wants to make the whole library
> larger just for you. :)
> 
> It's certainly something that probably should be
> thought out, but maybe 
> the advantages of verification aren't as large as
> the work involved.

  I agree that something needs to be done so you can
check if your XUL documents are valid. For now,
however, it's a low priority for me. Anyone who want's
to work on it is welcome.
 
> I looked up the XBL spec on the W3C site.  It's
> pretty much your 
> standard <!ELEMENT > <!ATTLIST > kind of tags. 
> Embedding the entire DTD 
> in the document would be silly, and I don't think
> there is a standard 
> (at least I didn't see one) that covered augmenting
> a DTD with more tags 
> when referencing an external DTD.

   You might want to look into Relax Schemas,
especially the compact syntax. DTD are pretty much a
"legacy" and not a good choice for newer stuff.
 
> Maybe I'll stop being so lazy and try to hack in the
> ability to do it 
> this way as well, that way my verification scripts
> won't complain about 
> tagdefs.  :)  I want to be able to give the GUI
> designers what they need 
> to make a good GUI without bothering me to code it
> in Swing.  It would 
> just make the entire process more effecient.

  Again your contributions are welcome. I hope to get
Beta 9 out soon.

> I am very impressed and appreciative of the fact
> that you considered 
> WebStart when making this project though.  How do
> you plan on keeping it 
> that way with SWT, or do you?  I've never heard of
> packaging native 
> libraries in a Web Start application, so I would be
> interested in 
> knowing how to do this.

  Please, check the mailinglist archive for an answer.
For a start you might wonna read the IBM
developerworks article titled "Deploy an SWT
application using Java Web Start" @
http://www-106.ibm.com/developerworks/opensource/library/os-jws/

  - Gerald



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01