-
- 1,131 Posts
Just a couple of suggestions for you guys!
The first one deals with the adjustable bar between the control options and the folder tree. Right now, the top frame is set for 200 pixels. Personally, I think it’s too small cause it tends to hide some of the control options. I think it would be better to default to around 350 pixels since this size won’t hide all the options. I tend to lean towards the idea that most people would prefer to see all the control options first rather than having a large tree area. The fix is simple...go to manager/frames/1.php and change line 23. It should have something like this in it:
frameset rows="200,*"
Change "200,*" to "350,*" and it’ll look a bit better by default. Just a suggestion!
Another one has to do with the opening logo on the login screen. Since the MODx Content Manager graphic is part of the background of sorts, it tends to be hidden behind the main login box. What I suggest is changing the CSS to where the logo is placed around 10 pixels from the top rather than the 85 pixels that it’s set for now (line 59 of manager/includes/accesscontrol.inc.php). Again...just a suggestion!
L8R!
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
-
- 56 Posts
My favourite change would be to get rid of the frames. The frequent reloading often gives errors that I can only solve with a refresh and sometimes by re-starting.
-
- 1,131 Posts
Without a major, major rewrite of the core code, getting rid of the frames would be a daunting task. It could be done though...but we’d be talking about some major work!
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
-
- 56 Posts
Indeed rthrash, they are frankly awful and make thing overly complex and unreliable.
Actually, it’s not all that bad. I had it half-done when this docman request came in. The action and processor scripts are all already neatly organized, and creating a nice menu was actually a pleasure
http://www.alistapart.com/d/hybrid/hybrid-4.html. It would even be better to have the menu options in a table in the database and build the menu on changing it, then cache it in a file or even another field in the database; this would make for easy addition of backend modules.
The main thing holding me up was what to do about the document tree; javascript is not my forte, and it really does need javascript to be done nicely. I was considering just shoveling the whole thing (the tree, that is) into an iframe for now, until somebody came up with a better idea.