backend structure/categorize forms

marios · 2006-04-05 06:05:06

Collapsible by category would be allready a huge improvement.
The other things that I describe are probably to complex,
In the meanwhile I’m trying to refine the naming convention method.

regards, marios

alexandra · 2006-04-05 14:39:55

I agree with mrdale, marios suggestion is a bit confusing… i like mrdales suggestion a bit better cuz it is easy to understand. so here is my suggestion based on mrdales work.

the image in fact shows 2 scenarios at the same time:

adding a new form
changing an existing form

Categories can be collapsed.

Understandable?

Last edited by alexandra (2006-04-05 14:47:37)

marios · 2006-04-05 16:16:56

Very nice GUI really, how comes, I’ve thought about the triangles as well, for a collapsible version.Triangles could be up and downright in red and green, or vice-versa.
I am not sure, if I understood the difference between change form and create form.When I change a form , Is there a special reason for it’s additional existence of the extra input and dropdown fields ?

Another thing that could be usefull, would be a color-code for the form types (could be done with CSS as well), let’s say: mint green for article forms,light orange for mics forms etc,

The default width of your form textarea field is allmost one tab shorter than in mrdales or my example, that might be good for small screen resolutions, but it causes problems with longer form tags that include li items or other cases where whitespace through linebreaking in your output code is unwanted .
(In most of my installs I keep the width at 120cols,which spans approxiamtely 7tabs, in a default install the 60cols is far too short,
I think a minimum of 85 cols should de thought of, while the row height is not so important.In one of my installs, if I wouldn’t have a minimum of 100cols,I would get the unwanted whitespace effect, like inside list elements.)

regards, marios

Last edited by marios (2006-04-05 16:20:40)

mrdale · 2006-04-05 16:24:50

>alexandra
I like your mockup, almost exactly what I was thinking (but was to busy(lazy) to flesh-out. I do think that consolidating the save/save_new into one would be better, less confusing.

You could do so by:

Putting both save/save_new side by side.
Having a “other…” in the category select that reveals a field for a new category.

Otherwise, magnifico

alexandra · 2006-04-05 16:47:07

Thanks guys for your feedback.

I did split ‘Create form’ and ‘Change form’ into two boxes as we need at least one button for ‘create forms’ as it is right now in TXP – but the current solution in TXP does not look appealing to me. so i change it.

The boxes can be collapsed so it should not be an confusing interface … in fact i regard it much better for beginners.

The category inputfield under ‘Change form’ should be a drop down field.

At this point, and if you agree, we should talk to some programmer (sencer) how about coding this and what the coding problems might be.
What you think?

Last edited by alexandra (2006-04-05 16:48:18)

marios · 2006-04-05 17:00:29

Defenitely, to have may be the chance to get it included at least in 4.1.0,

regards

mrdale · 2006-04-05 17:08:17

Don’t want to rain on this parade, because I think we’ve added some useful thoughts…

…But I doubt something like this is likely to make it into a release anytime soon. We have, at best, a consensus of three which is a start, but there are a great number of people using TXP.

The Devs are extremely sensitive to adding clutter to TXP, and watch over the “simplicity principle” like hawks. read here

It doesn’t hurt to try, but just be prepared for more feedback (good and bad) consensus is hard.

alexandra · 2006-04-05 18:13:04

Well, TXP development has to proceed anyway. And we have to start with something….
If stuff like that will not be added someone will come along, fork TXP and use what we worked out. It is that simple.

mrdale · 2006-04-05 18:20:39

>Alexandra
I wasn’t criticizing, merely wanting us all to calibrate our expectations about 4.1. By all means let’s present what we have, I think it’s pretty useful.

hakjoon · 2006-04-05 19:01:13

I like the current “create new form” (even though alex doesn’t like it :P) which basically throws a blank form in the editing area vs. having a whole separate “create a new form” area. It seems confusing to have mirror option sets available all the time.

For example, what am I doing in the mockup? Creating a new form or editing the all_sites form?

It seems that adding a category drop down to the current UI along with the collapsing flippers would accomplish the same thing with less confusion.

Lovin’ everything else though.

alexandra · 2006-04-05 19:29:10

hakjoon schrieb:

For example, what am I doing in the mockup? Creating a new form or editing the all_sites form?

As i mentioned above: the image displays 2 scenarios at the same time. (I was too lazy to prepare 2 images :)) Actually one of the boxes (Create new form / change form) will be closed and all you see is just a tab. It is not very different from the current solution.

However, it would be great to know, how much work it would be to programm form categories? Is the collapsing cat´s and boxes done by javascript?

hakjoon · 2006-04-05 20:52:05

alexandra wrote:
As i mentioned above: the image displays 2 scenarios at the same time. (I was too lazy to prepare 2 images :))

It helps if I read doesn’t it.

Is the collapsing cat´s and boxes done by javascript?

Javascript would seem like the ideal solution for me, as it would be fairly straight forward to implement. A simple class change on click would take care of it and it could work for making the category the currently edited form belongs to be expanded by default. (if currentFormcategory = thisCategory then class = expanded)

Only thing that I think could work just with javascript is the create new form area since that would need to reset the page to a blank form. Could probably be done with javascript though. I’d hae to take a closer look at how new forms are handled.

Textpattern CMS

Textpattern CMS support forum

#13 2006-04-05 06:05:06

Re: backend structure/categorize forms

#14 2006-04-05 14:39:55

Re: backend structure/categorize forms

#15 2006-04-05 16:16:56

Re: backend structure/categorize forms

#16 2006-04-05 16:24:50

Re: backend structure/categorize forms

#17 2006-04-05 16:47:07

Re: backend structure/categorize forms

#18 2006-04-05 17:00:29

Re: backend structure/categorize forms

#19 2006-04-05 17:08:17

Re: backend structure/categorize forms

#20 2006-04-05 18:13:04

Re: backend structure/categorize forms

#21 2006-04-05 18:20:39

Re: backend structure/categorize forms

#22 2006-04-05 19:01:13

Re: backend structure/categorize forms

#23 2006-04-05 19:29:10

Re: backend structure/categorize forms

#24 2006-04-05 20:52:05

Re: backend structure/categorize forms

Board footer