Comments on: Pluggable styling with SpringSource Slices http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/ The voice of SpringSource Sat, 13 Mar 2010 01:18:34 -0600 http://wordpress.org/?v=2.8.5 hourly 1 By: Andy Wilkinson http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167580 Andy Wilkinson Tue, 14 Jul 2009 19:46:22 +0000 http://blog.springsource.com/?p=2430#comment-167580 @Anoop, no, it won't. There's a chance that Slices will be part of M4, but while it's still a rapidly-evolving prototype we prefer to keep it a separate add-on. That said, we do have plans to start publishing ready-built zip files which will mean you don't have to build from source yourself: you can just unzip on top of dm Server, update the profile, and you're ready to go. @Anoop, no, it won't. There's a chance that Slices will be part of M4, but while it's still a rapidly-evolving prototype we prefer to keep it a separate add-on. That said, we do have plans to start publishing ready-built zip files which will mean you don't have to build from source yourself: you can just unzip on top of dm Server, update the profile, and you're ready to go.

]]> By: Anoop http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167573 Anoop Tue, 14 Jul 2009 07:00:37 +0000 http://blog.springsource.com/?p=2430#comment-167573 Will the slices implementation be part of DM Server 2.0.0.M3 ? Will the slices implementation be part of DM Server 2.0.0.M3 ?

]]> By: Gunnar http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167565 Gunnar Mon, 13 Jul 2009 06:46:03 +0000 http://blog.springsource.com/?p=2430#comment-167565 Cool, thanks for the link! Cool, thanks for the link!

]]> By: Andy Wilkinson http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167564 Andy Wilkinson Mon, 13 Jul 2009 06:43:12 +0000 http://blog.springsource.com/?p=2430#comment-167564 @Gunnar, there's been some discussion on this topic in the past, and it was raised with the OSGi Alliance. Their decision was not to use a prefix but, instead, to create a public registry of headers to prevent clashes. You can read some more about it in Glyn's blog entry: http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/ We'll be registering the Slices-related headers in the near future, and certainly before the M1 release. I've just raised an issue on the dm Server backlog so that you can track this work: https://issuetracker.springsource.com/browse/DMS-1136 @Gunnar, there's been some discussion on this topic in the past, and it was raised with the OSGi Alliance. Their decision was not to use a prefix but, instead, to create a public registry of headers to prevent clashes. You can read some more about it in Glyn's blog entry:
http://blog.springsource.com/2008/11/27/springsource-manifest-headers-registered-with-osgi/

We'll be registering the Slices-related headers in the near future, and certainly before the M1 release. I've just raised an issue on the dm Server backlog so that you can track this work: https://issuetracker.springsource.com/browse/DMS-1136

]]> By: Gunnar http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167563 Gunnar Mon, 13 Jul 2009 06:27:25 +0000 http://blog.springsource.com/?p=2430#comment-167563 Wouldn't it be better to prefix custom manifest headers with "SpringSource-..." to indicate to people that those aren't official OSGi header? Wouldn't it be better to prefix custom manifest headers with "SpringSource-…" to indicate to people that those aren't official OSGi header?

]]> By: Andy Wilkinson http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167547 Andy Wilkinson Sat, 11 Jul 2009 08:22:12 +0000 http://blog.springsource.com/?p=2430#comment-167547 @Dmitry, yes, this is possible too. I've added a new sample to Slices' Git repository in the samples/multiple-styles directory that provides a basic illustration of how this would work. In the sample, there are multiple Slices but, crucially, each is configured with a *different* Slice-ContextPath. This allows the Host to access all of them, rather than only being able to use a single style as was possible in the pluggable styling sample discussed above. I've also updated the Host so that it has a basic style of its own which is defined in the HTML as the default stylesheet. The HTML then lists each of the styles provided by the Slices as an alternate stylesheet as provides a drop-down to allow users to switch between styles. The sample's not perfect as it hardcodes the styles that it expects to be provided by its Slices, but I hope that it illustrates the basic technique. As you can see from the PetClinic Host, it's possible to determine which Slices are available at runtime, so the multiple styles sample could be updated to only offer users a choice of the styles which are actually available based on the Host's Slices. We plan (under DMS-914) to provide a tag library that, among other things, will make accessing a Host's Slices considerably more elegant than it is at the moment. Once that tag library's available, we'll update the PetClinic sample to make use of it, and probably update this sample to only offer the styles that are actually available. @Dmitry, yes, this is possible too. I've added a new sample to Slices' Git repository in the samples/multiple-styles directory that provides a basic illustration of how this would work.

In the sample, there are multiple Slices but, crucially, each is configured with a *different* Slice-ContextPath. This allows the Host to access all of them, rather than only being able to use a single style as was possible in the pluggable styling sample discussed above. I've also updated the Host so that it has a basic style of its own which is defined in the HTML as the default stylesheet. The HTML then lists each of the styles provided by the Slices as an alternate stylesheet as provides a drop-down to allow users to switch between styles. The sample's not perfect as it hardcodes the styles that it expects to be provided by its Slices, but I hope that it illustrates the basic technique.

As you can see from the PetClinic Host, it's possible to determine which Slices are available at runtime, so the multiple styles sample could be updated to only offer users a choice of the styles which are actually available based on the Host's Slices. We plan (under DMS-914) to provide a tag library that, among other things, will make accessing a Host's Slices considerably more elegant than it is at the moment. Once that tag library's available, we'll update the PetClinic sample to make use of it, and probably update this sample to only offer the styles that are actually available.

]]> By: Twitted by springneb http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167539 Twitted by springneb Fri, 10 Jul 2009 17:30:15 +0000 http://blog.springsource.com/?p=2430#comment-167539 [...] This post was Twitted by springneb [...] [...] This post was Twitted by springneb [...]

]]> By: Dmitry Sklyut http://blog.springsource.com/2009/07/10/pluggable-styling-with-springsource-slices/comment-page-1/#comment-167538 Dmitry Sklyut Fri, 10 Jul 2009 17:12:07 +0000 http://blog.springsource.com/?p=2430#comment-167538 What about having multiple styles deployed at the same time? Giving users an ability to choose from number of styles, i.e support for themes. Thanks Dmitry What about having multiple styles deployed at the same time? Giving users an ability to choose from number of styles, i.e support for themes.

Thanks
Dmitry

]]>