Hi (to Rafal mainly, I think),
I have code which extends the old TurbineUser and TurbineUserPeer - which I am now
updating it with the latest turbine stuff (as I want to use scheduling - but can't get
it to work with the old turbine - and I didn't keep the source - doh!).
The problem I am getting now is that there seems to be 2 definitions of the column
names - on TurbineUserPeer via the map builder - which was good, since I could
override that and use my custom table/column names.
But these column names are also on the User interface - as hard coded strings
(obviously a big no-no anyway.)
Now my problem is that a method like getUserName, uses User.USERNAME to find the
username value - but since this is the hard coded string, it does find my overridden
column name in the permstorage object....
So - is this area of turbine being worked on as part of the ACL changes, or is it
considered stable? My thoughts are to remove the column names from the user object
and change base user to use the peer column names (again) - allowing for mapbuilder
customisations - alternatively we move the mapbuilder stuff into the User interface
and out of turbine user peer - but that doesn't feel right.
Comments please? Or explanations about this should work?
Thanks,
Chris
---
"surely it is madness to accept life as it is and not as it could be"
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
