Re: [Web-erp-developers] Interface

[skaill <sk...@ro...>]

There's technically a quick menu and a main menu.  In my view though I don't
think of the quick menu as such.  It is part of the header and I view it
more as akin to a toolbar of options.  In fact I have some further ideas
about that toolbar concept but not worth discussing until I think and play
around some more.  So, viewing the fast access/quick menu options as a sort
of toolbar then there is one menu.  Besides, the quick menu appears all the
time so the Menu option can only mean the "main" menu.

To me, the various setup options within webERP fall into two categories:
support tables and setup/admin.  For the support tables I'm thinking they
belong more appropriately in their respective section.

My take on where setup options should be located runs parallel to the
following ideas.  First, I think that knowing there is Sales Type
Maintenance leads to better understanding by the users.  They would know
that if they don't see a Sales Type that should be there then it can be
added to Sales Types by someone with access.  Yes, maybe they should not
have access to it and those options inaccessible to them should be readily
recognizable as off limits.  Usually this means graying them out, etc.
Notice if you bring up Word and click the drop-down menus there are options
available and other options inaccessible.  It is based on context with the
grayed options being inaccessible.  The context, in the setup case, is the
user.  The second idea is about having things where they have the most
relevance.  e.g. Sales setup with Sales options.    Also, where they would
best be accessed by someone other than the administrator so that strictly
administration options are within the administrator area.  These would be
options that no one else should see and need not understand exist such as
backup/restore, user maintenance, etc.  Possibly some of the config options
should be in the admin section as well but that's another topic!

There still may be good points about keeping the setup all in the one area,
however, these are my viewpoints about it so far.  It's something to think
about.  I do know that at least some mid-sized erp systems do organize the
setup options within the areas as I have done.  Possibly others have them in
a separate area...

Steve

----- Original Message ----- 
From: "Phil Daintree" <p.d...@pa...>
To: <web...@li...>
Sent: Monday, August 02, 2004 2:52 PM
Subject: Re: [Web-erp-developers] Interface


> On Sun, 2004-08-01 at 15:35, skaill wrote:
> > I've been working with the interface quite a bit now.  For those who
> > would like to see what I've done go to http://weberp.gocom.ca.  Please
> > make many, many comments good or bad.
> >
> Steve,
>
> I didn't understand what "main" was for - looks like we could lose this
> happily?
>
> Having setup on the main menu by default could be inviting trouble? I
> prefer setup options out of the way and not in your face as it were - so
> folks arent tempted to have a look! This would leave more room for
> longer more descriptive links that dont straddle several lines. It would
> be nice to space the links somehow.
>
> Another 2c
>
> Phil
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers