Task #13192
UI improvement
| Status: | Accepted | Start date: | 2011-02-20 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assignee: | Rens Admiraal | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 6.0 | |||
| Votes: | 0 |
Description
Hello guys,
i'm currently writing a thesis about extbase in schools (oom and oop).
After using the kickstarter for a while now i wanna share some feedback:
negative feedback
1. buttons should be moved to toolbar (top)
2. Default actions should use checkboxes
3. Extension properties should be transformed in ext-window
4. extkey field should let me select one of my registered type (e.g. with autocompletition)
5. translations would be perfect
6. windows should look like extjs:windows
7. properties etc. should perhaps be transformed into extjs grids to save space?
there was many positive feedback
1. the yahoo wire editor is a very good choice.
2. input validation is great
Thanks a lot
Kay
History
Updated by Rens Admiraal about 2 years ago
- Status changed from New to Accepted
- Assignee set to Rens Admiraal
Updated by Rens Admiraal about 2 years ago
- Priority changed from Should have to Must have
Hi Kay,
Thanks for your feedback! We are currently working on a new UI since the technical limits (especially regarding space in the UI) of the current UI are a really big issue.
We'll take your results into account, hereby my first reaction on this feedback:
Agree, and will be in the new (ExtJS) UI:
1. buttons should be moved to toolbar (top)
2. Default actions should use checkboxes
3. Extension properties should be transformed in ext-window
5. translations would be perfect
6. windows should look like extjs:windows
7. properties etc. should perhaps be transformed into extjs grids to save space
The new UI will move all not Domain Model related stuff (like TCA configuration, plugin configuration, and so on) to another view based on ExtJS.
Partly disagree:
4. extkey field should let me select one of my registered type (e.g. with autocompletition)
We're thinking of an import function of some kind, but having autocomplete on the extKey field is to much. It would be better if this field is clearly rendered differently (for example with an exclamation mark) if your input conflicts with an existing extension. If we use autosuggest we would promote overwriting extensions, which is just a real small percentage of the usecases in which the kickstarter is used. The main function is still kickstarting new extensions.
We will take this remark into account though. We want a UI which supports a user to do developer work :)
Again, big thanks! If you've more suggestions (or ExtJS knowledge and time to help), please let us know.
Updated by Kay Strobach about 2 years ago
ok, than autocomplete should only work with extension which do not exist in filesystem and perhaps have no upload (info should be available through extmgm)
if there is an existing extension the import dialog may popup - what do you think about that ;)
Updated by Nico de Haen over 1 year ago
- Tracker changed from Bug to Task
- Target version set to 6.0