Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
I like the idea. Any other meta data we might need to output?
Portfolio
pieter wrote
are you asking me what I mean with:
If that is the case… We discussed somewhere that a field-property "hint" should be added. This property would hold extra info for the case a user does not know what he needs to enter for example…
I can imagen a property called "requiered" with the text of the error that would appear when not filled out…
Maybe other properties… so I think it would be good that all the possible properties of the future could be referenced by in the same way %%property{field-name}%% or something as logical as this
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Fine - you'll see I've used form-whatever for the label and hint, and we can extend this over time if we need other field meta data.
Portfolio
Yes… what's in a name, form is fine with me… and yes if we have this naming procedure we can always extend it in the future.
But I was not planning to use the word "field" or "form"…
I have a feeling that in the future wikidot will evolve to _templates with the form-syntax and not the "==== %%content{n}%%"-syntax… So why the %%FORM_label{MyInput-thing-name}%%, why not just %%label{MyInput-thing-name}%%
Why do you put form before the property-name?
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.