Hi Ben,
Glad it was helpful. By all means use whatever "landing page" you want, I
just use HomePage because FlexWiki guarantees that it will always exist, so
I've always used it as the root of any namespace.
Derek.
On 7/31/07, Ben Darbyshire <[EMAIL PROTECTED]> wrote:
>
> Hi Derek,
>
> That works perfectly and thanks for the prompt reply.
>
> I can't live with the default of "HomePage" though, seems so
> unsophisticated :). I will have to come up with a naming convention that
> your loop can cope with. Probably NamespaceName.NamespaceName
>
> thanks again,
> Ben
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Derek Lakin
> *Sent:* 31 July 2007 10:25
> *To:* FlexWiki Users Mailing List
> *Subject:* Re: [Flexwiki-users] Advice on wiki layout
>
>
> Hi Ben,
>
> Providing a namespace per software application would seem to make sense in
> your situation.
>
> I don't know what your WikiTalk looks like, but in order to provide a link
> to particular namespace, you need to link to the HomePage topic in that
> namespace. You also need to make sure that the name is fully qualified,
> e.g. NamespaceOne.HomePage, which is how you link (in WikiText) to a topic
> in another namespace, too, e.g. NamespaceOne.SubNamespace.MyTopic.
>
> I use the following WikiTalk to link to the namespaces on one of my wikis:
>
> @@federation.Namespaces.Collect{
> each | [" * ", Presentations.Link(
> federation.LinkMaker.LinkToTopic([each.Name, ".HomePage"].ToOneString),
> each.Name), Newline] }
> @@
>
> Hope this helps,
>
> Derek.
>
> On 7/31/07, Ben Darbyshire <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > I have installed FlexWiki 1.8 (which btw seems to run perfectly under
> > framework 2.0) with the intention of using it as an Intranet knowledge
> > store. The data I plan to store in the wiki will be support
> > information/How to/documentation for each software application that my
> > company runs internally.
> >
> > Due to this it seemed to make sense for me to create a Wiki Namespace
> > for each application. That way I would have good logical separation of the
> > data, plus the ability to have pages with the same name for each
> > application.
> >
> > After setting up a few test Namespaces the first thing I did was to add
> > some WikiTalk to the wiki's default homepage, that lists all of the
> > Namespaces in the Wiki. I thought that this would provide wiki users with a
> > easy link to each of the Namespaces. Unfortunately it would appear that
> > although the WikiTalk will happily produce the list of Namespaces, the names
> > do not become links to the homepage of each Namespace automatically.
> >
> > So I have two questions, the first is whether I have made a mistake in
> > creating lots of Namespaces. Should I just have one Namespace and use some
> > kind of page property to divide the applications?
> >
> > Secondly, is there some way that FlexWiki can automatically link to
> > topics in another Namespace?
> >
> > thanks
> > Ben
> >
> > ________________________________________________________________________
> > This email has been scanned for all known viruses by the MessageLabs
> > Email Security Service and the Macro 4 plc internal virus protection system.
> >
> > ________________________________________________________________________
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Flexwiki-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> >
> >
>
> ________________________________________________________________________
> This email has been scanned for all known viruses by the MessageLabs Email
> Security Service and the Macro 4 plc internal virus protection system.
> ________________________________________________________________________
>
> ________________________________________________________________________
> This email has been scanned for all known viruses by the MessageLabs Email
> Security Service and the Macro 4 plc internal virus protection system.
> ________________________________________________________________________
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Flexwiki-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
