I have tried my own, possibly lame, search for any strategies which would make software components easier to reuse*. Alas, I have not found much discussing this exact subject related to Perl. Of course there is our favorite CPAN which I am a big user myself. I am thinking of something that would be a level up from that.

For example. When I am building (web) applications there are a number of things that I wind up rolling myself. Log-in window, input forms, widgit-y things. I may end up tossing them in my own libraries but I am sure the wheel has been reinvented many times.

People have made various stabs at modulizing widgets. Unfortunately everyone's approach is different. Differnt methods and properties. Different documentation layouts, yadda yadda. This makes it difficult to create things like application servers or development environments without having to roll your own widget set.

Would the development of some guidelines and strategy to facillitate adopting or deploying widgets and components be a welcome addition to the Perl community?

Any comments and insight is most welcome!

* - If you do have references to documents and/or discussions please post/pass along - I missed them.

  • Comment on Thinking about reusable software components

Replies are listed 'Best First'.
Re: Thinking about reusable software components
by princepawn (Parson) on May 19, 2001 at 02:41 UTC
Re: Thinking about reusable software components
by AidanLee (Chaplain) on May 19, 2001 at 05:09 UTC
    I believe the Template Toolkit has a set of widgets and so forth, though it may not be as complete as you're looking for.