[Apachetoolbox-devel] Prototype almost ready

[Jay L. <jla...@in...>]

Kevin,

I think we're almost ready to test out the first prototype.

Legacy conf files to new conf file conversion would be excellent. I
think you'll find that it isn't that hard to do...but you never know.

My work is slim on docs but seems to be quite functional. The UI is a
bit clumsy but so am I. ;-)

Expect code in your hands very soon,
J

On Fri, 5 Oct 2001, Kevin J. Menard, Jr. wrote:

> Hey guys,
>
>     Well, I finally read this email.  This idea is pretty much the route I
>     was taking (actually almost to a T), but it's a hell of a lot prettier
>     than what I was coming up with :)  Right now, in school I am pretty
>     busy, and I don't think I would have had time to write out the core
>     program.
>
>     Jay, when you get the code up, let me know ASAP though, because I plan
>     on writing a legacy module conversion script (as well as allowing one to
>     add modules quite trivially).  This I think would ease the transition
>     quite a bit.
>
>     Other than that, I would like to head up a packaging implementation with
>     this as well.  I could work no the debianification, but the RPM support
>     on debian is rather minimal, so I would encourage someone else to work
>     on it.
>
>     That's all.
>
> --
>  Kevin
>
> Sunday, September 23, 2001, 5:49:26 PM, you wrote:
>
> B> Very impressive!  I can't thank you enough for the time and effort you're
> B> putting into this!  Have a blast with the house!  I've added you into the
> B> apachetoolbox project on sourceforge, if there's something something I
> B> missed on SF let me know.
>
> B> -Bryan
>
> B> On Sat, 22 Sep 2001, Jay Lawrence wrote:
>
> >>
> >> Dear Bryan,
> >>
> >> How are things? Just a quick note to let you know I have made some
> >> excellent progress with my concept for Apachetoolbox. I think you're
> >> going to be suprised.
> >>
> >> I have to say that what I am writing is a bit of a departure from what
> >> you have so far. Although I may have taken some more elaborate
> >> approaches to programming this I think you guys will find that it
> >> works well and logically.
> >>
> >> I don't want to send you demo code *just* yet because I want to pass
> >> it through one refactoration phase. At least then I will have better
> >> method naming and probably break it apart into more logical chuncks
> >> than it currently stands.
> >>
> >> In a nutshell however, this is what I've been doing:
> >>
> >>  a - Base class Apachetoolbox drives:
> >>        - build sequence
> >>        - save/load
> >>        - global preferences
> >>        - inherits its choice of ONE UI module below
> >>
> >>  b - Each software package has its own package which inherits
> >>      Apachetoolbox::Application. This package does:
> >>        - registers itsself with Apachetoolbox class
> >>        - fetch/check/unpack
> >>        - configure, make, and install
> >>        - configuration options list
> >>
> >>  c - Each software package can have a list of modules (Apache
> >>      being the most obvious case). Each module inherits
> >>      Apachetoolbox::<application>::mod. This package
> >>       - registers itsself with its application
> >>       - configuration options related to this module for the
> >>         main app
> >>
> >>  d - There are any number of UI modules. The one that I am going
> >>      to focus on is a Curses one. It is not a big stretch to build
> >>      a CGI, Tk or GTk UI module at all.
> >>       - provides all menus and user prompts
> >>
> >> What works now:
> >>  a - building of standard modules and libraries
> >>      - the funky processes like for mod_perl and PHP still needs to be
> >>        addressed - but all in good time
> >>      - I have not tackled 3rd party apache modules just yet either
> >>
> >>      - these will come next after I've finished refactoring and can
> >>        send you demo code
> >>
> >>  b - Main menu and submenu code in Curses module
> >>      - subject of my code refactoring now
> >>
> >>  c - Src download and verification
> >>      - one idea might be to build a list of sites for a program
> >>
> >> Things for consideration
> >>  1 - conversion of current configuration to new save file format
> >>  2 - I'm only building on RedHat 7.1 for now ... but I need to build
> >>      on Solaris as well. There are necessary hints for different
> >>      architectures, I am sure. (MySQL is one of them)
> >>  3 - scads of other stuff I am sure.
> >>
> >> Unfortunately, I have to focus on some other projects around here.
> >> Namely the renovation of my house! So I cannot put as much time into
> >> this as I'd like. But, I want to take this to deliverable status ASAP
> >> because I need it for my work too.
> >>
> >> Anyway, what I can do is upload the code to sourceforge and then you
> >> guys can try it on for size.
> >>
> >> Cheers,
> >> Jay
> >>
>
>
> B> _______________________________________________
> B> Apachetoolbox-devel mailing list
> B> Apa...@li...
> B> https://lists.sourceforge.net/lists/listinfo/apachetoolbox-devel
>

-- 
Jay Lawrence  - 613-795-9169 - ja...@in...
Infonium Inc. - Open Source Information Management Strategies