Hi,

On 03/06/2017 11:11 AM, Vincent Massol wrote:
Hi guys,

On 6 Mar 2017, at 10:48, Richter, Tobias <rich...@borsi.de> wrote:

Hi Vincent,

thanks a lot for your answer - indeed I`ve tried to find out how to create an 
own navpanel -

but after a lot trial and error the menu-content wasn`t "drag-and-droppable" 
(sry for the bad English) anymore. After a lot more trial and error I found out, that the 
drag-and-drop behavior of

this panel and the Navigation-heading belongs to this function:


#panelheader($services.localization.render('xe.panels.navigation'))

#panelheader means in CSS/HTML --> ID

But the "services.localization.render"- function with the 
'xe.panels.navigation' -String(?) is unfortunately too deep in the xwiki-backend for me. 
It would be nice if you could

Send a link, where this syntax and the meaning of the function is explained in the 
documentation. I know that often "2-lazy-2google" questions are asked - but 
that would be

The step I want to learn next for getting deeper in the backend - for being 
able to customize xwiki more for our company.

To create a panel is very simple: 
http://extensions.xwiki.org/xwiki/bin/view/Extension/Panels+Application

Thank you! Don't know why I missed this.

I now have a Panel "MyNavigation" with panel type "view" and category "navigation". The content part is a copy of the original navigation panel. So, I guess I can start from here and play around with the solutions Marius suggested, right!? There is one difference between the original navigation panel and mine: In my panel there is an extra menue entry "Panels" with "MyNavigation" as a child. In the original navigation panel there is no "Panels" entry in the navigation menue. Can you explain why this is so?

Best,
Willi


The $services.localization.render('xe.panels.navigation’) part is just an API 
call to get a translation key for internationalisation. If you create your own 
panel btw, you’ll get some default content.

You can use:

#panelheader(“My Panel")
…

Thanks
-Vincent


Cheers,

Toby.


That’s nice.

One recommendation though: you probably should create your own panel instead of 
reusing an existing one since when you next upgrade you may get some conflict if 
there are also changes in the officially-provided >Navigation Panel. Not a big 
issue though, you’ll just need to choose your version over the default one if 
you’re asked to choose. Also I case you need the original Nav panel it might be 
best to keep it as is.

Thanks
-Vincent

Cheers,

Toby


Reply via email to