2 Mar
2008
2 Mar
'08
12:01 p.m.
Hi all,
After googling for a while, I realize that the collapsing/expanding
trick is a quite vaste issue!
Please, is it possible to force XWiki to deliver collapsed panels? Or
even better: is it possible to set a panels to be delivered , by
default, collapsed or expanded?
Thanks!
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
2 Mar
2 Mar
12:07 p.m.
On Mar 2, 2008, at 12:01 PM, [Ricardo Rodriguez] Your EPEC Network ICT
Team wrote:
Hi all,
After googling for a while, I realize that the collapsing/expanding
trick is a quite vaste issue!
Please, is it possible to force XWiki to deliver collapsed panels? Or
even better: is it possible to set a panels to be delivered , by
default, collapsed or expanded?
Yes, that's what we do now.... :) Check in edit mode for example,
there are panels that are collapsed. Edit those panels and you'll see
how it's done.
Moreover we even remember when a user has collapsed/expanded a panel
in a cookie... :)
-Vincent
12:41 p.m.
Vincent Massol wrote:
Yes, that's what we do now.... :) Check in edit
mode for example,
there are panels that are collapsed. Edit those panels and you'll see
how it's done.
Moreover we even remember when a user has collapsed/expanded a panel
in a cookie... :)
I'm really starting to enjoy this stuff... :-)
Thanks! I see what you say: XWiki syntax help has the clues... even
though I don't see them right now :-)
I've also reached http://openrico.org/, what also seems of maximum interest.
By the way: XWiki syntax help seems to have some problems to expand
under Safari 3.0.4 (5523.15), Mac OS X 10.5.2. It works fine when
accessed from Panels, but it doesn't expand "sub-accordions" (Titles,
Paragraphs,...) when access in edit mode. Could you reproduce this
problem over there?
Thanks!
--
Ricardo Rodríguez
Your EPEC Network ICT Team
3 Mar
3 Mar
12:10 a.m.
[Ricardo Rodriguez] Your EPEC Network ICT Team wrote:
Vincent Massol wrote:
> Yes, that's what we do now.... :) Check in edit mode for example,
> there are panels that are collapsed. Edit those panels and you'll see
> how it's done.
>
> Moreover we even remember when a user has collapsed/expanded a panel
> in a cookie... :)
Hi,
I am afraid I am not able to understand how this is done.
There is a JavaScript script at the end of the panels show as collapsed
"by default". It must be togglePanelVisibility which is controlling the
collapsed state, but I am not able to understand how. For instance, the
XWiki Syntax Help panel reads:
<script type="text/javascript">new Rico.Accordion(
'xwikisyntaxhelp',
{panelHeight:'max'}
);togglePanelVisibility((document.getElementById('xwikisyntaxhelppanel')).getElementsByTagName(
'div').item(0));</script>
As far as I see here, if there are no child nodes in the accordion, it
is not possible to establish a "collapsed" state for the panel. Or I am
not able to find how.
Please, how could I collapse a panel as simple as...
#panelheader('Consumidores/as')
item 1
#panelfooter()
Thanks you so much for your help,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
12:36 p.m.
Hi,
I've temporarily solved the issue by:
1. Creating a new macro.vm file and storing it in the folder of the skin
used by the virtual xwiki. This avoid to modify the original macro.vm stored
in /templates.
2. Creating a new macro: #panelheaderc. It is just the same code than
#panelheader but $expanded is set to "collapsed".
I am not able to pass this parameter to #panelheader or/and
#largepanelheader. Keep trying...
Best,
Ricardo
--
View this message in context:
http://www.nabble.com/collapsed-panels-tp15786535p15799971.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
1:43 p.m.
Hi Ricardo,
On Mar 3, 2008, at 12:36 PM, [Ricardo Rodriguez] wrote:
Hi,
I've temporarily solved the issue by:
1. Creating a new macro.vm file and storing it in the folder of the
skin
used by the virtual xwiki. This avoid to modify the original
macro.vm stored
in /templates.
2. Creating a new macro: #panelheaderc. It is just the same code than
#panelheader but $expanded is set to "collapsed".
I am not able to pass this parameter to #panelheader or/and
#largepanelheader. Keep trying...
Yes you're right. I've checked and we have no panel macro that accepts
a collapsed/expanded status. This would be a good addition.
Feel free to create a jira issue for this and to attach a patch to
it! :)
Thanks
-Vincent
2:39 p.m.
vmassol wrote:
Yes you're right. I've checked and we have no panel macro that accepts
a collapsed/expanded status. This would be a good addition.
Feel free to create a jira issue for this and to attach a patch to
it! :)
Thanks, Vincent,
I'll do that as soon as I better understand how these panels work. My "trial
and error" approach is a bit dangerous so far!
In a previous message here I've proposed to create a new macro.vm file in
the skin folder. This doesn't work. It stopped here after a servlet
container restart. I have had to move the macros to /templates/macros.vm.
So, I've not avoided to edit the original file. And this makes the changes
hard to follow.
I am also facing some doubts with CSS behavior. Namely, those classes
defined in colorblack.css and used in panels macros.
I will keep this thread posted event though I will create a JIRA issue about
this.
Cheers,
Ricardo
--
View this message in context:
http://www.nabble.com/collapsed-panels-tp15786535p15804131.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
2:50 p.m.
On Mar 3, 2008, at 2:39 PM, [Ricardo Rodriguez] wrote:
vmassol wrote:
You can use #includeMacros("maropagename")
-Vincent
Yes you're right. I've checked and we have no panel macro that
accepts
a collapsed/expanded status. This would be a good addition.
Feel free to create a jira issue for this and to attach a patch to
it! :)
Thanks, Vincent,
I'll do that as soon as I better understand how these panels work.
My "trial
and error" approach is a bit dangerous so far!
In a previous message here I've proposed to create a new macro.vm
file in
the skin folder. This doesn't work. It stopped here after a servlet
container restart. I have had to move the macros to /templates/
macros.vm.
So, I've not avoided to edit the original file. And this makes the
changes
hard to follow. I am also facing some doubts with CSS behavior.
Namely, those classes
defined in colorblack.css and used in panels macros.
I will keep this thread posted event though I will create a JIRA
issue about
this.
Cheers,
4 Mar
4 Mar
12:20 a.m.
Vincent Massol wrote:
You can use #includeMacros("maropagename")
Used! It works fine with this line in each panel...
#includeMacros("XWiki.Macros")
XWiki.Macros contents the new macros and /templates/macro.vm remains
untouched.
I keep working on a panels macro that accepts a collapsed/expanded status.
Perhaps this doubt is silly but, must a JIRA issue about this be created
in XAPANELS, XE or XWIKI?
Thanks for your help,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
8:47 a.m.
On Mar 4, 2008, at 12:20 AM, [Ricardo Rodriguez] Your EPEC Network ICT
Team wrote:
Vincent Massol wrote:
XWIKI (i.e. Core), since it'll be located in the templates dir.
Thanks
-Vincent
You can use #includeMacros("maropagename")
Used! It works fine with this line in each panel...
#includeMacros("XWiki.Macros")
XWiki.Macros contents the new macros and /templates/macro.vm remains
untouched.
I keep working on a panels macro that accepts a collapsed/expanded
status.
Perhaps this doubt is silly but, must a JIRA issue about this be
created
in XAPANELS, XE or XWIKI? 
6 Mar
6 Mar
4:01 a.m.
[Ricardo Rodriguez] wrote:
vmassol wrote:
Also see http://jira.xwiki.org/jira/browse/XWIKI-1308
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Yes you're right. I've checked and we
have no panel macro that accepts
a collapsed/expanded status. This would be a good addition.
Feel free to create a jira issue for this and to attach a patch to
it! :)
Thanks, Vincent,
I'll do that as soon as I better understand how these panels work. My "trial
and error" approach is a bit dangerous so far!
In a previous message here I've proposed to create a new macro.vm file in
the skin folder. This doesn't work. It stopped here after a servlet
container restart. I have had to move the macros to /templates/macros.vm.
So, I've not avoided to edit the original file. And this makes the changes
hard to follow.
I am also facing some doubts with CSS behavior. Namely, those classes
defined in colorblack.css and used in panels macros.
I will keep this thread posted event though I will create a JIRA issue about
this.
Cheers,
Ricardo
6136
days inactive
6140
days old
10 comments
4 participants
participants (4)
-
[Ricardo Rodriguez] -
[Ricardo Rodriguez] Your EPEC Network ICT Team
-
Sergiu Dumitriu -
Vincent Massol