| Page 1 of 1 | [ 10 posts ] |
|
Hello
I'm looking for best practice techniques for applying a custom design to a YUI application. I'm a designer tasked with creating a new look and feel to an existing YUI 2.7 application. Any pointers or links to existing resources would be greatly appreciated. Thanks |
|
Hi Patrick,
You can start here: http://developer.yahoo.com/yui/articles/skinning/ Most of the widgets have their own skinning articles as well that break down the specific selectors you will need to extend or override to customize. Go to the widget landing page (e.g. http://developer.yahoo.com/yui/datatable/) and look for the skinning example (e.g. http://developer.yahoo.com/yui/examples ... nning.html). -Matt |
|
Hello Matt
Thanks for the links. I can't wait to dig in. From your experience what is the typical time range for skinning a component? Is this something that takes weeks or days? I'd like to get a feel for the real or hidden complexity. Thank you for your help. |
|
It really depends on your experience with CSS. It should be pretty straightforward.
Using the style view in Firebug can help to speed up the process by showing you exactly which styles are applied to which elements. |
|
It also depends on the widget you're styling.
Styling a DataTable can be quite extensive (comparatively at least). Especially if you combine it with a Paginator widget and perhaps some other widgets. Styling a Button widget is pretty straightforward. The first few times I worked with styling YUI widgets, it took anywhere from a day to a few days. I could whip together a DataTable with a Paginator in a couple hours now, maybe even less if I'm given a design to go by. Hope that helps. |
|
Hello Matt
I've read through those docs and I think I'm starting to understand. For simple presentational changes the UI is modified with standard CSS styles. Using color, font, and background graphic/colors. I've done hundreds of custom XHTML/CSS apps from the ground up so this will be typical. Code: Presentational CSS defines cosmetics such as color, imagery and typography. Without core CSS the controls stop working; without presentational CSS they simply look different. Beyond that level of applying presentation changes would it be considered an extension of the component? For instance if I wanted to add more DOM elements or change how the HTML/DOM is represented in the component. |
|
Hello Donald
Thanks for the time estimates Donald. Do you typically just skin a few components (as needed) or develop the UI as a whole, similar to a theme? My current project only uses about 5 components but plans to use many more. |
|
The level of markup customization depends on the widget. Most should have enough containers and hooks to support your design, and should also support adding extra elements. Replacing elements is possible, but will require extra CSS/JS customization, again, depending on the component.
|
|
I wrote something to help do minor changes in the style of widgets, not wholesale changes, but it can still be useful:
http://www.satyam.com.ar/yui/widgetstyles.html |
|
Hello patrick,
I normally style the widgets as I go. I try the keep the style sheet separated into sections for different widgets. But sometimes there's overlap like styling a Tool Bar -- Button on a Rich Text Editor where I keep the button style in the RTE section. I just added an auto complete for the first time and adding in the new styles was a snap. I basically just copied the colors from the other widgets, and plugged them in. (thanks to the sam skin) |
| Page 1 of 1 | [ 10 posts ] |
| You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum |
© 2006-2013 Yahoo! Inc. All rights reserved.
All code on this site is licensed under the BSD License unless stated otherwise.
About This Site · Security Contact Info
Powered by phpBB® Forum Software © phpBB Group