--- Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> Sorry, Let me clarify:
>
> Ovid - you have the seed of this readonly class... john mentioned
> what needs to happen for it to get rolled into rose. any chance
> that might happen?
I can give you a definite possibility of a firm "maybe". I developed
it at work. Even though it would be useful for others and isn't
specific to our business, I'm unsure if I can do that. I've managed to
get a generous exception to our intellectual property clauses at work,
but this might be a bit much.
Of course, if I were to take each method in my ReadOnly metadata class
and post them individually for comments ...
That certainly wouldn't let me be an author, but others might be able
to leverage it.
(Also, I have a four day weekend, so I won't even get back to see my
code until next Tuesday)
On a side note, the code you posted for making things 'read only'
seemed a bit complicated for me. I simply do something similar to
this:
package My::DataCentre;
use base 'My::Rose::DB::Object';
sub meta_class { 'My::Rose::DB::Metaclass::ReadOnly' }
...
That way, there really doesn't need to be anything special in creating
readonly objects. The metaclass properly handles everything for it.
Cheers,
Ovid
--
Buy the book -- http://www.oreilly.com/catalog/perlhks/
Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
