Re: [webmin-devel] Virtualmin: fondant_index and webalizer_bits

[paddy <pa...@pa...>]

Hi,

In the bakery this morning, a lady said "I only have to see fresh cream 
and I blow up like a baloon".  There was a strange light, a moment of
quiet and the unshakeable impression that all the ladies, customers and
staff alike, were sharing a moment of telepathic psychic unity.  I almost
expected some cheesy "choirs of angels" film music, and then it was gone.
Really, I kid you not.

Attached is a little number I'm calling fondant_index although the actual
implementation takes place in the lib, and a by the numbers icon collection
to go with it.  In it's defence:

	language independence
	appeals to some users
	economical on space, easier to read
	a thousand links on a page (scary!)
	low in calories

Nevertheless it could probably use some cleaning up.

Also attached: webalizer bits. check_configured and details.cgi sketches 
for webalizer.  I finally read the code/figured out how virtualmin does it.

Random Musings:

This webalizer check_configured starts to expand on the idea of a more than
binary output.  I have already wondered whether the dependencies of a 
a given service couldn't be structured so as to enable a generic 
implementation and rapid customisation.  But that's a long way off ;)

I currently have a set up where all the webalizer runs off a single daily
cron job.  This has the virtue of queing the jobs rather than kicking off
a large number simultaneously, I'm lazily imagining the converse for the
present setup without actually checking the details.

In general, I can't see how it could be practical to trace all possibities
when it comes to figuring out whether a job is cronned or not, perhaps
some index is called for.  Of course this is a general problem.

Standard disclaimers:

Yes, none of the code is good enough to include yet, although I hope it
is worth looking at.  I still have a todo list :)

Although (in my walter mitty imagination!) I am an experienced programmer,
my perl is at 'pigeon' level.  I mostly 'monkey see, monkey do', I will
certainly misguess the consequences of some logical operations, leading
to straight-foward bugs, and I have no concept of what is happening under
the covers, so can make only simple guesses about performance implications.
Beware!

Thanks once again for looking at this stuff.

Regards,
Paddy
-- 
Perl 6 will give you the big knob. -- Larry Wall