[ http://jira.jboss.com/jira/browse/JBIDE-1169?page=all ] Max Andersen updated JBIDE-1169: -------------------------------- Assignee: Sergey Smirnov Priority: Critical (was: Major) How hard would this be to do ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1169?page=comments#action_12396821 ] Max Andersen commented on JBIDE-1169: ------------------------------------- yes - sorry about that ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1169?page=all ] Max Andersen updated JBIDE-1169: -------------------------------- Fix Version/s: 2.2.x (was: 2.1) Sergey - any status/comments on this one ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Maxim Areshkau reassigned JBIDE-1169: ------------------------------------- Assignee: Maxim Areshkau (was: Sergey Vasilyev) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Maxim Areshkau commented on JBIDE-1169: --------------------------------------- It's very laborious work and i think it useless thing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Maxim Areshkau commented on JBIDE-1169: --------------------------------------- All styles which now is used in RichFaces are been copied manually, and each element in RichFaces templates has it's own folder with styles, we haven't store styles centralized. Allso in RichFaces exist many img elements which are generated by richfaces in runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Maxim Areshkau commented on JBIDE-1169: --------------------------------------- I propose following steps to resolve this issue: 1) We should send for richfaces templates information about skin which we should to use. For it we can create input field in page design option dialog, in which user can specify template specific options. For example skin. String will be looks like following "org.richfaces.SKIN=default", also in this field can be added configuration options for other templates. 2) I have reviewed sources of richfaces and there no possibility to get generated styles without running it's on server. I have run richfaces-demo on server and it's generated only one style file for each skin, so we can simply generate style on server and put it's in our resources folder in richfaces templates plugin.(by default richfaces support only 8 skins, so it's will be 8 style files). Also in richfaces are used many images which generated automatically(icons for tree for each skin, background images for panel and others) in runtime. It's also should be copied from demo application and placed in richfaces template resources folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-1169: -------------------------------------------- #1 Not sure I understand why field would contain org.richfaces.SKIN=default ? Wouldn't it just be picking this value up from faces-config.xml/web.xml and/or have a "Richfaces skin" combobox wich the following choices: Automatic, default, skin1, skin2, skin.. etc ? #2 okey - any chance that could be done so users could point to a dir with the generated styles to work with older/newer versions of the styles ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Dan Allen commented on JBIDE-1169: ---------------------------------- I wouldn't really worry about the custom, runtime manipulation of styles at this point. As a first step, I would say that you need to pick up the skin from web.xml (it is not in faces-config.xml) and get the styles that are used for the skin. You could even have a setting in a JBoss Tools property sheet where the user can enter a skin override. In the end, a skin is nothing more than a Java properties file which is fed into the XCSS files for processing. Rather than having to render the components, you could simply grab the XCSS file for a given component from the classpath and process it. Additionally, the VPE should process a custom XCSS file (declared using <a:loadStyle src="resource:///stylesheet/custom.xcss"/>), apply the skin Java properties file to get a CSS file that is fed into the HTML rendering engine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-1169?page=com.atlassian.jira.plu... ] Maxim Areshkau updated JBIDE-1169: ---------------------------------- Fix Version/s: LATER (was: 3.0.0.cr1) Too much work to fix this issue, see previous comments. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira