Re: [cowiki-dev] markup language, plugin list

OK, thanks.  I would be OK with a help popup (except that I have popups 
disabled!)  I don't find the plugin list very helpful because it doesn't 
identify either the purpose or the parameters to the plugin.

Actually, I would like help to be more generally available without 
having to go to another page on the wiki.

I've seen a cool trick done with JavaScript to make an "Accordian" 
display-- Click on a bar to reveal the content inside it.  It lets you 
choose how your display space gets used, very nice.  Along the same 
lines, we could do a tabbed display where it was appropriate.

(I've been working at learning what can be done client side with 
JavaScript.  It's really quite impressive!)

Paul

John (yt) Hogenmiller wrote:

>You know, if you're looking for change ideas, I would suggest putting
>the markup language guide underneath the edit box instead of the
>plugin list.  I have been using cowiki for a while now, and I often
>have a tab where I'm editing, and then another tab with the markup
>page open.  It's an easy language, and after you use it for a good
>while, it becomes memory, but I think most people starting out would
>like to see that below.  If having the plugins is worthwhile, I would
>recommend using layers that would have both, but the user would only
>show the important bit, or hide both.
>
>Now that I think about it, this would be a theme issue.  I've been
>working on a new theme for cowiki with some interesting features
>(collapsible menus, right/left menu, configurable logos/graphics)
>geared towards greater customization of the overall site.
>I think I will throw this idea into it and hopefully release a
>pre-beta sometime this week for people to check out.
>
>-John
>
>  
>