As I start to see we could grow with Sections and Tabs pretty quickly.

 

I'm not against an author installing their own major tab/menu.

 

However, I would like us to consider some new standard section names.

 

I have been thinking.

 

Files (operates on files & Directories within the filesystems, managers searchers, scanners, viewers).

 

Disks (collection of tools that operate on disks. usage display, cross reference of md vs sd, mount, unmount foreigh disks, fdisk viewers, etc, etc).

 

Services (This is not events, this is a core application service that you may want to manage outside of an event. An event runs programs or services, this is the base service.)

  Example,  small webserver, mt-daapd, slimserver, nagios, samba, nfs, cups, etc, etc.

  samba and nfs will not be configured here, buy you may want to restart it.

 

Events (This is a grouping of actions to take place, which encompass, config restore, start, stop, config backup.)  A service or program operation participates in an event.

 

Authors (This could be a cool place to build on demand which collects or lists author plugins and provides hyperlinks to get there).

 

Before I get slammed, it's just some idea's of grouping. it's a community effort, so it is open for discussion.

 

I suppose it would look like

Main Settings Shares Users Utils authors disks events files services

 

(order is according to how it would sort. It seems to use alphabetical sequence)

 

In taking this further.

 

If I create a mt-daapd service. I would expect the service manager to see mt-daapd in the /etc/init.d directory and be able to control it.

 

I would expect through some tool or configuration links would be placed in the proper event directories to manage it automatically.

 

I would expect another plugin to install itself into the Settings subsystem to allow configuration of the mt-daapd file.

 

If I make a change here. the service has to be stopped and started.

Upon shutdown the service has to know enough to save any etc files to boot/etc

Upon boot the service has to know to restore any saved files from /boot/etc

These operations could be performed by start and stop also. I'm just elaborating.

 

Comments welcome.

 

I think if the Utils tab had subsections it would go a long way in assisting organization.

 

http://lime-technology.com/forum/index.php?topic=7092.0

 

Also, if too many tabs are defined, they wrap (although not really pretty, they work).

I did see the Section.

I used it in my Files page and put locate tool in a "Search Files" Section.

 

I thought that some of the Major Sections might be better grouped on top.

 

If I want to operate on Files in some manner do I want just to a utility section?

I see us having the following in the future.

Locate.

Browser (look around the fs).

Peeker (head/tail/read into /dev/null to cache the file, md5sum)

Grepper (or find derivative).

Open Files

 

on Disk I see

df -vH style usage tools.

cross reference of md vs sd.

smart health review tools.

fdisk lister, mount management,etc.

 

So should these be in sections under Utils?

 

Authors, I see this one being interesting as it could just traverse the .page files and present authors and versions along with jump points.

 

I see people wanting to manage events (or see last when or what is scheduled to occur in them).

Same with services.

 

Why burden Tom with that?  If you want, you can write an "authors" plugin that does it by scanning the .page files and presenting them however you want!

 

Also, you can nest subpages (ie => Task/menu/menu/menu/php) , and when you click on the icon, the icons on the submenu under that will then be displayed in the UI.... so you can have very deep nesting.

 

When you use nesting however, you need breadcrumbs to go backwards.... and that needs to be added to stock.

I was kinda thinking the way this forum works. You guys can't see it, but in the Admin panel you have your regular tabs and then there is a tab called Modifications. Normally all the settings of additonal plugins aka packages go on that tab. I kinda like it that way because it leaves the core stuff alone and you know if you installed a package it normally goes there and it does not conflict at all with the core system.

 

Under that of course when you click on it there are more tabs kinda like this.

Misc | Site Map | Glossary |

 

So when you enter the Modifications area they have more or less buttons you click which will open up the tabs or link to the page that has the settings for that particuar package. So ideally speaking all you would in a matter of words be doing is creating a link on the Modifications page that way it that particular page isn't long as heck full of stuff.

 

I don't see why the settings couldn't all be on that page in a sub section, but thats not how they do it.

Why burden Tom with that?  If you want, you can write an "authors" plugin that does it by scanning the .page files and presenting them however you want!

 

It wasn't my intention to burden tom with anything.

It was just some comments that I thought it could be of use.

I mentioned it because it seemed just as you said. scan the page files and present them.