Title: Best practices for designers and developers: XMLC
Hi all,
This is my first post here. (at least on purpose!) I got this question yesterday and my answer as noted below to the other list. I do the design part, but I was wondering if there is additional requirements concerning XMLC I may have missed in my response.
> what would be the best environment and directory structure for the
> designers
> and developers to work together?
Thanks,
Lyrad
--------------------------------------------------------------
Hi Devlop01,
I am a designer at Lutris and have had some experience doing just this kind
of thing. It depends on the apps producing the graphics and the size of the
project.
For any size project I reccomend the directory structure is determined by
the business need so that later on updates can be made quickly.
example in a shoe site: Closet/Shoe/Lace
In large projects, file names can be generated by an application. The
naming has a lot to do with efficient production. It s faster and easier for
designers to use a naming format that does not require a key and is provided
as a list in advance.
For example:
shoe/shoeLace/orangeLace.gif
Large apps can be more challenging
For example I worked on a project that had 20,000 images. The directory
structure was nested directories per shoe with the application providing the
file name.
shoe/shoeLace/215_215.gif
The engineers used a custom application to generate the file names so a key
was needed, delivered in the form of an XL spreadsheet. This key was
delivered before the start of the project and allowed cross checking before
UI development began. It allowed us to catch problems early. In addition
this list can be signed off by the "Client" providing protection. It should
have a version also if here are edits. Also request that the key have no
redundant information so naming goes faster.
Advanced use:
If the App (Photoshop) application can produce multiple files & name them
automatically using scripts or macros. AND the engineering side uses an
application that can produce the same exact name requirements. It is
possible to completely automate the image production and meet engineering
requirements for naming without additional work. generally this must be a
simple namimg scheme like 1.gif. 2.gif, etc..
For example:
shoe/shoeLace/1.gif
Best Environment: Basically any place both the designer and engineer can
FTP is good. Back up the directories whenever there are changes, this way
the most recent files are available. There has been mixed success with CVS
on the Mac side. Also many design firms do not use CVS so having a common
place were the Designers are responsible for posting the most recent data
set is important. These images must be backed up daily if there are changes
daily.
Both sides should have a duplicate set of data as well.
also if the two teams are remote which happens often with XMLC produced
sites; Setting up a mini "Project Central" is reccommended. I use
intranets.com (free) they provide calendaring, groups, schedules, discussion
threads and yo can post links, provide team info the works..There are others
But I having a central point for the team is nice.
> -------- Original Message --------
> Subject: Enhydra: best practices for designer/developer environment
> Date: Tue, 20 Feb 2001 18:47:23 +0900
> From: Develop01 <Develop01@iq3.co.jp>
> Reply-To: enhydra@enhydra.org
> To: "'enhydra@enhydra.org'" <enhydra@enhydra.org>
>
> on our project, our designers are using dreamweaver and storing their
> html
> in a directory appropriately named "html". the developers are using
> enhydra+jbuilder to develop the business logic.
>
> the designers will use dreamweaver's check-in/check-out feature for
> their
> version control and the developers will use cvs to handle version
> control of
> the .java source and other enhydra-related files.
>
> what would be the best environment and directory structure for the
> designers
> and developers to work together?
>
> thank you.
|
|
