From: Peter L. <pe...@pe...> - 2005-02-24 20:19:10
|
So an attempt to start the discussions moving forward. With my new gig, I've inherited a codebase that, while stable, is going to be revised from the ground up. It's a pretty complex bit of software, but I already see a pretty clear path as to where I want to be at the end. And it really needs a support framework. I'm not even thinking about mod_perl integration at the moment. Simply the framework to really make a large perl application easier to deal with. I'm already looking at stealing large parts of the Krang codebase, but I'd like to do it in a constructive fashion if possible. The problem is that I'm not 100% sure of how to go forward in a way that would make it easy for others to build their own code out in the same fashion. Should I just go & steal liberally, or is there some desire elsehwere to try and get something going with MatchStick? --pete ---- Peter Leonard pe...@pe... |
From: Sam T. <sa...@tr...> - 2005-02-24 20:59:41
|
On Thu, 24 Feb 2005, Peter Leonard wrote: > I'm already looking at stealing large parts of the Krang codebase, but I'd > like to do it in a constructive fashion if possible. The problem is that I'm > not 100% sure of how to go forward in a way that would make it easy for others > to build their own code out in the same fashion. > > Should I just go & steal liberally, or is there some desire elsehwere to try > and get something going with MatchStick? There's definitely a desire to get something going with Matchstick. I expect to put some time into it sometime in the next few months. Within the next couple weeks I may know more specifically. But if you want to jump in here's the plan, as far as I've thought it out so far: - Modularize the stuff in the important bin/ scripts in Krang. Try to make them easy to extend via inheritence where possible. Put them in the Matchstick:: namespace. - Create a 'matchstick_create' script which creates little stubs scripts that do nothing more than bootstrap PERL5LIB and run. For example, a generated foo_install script might look like: use Matchstick::Installer; Matchstick::Installer->run(); I started on matchstick_create but I don't think I got very far. I think I put what I had in CVS. -sam |