Multiple themes and img f:url-norewrite

Hi group:

First, a request for including a configuration of multiple themes using
properties or something like that ( I miss the epilogue-servlet.xpl :( ).

Second, a weird behaviour came across when I was porting an app from 3.6
to 3.7. The external css included via link needed url-norewrite=true and
the external imgs were not working with this attribute. I could view
them only if they were under the orbeon path (/apps/myapp/...).

Regards.


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws

On Oct 30, 2008, at 8:17 PM, Rodrigo Ojeda <[hidden email]> wrote:
> First, a request for including a configuration of multiple themes
> using properties or something like that ( I miss the epilogue-
> servlet.xpl :( ).

Could you share with us some more details regarding your need for
multiple themes? One way to have different themes for different parts
of your site is to have different epilogues. This can be
done with a main page flow which delegates processing to other sub-
page flows, as done in the examples that ship with Orbeon Forms.

> Second, a weird behaviour came across when I was porting an app from
> 3.6 to 3.7. The external css included via link needed url-
> norewrite=true and the external imgs were not working with this
> attribute. I could view them only if they were under the orbeon path
> (/apps/myapp/...).

We would really need more information about this one to able to
reproduce the problem.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws

Alessandro Vernet escribió:

On Oct 30, 2008, at 8:17 PM, Rodrigo Ojeda [hidden email] wrote:
  

First, a request for including a configuration of multiple themes
using properties or something like that ( I miss the epilogue-
servlet.xpl :( ).
    

Could you share with us some more details regarding your need for
multiple themes? One way to have different themes for different parts
of your site is to have different epilogues. This can be
done with a main page flow which delegates processing to other sub-
page flows, as done in the examples that ship with Orbeon Forms.

  

For example, I have 2 applications on http://myhost/orbeon/myapp1 and http://myhost/orbeon/myapp2. I extracted the epilogue-servlet.xpl from the orbeon-resources-private.jar and I put it in the config folder. Then, I added more alternatives, for example, <p:when test="starts-with(request-path, 'myapp1'"> and the same for others applications.But that "hacky" style it's not so friendly. When I talked about a configuration for multiples themes I meant some changes in the properties-base.xml file, for example:

<property as="xs:anyURI"  name="oxf.epilogue.theme.myapp1" value="oxf:/config/theme-myapp1.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme.myapp1" value="true"/>
<property as="xs:anyURI"  name="oxf.epilogue.theme.myapp2" value="oxf:/config/theme-myapp2.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme.myapp2" value="false"/>

or:

<property as="xs:anyURI"  name="oxf.epilogue.theme" application-name="myapp1" value="oxf:/config/theme-myapp1.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme" application-name="myapp1" value="true"/>
<property as="xs:anyURI"  name="oxf.epilogue.theme" application-name="myapp2" value="oxf:/config/theme-myapp2.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme" application-name="myapp2" value="false"/>

Something like that.

Second, a weird behaviour came across when I was porting an app from
3.6 to 3.7. The external css included via link needed url-
norewrite=true and the external imgs were not working with this
attribute. I could view them only if they were under the orbeon path
(/apps/myapp/...).
    

We would really need more information about this one to able to
reproduce the problem.

  

For example, I have the images and the css files under /var/www/imgs and /var/www/css (for sharing with others apps not under orbeon). In version 3.6 linking an external css was quite simple adding <link rel="stylesheet" type="text/css" href="/css/myapp1.css"/> and in 3.7 I had to add the attribute f:url-norewrite="true". In addition, the css worked perfectly under 3.6 in FF2 and IE7 and it half worked under 3.7.

For images, it's other history. They aren't working outside the orbeon "influence":

/var/www/img/icons/...
<img alt="" border="0" src="/img/icons/shopping-cart-zip.png" f:url-norewrite="true"/> ----> works on 3.6, not in 3.7
<img alt="" border="0" src="/img/icons/shopping-cart-zip.png"/> ------> not works in both

/<orbeonpath>/apps/myapp1/img/icons/...
<img alt="" border="0" src="oxf:/apps/myapp1/img/icons/shopping-cart-zip.png"/> works in both

I hope the new explanations had been more clear.

Alex
  

Thanks for your time, Alex.
Regards.


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws

Rodrigo Ojeda wrote

For example, I have 2 applications on http://myhost/orbeon/myapp1 and
http://myhost/orbeon/myapp2. I extracted the epilogue-servlet.xpl from
the orbeon-resources-private.jar and I put it in the config folder.
Then, I added more alternatives, for example, <p:when
test="starts-with(request-path, 'myapp1'"> and the same for others
applications.But that "hacky" style it's not so friendly. When I talked
about a configuration for multiples themes I meant some changes in the
properties-base.xml file, for example:

<property as="xs:anyURI"  name="oxf.epilogue.theme*.myapp1*"
value="oxf:/config/theme-myapp1.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme*.myapp1*"
value="true"/>
<property as="xs:anyURI"  name="oxf.epilogue.theme*.myapp2*"
value="oxf:/config/theme-myapp2.xsl"/>
<property as="xs:anyURI"  name="oxf.epilogue.use-theme*.myapp2*"
value="false"/>

This is one way to do it. The downside, I guess, it that you need to change the epilogue, which means that every time you upgrade Orbeon Forms you'll also need to merge those changes. But I am not sure that I have a better alternative to suggest :).

Rodrigo Ojeda wrote

/var/www/img/icons/...
 ----> works on 3.6, not in 3.7
 ------>
not works in both

Is this with separate deployment? Otherwise this should work in 3.7 as well. Have you tried with the nightly builds? If the problem persists with the nightly builds, could you send us an example that runs in the sandbox, making a reference to some image that ships with Orbeon Forms?

Rodrigo Ojeda wrote

<img alt="" border="0" src="oxf:/apps/myapp1/img/icons/shopping-cart-zip.png"/> works in both

This should not work, at least if you put it as is in HTML. Do you have this code somewhere else?

Alex