Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS support needs to be improved to allow more control over styles applied by the library. [moved] #21

Open
jonnybbb opened this issue Nov 18, 2012 · 0 comments

Comments

@jonnybbb
Copy link
Contributor

This is Issue 21 moved from a Google Code project.
Added by 2010-05-05T06:34:00.000Z by andrew.pietsch.
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Medium

Original description

Currently both the validation & metadata plugin apply styles to widgets
that are defined in a public css file and automatically imported.

This needs to be improved so that users can at least specify what style
names are used.

Possible Options:
Let users specify global styles names for the plugin.  E.g.
ValidationPlugin.defaults().registerStyleName(Severity.ERROR,
"someArbitraryClassNameTheUserWants");
Let binders that apply style take a CssResource in thier constructor. 
ValidationBinder validationBinder = new ValidationBinder(ValidationCss css);

Other ideas welcome.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant