Re: [Apachetoolbox-devel] First Pass Implementation

[Bryan <io...@ap...>]

This is a very good idea! I was thinkin along the same line, could we use
directories in the bin/ directory to build a submenu from? it would be
nice to have the menu placement information, the module version
information, and the actions the module needs to do, all right there in 1
file.

We'll need to take into consideration global modules like openssl. it
needs to be a module to install, but it also needs to be called from
mod_php if the --with-openssl option was selected from mod_php. and of
cource mod_ssl needs to run it to make sure openssl is installed before it
runs. we'll have to have bin/openssl (or whatever it's callee) 'export' a
global variable with openssl's version number after it runs the first
time. this way any modules afterward that need openssl wont have to run
anything.

you know this is a seperate program in of itself.  a lot of poeple would
have a use for this menu-system-framework. make it easy and stablable and
we'll have to register it's own domain just for it! hehe I've been working
more and more in perl (little system utilities) so I shouldn't be
completely worthless.

Do you want ke...@ap... to forward to your real account? Do
you even want an @apachetoolbox.com email address? It's yours if you want
it.

-Bryan


On Mon, 23 Jul 2001, Kevin J. Menard, Jr. wrote:

> Hey guys,
>
>     So, yeah, I haven't actually started to code anything yet <g>, but I
>     came up with an awesome idea this weekend (or so it seems atm).
>
>     This really should allow us to do a drop in module type thing.
>     Basically, the main atb program contains a hash of hashes.  When the
>     script starts up, we read all the entries in bin/ (or where ever),
>     which would correspond to one module accordingly.  This would populate
>     the hash and it's child hash.
>
>     Now, follow me here.
>
>     We sort the hash based on keys, and have a little for loop spit out the
>     menu, so it'll look like the existing one.
>
>     Now, the parent hash uses the value to select on the menu as the key.
>     So, for instance, PHP would have the key "php".  Then the sub hash would
>     have for instance a "title" key, which would say "PHP Menu" or what have
>     you.  Then a "code" key could contain a reference to code block
>     contained in the bin/ entry.
>
>     So, ideally, to add a new module, all you need to do is drop it into
>     bin, and hope the index value doesn't conflict with any others.  I'm
>     gonna try to start coding this soon.  Just been busy as hell lately.
>
>