Re: [xwiki-users] TOC from other Page
that {{context}} sounds like great solution for the needs.
I thought about classes/objects before but it seemed like it would only
obfuscate texts making editability harder for no real gain (like replacing
wiki editor with simple text field for method description).
Descriptions are heavily formatted, with its own signatures, macros and
examples (preview required). With "edit" button for each heading it makes
things nice and easy. Wiki itself is good way to make articles, compatible
with internal code commentaries/intellisense.
Life table, while it might solve merging records from multiple pages (not
clue how) is quite worse then TOC (filtering method names is never required,
finding them with browser Ctrl+F works perfectly if needed and TOC takes
only fraction of space life table does so overview is more clear).
Normally it would deserve it's own customized application. But that is the
part we chose to use wiki pages we have.
--
View this message in context:
http://xwiki.475771.n2.nabble.com/TOC-from-other-Page-tp7601369p7601379.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] TOC from other Page
> http://jira.xwiki.org/browse/XRENDERING-240
not exactly sure but sounds like it would solve it. (Your comment about
{{context}} macro sounds actually better. It could help with more things
then just this.)
> Could you explain your need since there may be other ways of achieving it?
I would like to document widgets for our framework. And now I'm trying to
deal with occasional inheritance. Reasonably easy to write for authors and
readable for implementators.
I changed TOC style so it looks similar to QuickNav here:
http://api.jqueryui.com/dialog/
The "working" idea is to use one {{include}} for each property/method of
base class. That way inherited content is shown on subclass page, TOC is
ok, and we are happy. Downside is it requires to copy all those includes
several times (base is heavy). And if there is new property/method in base
class it is required to manually copy it into all descendants (not that many
but still).
So I was thinking. If I could just get TOC for base class into subclass
page, it might be much better and easier. It would be always "up-to-date",
you would see what makes subclass different, and if you click the base class
TOC it will just take you to the base page heading, seeing all related
properties/methods together.
So my closest idea was something like this:
{{display reference="baseClassPage" section="HbaseClass"/}}
=== subClass ===
{{TOC /}}
--
View this message in context:
http://xwiki.475771.n2.nabble.com/TOC-from-other-Page-tp7601369p7601371.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] TOC from other Page
Probably easy for someone familiar with API.
How can I display TOC from other page? Played with {{include}}, {{display}},
{{context}} but none gives results. ( {{display}} is close if it had
original page as a context instead of "new".) All I get is heading and empty
(or current page) TOC.
There must be a way with some velocity based rendering and cropping specific
header but have no idea how.
Thanks
--
View this message in context:
http://xwiki.475771.n2.nabble.com/TOC-from-other-Page-tp7601369.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
___
users mailing list
users@xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] Wanted pages as siblings
According to http://xwiki.475771.n2.nabble.com/Include-Macro-Usage-tp7597998.html and http://jira.xwiki.org/browse/XWIKI-13148 Is there any switch to make non-existent links create sibling pages rather then children? We are trying to use xwiki as a wiki. Meaning we have many terms that interlinks between each other. Atm. it hits "almost unusable" barrier :/ Using Ecaterina Moraru (Valica) example: [[TestMain]] [[TestMain1]] [[TestMain2]] - new link results in: http://localhost:8080/xwiki/bin/view/Main/TestMain/ http://localhost:8080/xwiki/bin/view/Main/TestMain1/ http://localhost:8080/xwiki/bin/view/Main/TestMain1/TestMain2/ In this case TestMain2 cannot use [[TestMain]] nor [[TestMain1]] links (another great inconvenient for "wiki", but let's put that one aside). Given there is no parent linking, we need to use absolute path for any and all links that actually goes to other branches, which is inconvenient on its own. But with unrestricted "create new links as children by default" it means hell. Even worse, creating new page from link doesn't offer any choice of correcting parent, so atm. non-existent links are liability because they must not be under no circumstances clicked or they create unwanted children where no links will work. And to extend the bad things.. we use templates. There are more of them so we need to restrict templates just to specific departments they are meant for. But template provider's visibility restriction seems absolute. It doesn't extend to children of checked parent. Which is also bad, because we cannot even create children easily as they won't see templates they need to. But it also means [[TestMain2]] from above example cannot even be created using template because with "always child link" it doesn't see templates defined for [[Main]]. I tried to make [[TestMain1]] terminal page even if it's not recommended (nor wanted really) but it didn't help. [[TestMain2]] is still offered as [[TestMain1/TestMain2/WebHome]]. And since it's a child it won't see templates defined for [[Main]] even when it should because we need templates for entire branch, without the need to manually administrate every new nested page created so its pages can use templates as well. Any way out of it? Config param to make new links siblings and [[.TestPage1]] for explicit child would solve the worst problems. Offering the same dialog as for new pages so parent could be fixed manually each time would at least help. But links are already pretty hard to use (again, for a wiki; namely anchors and pages from other branches) to make it even harder (with something like mandatory [[..link]] added to every link there is) Using v.8.0 -- View this message in context: http://xwiki.475771.n2.nabble.com/Wanted-pages-as-siblings-tp7601368.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
[xwiki-users] All links are shown as "WebHome"
I'm a bit desperate. We have newly installed XWiki (Enterprise 8.0-milestone-1) and I'm trying to get familiar with very basic page editing. For some reason every single link like [[whatever]] shows "WebHome" as a text. I need to use [[whatever>>whatever]] with all links to show what it actually is. It doesn't act like that on xwiki playground (or any other wiki) so I don't know what could be wrong. A steps I do: 1) open: http://url.com/view/NET/String/ 2) click edit > Source 3) write: [[Number]] 4) Save and View 5) and I see "WebHome(?)" with link http://url.com/create/NET/Number/WebHome?parent=NET.String.WebHome 6) after click and template selection it creates new page, which look ok, I save that one 7) and the original link shows now as "WebHome" with link http://url.com/view/NET/Number/ So.. how can I convince it to actually show "Number" instead of "WebHome" without writing [[Number>>Number]] every single time? -- View this message in context: http://xwiki.475771.n2.nabble.com/All-links-are-shown-as-WebHome-tp7598043.html Sent from the XWiki- Users mailing list archive at Nabble.com. ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
