click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLK-565) Provide Control builder / factory class
Date Sat, 02 Nov 2013 13:17:18 GMT

     [ https://issues.apache.org/jira/browse/CLK-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adrian A. resolved CLK-565.
---------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.4.0)
                   2.3.0

The project Chainer:
http://code.google.com/p/chainer/
solves this problem nicely and it's already listed on the Click main site.

> Provide Control builder / factory class
> ---------------------------------------
>
>                 Key: CLK-565
>                 URL: https://issues.apache.org/jira/browse/CLK-565
>             Project: Click
>          Issue Type: New Feature
>          Components: examples
>    Affects Versions: 2.1.0
>            Reporter: Malcolm Edgar
>            Assignee: Adrian A.
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: ControlFactory.java, TableBuilder.java
>
>
> Using a factory or builder pattern to create controls is a great way to reduce the number
of lines of code in an application and can also help standardize your application.
> There are 2 common pattners for doing this, one is the factory pattern, for example:
>         Table sizesTable = new Table("sizes");
>         ControlFactory.addColumn(table, "label", "Metric");
>         ControlFactory.addColumn(table, "value");
> The other is the builder pattern, for example:
>         Table sizesTable = TableBuilder.simpleBuilder("sizes").addColumn("label", "Metric").addColumn("value").build();
> Both of these styles have pros and cons.  Please see attached examples.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message