Yes to all of this :) 1. I did create more endpoints since that push in an attempt to not break nav_json (and keep it light for non-admin users) 2. mount_order is hacky -- I agree. I actually wrote that just to get something working until I had a chance bounce some ideas off you. 3. I'll make sure I add all the licenses, thanks for the reminder. 4. Yes, when editing, the names should stay consistant -- which is another reason I created another endpoint instead of using nav_json. The whole look of the edit mode needs some love (although the add new tool interface is looking really good). 5. There is currently a delay -- but I think it is avoidable... let me get back to you on this. 6. Support JS off? no way. 7. ^ just kidding -- Yeah, an html might work -- but since react is going to have to override the existing dom, it might flicker. Maybe we could have it load when unlock is clicked and attach the unlock button to another part of the dom outside the hiarchy of the AdminMenu. My first attempt at that didn't go so well, but I'm more comforitable with it now :)
Thanks for the great feedback! --- ** [tickets:#7919] Create backend for new admin toolbar** **Status:** in-progress **Milestone:** unreleased **Labels:** new-admin sf-4 sf-current **Created:** Fri Jul 10, 2015 07:20 PM UTC by Heith Seewald **Last Updated:** Fri Oct 09, 2015 07:02 PM UTC **Owner:** Heith Seewald We need api endpoints for getting and setting: - Tool ordering - Tool grouping - Tool options - Ability to rename or remove a tool There are some endpoints that already exist that can be referenced (like `update_mount_order`). --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
