click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Finn Bock (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLK-696) Use typesafe collection
Date Wed, 23 Jun 2010 19:54:54 GMT

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

Finn Bock updated CLK-696:
--------------------------

    Attachment: typesafe-select.patch

Making the Select control typesafe requires some non trivial changes. In the typesafe-select.patch
I have shown my take on it.

The main change is a common interface for both Option and OptionGroup (unimaginative called
OptionOrGroup).

A typesafe use of by the DataProvider becomes:

        select.setDataProvider(new DataProvider<OptionOrGroup>() {
            public Iterable<OptionOrGroup> getData() {
                List<OptionOrGroup> list = new ArrayList<OptionOrGroup>(); 
                list.add(...);
                return list;
            }
        });



> Use typesafe collection
> -----------------------
>
>                 Key: CLK-696
>                 URL: https://issues.apache.org/jira/browse/CLK-696
>             Project: Click
>          Issue Type: Improvement
>          Components: core, extras
>            Reporter: Finn Bock
>            Assignee: Finn Bock
>            Priority: Minor
>         Attachments: typesafe-select.patch
>
>
> In CLK-633, the API was upgraded to use type safe collections. The remaining internal
parts of Click should also be upgraded.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message