Form Layout
Steven Heynderickx wrote on 21 Dec 2009 10:35
I wish to be in control of the way a contributer sees the layout of the form. In other words I wish to design the user interface. Just like using some database program: I would like to be able to design my form and to design my report. For the report we have ":_template", could it not be possible to make ":_form" that holds the layout of the form?
I think the property "join" for example will not be needed any more.
Example: Myform:_template
++ %%field{$title}%%
[[div class="report_header"]]
%%field{$header}%%
[[/div]]
[[div class="report_body"]]
%%field{$body}%%
[[/div]]
[[div class="report_author"]]
%%field{$author}%%
[[/div]]
Example: Myform:_form
++ Complete the following
[[div class="form_header"]]
%%label{$header}%%:%%field{$header}%%
[[/div]]
[[div class="form_body"]]
%%label{$body}%%:%%field{$body}%%
[[/div]]
[[div class="form_author"]]
%%label{$author}%%:%%field{$author}%%
[[/div]]
[[form]]
fields:
title:
label: Give the title of your article
type: text
width: 30
header:
label: Write the short contents of your article
type: text
width: 50
height: 3
body:
label: Write the full contents of your article, keep in mind that the header will always appear together with this
type: text
width: 50
height: 3
author:
label: Give your name or initials as an author
type: text
width: 30
[[/form]]
Comments: 9
page revision: 1, last edited: 21 Dec 2009 14:48
Agree 100%
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
now lets find some 10.000 other users that also agree and get this thing made :-)
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
This would be cool. Form follows function though… Any sense of where a broader functioning module fits into the dev team's workplan?
This thread makes no sense.
The form is the layout. We plan, and if you read the design you will see, additional functionality used to properly format the user interface.
The only case for a separate layout is for making multiple views on a single form and that is beyond any use case I've seen so far.
Please, stop making proposals for technical changes that are not tied to clear use cases. If there are functional requirements, specify them and allow the designers (that's me in this case) propose solutions.
I'm closing this thread.
Portfolio
maybe it was the wrong section to suggest this.
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Sorry to be brutal about closing threads but this proposal is just contradictory to the concept of forms. I think I understand what you want to do but it's unclear since you don't explain your use case.
Always, please use this procedure when discussing changes:
What you have here is a proposal for a major change to an existing design, without the rest of the process. We can't deal with that, it would create a mess. (Experience, not opinion…)
Portfolio
It's good to know how you prefer these wiki-improvement iterations to work.
Whenever I post about a Wikidot issue or a wishlist item, I always feel like a kid on Santa's lap. I'm a little bewildered, and I have no idea what motivates this guy to give me what I want. But I figure, "what the heck, it's worth a try".
What amazes me is how often this elven wiki-workshop delivers. They don't even get any milk and cookies!
That can be easily fixed :)
Wikidot Inc. S.A. Oddział w Polsce, Pl. Św. Katarzyny 9, 87-100 Toruń, Poland.1
The milk might be a bit spoilt by the time it arrives though :(
~ Leiger - Wikidot Community Admin - Volunteer
Wikidot: Official Documentation | Wikidot Discord server | NEW: Wikiroo, backup tool (in development)
I've copied this explanation to the "how it works" part of the design section. It's not obvious and took us a long time to learn. Mainly, without clear problem statements, the best ideas in the world are useless.
We enjoy making Wikidot better, indeed that's our job, and it's made so much easier by you folk.
Portfolio