Space after <xforms:output>

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Space after <xforms:output>

Erik Bruchez
Administrator
Henrik,

 > I think customizable rendering of XForms Controls would be a great
 > selling point (at least it would be for me!). And it's allready 80%
 > there with the CSS and divs done. When I get around to looking at
 > your css in more depth, I'll make sure to share my notes with all of
 > you.  Just one question: I assume the naming, behaviour and
 > positioning of the <div>s are fairly stable at this point?

I wouldn't quite assume that, because we had for a long time a plan to
address this bug/feature:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304727&group_id=168&atid=350207

The purpose of this is to help styling by consistently providing a
container around every control, which we don't do at the moment.

No single solution is perfect with regards to styling, unfortunately.

-Erik

--
Orbeon Forms - XForms Everywhere
http://www.orbeon.com/blog/




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Space after <xforms:output>

Erik Bruchez
Administrator
In reply to this post by Henrik Pettersen
Henrik,

 > seems to me like it would be beneficial for users of Orbeon Forms to
 > be able to configure how the XForms controls are rendered. The
 > one-size-fits-all approach might not be appropriate for many
 > websites, where design is of greater importance. Other devices, such
 > as screen-readers and mobile/cell phones, are not so focused on
 > design and might benefit from more consistent rendering.

Well, we used to do all this in XSLT, which had the drawback of being
quite slow. So instead we opted for a fixed markup output configurable
with CSS. Neither solution is perfect (the current one because of CSS
and CSS implementations deficiencies), but at least this one is
reasonably fast.

Note that besides HTML controls, we use almost strictly <div>, <span>
and <label>. Just do a "view source" of your page in the web browser
to see what it looks like.

 > Not having done the research, I am assuming it is a question of
 > overriding the default CSS (and perhaps javascript?). When I get a
 > chance to have a look at it, I shall post my findings here.

Check xforms.css.

 > Also, if Orbeon was to facilitate the customization of XForms
 > controls through declerative configuration files / documentation, I
 > believe this would be a strong selling point of "XForms with AJAX"
 > over the XForms browser, where this is not posssible.

Yes it would be nice ;-)

-Erik

--
Orbeon Forms - XForms Everywhere
http://www.orbeon.com/blog/




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Space after <xforms:output>

Henrik Pettersen
In reply to this post by Erik Bruchez
> The purpose of this is to help styling by consistently providing a
> container around every control, which we don't do at the moment.

Ah, I see. I'll take a look at it.

> No single solution is perfect with regards to styling, unfortunately.

Couldn't agree more - A problem possibly solved by some carefull use of divs and custom CSS ?

Henrik

On 11/21/06, Erik Bruchez <[hidden email]> wrote:
Henrik,

> I think customizable rendering of XForms Controls would be a great
> selling point (at least it would be for me!). And it's allready 80%
> there with the CSS and divs done. When I get around to looking at
> your css in more depth, I'll make sure to share my notes with all of
> you.  Just one question: I assume the naming, behaviour and
> positioning of the <div>s are fairly stable at this point?

I wouldn't quite assume that, because we had for a long time a plan to
address this bug/feature:

http://forge.objectweb.org/tracker/index.php?func=detail&aid=304727&group_id=168&atid=350207

The purpose of this is to help styling by consistently providing a
container around every control, which we don't do at the moment.

No single solution is perfect with regards to styling, unfortunately.

-Erik

--
Orbeon Forms - XForms Everywhere
http://www.orbeon.com/blog/





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws





--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Space after <xforms:output>

Erik Bruchez
Administrator
Henrik Pettersen wrote:
>  > The purpose of this is to help styling by consistently providing a
>  > container around every control, which we don't do at the moment.
>
> Ah, I see. I'll take a look at it.
>
>  > No single solution is perfect with regards to styling, unfortunately.
>
> Couldn't agree more - A problem possibly solved by some carefull use of
> divs and custom CSS ?

Well, that's just one of the imperfects solutions ;-)

-Erik

--
Orbeon Forms - XForms Everywhere
http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
12