--- Mark Fuller [EMAIL PROTECTED] wrote:
On Sun, Mar 16, 2008 at 4:31 PM, James.Q.L [EMAIL PROTECTED] wrote:
I store ONLY $uuid in param because i need it in other controller. i
am passing $dbh to
Company:: modules because these modules are not inherited from C::A.
The example your
James.Q.L wrote:
I might be missing the point, but what's wrong with storing $uuid in
Company::Util as an our variable and accessing it from anywhere as
$Company::Util::uuid ?
correct me if i am wrong. that won't work under mod_perl. because our $uuid
is a global package
variable and
On Mon, Mar 17, 2008 at 7:05 AM, James.Q.L [EMAIL PROTECTED] wrote:
I might be missing the point, but what's wrong with storing $uuid in
Company::Util as an our variable and accessing it from anywhere as
$Company::Util::uuid ?
correct me if i am wrong. that won't work under mod_perl.
I want to know how I can layer pictures on top of each other like in a paint
program.
I have picture1.gif picture2.gif and picture3.gif and I want to put 1 on
top of 2 on top of 3.
I know I have to use transparent backgrounds or a masks but I have no
clue if it can be done
in an module
--- Mark Fuller [EMAIL PROTECTED] wrote:
On Mon, Mar 17, 2008 at 7:05 AM, James.Q.L [EMAIL PROTECTED] wrote:
I might be missing the point, but what's wrong with storing $uuid in
Company::Util as an our variable and accessing it from anywhere as
$Company::Util::uuid ?
correct me
On Mon, Mar 17, 2008 at 1:00 PM, James.Q.L [EMAIL PROTECTED] wrote:
i think you are right. it is fine as long as the global variable is
explicitly initialized.
No problem. So, what I was thinking is that you could initialize the
our $uuid with specific method you'd call from cgiapp_init (like
Hello Graham,
I just ran into this same problem last week. I was just crafting an email about
it but found it hard to explain. You did a great job :)
So, I load up CAP::Authen and CAP::Authz in my App superclass and the prerun
hooks get invoked in order (authen first, then authz).
Some people argue that with an MVC architecture, the database handle should
never reside in the controller, and should only be accessible in the model,
e.g.
http://www.oreillynet.com/onlamp/blog/2007/06/what_is_mvc.html
I'd be interested to know how other C::A people implement this in their
Evening,
I have been a CGI::Application follower for quite a while now. I
used it to create the engine off which my personal website/blog/
everything site runs. Back when I first started the documentation
was not as good as it is now and it took me a while to get everything
started.
