Planned%20Features.textile in Soks-0.0.6

- old
+ new
@@ -1,19 +1,40 @@
 h1. Planned Features
 
-As an aside, in the longer term I'm hoping to incorporate some of the features of Soks into instiki, but in the mean time:
+In the long term I'm hoping to spend some time working on the instiki project to incorporate some of the features of Soks into instiki, but not until I've got soks stable and smooth.
 
-No plan survives, so this has changed:
+h2. v0-0-7:
 
-h2. v0-0-6: Focus on quality
+* Write a new Recent Changes class
+* Perhaps incorporate Bil Kleb's new page templates or categories code
+* A housekeeping routine that could periodically prune large revision files, and perhaps permanantly remove deleted pages after a while.
 
-# Improving the standard, beauty and quality of the included templates / skins / wiki looks
-# Refactoring to make the code easier to understand and hack
+h1. Desired Features
 
-h2. Desired Features
-
 Let me know if there is anything that you would like to see, or add it here:
 
+* Flesh out the RSS feed:
+** Have the item content render the most recent change information like that shown at the bottom of an edit page. (Remove the logo and search box?)
+** Have the source link be the "view" view and not the "rss" view.
+** Replace the <notextile>* [[ page title ]]</notextile> asterisk and brackets with quotation marks? --Bil
 * Fast CGI or the like as an alternative to Webrick
 * Give each automaticsummary a unique name so several can update the same page
 * Some form of tag to automatically create automatic summaries.
-* Make the wiki fork, and give commands to gracefully start and top it.
+* Make the wiki fork, and give commands to gracefully start and stop it.
+* I was going to make a suggestion, then I noticed that something like it had been added and deleted. Perhaps some explanitory text explaining what has already been suggested or what is or is not acceptable would be a good idea? - Sorry. A mistake on my part.  Please do make your suggestion again, and I won't delete any in future - tamc2
+** I think a generalized way of extending soks to be very much more dynamic would be allowing dirt-simple extensions. One way would be to put a @scripts@ directory in parallel with @attachment@ and extend @insert@ to then include the output of the script. So something like @[ [insert script helloworld blah ] ]@ would run helloworld.rb with the argument blah and the output would get pasted right into the wiki page. What do people think? --Skorgu
+** Interesting, what types of script did you have in mind?  The only challenge I can see is deciding how frequently to call the script to update the page, every time the page is viewed? or every time it is editted? or somewhere in between? what do you think? -- tamc
+** I'd say call the script each time the page is updated and let the script handle any sort of caching. The situation I had in mind is something like this: I have a page on Soks that has my frequently-loaded websites that I use as a start page. I'd like it if, instead of just saying "Red Handed":http://redhanded.hobix.com it said "Red Handed":http://redhanded.hobix.com (Last Post "Killer Hobix Tutorial...":http://redhanded.hobix.com/inspect/killerHobixTutorialInEnglishAndFrench.html ) and have the script pull the RSS and just update that. A more ambitious project would pull a list of URLs from say del.icio.us with tag "feed" or something and generate the link list itself. Once the capability exists to pipe script output into the wiki, everything else can be handled in those scripts. --Skorgu
+* Making the automatic linking only link one occurance of a title per page.  Currently can end up with far too many links to the same place on the same page.
+* A setting in start.rb to switch between Soks-style freeform pagenames and Instiki-style autolinks --Skorgu
+** By this, do you mean that you would like the option to have a WikiWord create a link? If so sounds possible as an option, although I personally dislike them! -- tamc 
+** I like the freeform linking, but there is one huge problem: if I'm writing a page and I decide that I want to add a link to a non-existant page, I need to either @[ [Double Bracket] ]@ it or click Add New Page, type the name, remember if I used a space or not, and then write my content. In Instiki, if you just write CamelCase it creates a link to the 'create this page' form with the title filled in and everything. Maybe keep the freeform linking but have an option to enable auto-linking for wiki words? --Skorgu
+** Ok, I'll look into it.  By the way, another way of doing this (if your browser supports this) is to highlight the text you wish to link and press ctrl-n. --Tom
+* Perhaps a category helper? To index references to particular key words
+* Perhaps the default layout should have a little table of contents menu like wikipedia pages.  (
+** I'm confused, isn't this already in 0.0.5? --Bil
+** Sorry, I'm not being clear.  What I was talking about is the thing labeled 'contents' at http://en.wikipedia.org/wiki/Wiki. If you create a long page with several headings, it creates a little table of contents at the top so you can leap down the page quickly.
+** Ah, cool item but it would seem to encourage long pages? --Bil
+
+Also considering these bigger changes (interested in your thoughts):
+* Making the automatic linking ignore punctuation.  Only the words in page titles would be significant, so "Bug: A bug" would be treated the same as "Bug- A bug" -- tamc
+* Making the automatic linking link to 'similarly' title pages. e.g: If you have a page called "Page One" and another called "Page Two" all instances of the word "One" in "Page Two" would link to "Page One".  Would add a lot of processing, but might allow distinct namespaces. -- tamc