Re: tags
The prefix idea has merit. The other alternative, of course, would be to delete all tags & replace them with the ones specified in the form (the form would be pre-populated with the current tags when editing the page, I assume)
What would be perfect, though not necessary, is an alias for each tag. For example, my "Three Word Category" could be represented by the tag _3 , and I'd want to show 'Three Word Category' to the page creator, instead of the actual tag name.
Re: parents at creation
Exactly. So for me, that would work well. For someone else, they may also need to convert a plain text field that the page creator enters, so that it's the parent of the page?
Re: filenames
The thought crossed my mind that the field might be something like C:\user\shane\desktop\image.png, but if it's just the filename, that works fine for my own needs, at least.
Or:
Possible solution for parents, tags and everything else like that?
Design: 5 - Page Metadata
We need: weneed:85
Maybe it's not worth even discussing this at all! If you were able to work on that MetaData design first, then it would be as simple as making forms work with it, like this:
[[meta]]
[!-- For me, this would be a 'hidden' data type, already pre-determined --]
parent = %%field{parent}%%
[!-- Tags can be entered using multiple boxes --]
tags = %%field{tag1}%%%20%%field{taglist}%%
[!-- Page title --]
title = %%field{page-title}%%
[[/meta]]
Doing it the MetaData way, you're essentially putting more code into user space, and not wikidot dev space :P
You're also making forms a whole lot more generalised. A bunch of tools, in the form of textboxes, radio buttons, etc — all accessed using %%field{fieldname}%%. And %%field{fieldname}%% able to be used by the meta data idea. Perfect.
The only complex field type needed would be for file uploads.
(account deleted)