+++ Bug: Crash when using IE or Mozilla as preview +++ Set pages read-only *Details*: Needs 2.0 format change +++ Attribute to use wiki words case-insensitive > I keep my entries pretty heavily cross-referenced, and most of them > are written in prose, so I usually use [Not Camel Case] wiki words, > and add aliases for pluralizations, -ing, -est, and other alternate > endings, so as not to break the flow of the writing. *Details* Different attributes for camel-case and non-camelcase +++ HTML export not case-sensitive Solve problem with case sensitive html export, if possible. Wikidpad is in principal not case sensitive about file names, so it shouldn't be here either. +++ Insertion for internal icons [Req count: 2] E.g. \[:imageicon:notepad] *Details*: Wait for free icon set to avoid legal problems +++ Differential auto-update [Req count: 4] Ok, I have put it on my todo list. There are a few little things yet to mention: 1. Changes on a page that affect other pages (e.g. adding/removing attribute "[global.camelCaseWordsEnabled: false]") will not change the already exported pages until they are re-exported. 2. The set of pages to export will be static under some circumstances (maybe I will make this optional), e.g. if you start auto-export for all children of page "GoodParent", it will only export pages which were children when auto-export started. Otherwise WikidPad would have to recalculate the list of exported pages everytime a page was changed which may need some time (does not apply if all pages should be exported or only a regular expression must be matched against the page name). +++ Handle insertion heading level smart [Req count: 2] <
>


+++ Handle insertion indent level smart.


+++ Use image title as alt text
Check if the image title can be used as/converted to the image "alt" text, as in \text



+++ Shortcuts to go to next/previous heading
> Are there keyboard shortcuts for folding and unfolding, as well as to
> skip to the next/previous header? (I guess skipping to the structure
> window and using arroes would be a workaround... if we could skip
> there ;) anyway it wouldn'i be very efficient)


+++ Tree context menu: Copy wiki link to clipboard
> What I try to do, is find the "copy" option in the context menu of a tree node,
> expecting that to copy the link name and then being able to paste that as a link
> somewhere in the text, where I need it.


+++ "Save as" for wiki
Aka copy the whole wiki to new place and rename it.
Don't name it "save as".


+++ "Search wiki" dialog: Show page list used
Do you think it could be possible to add some sort of visual indication to the
full search dialog, that the current search is based on/limited by a page list?
Even if it would, for the time being, be something simple - but rather
inconspicuous - like changing the text on the page list button from "set page
list" to "Reset page list"? Or put a (wikidpad controled only) checkbox next to
it, that indicates yes/no page list?


+++ Command line call plugin
>> For example, the user could select some text in the editor and press a
>> kexy. The text would then be executed as if it was enter in a
>> console(=DOS box) window and the output would then added after the
>> selection in the editor (similar to the way as eval behaves).


+++ More form field types
> Whichever of these solutions is embraced, I believe that something
> like &&t and &&T tokens should definitely be added to the FORM (not
> template) syntax, allowing explicit insertion of the space-separated
> (&&t) or non-space-separated (&&T) originating wiki words. Along
> similar lines, I believe that forms should interpret a variety of
> other auto insertion codes in addition to &&i. (The one that comes to
> mind as absolutely necessary is &&d for the current date/time.)
*My answer*
As these fields should be filled automatically when creating a new page from a template (unlike the &&i token) they should get some sort of prefix letter to distinguish them from &&i and because the space of available letters is rather small.

So I would recommend &&at, &&aT, &&ad as tokens. The "a" stands for automatic replace (not very creative, I know :-) ).



+++ Attributes on inserted pages processed by inserting pages
is it possible to dó let html attributes on inserted pages influence the formatting of the inserting page?
This would make it possible to use inserted pages as a type of style-sheet (colors, etc) for individual pages.
This would require an extra parameter for the [:page:] attribute; yes/no process attributes switch.


+++ Table parameter to define CSS class
> Do you think it would at some point be possible to add a parameter to the "start
> table" tag, that could be used as the table class name?
> Like:
>
>     <<|    cssClass
>
> becoming
>
>     \
>
> It is simply a heck of a lot simpler to define a table in wikidpad format, then
> using the whole 
 etc. stuff.
> Something similar for <
\> block, in which the insertion of line breaks, the conversion of indents into unordered lists and possible other harmfull actions - don't think there are any? - are omitted. Except for the line breaks, etc., it should be roughly equivalent to the \<\<| ....\>\> table block.


+++ Support footnotes in inserted page


+++ Add document structure window to F6 cycle
*Details*:
Make cycle configurable
Create a shortcut for backward cycle.


+++ Allow own icon for each wiki (Done for systray)
*Details*:
Works for systray icon, but problems with main icon in Windows


+++ Allow config. of script keybindings
Probably the CTRL+number keybindings are hard wired to the inline
scripts? At least they don't show up in KeyBindings.py. I would
appreciate it very much if you could change that


+++ Command line automation
I would like to automate certain things like wiki word creation (for
example through other programs) Is there a way to pass arguments to
wikipad.exe that would perform certain actions on currently opened
database-selected database like opening or deleting a wiki word or
adding a sentence to end of a certain wiki word page?


+++ Suppress self-referencing auto-links
My only suggestion would be that it maybe shouldn't work on its own page? I mean, say I create a wikiword called [Germany]. Chances are that the number of occurences of the word 'Germany' on this page is plentiful, and so are the links (that are in fact useless and so only litter the page).


+++ Reload menu plugins during session (partly working)
For debugging purposes it would be great if I could force WikidPad to
reload the extensions without exiting WikidPad and starting it again.
Is there some function I could call to do that?


+++ Options to control relation graph/child graph better
> 1. Size
> The resulting graphs are relatively big; possibly a result of the rather large
> font size for the nodes.
> This results in too small a portion of the graph being visible in the (page) window.
> Having a larger part visible would more practical.
>
> 2. Style
> I think a "sans serif" font like arial or verdana would give a better display.
> The font size could be smaller; depending on the font name, something like 10
> would do, I guess.
> A slightly lighter gray for the default node fill color would be better also.
>
> Can you change that, or is there a place, where I can change it myself?



+++ Page insert graph
> 3. Page Insert graph
> Maybe Relation graph is supposed to show it, but if it isn't, it maight be an
> idea to create a graph that shows where pages are used as inserts; a bit like it
> is done for templates. Currently there is no other way to check the use of page
> inserts, since their relations are neither shown in parent- and/or child lists
> nor in the views tree.


+++ HTML import [Req count: 2]
This is one of the most important features for me. Perhaps it could be
implemented as a translation. Pasted HTML would be translated to
wikidPad equivalents. I currently use Zoot. I, and many others, are
looking for an alternative because Zoot does not handle HTML or images.
*Details*:
Also option to just import text and URL links from clipboard (also with clipboard catcher).


+++ Functions for middle click on tab
Possibilities:
    * Clone tab
    * Close tab


+++ Use paragraph (p) html tag if appropriate
> I noticed, that the generated html for preview - have not yet tried export -
> does not use the
> 
 element; also not when paragraph_mode is set to true.
> So it's no use, trying to use p{ .....} style elements in the css file(s)
*Addition:*
Just make shure though that you don't get yourself into additional trouble,
because browsers have their own idea's about what to do with default margins,
padding and other stuff in and around paragraphs. It might become more difficult
to get the layout (roughly) the same in internal preview and external
preview/browsers. And also into additional parsing problems, since you would
have to be quite sure about what ís and what is not a paragraph and that might
be a bit difficult to do if you - next to the standard wikidpad stuff - also
have to deal with inline html, that might contain it's own paragraph elements,
next to div's, tables, lists, etc. You might be getting close to creating a full
fledged (x)html parser.

The reason I'm also saying this is with the memory in the back of my head of
what the present insertion of \
's and \