Annet - I think there is nothing obviously "wrong" with what you have said, except that it's not clear nor specific enough yet to implement (I think). If you get a little organized, you will start thinking about the details, and then you can ask again about specifics.
I have translated what I could from your post into a bit of a diagram for
starters. You should extend this (or at least make some outline notes that
represent this), and then add some specific use cases to clear up how you
want things to be.
The good news: it should be do-able.
Getting it to where you (and users) are happy will take some work (mostly in
sorting out the details). Getting it _really_ to a "web page" like thing
will mean a little more complexity, but if you get there little-by-little,
step-by-step, and think carefully about the structures you build, you should
be able to eventually get to that also.
- "kind of things" I thought of as being per-controller / per-module,
the latter being easier to add per level of service per user, perhaps
- For "model" editing by the user, I would start with fixed css class
names (per kind.function naming, for example) and fixed css definition
- An easy first thing to add would be "show / not-show" for a user
option;
- a second step might be position (you'd want a fixed grid, and assign
an easy-css container to a view-variable - this should be pretty easy)
- a harder one will be allowing the user to position by moving display
boxes
- a harder still step will be allowing layout (sizing, griding)
control by the user.
The last of these you might never want to do; the first 3 should be
do-able, and satisfying. Working out an edit form for actions per
component, or assigning component to layout - this will be most of your work
I will guess. Everything else, and most of what you want will be easy by
comparison.
Best regards,
Yarko
<<attachment: annet.svg>>
