Wednesday 02 December 2009 3:57:48 am

The new admin is great, but I got some comments:

• Could the main column be divided vertical, to avoid scrolling down to subitems?
• Butten bar and sorting for subitems should also be added above the list
• Is the common buttons like Edit, Move, Copy.. can rather use icons to save horizontal spacing and to keep backend more similar on multi language sites.
• Would an accordion view be better on the tabbed node detail pane? (especially if you dived main area vertically)
• Would be cool to have "Quick look into" ajax view of container content types when you hover over it in lineview
• A kind of dashboard view would be cool to. Show the latest changes, "quick create", online visitors, and a widget api for this dashboard

Senior webdesigner
Netmaking, Norway
http://www.netmaking.no

Triathlon, Webdev, Novels and Cooking..
Personal site: http://www.gersh.no

Wednesday 02 December 2009 4:58:24 am

I think really important is to also improve the changing of the order of the attribute in class edit

www.all2e.com

Wednesday 02 December 2009 5:06:18 am

Hi

Just hope to see something on new admin panel: at the moment, we could defined a max 'show nodes" on settings.. Maybe could be great we could override this value for a or more nodes.

Thanks

Certified Developer (4.1): http://auth.ez.no/certification/verify/272607
Certified Developer (4.4): http://auth.ez.no/certification/verify/377321

G+ : http://plus.tl/dspe
Twitter : http://twitter.com/dspe

Wednesday 02 December 2009 5:55:46 am

The requirements looking good. I have some more ideas:

1. A cool feature would be, too if the tabs, right_menu and left_menu boxes should be assign to a user role.
   For example: only administrator users could be see the 'setup' tab. Or only admins should be see the right toolbar where you can delete cache ....

   As standard all can see all and may be a defintion in an ini file can deny or give access to tabs, menues ...

   With this feature we only show the important feature for the customer and the admin has still the full backend without defining a seperate siteaccess.

2. admin content/browse enhancement http://issues.ez.no/IssueView.php?Id=14567 so we can for example copy a node in the same folder easily - very usefull!

What do you think about these ideas?

http://www.jac-systeme.de - Developers united in eZ Publish: http://www.cjw-network.com

CJW Newsletter 1.0.0 released: http://projects.ez.no/cjw_newsletter

Wednesday 02 December 2009 7:48:41 am

@Gerhard : Check your mail, didn't quite get what you meant on some of those. Screen shoots / Mock ups please! :P ;) (And dashboard is covered by the document, not with quick create though)

@Mark: That is covered by the document, also includes adding and removing attributes.

@James: We have considered that, but since we have a content structure and corresponding content structure menu that uses this left column we didn't include that. But what about only showing the first 5 (by setting) tabs and a "more" tab after that has a drop down on hover? (using pure CSS or javascript)

@Phillipe: Are you referring to the show children attribute or the 10 25 50 sub items selector?

@Kristof: Could be cool, but I think it won't benefit anyone but the super advance users though, and our current aim is everyone but especially editors (and developers by allowing them to extending the new parts). But if you have some idea on how that could be done in eZ Publish and for what, then please share and we can add it to the document.

@Felix: #1 Yes, Gaetano brought that up recently as well (I think he created an enhancement issue on it) so I'll add that to the document. #2 The doc mentions ajaxed browse interface, but that enhancement could make sense in the mean time (patch needs cleaning though, but I'll look into adding a misc section in the document).

@Pablo: Key ajax parts are mentioned in the document, if you have some suggestions on other key parts as well, please share ;)

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Wednesday 02 December 2009 9:05:12 am

I don't think the tabbed view for node information is such a good idea because it would result in alot more clicking around. The old way is perfect to me, although I wouldn't mind it being ajaxified.

Also I would not like to see the context menu taken away or compromised. I use it frequently with the tree menu and sub items list to save alot of clicks.

Wednesday 02 December 2009 10:23:14 am

@Eirik: #1 Noted #2 I agree #3 It has been asked for to be able to drag it so it is totally up to the user, will try to implement that. #4 It's 4 or 5 design firms in the loop, I'll have more info on that by mid December +/-

@Magnus:#node information: Our main goal is to reduce scrolling here, so any other suggestions?
#context menu: Have you used dropbox? We're aiming at something like the menu they have on file lists, as in a menu at the far right side of the sub items list (pr item), so it will save you a click and be far more intuitive. Personally I have met at least a couple of people pr year that didn't know about our context sensitive menus, unless they take a course or watch how others use eZ Publish..

@Pablo: Yes it is a bit general for the workflow gui, but if you have some specific ideas on what would make it more intuitive and easier/faster to work with then I'll add it. If you don't have any specifics we can see what the UI guy can propose on this (~2010 q1).

UPDATE: I have started implementing some of the concepts, and as part of it also syncing the pagelayout code with ezwebin to 1. enable cache-block's and 2. make it easier to override parts of it. Result so far: gone from 0.37 to 0.19 (On Windows Vista, so both way lower on linux!) seconds when refreshing while cached, so slightly faster to navigate admin :)

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Thursday 03 December 2009 12:50:20 am

#node information: I could see the scrolling being an issue with small screens. How about making it customizable? For instance you could make the tabs drag-n-dropable into the view field and vice versa.

#context menu: I'm note sure how that would save me a click though, it's the same principle isn't it? Click on the sub item and get a list of options. Is the plan to apply the same idea for the nodes in the tree menu?

Not knowing about context sensitive menu is a lot of time wasted!

Thursday 03 December 2009 2:40:50 am

I'd like to see the ability to limit options available to non-admin level users.

Create Here - It'd be nice to be able to easily control which classes appear in the create here dropdown. If you are using the Website Interface you often end up with a lot of unused, or rarely used, classes. If you give a user the ability to make the wrong choice sooner or later they will!

Image Aliases - Likewise, if you are using the image alias system to produce presentation graphics (and it's possible to do some pretty powerful stuff with the image processing, make changing banner and background graphics something a non-technical site administrator can do by simply uploading new pictures) it would be really nice to be able to hide image aliases so content editors don't have the ability to add banner images to the content area - whatever.

The idea of having a dedicated UI person is fantastic. It'd be great to have a some sort of user feedback system to collect initial reactions from editor level users when they first encounter Ez. I find non technical users find the admin interface, both the ezwebin front end and the main admin interface, quite daunting initially.

Paul Bolger

Thursday 03 December 2009 3:15:22 am

Nice one Paul

"I'd like to see the ability to limit options available to non-admin level users."

The tab system for tasks like the admin tasks needs to change too.

An admin user is different from a SEO administrator who needs to see stats. So we need to think as tasks being role based not globally defined.

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future