[Apachetoolbox-devel] Re: Perlifying AT
Brought to you by:
bryanandrews
From: Bryan <io...@ap...> - 2001-09-18 15:27:50
|
You've got me very excited now! I can't wait to see an alpha version. Its hard to get started, but I feel once you have a working framework it will be easy for us to get going. If you'd like on the offical ATB devel list let me know your handle on sourceforge. If not don't worry about it, not really needed. The only catch I see so far (from what I've read) is a lack of module dependancie, freetype2 is needed by GD which needs libPNG, etc. Shouldn't be too difficult I guess. I can't thank you enough! -Bryan On Tue, 18 Sep 2001, Jay Lawrence wrote: > > Dear Bryan, > > I have been making a stab at the perlification process. Here is the > general gist of what I'm doing. > > a - every application, module or library is its own class file that > inherits basic operations from a base class > > b - there's a main class for all general configurations. > > c - all "configured" or "configurable" parameters are expressed in > each class file as a multilevel hash. Have a program - configure2pl > that extracts ./configure --help output to ease the development > process. > > d - nothing is/will be hardcoded except default values - but then we > can make anything configurable. > > e - each application, module or library has a descriptive block all > about itsself > > f - provisions for descriptions and help text for everything > > g - provisions for pick lists of value choices > > h - provisions for several prompt levels = basic choices -> advanced > user choices > > i - No module dependancies for Perl (at this point) - I have even > elected to use "wget" as it seems like a pretty slick tool! Not > everybody has "LWP" installed but existing Apachetoolbox users will no > doubt have wget. > > > I've been working with MySQL as my first app and am now up to: > - get source > - unpack > - configure > - make > - test > - install > > I've included a mechansim to check source files using md5sum or > expected file length. > > There's no practical limitations that I know of at this time. > > ----------- > > I don't want to steal your thunder on Apachetoolbox - I just sat down > tonight and got on a roll. ;-) > > I do hope you're cool if I put my name on the copyright ALONG with > yours for the stuff that I write? Is that ok? > > Anyway, once I get load/save and menu prompts working I'll send you > demo. > > Cheers, > Jay > > On Mon, 10 Sep 2001, Bryan wrote: > > > I'd love the help! I've currently setup a project on sourceforge.net for > > the development of ATB v2.0. Besides me, there's currently 1 other > > member, and he's back in school now. I'm just beginning with perl and I > > don't feel like I'm at the level I need to be for ATB 2.0 yet. So I'll > > take any and all help I could get! > > > > -Bryan > > > > On Sun, 9 Sep 2001, Jay Lawrence wrote: > > > > > > > > Hey Bryan, > > > > > > I have been exercising AT recently. (Myself, I had my own automated > > > build system underway before seeing yours). Anyway, I really like what > > > I see but of course have uncovered a number of limitations that I'd > > > like to work around. > > > > > > Being that I program in Perl 99% of my life I'd like to migrate Bourne > > > shell code to Perl. I thought I saw a reference somewhere that said > > > you'd like to see that happen. > > > > > > I have been thinking/sketching out what I think is a very viable way > > > to offer a flexible and robust interface to what has been written > > > already. > > > > > > Is this of interest to you? > > > Have you written anything to this end already? > > > Do you have things that you want to achieve going forward? > > > > > > Lemme know - I'd be glad to collaborate and have prototyped some stuff > > > already. > > > > > > Cheers, > > > Jay > > > > > > > > > > > > > |