> >
> > >>ok_tables
> > >>---------
> > >>the description is clearly incomplete but I have no idea when this
> > >>method is supposed to be used, so I can't complete the description.
> > >
> > > This is a hash representation of display_tables(), used as cache.
> >
> > Then I'd suggest changing the description of display_tables and
> > ok_tables as follows:
> >
> > =head3 display_tables
> >
> > This is a list of the tables that are public to your Maypole
> > application. Defaults to all the tables in the database.
> >
> > =head3 ok_tables
> >
> > This is a hash of the public tables. It is populated automatically by
> > Maypole from the list in display_tables and should not be changed.
> >
>
> Done.
>
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:
sub display tables { qw/service/ };
sub ok_tables { qw/service price service_pkg/ };
Then i put some permissions on the price and service_pkg classes and managers
can change prices and service_pkgs but no one else knows the interface exists.
Please don't change it.
> maypole mailing list
> maypole at lists.netthink.co.uk
> http://lists.netthink.co.uk/listinfo/maypole
>
=====
pjs
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now.
http://messenger.yahoo.com
_______________________________________________
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:56 GMT