[drupal-devel] [task] Remove admin.module
Project: Drupal Version: cvs Component: admin.module Category: tasks Priority: normal Assigned to: drumm Reported by: drumm Updated by: Goba Status: patch +1 on removing the admin module, but why not name the admin page function system_admin_main_page() or something prefixed with 'system', to be consistent? Goba Previous comments: ------------------------------------------------------------------------ January 14, 2005 - 01:55 : drumm Attachment: http://drupal.org/files/issues/system.module_1.patch (1.85 KB) This incredibly small module seems like it should be rolled into system.module to me. Admin.module can be removed once this patch for system.module is applied. -- View: http://drupal.org/node/15570 Edit: http://drupal.org/project/comments/add/15570
Goba wrote:
Project: Drupal Version: cvs Component: admin.module Category: tasks Priority: normal Assigned to: drumm Reported by: drumm Updated by: Goba Status: patch
+1 on removing the admin module, but why not name the admin page function system_admin_main_page() or something prefixed with 'system', to be consistent? Goba
Previous comments: ------------------------------------------------------------------------
January 14, 2005 - 01:55 : drumm
Attachment: http://drupal.org/files/issues/system.module_1.patch (1.85 KB)
This incredibly small module seems like it should be rolled into system.module to me. Admin.module can be removed once this patch for system.module is applied.
I vote no on this being removed. Drupal desperately needs a control panel page rather than a block adminstration list. This module suits that purpose. It just needs to be developed. Developing this into a real control panel will allow the removal of the link list from the user list and simply usage for everyone. A control panel has more possiblities for improvements and seperates the adminstration from the user section which is a plus for all that use Drupal in a corporate or intranet environment. Carl
Op dinsdag 25 januari 2005 18:50, schreef Carl McDade:
ote no on this being removed. Drupal desperately needs a control panel page rather than a block adminstration list. This module suits that purpose. It just needs to be developed.
Its very much debateable if we actually really want an admin-panel. I for one do not want this at all. There are much cleaner *and modular* methods available. Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
* B?r Kessels <berdrupal@tiscali.be> [2005-01-25 13:02]:
Op dinsdag 25 januari 2005 18:50, schreef Carl McDade:
ote no on this being removed. Drupal desperately needs a control panel page rather than a block adminstration list. This module suits that purpose. It just needs to be developed.
Its very much debateable if we actually really want an admin-panel. I for one do not want this at all. There are much cleaner *and modular* methods available.
This is a contentious issue as Ber hints at here. Newcomers may not know that once upon a time (4.3?) there was a separate "control panel" or admin side to Drupal sites; clearly the "combine them all into the public UI" side won that debate. Perhaps a suitable solution could be setting a CSS id attribute ('is_admin'?) to be used in the HTML body tag so that those who want to could format admin pages differently? Or some other sort of CSS flag? I personally find having to squeeze/use all the admin forms and layouts within the public site layout troublesome, but maybe this would be a solution to allow both usages? I imagine the difficulty occurs in deciding which actions are "admin" actions or just user or contributor actions. Probably somewhat ambiguous. Thoughts? -- ______________________________ toddgrimason*todd-AT-slack.net
Op dinsdag 25 januari 2005 22:49, schreef Todd Grimason:
Perhaps a suitable solution could be setting a CSS id attribute ('is_admin'?) to be used in the HTML body tag so that those who want to could format admin pages differently? Or some other sort of CSS flag?
You can use sections.module perfectly for this. Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
Bèr Kessels wrote:
Op dinsdag 25 januari 2005 22:49, schreef Todd Grimason:
Perhaps a suitable solution could be setting a CSS id attribute ('is_admin'?) to be used in the HTML body tag so that those who want to could format admin pages differently? Or some other sort of CSS flag?
You can use sections.module perfectly for this.
Regards, Bèr
But has anyone noticed that There is a growing problem with the user not being able to find functionality within the present UI because most of it is hidden within collapsed list. At present listing is starting to get more out of hand as modules and their administration become more complicated. This will be escalated by the addition of more core modules which are not configurable and cannot be turned off in most cases. A UI I nested list should never be more than 3 deep and 7 items per list. after that the user starts getting lost and frustrated. I is very close to CLI in that the user is expected to learn the structure and syntax first before being able to give a command. The list admin structure is counter intuitive and has absolutly no visual cues. Visual overview, grouping and visual cues are the reason for the popularity of just about every UI including the most popular, Windows. In this particular case it is not a matter of themeing either. The child pages are complete and have explainations within them. It it the UI leading to them that is the bottleneck. There is no overview of the structure of the admin UI.
Carl McDade wrote:
But has anyone noticed that There is a growing problem with the user not being able to find functionality within the present UI because most of it is hidden within collapsed list.
I agree that this is an issue. In most of the sites I'm building these days, I wind up building two menu structures: one for the site map and another for user actions. -Eric
Op woensdag 26 januari 2005 06:13, schreef Eric Scouten:
Carl McDade wrote:
But has anyone noticed that There is a growing problem with the user not being able to find functionality within the present UI because most of it is hidden within collapsed list.
I agree that this is an issue. In most of the sites I'm building these days, I wind up building two menu structures: one for the site map and another for user actions.
-Eric
I am working on this, but up till now received no comments. I would like people to review (and report back!!) my efforts till now. 1) documentation is on http://dev.bryght.com/t/wiki/DrupalRestructure 2) working example is at http://consistent.drupaldevs.org/ Please log in there with your drupal ID, and give me a shout (IM or mail) ***NOTE!! the settings and changes wont make any sense for anonymous **nor** for registered users. Only adminsitrators see how it should look!** So again: Do not start yelling: "it looks like crap" when you do not have admin rights there!! Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
Bèr Kessels wrote:
Op woensdag 26 januari 2005 06:13, schreef Eric Scouten:
Carl McDade wrote:
But has anyone noticed that There is a growing problem with the
user not
being able to find functionality within the present UI because most
of
it is hidden within collapsed list.
I agree that this is an issue. In most of the sites I'm building
these
days, I wind up building two menu structures: one for the site map
and
another for user actions.
-Eric
I am working on this, but up till now received no comments. I would like people to review (and report back!!) my efforts till now.
1) documentation is on http://dev.bryght.com/t/wiki/DrupalRestructure 2) working example is at http://consistent.drupaldevs.org/ Please log in there with your drupal ID, and give me a shout (IM or mail) ***NOTE!! the settings and changes wont make any sense for anonymous **nor** for registered users. Only adminsitrators see how it should look!** So again: Do not start yelling: "it looks like crap" when you do not have admin rights there!!
Regards, Bèr
So if I can't see it how can I give feedback ;)
You, and all others now have have admin rights. Bèr Op donderdag 27 januari 2005 08:42, schreef Carl McDade:
Bèr Kessels wrote:
Op woensdag 26 januari 2005 06:13, schreef Eric Scouten:
Carl McDade wrote:
But has anyone noticed that There is a growing problem with the
user not
being able to find functionality within the present UI because most
of
it is hidden within collapsed list.
I agree that this is an issue. In most of the sites I'm building
these
days, I wind up building two menu structures: one for the site map
and
another for user actions.
-Eric
I am working on this, but up till now received no comments. I would like people to review (and report back!!) my efforts till now.
1) documentation is on http://dev.bryght.com/t/wiki/DrupalRestructure 2) working example is at http://consistent.drupaldevs.org/ Please log in there with your drupal ID, and give me a shout (IM or mail) ***NOTE!! the settings and changes wont make any sense for anonymous **nor** for registered users. Only adminsitrators see how it should look!** So again: Do not start yelling: "it looks like crap" when you do not have admin rights there!!
Regards, Bèr
So if I can't see it how can I give feedback ;) Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
On 25 Jan 2005, at 11:49 PM, Todd Grimason wrote:
* B?r Kessels <berdrupal@tiscali.be> [2005-01-25 13:02]:
Op dinsdag 25 januari 2005 18:50, schreef Carl McDade:
ote no on this being removed. Drupal desperately needs a control panel page rather than a block adminstration list. This module suits that purpose. It just needs to be developed.
Its very much debateable if we actually really want an admin-panel. I for one do not want this at all. There are much cleaner *and modular* methods available.
I personally find having to squeeze/use all the admin forms and layouts within the public site layout troublesome, but maybe this would be a solution to allow both usages? I imagine the difficulty occurs in deciding which actions are "admin" actions or just user or contributor actions. Probably somewhat ambiguous. Thoughts?
You could just have a seperate theme / template for the admin site and switch based on if (arg(0) == 'admin') { $custom_theme = 'admin'; } -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
You could just have a seperate theme / template for the admin site and switch based on if (arg(0) == 'admin') { $custom_theme = 'admin'; }
Which, despite a lot of people suggesting is not working for stuff like the node/$nide/edit pages or the book outline editors for non-book pages. Goba
participants (7)
-
Adrian Rossouw -
Bèr Kessels -
Carl McDade -
Eric Scouten -
Gabor Hojtsy -
Goba -
Todd Grimason