This is Interesting: Free Magazines for Graphics designers and webmasters  


Home > Archive > Mozilla XML > April 2005 > xforms build help





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author xforms build help
Andrew Douglas

2005-04-04, 12:35 pm

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..
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.
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.

Any help would be greatly appreciated.
-Andrew


Aaron Reed

2005-04-04, 12:35 pm

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....refox/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
>
>

Aaron Reed

2005-04-04, 12:35 pm

Ok, I just did a Firefox build.

I did it just like a mozilla build, other than I had to change these things:

1) Added ". $topsrcdir/browser/config/mozconfig" as my top,
non-commented line in .mozconfig
2) in my .mozconfig I changed MOZ_CO_PROJECT and --enable-application to
be browser instead of suite
For example:
mk_add_options MOZ_CO_PROJECT=browser
ac_add_options --enable-application=browser
3)in addition to checking out mozilla/client.mk I checked out
mozilla/browser/config/mozconfig. THEN I did "cd mozilla" and then
"make -f client.mk pull_all" followed by "make -f client.mk build".

and remember that you need: ac_add_options
--enable-extensions="default,xforms,schema-validation" in your
..mozconfig to build xforms.

After building, XForms worked for me just fine.

Please let me know if you still have problems.

--Aaron

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..
> 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.
> 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.
>
> Any help would be greatly appreciated.
> -Andrew
>
>

Andrew Douglas

2005-04-04, 12:35 pm

I don't know what step did it, as all the config settings were pretty much
there (maybe the pull_all got something that I didn't have before I tried
building seamonkey), but it worked! I really appreciate the hand holding :)

I'll let you know what tests I get created shortly. Thanks again.
-Andrew

"Aaron Reed" <aaronr@us.ibm.com> wrote in message
news:cugjcu$lk03@ripley.netscape.com...[color=darkred]
> Ok, I just did a Firefox build.
>
> I did it just like a mozilla build, other than I had to change these
> things:
>
> 1) Added ". $topsrcdir/browser/config/mozconfig" as my top, non-commented
> line in .mozconfig
> 2) in my .mozconfig I changed MOZ_CO_PROJECT and --enable-application to
> be browser instead of suite
> For example:
> mk_add_options MOZ_CO_PROJECT=browser
> ac_add_options --enable-application=browser
> 3)in addition to checking out mozilla/client.mk I checked out
> mozilla/browser/config/mozconfig. THEN I did "cd mozilla" and then
> "make -f client.mk pull_all" followed by "make -f client.mk build".
>
> and remember that you need:
> ac_add_options --enable-extensions="default,xforms,schema-validation" in
> your .mozconfig to build xforms.
>
> After building, XForms worked for me just fine.
>
> Please let me know if you still have problems.
>
> --Aaron
>
> Andrew Douglas wrote:


Allan Beaufour

2005-04-04, 12:35 pm

Hi Andrew,

I can see that you and Aaron got FF working, so I'll stay out of that :)

On Thursday 10 February 2005 17:30, Andrew Douglas wrote:
> 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.. :)


As Aaron said, the nightly XPI-build will get you what's in trunk, stay with
that. I'll have some goodies coming up next week I hope :)

> 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.


My plan is to do a weekly "XForms update" each Monday from now on, on my blog
(http://beaufour.dk/blog). I'll try to sum up what has happened the previous
week -- bugs on the way, bugs checked in, etc. It works in theory, let's see
whether I can make it happen in practice :)

--
Allan Beaufour
Novell Denmark

Novell, Inc., the leading provider of Net Business Solutions.

www.novell.com
Andrew Douglas

2005-04-04, 12:35 pm

Excellent news about the blog update. Bonsai is great but there's nothing
like hearing what's going on from "the horse's mouth".

As far as my testing goes.. I've run several svg tests with xforms beside it
and everythings fine.. what I haven't gotten working is any "built in"
integration of the two (I know there are other ways around that such as
javascript, xslt, etc.). For example something like the following would be
great it if it actually worked:

.... header/namespace declarations..

<svg:svg>
<svg:text style="blah">
<xf:output value="Hello World" />
</svg:text>
</svg:svg>

Obviously there are some xf tags that wouldn't work in this scenario, but
using output like this would rock. Alternatively, I can't get <xf:ouptut> to
output actual svg content for the life of me.. generally it breaks on tag
issues or I get nothing at all. I can send some "complete" broken examples
if you think it might help to visualize what I'm trying to do with it.

I'm sorry for posting this here (in fact it's quite likely this is more of
an svg issue than xforms). I really am working on test cases that are valid
but maybe I'm missing something obvious that would help make this kind of
integration work too.
-Andrew

"Allan Beaufour" <ABeaufour@novell.com> wrote in message
news:mailman.1108115820.11178.mozilla-xml@mozilla.org...
> Hi Andrew,
>
> I can see that you and Aaron got FF working, so I'll stay out of that :)
>
> On Thursday 10 February 2005 17:30, Andrew Douglas wrote:
>
> As Aaron said, the nightly XPI-build will get you what's in trunk, stay
> with
> that. I'll have some goodies coming up next week I hope :)
>
>
> My plan is to do a weekly "XForms update" each Monday from now on, on my
> blog
> (http://beaufour.dk/blog). I'll try to sum up what has happened the
> previous
> week -- bugs on the way, bugs checked in, etc. It works in theory, let's
> see
> whether I can make it happen in practice :)
>
> --
> Allan Beaufour
> Novell Denmark
>
> Novell, Inc., the leading provider of Net Business Solutions.
>
> www.novell.com



T Rowley

2005-04-04, 12:35 pm

Andrew Douglas wrote:
> As far as my testing goes.. I've run several svg tests with xforms beside it
> and everythings fine.. what I haven't gotten working is any "built in"
> integration of the two (I know there are other ways around that such as
> javascript, xslt, etc.). For example something like the following would be
> great it if it actually worked:
>
> ... header/namespace declarations..
>
> <svg:svg>
> <svg:text style="blah">
> <xf:output value="Hello World" />
> </svg:text>
> </svg:svg>
>
> Obviously there are some xf tags that wouldn't work in this scenario, but
> using output like this would rock. Alternatively, I can't get <xf:ouptut> to
> output actual svg content for the life of me.. generally it breaks on tag
> issues or I get nothing at all. I can send some "complete" broken examples
> if you think it might help to visualize what I'm trying to do with it.


Non-svg children of a svg container won't draw anything, as painting
goes through a svg paint propagation scheme at that point, so anything
that doesn't implement the nsISVGChildFrame interface won't be notified
to draw. If you place the non-svg content in a <svg:foreignObject> then
it should be drawn correctly.

Looking at the SVG specification, I couldn't see if what we currently
implement is what should be happening for compound documents or not.
Compound documents structured the other way around, with svg as the
"embedded language" should work fine with our current implementation.

If you could make the full examples of what you're experimenting with
available it would be useful as we try to figure out the correct behavior.

Thanks.

-tor
Andrew Douglas

2005-04-04, 12:35 pm

Okay, so that's good stuff! I've uploaded a sample using foreignObject. It's
very close to what I want, but it seems like implementing the svg interfaces
would rock even more. Note: you'll need xforms and svg support for this.

http://artforms.progressivex.com/mozilla/sample01.xml

I'm working on translating the calculator demo to use svg.. some of that
will need to output dynamic svg.. so once I get to that point I'll post it.
I'll also post some "wouldn't it be nice" versions too.

Thanks for the info!

-Andrew


"T Rowley" <tor@acm.org> wrote in message
news:cuj3ac$qio1@ripley.netscape.com...
> Andrew Douglas wrote:
>
> Non-svg children of a svg container won't draw anything, as painting goes
> through a svg paint propagation scheme at that point, so anything
> that doesn't implement the nsISVGChildFrame interface won't be notified
> to draw. If you place the non-svg content in a <svg:foreignObject> then
> it should be drawn correctly.
>
> Looking at the SVG specification, I couldn't see if what we currently
> implement is what should be happening for compound documents or not.
> Compound documents structured the other way around, with svg as the
> "embedded language" should work fine with our current implementation.
>
> If you could make the full examples of what you're experimenting with
> available it would be useful as we try to figure out the correct behavior.
>
> Thanks.
>
> -tor



daa

2005-04-04, 12:35 pm

Andrew Douglas wrote:
> Okay, so that's good stuff! I've uploaded a sample using foreignObject. It's
> very close to what I want, but it seems like implementing the svg interfaces
> would rock even more. Note: you'll need xforms and svg support for this.
>
> http://artforms.progressivex.com/mozilla/sample01.xml


just a note - i do a nightly svg+webdav+xforms ( extensions=all) build

http://ftp.mozilla.org/pub/mozilla....v-xform-GDI.zip

dave
Allan Beaufour

2005-04-04, 12:35 pm

On Friday 11 February 2005 14:44, Andrew Douglas wrote:
> Excellent news about the blog update. Bonsai is great but there's nothing
> like hearing what's going on from "the horse's mouth".


:) Just posted by first update. Comments are more than welcome.

> As far as my testing goes.. I've run several svg tests with xforms beside
> it and everythings fine..


I haven't had time to play around with XForms+SVG, so I'm looking forward to
follow your explorations!

--
Allan Beaufour
Novell Denmark

Novell, Inc., the leading provider of Net Business Solutions.

www.novell.com
Sponsored Links


Copyright 2003 - 2008 forum4designers.com  Software forum  Computer Hardware reviews