Hi Michael, No worries. Includes of a large number of global functions is a real pain. The system of includes your legacy app uses sounds horrific! :-)
I have used Agavi on a number of large projects over here in the UK, but nothing back in Aus yet. Thanks, Simon On 2 December 2010 20:25, Michael McHugh <[email protected]>wrote: > Hi Simon, > > Thanks for the reference. Nice article, but unfortunately doesn't help in > this particular case since the code does not use any objects :( (I think the > philosophy of the application is 'favour include over function') > > Nice to see another Aussie Agavi user :) > > Regards, > Michael > > On 03/12/2010, at 4:43 AM, Simon Holywell wrote: > > Hi Michael, > > I have been working on a blog post recently about dealing with globals > in large legacy code bases and my approach to it. I have just > published it and I think it might be of some use to you > > http://blog.simonholywell.com/post/2072272471/logging-global-php-objects-lazy-loading-proxy > > Basically I have put a proxy object in place that is best described as > a lazy loading proxy, which can also be used to better understand what > your legacy application is doing with global objects through logging. > > I am in the process of doing something similar to yourself where I am > slowly swapping out various parts of the application as I go. I am not > swapping in Agavi though on this one. > > Thanks, > Simon > > On 2 December 2010 06:56, Michael McHugh <[email protected]> wrote: > > Hi Folks, > > > Company I work for licenses the source code of a legacy system that has > been drip feeding updates over the last few years and I have finally been > given approval to migrate it to the Agavi framework (license allows us to > change any code). > > > I'm curious on any advice, tips, tricks or thoughts any others may have > from experience doing a similar thing. A couple of my ideas on this are > below.. > > > 1/ The idea is to initially wrap the application in the framework and > slowly refactor/extract parts of the original code into Agavi. I was > thinking of using a default route that passed to a module/action pair of > something like Legacy/Default that simply called the appropriate legacy > script. > > > 2/ Legacy code has significant use of globals and $_POST, $_GET, $_REQUEST > and $_COOKIE variables...<shudders> so in factories.xml would need to set > the 'unset_input' parameter to false on the AgaviWebRequest object. Until > this was addressed anyway. > > > And just to vent because I am the only coder on this project - this legacy > beast uses include('someFunction.inc') as if it were equivalent to > someFunction() ;) > > > Regards, > > Michael (@AlchemyCS) > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.agavi.org/mailman/listinfo/users > > > > > > -- > Simon Holywell > simonholywell.com > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > > > > > *Michael McHugh* | Chief Technical Officer > CompliSpace Pty Ltd | Bringing Good Governance To Life > Sydney - Level 1, 191 Clarence Street, Sydney NSW 2000 | T. +61 (2) 9299 > 6105 | F. +61 (2) 9299 2805 > Perth - Level 18, Central Park 152-158 St Georges Terrace, Perth WA 7000 > | T. +61 (8) 9288 1826 | F. +61 (8) 9288 1827 > E: [email protected] | W. www.complispace.com.au > > > IMPORTANT > (1) The contents of this email from CompliSpace Pty Ltd ABN 24 099 302 655 > and any attachments are confidential and privileged. Any review, > retransmission, dissemination or other use of, or taking of any action in > reliance upon, this information by persons or entities other than the > intended recipient is prohibited. If you receive this email in error, please > contact the sender, then delete the email. (2) Before opening or using > attachments, check them for viruses and defects. The contents of this email > and its attachments may become scrambled, truncated or altered in > transmission. Please notify us of any anomalies. (3) Our liability is > limited to re-supplying the email and attached files or the cost of having > them re-supplied. (4) This email is also subject to copyright. No part of it > should be reproduced, adapted or communicated without the written consent of > the copyright owner. Any personal information in this email must be handled > in accordance with the Privacy Act 1988 (Cth). > > > > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > > -- Simon Holywell simonholywell.com
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
