> > I will post the thing in a few days, we are still polishing
> > some details...
>
> The service repository should be done than so there will be no harm
> in adding it to the Fulcrum repository when you're finished :-)
Ok. If and when that happens, I would also like to back-port the menu
service to 2.1 (or 2.2, or whatever). For now, a short heads up:
* There is a basic implementation of a Menu in the service;
this implementation, called TurbineMenu, reads menu information
from a set of tables (seven tables in total). For now, the
names for those tables are in our project's namespace, but
we could change that to TURBINE_* if it is necessary.
* The thing we are now changing is this: two of the tables have
references to Turbine permissions in them. The original design
placed an integer column in those tables, pointing to the
permissions table primary key. However, this presents a problem:
some of our tools generate the contents of the menu tables
automatically, and in order to generate the primary keys, the
tools would have to know the mapping key=>permission. So, what we
are doing is changing this so that the menu tables store the
permission name (String). It is not as clean as the original
idea, but it looks a lot more flexible... Any opinions?
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
