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] Commented: (CLK-512) Dropdown Menu Control
Date Fri, 05 Mar 2010 11:01:32 GMT

    [ https://issues.apache.org/jira/browse/CLK-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841816#action_12841816
] 

Adrian A. commented on CLK-512:
-------------------------------

>Its slippery because once you theme one control there will be requests to theme others
as
> well. Themeing individual component is at the wrong level of abstraction anyway. For

> example:
>
> Table.setStyle(BLUE);
> Butotn.setStyle(YELLOW);
> Menu.setStyle(BROWN);
> 
> The above is nonsensical and confusing, 
It is, if you present it like that :) , but we must also be pragmatic and see how our users
make use (or are willing to make use) of Click :).

Table.setStyle(BLUE) might not be a clear API naming at all, but the effect it is very practical.

> especially with a technology such as CSS 
> which can style the entire application from a single file.
I agree with that, but is there a simple way for the user to achieve this with Click? (With
just a few lines of code in 2 minutes for 80% of the use cases?)

I like complete theming (e.g. like in jQuery UI and especially the ThemeRoller) too, 
but how many users will invest the time to make thier own themes by constantly tweaking
controls and running the pages again until the desired effect is obtained? IMHO it's too error
prone (we have no "ThemeRoller for Click" to make this job easy).

IMHO it's very important to have a few good looking defauts.

IMHO  it would be better to have them on the application/Page (Border Page) level - of course
- and not on the control level, e.g.:

BorderPage#setDefaultStyling("/blue-look");
to apply the styling to all children of that BorderPage.
But there should be a  few styles (not just one) for the user to be able to choose from as
simple as it is now for the Table.

> CSS3 is also starting to provide a very cheap alternative to image based styling. 
> See the buttons on the Click home for an example
>  (yes, I realize IE doesn't understand  it :))
Untill CSS3 takes on, and considering that Click is very backwards compatible ... :).
An interesting idea (for this CSS3 but backaward compatibility too) could be to use "progressive
enhancement" instead of "graceful degradation", e.g.:
http://code.google.com/p/enhancejs/

> Dropdown Menu Control
> ---------------------
>
>                 Key: CLK-512
>                 URL: https://issues.apache.org/jira/browse/CLK-512
>             Project: Click
>          Issue Type: Sub-task
>          Components: extras
>            Reporter: Joseph Schmidt
>
> Please create a DropdownMenu control.
> This would be basically what the actual menu in click-examples does (+more looks).
> Here is a list of various decorations the DropdownMenu could take:
> http://vandelaydesign.com/blog/tools/dropdown-navigation-menus/
> It would be very helpful if the DropdownMenu would simply allow to choose another decoration,
> e.g. exactly like it's possible with the Table control:
> http://www.avoka.com/click-examples/table/table-styles.htm
> (there are many good styles at that blog page)
> This would save users allot of work - the same way the Table control does.
> I think the Menu control should be than more generic (not the dropdown version that it
is now), and it should be simpler
> to extend. For this it would also require additional properties, mentioned below:
> https://issues.apache.org/jira/browse/CLK-407
> https://issues.apache.org/jira/browse/CLK-406
> thanks,
> Joseph.

-- 
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