felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Valchev (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-1959) Move towards unified L&F and extended branding support
Date Wed, 06 Jan 2010 14:27:54 GMT

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

Valentin Valchev updated FELIX-1959:

    Attachment: tb6_1.0.1.jar

Attached tb6_1.0.1.jar

Available plugins:
- log 
- license 
- config manager 
- vmstat (System Information)

New features:
- simplified & unified :&F. The bundles only deploy plain HTML with minimal styling.
Static elements (button, input boxes) gets automatically updated with the theme colors. (See
support.css & support.js)
- i18n support - simple but efficient
- SimpleWebConsolePlugins with build-in i18n, templates support, template caching.
- examples!
- all plugins with English & Bulgarian language support :)

The default Web Console stylesheet included in the header changes the original L&F. It's
most visible in vmstat - table gets left and right border, but shouldn't and in log - the
links get green.

What I'm going to do next is the bundles manager plugin. I need you opinion - should I continue
or not? Do you plan adding JQuery UI to the Web Console, if so - when?

> Move towards unified L&F and extended branding support
> ------------------------------------------------------
>                 Key: FELIX-1959
>                 URL: https://issues.apache.org/jira/browse/FELIX-1959
>             Project: Felix
>          Issue Type: New Feature
>          Components: Web Console
>            Reporter: Valentin Valchev
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>         Attachments: jqueryui-vs-default-lnf.png, tb6.jar, tb6_1.0.1.jar
> Currently the Web Console uses heavily on the JQuery framework. Using a unified JavaScript
framework simplifies development of all plugins and unifies the used approach.
> However, when talking about visual styling, there are number of differences because each
plugin developer uses own styles.
> My suggestion is to adopt the JQuery UI . The benefits of using it as unified widget/css
framework are:
> - no time to spend on writing widgets already in the library
> - clean CSS visual styling
> - easy way to change the L&F by changing the theme (extended branding support!)
> - improved cross-browser support (JQuery UI takes care of CSS differences)
> Using the JQuery UI framework the developer shouldn't care about color but only for layout
- components position; and for data being displayed.
> To illustrate the benefits I've saved the "Log Service" page, modified it to use JQuery
UI, took screen-shot, modified the theme CSS only, and again took screen-shot, and finally
added the original L&F for reference, so you can easily compare the result.
> The attached image contains the combined screen-shots.
> "

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

View raw message