Jesse Vincent wrote:
*nod* though I guess I expect that in ~any application, you're going to want to extend the model classes from your app, so saying that your user class needs to use J:P:Login::ModelMixins::User feels like it might be right. I'm not SURE though.
The way I'm planning on using the Login plugin is to have a Person class with the application specific details and leave the User class stripped down, but we should be able to support either way with a minimum of difficulty. I plan on prepopulating the Person class (it's for a membership database) and only have an associated User record if they want to log in to the website itself.
*nod* The second half makes sense, but tying it to a class named User makes me a bit sad..but if that's the next step to get us closer to usable, so be it.
How about making it a fully qualified name, e.g APP::Model::PLUGIN::Class, so for this purpose it would be APP::Model::Login::User, which won't munge up the namespace so much. This would also make it easier to eventually create those on the fly. I'm not sure how this will play with the existing table creation code, i.e. are we still burning "User" as a tablename?
John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 _______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
