You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Ioannis Kanellopoulos <io...@jrc.it> on 2005/09/19 17:35:13 UTC
jetspeed2 navigation
Hello,
We have been evaluating jetspeed 2 for the last couple of months for the
creation of a portal on geographic information, which will include
catalog and mapping services.
We have successfully downloaded and installed jetspeed2-M3 and built the
latest jetspeed2-M4 from source.
platforms include Linux Red Hat ES 4, Mac OSX and WinXP.
We require to have the top level navigation menu (root folders) visible
at all times, instead of having a link through "back to root folder" or
to "root" depending on the decoration use for the layout. Is this
possible? and if yes can you please indicate how we can do this?
We have also some other problems one of which is that we are not able to
connect to mySQL but I will come back to that in another email with more
details.
thanks a lot for the help
Ioannis
--
Ioannis Kanellopoulos
EC-Joint Research Centre
European Spatial Data Infrastructure - ESDI Action
Institute for Environment and Sustainability
TP 262
21020 Ispra(VA)
Italy
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by David Sean Taylor <da...@bluesunrise.com>.
Ioannis Kanellopoulos wrote:
> Hello,
>
> We have been evaluating jetspeed 2 for the last couple of months for the
> creation of a portal on geographic information, which will include
> catalog and mapping services.
> We have successfully downloaded and installed jetspeed2-M3 and built the
> latest jetspeed2-M4 from source.
> platforms include Linux Red Hat ES 4, Mac OSX and WinXP.
>
> We require to have the top level navigation menu (root folders) visible
> at all times, instead of having a link through "back to root folder" or
> to "root" depending on the decoration use for the layout. Is this
> possible? and if yes can you please indicate how we can do this?
>
With M4, put a root level menu definition in your root folder.metadata:
<menu name="root-level-menu" regexp="true" options="/*.psml,/*/"/>
Here is another example, a current working directory menu:
<menu name="cwd-level-menu">
<options regexp="true">./*/,./*.psml</options>
<exclude>root-level-menu</exclude>
</menu>
And then in your page layout, reference the menu:
#set($rootMenu = $site.getMenu("root-level-menu"))
#if(!$rootMenu.empty)
#includeTabsNavigation($rootMenu $LEFT_TO_RIGHT)
#end
<!-- CWD Tabs Menu -->
#set($cwdMenu = $site.getMenu("cwd-level-menu"))
#if(!$cwdMenu.empty)
#includeTabsNavigation($cwdMenu $LEFT_TO_RIGHT)
#end
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: J1.6 v J2.0
Posted by Jonathan Hawkins <jo...@hawkinsweb.co.uk>.
Found out how to add a portlet, not sure about adding additional panes etc.
I have built J2 from source this morning, I am assuming that the two
column layout is being used by default, however, all the portlets are
inone column and if I try to move it the right the portlet dissappears.
Any assistance greatly appreciated
Jon
Jonathan Hawkins wrote:
> I am now working on porting our current portal from 1.6 to 2.0 and
> have a couple of questions.
>
> 1. What are the current timescales for a production relase of 2.0
> 2. Our users like the ability to create new panes and add portlets,
> how is this achieved in 2.0, am I missing sometrhing fundamental ?
> 3. In J1.6 I use forwards to target a specific portlet, to become
> JSR-168 compliant how do I target a specific portlet on a specific
> page. We have a portlet where users can add their own hyperlinks
> targetting a spcific portlet.
>
> I'm sure there will be many more questions.
>
> Thanks
>
> Jon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: J1.6 v J2.0
Posted by Jonathan Hawkins <jo...@hawkinsweb.co.uk>.
Perfect, many thanks
Jon
David Sean Taylor wrote:
> Jonathan Hawkins wrote:
>
>> David,
>>
>> Thanks for the info. Can you give me any pointers on the bridges
>> framework to repliocate forward type functionality.
>>
>
> If it can wait til tonight, I'll package up an example app and
> documentation, and send it off to you then
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: J1.6 v J2.0
Posted by David Sean Taylor <da...@bluesunrise.com>.
Jonathan Hawkins wrote:
> David,
>
> Thanks for the info. Can you give me any pointers on the bridges
> framework to repliocate forward type functionality.
>
If it can wait til tonight, I'll package up an example app and
documentation, and send it off to you then
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: J1.6 v J2.0
Posted by Jonathan Hawkins <jo...@hawkinsweb.co.uk>.
David,
Thanks for the info. Can you give me any pointers on the bridges
framework to repliocate forward type functionality.
Cheers
Jon
David Sean Taylor wrote:
> Jonathan Hawkins wrote:
>
>> I am now working on porting our current portal from 1.6 to 2.0 and
>> have a couple of questions.
>>
>> 1. What are the current timescales for a production relase of 2.0
>
>
> in my opinion, the 2.0 release will now be pushed back to end of
> November. Many of my core requirements are still not implemented
>
>> 2. Our users like the ability to create new panes and add portlets,
>> how is this achieved in 2.0, am I missing sometrhing fundamental ?
>
>
> There is a basic portlet selector to add new portlets to a page, but
> currently no menu editor. This is one of the core requirements for a
> 2.0 final release
>
>> 3. In J1.6 I use forwards to target a specific portlet, to become
>> JSR-168 compliant how do I target a specific portlet on a specific
>> page. We have a portlet where users can add their own hyperlinks
>> targetting a spcific portlet.
>>
> Forwards are not a part of the 1.6 spec.
> I really like the concept of abstracting forwards, and have added it
> to the Bridges Framework in 2.0, although this framework is not used
> by any developers afaik
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: J1.6 v J2.0
Posted by David Sean Taylor <da...@bluesunrise.com>.
Jonathan Hawkins wrote:
> I am now working on porting our current portal from 1.6 to 2.0 and have
> a couple of questions.
>
> 1. What are the current timescales for a production relase of 2.0
in my opinion, the 2.0 release will now be pushed back to end of
November. Many of my core requirements are still not implemented
> 2. Our users like the ability to create new panes and add portlets, how
> is this achieved in 2.0, am I missing sometrhing fundamental ?
There is a basic portlet selector to add new portlets to a page, but
currently no menu editor. This is one of the core requirements for a 2.0
final release
> 3. In J1.6 I use forwards to target a specific portlet, to become
> JSR-168 compliant how do I target a specific portlet on a specific page.
> We have a portlet where users can add their own hyperlinks targetting a
> spcific portlet.
>
Forwards are not a part of the 1.6 spec.
I really like the concept of abstracting forwards, and have added it to
the Bridges Framework in 2.0, although this framework is not used by any
developers afaik
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
J1.6 v J2.0
Posted by Jonathan Hawkins <jo...@hawkinsweb.co.uk>.
I am now working on porting our current portal from 1.6 to 2.0 and have
a couple of questions.
1. What are the current timescales for a production relase of 2.0
2. Our users like the ability to create new panes and add portlets, how
is this achieved in 2.0, am I missing sometrhing fundamental ?
3. In J1.6 I use forwards to target a specific portlet, to become
JSR-168 compliant how do I target a specific portlet on a specific page.
We have a portlet where users can add their own hyperlinks targetting a
spcific portlet.
I'm sure there will be many more questions.
Thanks
Jon
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by Randy Watler <wa...@wispertel.net>.
Jacek,
The dev team is in the final stages of the last milestone build. We need
to get a RC1 build out soon and are trying to address the biggest gaps
in the functionality of J2... M4 declarative menus was an example of
this. Yes, it can be challenging to keep up with the changes, even for
us developers. In the end, we hope the drive toward a release is a good
thing for the whole J2 community.
Randy
Jacek Wiślicki wrote:
> Wiadomosc od Randy Watler z 2005-09-19 19:56 brzmiala:
>
>> This functionality has already been built into M4 and declarative
>> menus and is part of the default decorators. Thanks for the input
>> though :-).
>
> As I see, my knowlege is quite out-of-date, although I'm dealing with
> Jetspeed no longer than a month :/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od Randy Watler z 2005-09-19 19:56 brzmiala:
> This functionality has already been built into M4 and declarative menus
> and is part of the default decorators. Thanks for the input though :-).
As I see, my knowlege is quite out-of-date, although I'm dealing with
Jetspeed no longer than a month :/
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by Randy Watler <wa...@wispertel.net>.
Jacek,
This functionality has already been built into M4 and declarative menus
and is part of the default decorators. Thanks for the input though :-).
Randy
Jacek Wiślicki wrote:
> Wiadomosc od Jacek Wiślicki z 2005-09-19 19:50 brzmiala:
>
>> Wiadomosc od Ioannis Kanellopoulos z 2005-09-19 17:35 brzmiala:
>>
>>> We require to have the top level navigation menu (root folders)
>>> visible at all times, instead of having a link through "back to root
>>> folder" or to "root" depending on the decoration use for the layout.
>>> Is this possible? and if yes can you please indicate how we can do
>>> this?
>>
>>
>> I have extended JetspeedPowerTool with a method displaying the
>> current path (each element is presented as a link), e.g.
>> 'root folder' -> 'directory 1' -> 'directory 1.1' -> 'current page'
>> /**
>> * Retrieves a current path in the portal structure in a form of HTTP
>> * links. For velocity macros use: $jetspeed.getCurrentPath()
>> * @author Jacek Wiślicki
>> * @version 2005-09-12
>> * @return current path
>> */
>> public String getCurrentPath()
>> {
>> String basePath = getBasePath();
>> Node currentSite = requestContext.getPage();
>>
>> Vector path = new Vector();
>> buildNodePath(currentSite, path);
>>
>> String displayPath = "";
>> for(int i = 0; i < path.size(); i++)
>> {
>> Node node = (Node)path.get(i);
>> displayPath +=
>> "<a href=\"" + basePath + node.getPath() + "\">" +
>> node.getShortTitle(locale) +
>> "</a> → ";
>> if(node.equals(path.lastElement()))
>> displayPath += " → " + currentSite.getShortTitle(locale);
>> }
>>
>> return displayPath;
>> }
>>
>> It's quite useful, I think...
>
> Oops, I've forgotten about one more method for JPT:
> /**
> * Builds reqursively a node path for a given page.*
> * @author Jacek Wiślicki
> * @version 2005-09-12
> * @param page subsequent page in the iterration
> * @param path Vector stores path elements
> */
> private void buildNodePath(Node page, Vector path)
> {
> Node parent = page.getParent();
> if(parent != null)
> {
> path.insertElementAt(parent, 0);
> buildNodePath(parent, path);
> }
> }
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od Jacek Wiślicki z 2005-09-19 19:50 brzmiala:
> Wiadomosc od Ioannis Kanellopoulos z 2005-09-19 17:35 brzmiala:
>
>> We require to have the top level navigation menu (root folders)
>> visible at all times, instead of having a link through "back to root
>> folder" or to "root" depending on the decoration use for the layout.
>> Is this possible? and if yes can you please indicate how we can do this?
>
> I have extended JetspeedPowerTool with a method displaying the current
> path (each element is presented as a link), e.g.
> 'root folder' -> 'directory 1' -> 'directory 1.1' -> 'current page'
> /**
> * Retrieves a current path in the portal structure in a form of HTTP
> * links. For velocity macros use: $jetspeed.getCurrentPath()
> * @author Jacek Wiślicki
> * @version 2005-09-12
> * @return current path
> */
> public String getCurrentPath()
> {
> String basePath = getBasePath();
> Node currentSite = requestContext.getPage();
>
> Vector path = new Vector();
> buildNodePath(currentSite, path);
>
> String displayPath = "";
> for(int i = 0; i < path.size(); i++)
> {
> Node node = (Node)path.get(i);
> displayPath +=
> "<a href=\"" + basePath + node.getPath() + "\">" +
> node.getShortTitle(locale) +
> "</a> → ";
> if(node.equals(path.lastElement()))
> displayPath += " → " + currentSite.getShortTitle(locale);
> }
>
> return displayPath;
> }
>
> It's quite useful, I think...
Oops, I've forgotten about one more method for JPT:
/**
* Builds reqursively a node path for a given page.*
* @author Jacek Wiślicki
* @version 2005-09-12
* @param page subsequent page in the iterration
* @param path Vector stores path elements
*/
private void buildNodePath(Node page, Vector path)
{
Node parent = page.getParent();
if(parent != null)
{
path.insertElementAt(parent, 0);
buildNodePath(parent, path);
}
}
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: jetspeed2 navigation
Posted by Jacek Wiślicki <ja...@gmail.com>.
Wiadomosc od Ioannis Kanellopoulos z 2005-09-19 17:35 brzmiala:
> We require to have the top level navigation menu (root folders) visible
> at all times, instead of having a link through "back to root folder" or
> to "root" depending on the decoration use for the layout. Is this
> possible? and if yes can you please indicate how we can do this?
I have extended JetspeedPowerTool with a method displaying the current
path (each element is presented as a link), e.g.
'root folder' -> 'directory 1' -> 'directory 1.1' -> 'current page'
/**
* Retrieves a current path in the portal structure in a form of HTTP
* links. For velocity macros use: $jetspeed.getCurrentPath()
* @author Jacek Wiślicki
* @version 2005-09-12
* @return current path
*/
public String getCurrentPath()
{
String basePath = getBasePath();
Node currentSite = requestContext.getPage();
Vector path = new Vector();
buildNodePath(currentSite, path);
String displayPath = "";
for(int i = 0; i < path.size(); i++)
{
Node node = (Node)path.get(i);
displayPath +=
"<a href=\"" + basePath + node.getPath() + "\">" +
node.getShortTitle(locale) +
"</a> → ";
if(node.equals(path.lastElement()))
displayPath += " → " + currentSite.getShortTitle(locale);
}
return displayPath;
}
It's quite useful, I think...
--
pozdrawiam,
Jacek Wislicki
jacek.wislicki@gmail.com
tel.: +48 502 408 444
gg: 2540358
skype: jacek_wislicki
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org