Hi,
Thanks for a great program!
I'm a newcomer to the ht://Dig community, but I'm about to go
elbows-deep into the source code--specifically for the htdig
component--to add some features required by a client.
>From reading the source code over the past few days, it seems to me
that the current htdig design has lots of interdependencies between
the classes which will make it difficult to substitute plug-compatible
replacements for the standard components. Has anybody considered the
need for a big-time refactoring of the classes, to try to tease apart
separate elements of the functionality? Ideally I'd like to package
some of the more useful components as separate libraries that could
also be used outside of ht://Dig.
I will probably have to do some such refactoring for my work.
Assuming that it is successful, I would love to re-integrate any
improvements back into the ht://Dig source code. Would it be possible
to get temporary read/write CVS access to the source code on
SourceForge? I would create a separate experimental branch for my
work and only integrate it back into the main branch if I got the OK
of the more experienced developers. I would also keep the dev list
posted about progress and solicit feedback.
If that is not acceptable, what is the feeling of the existing
developers getting lots of patches from me?
If neither of these is acceptable, I will probably have to fork off my
own private copy of ht://Dig to work on, which would be very much less
practical.
My SourceForge id is "mhagger".
Yours,
Michael
--
Michael Haggerty
[EMAIL PROTECTED]
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
