Hi,
I noticed that compared to 3.7.1 release, in the nightly builds the file theme-portlet-fr.xsl is no longer present in the config directory of orbeon-resources-private.jar. My guess is that this was done while renaming property oxf.epilogue.theme.portlet has been to oxf.epilogue.theme.embeddable (see thread http://www.nabble.com/oxf.epilogue.embeddable%3Dtrue-leads-to-non-XML-pipeline-output-td24219871.html). But now there is no longer a standard theme available that can be used in embeddable mode; i.e. one that surrounds output with a <xhtml:div class="orbeon-portlet-div">. There is a theme-embeddable-examples.xsl available but that has links to orbeon.css and to Home. Am I correct here and if so, any chance that a theme-embeddable.xsl could be introduced, preferably in WEB-INF/resources/config? TIA Jeroen Hoffman -- 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 |
Administrator
|
Jeroen,
You can put your own my-theme-embeddable.xsl and change the property oxf.epilogue.theme.embeddable to point to that file. Just like you can put your own my-theme.xsl and change oxf.epilogue.theme to point to that file. If you are using the "apps" directory structure, you can also put your theme-embeddable.xsl in your app directory (like FR does; see the theme-embeddable.xsl in resources/apps/fr). Would that do the trick? Alex |
Alessandro Vernet wrote:
> Jeroen, > > > Jeroen Hoffman wrote: >> Am I correct here and if so, any chance that a theme-embeddable.xsl could >> be >> introduced, preferably in WEB-INF/resources/config? >> > > You can put your own my-theme-embeddable.xsl and change the property > oxf.epilogue.theme.embeddable to point to that file. > > Just like you can put your own my-theme.xsl and change oxf.epilogue.theme to > point to that file. > > If you are using the "apps" directory structure, you can also put your > theme-embeddable.xsl in your app directory (like FR does; see the > theme-embeddable.xsl in resources/apps/fr). > > Would that do the trick? (i.e. presence of a ready-to-use embeddable theme) has dropped by deleting theme-portlet-fr.xsl (although in the private jar). So I was actually asking if a replacement for theme-portlet-fr.xsl could be entered into your nightly distribution. Call it a request for enhancement :-) What do you think? Jeroen -- 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 |
Administrator
|
Jeroen,
So right now we have: * config/theme-embeddable-examples.xsl (used for the examples) * apps/fr/theme-embeddable.xsl (for Form Runner) Would theme-portlet-fr.xsl be different from these two? -Erik On Mon, Aug 10, 2009 at 2:47 AM, Jeroen Hoffman<[hidden email]> wrote: > Alessandro Vernet wrote: >> >> Jeroen, >> >> >> Jeroen Hoffman wrote: >>> >>> Am I correct here and if so, any chance that a theme-embeddable.xsl could >>> be introduced, preferably in WEB-INF/resources/config? >>> >> >> You can put your own my-theme-embeddable.xsl and change the property >> oxf.epilogue.theme.embeddable to point to that file. >> >> Just like you can put your own my-theme.xsl and change oxf.epilogue.theme >> to >> point to that file. >> >> If you are using the "apps" directory structure, you can also put your >> theme-embeddable.xsl in your app directory (like FR does; see the >> theme-embeddable.xsl in resources/apps/fr). >> >> Would that do the trick? > > Yes this the solution, I understand that. However I feel that functionality > (i.e. presence of a ready-to-use embeddable theme) has dropped by deleting > theme-portlet-fr.xsl (although in the private jar). > > So I was actually asking if a replacement for theme-portlet-fr.xsl could be > entered into your nightly distribution. Call it a request for enhancement > :-) > > What do you think? > Jeroen > > > > -- > 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 > > -- 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 |
So the former config/theme-portlet-fr.xsl has moved to it's application, that's it, no? Makes sense. In the used deployment all apps are removed from the distribution so apps/fr/theme-embeddable.xsl is not available.. but the solutions are there so no worries. Thanks guys Jeroen Erik Bruchez wrote: > Jeroen, > > So right now we have: > > * config/theme-embeddable-examples.xsl (used for the examples) > * apps/fr/theme-embeddable.xsl (for Form Runner) > > Would theme-portlet-fr.xsl be different from these two? > > -Erik > > On Mon, Aug 10, 2009 at 2:47 AM, Jeroen Hoffman<[hidden email]> wrote: >> Alessandro Vernet wrote: >>> Jeroen, >>> >>> >>> Jeroen Hoffman wrote: >>>> Am I correct here and if so, any chance that a theme-embeddable.xsl could >>>> be introduced, preferably in WEB-INF/resources/config? >>>> >>> You can put your own my-theme-embeddable.xsl and change the property >>> oxf.epilogue.theme.embeddable to point to that file. >>> >>> Just like you can put your own my-theme.xsl and change oxf.epilogue.theme >>> to >>> point to that file. >>> >>> If you are using the "apps" directory structure, you can also put your >>> theme-embeddable.xsl in your app directory (like FR does; see the >>> theme-embeddable.xsl in resources/apps/fr). >>> >>> Would that do the trick? >> Yes this the solution, I understand that. However I feel that functionality >> (i.e. presence of a ready-to-use embeddable theme) has dropped by deleting >> theme-portlet-fr.xsl (although in the private jar). >> >> So I was actually asking if a replacement for theme-portlet-fr.xsl could be >> entered into your nightly distribution. Call it a request for enhancement >> :-) >> >> What do you think? >> Jeroen >> >> >> >> -- >> 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 >> >> -- 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 |
Administrator
|
Jeroen,
Exactly: this avoids having code specific to one application (here "fr") that uses a different portlet epilogue (used to be config/theme-portlet-fr.xsl) if the request path starts with /fr. This way Form Runner is not a "privileged" application and all applications are treated the same. Look at it as social equality for applications ;). Alex |
Free forum by Nabble | Edit this page |