jboss-dev-forums

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[<roy...@jb...>]

"legolas" wrote : I wrote 2 tags that could be useful for others. One tag, named isNotEmptyRegion, is doing the exact opposite of Julian's original isEmptyTag, it evaluates the body only if the region has content.
  | The second tag, named navigation, adds 2 objects to the pageContext within the scope of the tag. These objects allow the layout developer to iterate over the defined pages, and detect the currently active page. If you are interested in the code please let me know how I can submit them your repository.

Can you archive this and send it over to julien, martin, or me please?

"legolas" wrote : 
  | What is the actual purpose of it, is it merely to define each page and its layout, or is it meant to define the whole navigation structure of the portal including page layout?
  | 

To define each its page and the portlets assigned to it. 

"legolas" wrote : 
  | What are your plans about this?
  | 

Our ears are open. ;-)

"legolas" wrote : 
  | Is it, or will it be, possibile to define a renderer per window?
  | 

I'm not sure we've discussed this idea, and I'm not really sure how this has real-world application. Martin (which is on vacation) may be able to elaborate his thoughts on it.

"legolas" wrote : 
  | To test my layout, I created a simple portlet. Only showing some default text. I followed the instructions in chapter 2 of the reference guide and included the descriptors portlet.xml, jboss-portlet.xml, jboss-app.xml and portlet-instance.xml.
  | Which of these re mandatory?
  | 

The above 3 are. Until we have dynamicity (2.2 Blade), this is the way to deploy your portlets.

"legolas" wrote : 
  | BTW the reference guide, paragraph 2.6, describes that the first part of the instance-ref is the application name as defined in the jboss-portlet.xml, I think it should be the jboss-app.xml, is that correct?
  | anonymous wrote : 
  |   | 
  |   | You are correct. I will change it.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883917#3883917

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883917

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[mholzner <nu...@jb...>]

anonymous wrote : Is it, or will it be, possibile to define a renderer per window?

So far I haven't thought about it. What is the use case? Why would you need to do this ? 


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884547#3884547

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884547

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[martingi <nu...@jb...>]

"legolas" wrote : Also no localisation is provided, I (ab)used the pages name as key for retrieving the actual localized page name.
  | 
I like this approach, because if the page names could be used as a key for retrieval from the page definitions, another benefit would be more simplicity creating links from 'normal' text fragments to already defined pages. At the moment I am creating a new PortletURL for each normal text link to a page, although this is a redundancy since the page is actually already defined.

Or maybe I am missing something here? The only way I see at the moment to access the page definitions is getting the iterator of all pages with JBossRenderRequest#getPortalObjects(). Maybe it would be easier to introduce an accessor like getPageByName(pageName) in order include a link to an already defined page. Furthermore an automated link checking (or simple exception throwing) by the portal could be possible with this, if the page should be not defined anymore.

"mholzner" wrote : So far I haven't thought about it. What is the use case? Why would you need to do this ? 
A scenario for per window rendering might be that you have a window rendering the navigation (which you always want to get displayed and where you don't want to have any decorations) and another window with news and window decorations, where you will let it up to the user whether to minimize it or not.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885192#3885192

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885192

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[mholzner <nu...@jb...>]

anonymous wrote : A scenario for per window rendering might be that you have a window rendering the navigation (which you always want to get displayed and where you don't want to have any decorations) and another window with news and window decorations, where you will let it up to the user whether to minimize it or not.

I would rather put that into a "portlet setting" where the admin and / or user can decide wether to render the portlet with the links for window states and portlet modes or not, when they place the portlet on a page. In other words: it would be a property of the window that decides if there is a maximize link etc. The renderer would be the same, but it would check that window setting. 


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885267#3885267

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885267

[Jboss-dev-forums] [Design of JBoss Portal] - Re: Page info in theme, revisited

[legolas <nu...@jb...>]

Hi,

Sorry for my late response, I also was on holiday. Just before leaving I've send the source archive to Roy.

The difference in renderer in our case, will be that it either does or does not draw a simple border around the content.
I think this could just as well be delegated to the portlet itself and use the empty renderer.

anonymous wrote : "legolas" wrote:
  | 
  | What are your plans about this?
  | 
  | Our ears are open. ;-) 

Just like martingi wrote, I think the page name can be (ab) used as key for retrieving the actual localized name.
Another solution might be to add translations to the *-pages.xml file like:
<page>
  |   <page-name locale="en">Sample</page-name>
  |   <page-name locale="fr">&Eacute;chantillon</page-name>
  |   <page-name locale="de">Probe</page-name>
  |   ...
  | </page>

The latter is used by GridSphere. I don't particularly like this solution because it clutters the configuration file and the former allows one to manage translations in one place.

anonymous wrote : The above 3 are. Until we have dynamicity (2.2 Blade), this is the way to deploy your portlets.
  | 
What do I need to do to override the portlet deployer, one that automigically generates the jboss-app.xml and jboss-portlet.xml files.?


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886535#3886535

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886535