If you just need to generate a sprite: http://spritegen.website-
performance.org/
How to use it, http://css-tricks.com/video-screencasts/43-how-to-use-
css-sprites/
David B.
Le 26 mai 10 à 18:37, David Avendasora a écrit :
> I'm not a CSS guru... but I'll try. :-)
>
> On May 26, 2010, at 3:29 PM, David BON wrote:
>
>> +1 for CSS sprites.
>>
>> David B.
>>
>> Le 26 mai 10 à 14:13, Anjo Krank a écrit :
>>
>>> You probably could also make the images to CSS sprites? All
>>> images in one file? Might be easier to customize?
>>>
>>> Cheers, Anjo
>>>
>>>
>>>
>>> Am 26.05.2010 um 16:03 schrieb David Avendasora:
>>>
>>>> I've actually been planning an "ERSkin" template that would
>>>> include the ability to specify colors and such at project
>>>> creation and it will include the base .PSD file so you could
>>>> customize the original graphics as well and then export the slices.
>>>>
>>>> Look for it pre-WOWODC
>>>>
>>>> Dave
>>>>
>>>>
>>>>
>>>> On May 25, 2010, at 1:05 PM, David Holt wrote:
>>>>
>>>>> I'm sure that this could all be made into a customized "new
>>>>> framework template" if it's going to happen often.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>> On 25-May-10, at 7:30 AM, Andrew R. Kinnie wrote:
>>>>>
>>>>>> OK, so I'm dabbling in ERModernLook, finally, and I copied the
>>>>>> default skin into my workspace so I could fiddle with it and
>>>>>> make it match my apps proposed color scheme/design. I
>>>>>> therefore grabbed my friendly neighborhood Dave (in this case
>>>>>> Avendasora) and asked him what the best way to do this was.
>>>>>>
>>>>>> He said I need to:
>>>>>> 1. export it from the Wonder SVN into the path for my workspace,
>>>>>> 2. change the name
>>>>>> 3. then import it into the workspace (unnecessary if I didn't
>>>>>> already have the default skin checked out as part of my wonder
>>>>>> frameworks)
>>>>>> 4. then...
>>>>>> A. change the .project file so it's name property is the same
>>>>>> as the new project name
>>>>>> B. change the build.xml file to change the project name
>>>>>> C. change the build.properties file so:
>>>>>> 1) project.name is the same as the project name and
>>>>>> 2) project.name.lowercase is the . . . um . . . lowercase
>>>>>> version of the project name.
>>>>>>
>>>>>> It occurred to me that
>>>>>> 1. Not everyone has a friendly neighborhood Dave to ask, and
>>>>>> 2. For those that don't, it would be cool if this was actually
>>>>>> documented in some obvious place so that new people won't
>>>>>> immediately become so frustrated as to throw their computers
>>>>>> out the window when it doesn't work,
>>>>>>
>>>>>> AND/OR
>>>>>>
>>>>>> 3. That the re-factor mechanism change all this stuff for you.
>>>>>>
>>>>>> My 2 cents (for whatever that is worth, apparently more than
>>>>>> before against the Euro, less against the Canadian dollar, but
>>>>>> I digress)
>>>>>>
>>>>>> Andrew
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed May 26 2010 - 19:12:04 UTC