Re: xforms build help

Andrew Douglas wrote:
> I've got my build environment setup on win32 working great. Now I want more. 
> Any help would be greatly appreciated.
> 
> 1. Building seamonkey locally with xforms support works great, but for some 
> reason building firefox with xforms support built in doesn't seem to work. 
> Is it possible to do this or is there anything special I need to do?
> If this is a dumb newbie question I apologize... it's also possible that I 
> did something stupid.. who knows..

I personally only build Mozilla.  I will do a Firefox build this 
afternoon, but there shouldn't be a build problem since Firefox 
tinderboxes build our .xpi.  I'll let you know if I run into anything 
strange.

> If I'm stuck on seamonkey that's okay, but I'm more of a firefox kinda guy.
> 2. Are there pending patches that you have included in the xpi build or any 
> that you would recommend applying (gecko or xforms related).. there appears 
> to me to be quite a few in the works.. so i feel a bit over my head.. :)
> For example the svg status blog update that says not only what's checked in 
> but what's "lurking". I wouldn't mind helping with maintaining something 
> like that if it would be helpful and folks are interested.

Every patch is 'pending' :)  Most of our patches don't last long once 
they are attached to a bug.  Usually reviewed and corrected and checked 
in within a week.  But we've had some in the recent past that lingered 
for one reason or another.  We'll have to see if we can identify them in 
some way that would be visable to others.  I'll let you know.  If I 
don't, bug me about it until I do :)

Our .xpi is currently built nightly so you should be able to get every 
day's change the next day.  You can get to them by going to: 
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/, then pick the 
latest trunk that has linux, windows or mac xpi's that you are 
interested in.  xforms:insert and xforms:delete just went in yesterday, 
so that is cool.  Very useful elements to be sure!

> 3. I'm very interested in working with compound documents - namely svg and 
> xforms. Before I jump in with both feet, are there any really big holes in 
> this that I should avoid? I'll post any bugs I run into obviously, just 
> trying to avoid too much wasted effort.

We haven't done much on the XForms side with compound documents, yet. 
Maybe the SVG guys have.  Any testcases along those lines would be 
appreciated.  We are very interested in making sure that we play nicely 
with others, but honestly haven't had the time or access to some simple 
testcases to help us to start evaluating how we'd behave.  If you can 
come up with some, that would be great.

> 
> Any help would be greatly appreciated.
> -Andrew 
> 
>