Hi,
I will step up to write this code. (if it is what I think it is)
I have responded to the message by beginning a requirements document.
http://www.officevision.com/pub/HTML-Widget/
Please read it and send me any comments.
The following are the questions I need advice on in order to proceed.
* What CPAN package namespace should I use?
I studied the existing packages, and what we are trying to do looks
like it fits under the existing top level package HTML.
I propose to take the space "HTML::Widget" (see package layout in
design doc). Gunther suggested the top-level "Widget" name space.
I was under the impression that we should stay away from creating
new top-level entries at CPAN unless there was really *nothing*
similar. Confusingly, there is already an HTML::Widgets. Thoughts?
* What CPAN packages should I begin with and build upon?
CGI and Apache::Request were mentioned. I figure I will use these.
HTML::StickyWidgets was also mentioned. Do you mean HTML::StickyForms?
Are there others I should build dependencies on?
* Should I begin immediately with a new Sourceforge project? another way?
The codebase I will begin with is in CVS on my local server.
Perhaps I should just continue that way and post versions to CPAN
for distribution. However, we may have email traffic for the project
that exceeds the general interests of the modperl list. Thoughts?
I would need to get enough responses from people who would join that
Sourceforge mailing list before it would be worth it to go do that.
Stephen
>There has been some discussion on the list lately about generating widgets
>ala CGI.pm, HTML::StickyWidgets etc...
>
>The thing is that these products or plug-ins are very HTML oriented. The
>widget is defined as an HTML widget like a textfield or checkbox or
>dropdown or what-have-you.
>
>What I am really looking for is a library that abstracts and allows widgets
>to be developed that are tied to an application not to a set of HTML
>necessarily. I guess I will start by providing an example of what I want
>based on what we currently do in our Java framework when he use Templating
>there. I'd like it if someone has developed the same thing in Perl that we
>could reuse, otherwise, we may need to write this.
<... snip ...>
