MODULE UI ISSUE
I also think a "Add Module Above" "Add Module Below" (to this tab)
above each module on a Tab would be great. There is no reason to have to edit a Tab to toss in one more tab.
FUNDAMENTAL UI ISSUES
- I also think most of the Editors and Editors spawned from Add Dialogs have text links for "ok" or "apply" that need to be buttons NOT TEXT and those buttons need DEFAULT FOCUS so one can enter a title and add module to the pane and press ENTER to complete task instead of scrolling.
- Pencil, Padlock, Module setting icons need to be on left side NOT RIGHT SIDE so they are not scrolled off screen when browser window is not super wide.
- A "Add Tab Above This Tab" and "Add Tab Below This Tab" on top and/or bottom would be great for menus with several children where one wants to add a sibling at same level as this tab quick.
- The unamed module with no title and no theme having no admin
capability could be addressed by Pencil icons, "Module Settings" icon and "Module Permission" icons next to buttons alluded to in #1. http://url123.com/ueds5
ANY MODULE THAT CONNECTS TO DB
- Table Edit and any modules that have to connect to DB mostly have explicit USerID, Password and DataBase, Server textboxes. 90% of the average developers only know web.config keys or full connection strings. If they could enter appkeys from web.config or connection strings most don't want to mentally parse it all out of that string and fill in individual boxes.
BUG
- The "whos on" omits the Admin usually and give no indicator if multiple people are in as Admin. This lack of info undermines their confidence. It should identify 1 or more admins logged on and distinguish them by name/email if needed.
BUG
- Deleting Roles that are assigned to users results in severe error. Should list the users in that role and warn that deleting the role will affect all those users. Should also allow assigning those users to a new role if a role if new role replaces those.
Rainbow Master Menu
- The other thing about the menu is that if a menu has children (for example movies) and no content tab (as I often do for parent tabs) it would make sense to show child menus next to it rather than blanks. A bookmark like http://url123.com/cvq4p for movies seems to the visitor to lead nowhere. Right side should show all children of movie tab (Action Comedies, etc.) - no need to Jscript cascade.
BACK Button, Adding Tabs
- Sometimes in web apps where I want to add many things (like Tabs) I merely hit back button. Imagine I want to a add 20 children tabs to a Parent. I click "add Tab" and then assign the parent and name tab and click "ok".
Then I hit back and the same parent is selected I just enter new child name and press ok and voila in most software I have got 20 children quick. In Rainbow the 19 children never got created I kept overwriting same tab to my horror I discovered at end.
The Problem with Buttons
- Buttons they have to scroll way to bottom to press to make a change. They change some simple setting at top of screen and then have to scroll down to find what to push to complete action.
a. Easiest fix is to have buttons at Top -or- Top and Bottom
b. Also not putting several tabs on a page in admin interfaces would reduce pain
- The use of "ok" and "Apply" are confusing and inconsistent.
suggestions
- The use of text instead of buttons depending on what theme one is in. People want buttons not text. Themes should not change the way Admin works.
Potential Solutions:
- Always buttons regardless of themes. Themes are for Consumers/CMS entry folks not themes.
- dmin only uses themes if specified in checkbox site settings. Otherwise it uses a standard theme.
Tab Editing: Ouch!!!
- Postbacks for each tab move
- need to be able to collapse children under parents or make hirearchy into dependent lists
A glance at http://www.learnasp.com/chaz indicates I have over 400 tabs (and more being added constantly). I should not have to endure 20+ postbacks for a simple tab move that should be 1 step.