|
|
|
|
|
|
|
|
|
|
| WEBSPHEREPOWER MAGAZINE ARTICLE DIRECTORY |
|
|
|
|
|
|
|
Projects > Reusable Code
Home > Projects > Reusable Code
Articles
Using a reusable code approach to HTML select option lists, part VI
WebSpherePower Magazine - January 2004
During the course Jeff Chilton's series, he showed you how to create a small, but robust framework through a succession of systematic, incremental steps. In this final installment, he looks back on and sums up this long journey.
Using a reusable code approach to HTML select option lists, part V
WebSpherePower Magazine - December 2003
In Jeff Chilton's continuing series, he's shown you how to create a framework for populating HTML select statements with options from a variety of potential sources. In this installment, he'll show you how to use the framework for a new, unintended purpose.
Using a reusable code approach to HTML select option lists, part IV
WebSpherePower Magazine - December 2003
If you've been following Jeff Chilton's continuing series, you're now well familiar with his framework for populating HTML select statements with options from a variety of potential sources. In this installment, he'll show you how to create a component factory.
Using a reusable code approach to HTML select option lists: part III
WebSpherePower Magazine - November 2003
In Part I of this series, Jeff Chilton created a simple framework for the purpose of obtaining an ArrayList of Struts LabelValueBeans to support an html:options tag. In Part II, he added an additional implementing class to the portfolio and enhanced the base framework. This time, he'll show you how to reverse the order of things by first enhancing the base framework and then adding yet another implementing class.
Using a reusable code approach to HTML select option lists: part II
WebSpherePower Magazine - October 2003
In the first installment of this series, Jeff Chilton created a simple framework for the purpose of obtaining an ArrayList of Struts LabelValueBeans to support an html:options tag. He continues with this little microcosm of framework concepts, by adding another flavor of an implementing class to the portfolio.
|
|
|
|
|
|
|
|
|
|
|
