New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: allow non-WikiWord page titles #513

Merged
merged 5 commits into from Oct 30, 2014

Conversation

Projects
None yet
3 participants
@amolenaar
Collaborator

amolenaar commented Oct 9, 2014

.. and add some syntax to be able to link to them anyway.

@amolenaar

This comment has been minimized.

Collaborator

amolenaar commented Aug 28, 2014

There is the link syntax in the wiki [[some phrase][linkedpage]]. It would make the page naming more relazed indeed. Esp. since we can use !contents to list subwiki's anyway.

@six42

This comment has been minimized.

Contributor

six42 commented Sep 28, 2014

Why would you need this?

The feature I miss is to create a table of content which is ordered manual based on the logical order of the content and not alphabetical. The same order should also be used when the test results of a suite are shown on the screen. Somebody who reads the results should finds them ordered in a logical manner.

One solution to this would be to allow wiki words to start with a number and an underscore or a letter and an underscore.
Another solution would be to define the order via a tag or a new property defined for each page.
A third solution could be to extend the "content" function to store the manual order of the child pages and add to the end any child pages for which no manual order is given.

Extending wiki words seems maybe the easiest solution to this problem which requires the least changes in the code. But assume you want to add a page at the top of the table of content. All pages below must be renamed and all links to the ages must be updated. This sounds not like the best solution. A tag might be the more logical solution. Still needs the properties from all pages to be updated but no link changes and no page name. The third solution would just require an update on the parent page.

Do you want to solve the same problem or do you have a different problem you want to solve?

@amolenaar

This comment has been minimized.

Collaborator

amolenaar commented Sep 28, 2014

I find in many cases the page names to be artificial (you have to use to capital letters, whether the name itself requires it or not). I came across this when looking at the html page feature in fitnesse and also while creating the JBehave test system and page support (to be released still, see my github page). Simple page name (with or without underscores) are modified to look like a WikiWord (e.i. spelled as WikiworD). This is odd.

In my daily work I also see more confusion raised from the wiki word system strictness than necessary. Since the !contents symbol can take care of listing child pages there is less need to name pages in this manner. As long as we can figure out what's a wiki page and what's not.

I haven't thought about the !contents ordering, although it's an interesting issue. I used to create a "short" ToC myself in the wiki, hiding the !contents in a collapsible section.

@raboof

This comment has been minimized.

Contributor

raboof commented Sep 29, 2014

@six42 while I agree more control over the TOC/testresults ordering would be nice, IMO that's a separate issue (and I appreciate your considerations here). In this issue I just wanted to get rid of artificially wikiworded test page names ;).

@six42

This comment has been minimized.

Contributor

six42 commented Oct 17, 2014

Nice

@amolenaar amolenaar merged commit 9a9879a into unclebob:master Oct 30, 2014

amolenaar added a commit that referenced this pull request Oct 30, 2014

Merge pull request #513 from amolenaar/wikiword
Feature: allow non-WikiWord page titles

@amolenaar amolenaar deleted the amolenaar:wikiword branch Nov 7, 2014

@amolenaar amolenaar added this to the Next release milestone Nov 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment