--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/udg3vhNdViYJ.
To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.
I agree that its too clumsy to get from "Edit Page" to "Add Page" only by expanding the menu,and that its a very common use case. I'd be happy to put an "add page" button above the tree.It also leaves the button in more or less the same place as in 2.4 (top right above the tree),which will help people in switching to 3.0. How do others feel about that?
What about putting the current 'Edit Page' menu item as a sub-item of pages?
So, when you first click pages you will see this in the LHS menu:
Pages
- **Edit & Organise**
- Add Page
And then when you click on "About us" in the tree, to edit it, you will see this in the LHS menu:
Pages
- Edit & Organise
- **Edit "About us"**
- Add Page
Putting the page title into the LHS menu made more sense than having "Edit & Organise" and "Edit page" as two items.
Felipe mocked this up here: https://github.com/silverstripe/silverstripe-design/blob/master/Design/ss3-ui_Pages-nested-nav.jpg
Frankly, its going to be a royal pain to change the UI around to accommodate it at this point in time,
as we need to make the tabs load via ajax, hook them into the HTML5 history state,
and create styles + behaviour for secondary tabs. There was a thread about this on the mailing list
shortly after alpha2 came out I think.
> --
> You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
> To post to this group, send email to silverst...@googlegroups.com (mailto:silverst...@googlegroups.com).
> To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com (mailto:silverstripe-d...@googlegroups.com).
> We'll need to put the "Content", "Settings" and "History" sections somewhere:
Doh, I missed that I thought they were already in tabs.
> Frankly, its going to be a royal pain to change the UI around to accommodate it at this point in time,
> as we need to make the tabs load via ajax, hook them into the HTML5 history state,
> and create styles + behaviour for secondary tabs. There was a thread about this on the mailing list
> shortly after alpha2 came out I think.
OK - let's go for a simple fix for now and see what it's like.
> > > > To post to this group, send email to silverstripe-dev@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > silverstripe-dev+unsubscribe@googlegroups.com.
Sam Minnée
CEO
SilverStripe
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/BsO8LDARNckJ.
To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
Hm, one and a half steps forward, one step back. We're getting there...
Particularly due to the layout context switches (toggle various panels, complex view/panel reloads)this is not going to be an easy task, and as so often, the devil is in the details.More details than a graphic can express, so I think any design effort has to be accompaniedwith actually writing stuff down in a ticket: http://open.silverstripe.org/ticket/7094Felipe, if you change the design, can you please ensure the ticket stays up to date?(from a UI perspective rather than the technical details).
As Frank noted, we still need a place for the "Settings" and "History" views of a single page. Felipe?I don't particularly like the pill+tab solution displayed here: https://github.com/silverstripe/silverstripe-design/blob/master/Design/ss3-ui_Pages-nested-nav.jpgIts quite common to have two levels of tabs in 2.4, so this solution would make it three levels.Yes, that's bad usability practice, but nevertheless a widely used one in pretty much all SilverStripe sites out there.Technically, the first level ("Content"/"Settings"/"History") won't affect tabsets created via SiteTree->getCMSFields(), its more of a visual problem.
We could ask devs (module + custom code) to consolidate their content-related tabs into a single level,but that's not always feasible due to the sheer amount of logical sections as well as the limited width for tabs in the designs (and no way to horizontally scroll them).On the other hand, this record-specific first level conceptually doesn't belong in the menu.How about displaying second level content tabs inline as "sections"/headlines within the same tab? Take the following (made up) example: https://skitch.com/chillu/8q6m7/myimageMore challenges:* Its unclear how this solution works with the preview expanded. When you navigate to a different page within the preview, I assume that a click on the "pages" icon would take you to the edit view of this new page? In other words: There's no direct way to get from preview to the full "pages" tree view (which I think is OK).
* How do you get from the "tree sidebar + edit page" view back to the full tree? The only way I see currently is clicking on the menu entry
* We can't easily show the amount of pages matching a filter, due to the way querying is implemented behind the scenes ("marking filter"). That'll be a major refactoring to fix in a clean and performant way.
* The "filter" sidebar is hidden in "edit view", that's on purpose, right? More work, but makes the view easier on the eyes, and less confusing (no edge cases around changing filters while editing a page)
* If the list or gallery view (not the tree) is shown, what happens when switching to "edit page"? I guess we'd have to switch to the tree view, and ensure its expanded in the right level? (assuming you can navigate into children/parent "folders" from the list view)
* Implementation detail: "Ignore edge case where modifications to the currently edited page would remove the page from the filtered tree"
Code:Specifically this commit: https://github.com/silverstripe-big-o/silverstripe-cms/commit/6aeac37906bc2d244bccedd467f0402e5942166eNotes:- Only works in Webkit, cuts off tabs in other browsers (jQuery UI weirdness?). As I said, work in progress ;)- Preloaded instance with a couple of hundred pages to demonstrate tree performance- Tree HTML is cached on client after first load, so switching from admin/pages to admin/pages/edit/show/<id> is not as slow as it could be- That being said, its still slow, as the tree needs to be rendered again from HTML. Looking into partial reloads, which will make things more complex, but faster. Post beta2 most likely.- Breadcrumbs don't refresh on list navigation, same problem essentially - Julian has solved this in a branch.- Jeremy is doing the required design changes at the moment, so tabs etc. still look rough- Try filtering on admin/pages, it keeps it in the URL (which authors can bookmark/share => FTW).Also retains tree filtering when switching to page edit view.- Lazy loading both tree and list view, which makes the initial admin/pages load perceived faster.Probably changing that to only lazy load the current view (denoted by query param), less processing on client.