--- Tony Bowden <tony-maypole at kasei.com> wrote:
> On Sat, Oct 30, 2004 at 02:00:07AM -0700, Peter Speltz wrote:
> > ok_tables is different from display tables in that it doesn't put a tab in
> the
> > navbar for the table. Its very useful for private tables you want access
> to,
> > for example administration tables or tables you don't want a tab for and
> would
> > rather make a link for somewhere on certain pages.
> >
> > If you set it you have to add your display tables to it as well because the
> > code doesn't add display tables to it if it exists. I could be wrong as it
> > should add display tables to it if it exists. Anyway i use it like this:
> >
Actually maybe it shouldn't add display tables to ok_tables. I don't know.
> > sub display tables { qw/service/ };
> > sub ok_tables { qw/service price service_pkg/ };
> >
> Wouldn't it be better to have a private_tables() instead?
>
> sub display tables { qw/service/ };
> sub private_tables { qw/price service_pkg/ };
>
> Tony
>
Well, private to who? Privacy is a matter of
access/authorization/authentication. You need a user and maypole doesn't
provide that.
access_tables or accessible_tables would be better. ok_tables is easier to
type and is pretty descriptive but it really means these tables are ok to
acess. Since maypole revolves around providing access to tables , that may be
redundant.
My vote -- accessible_tables .
> _______________________________________________
> maypole mailing list
> maypole at lists.netthink.co.uk
> http://lists.netthink.co.uk/listinfo/maypole
>
=====
pjs
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT