How to manage a large control library?

16 Mar 2006 - 12:38pm
8 years ago
1 reply
355 reads
breezemaster
2006

Thanks for the insights Rob and good to know I'm not alone in the chaos.
Your process sounds much the same as what we have in place currently,
yet whats also proving difficult to manage within our team of six Visual
Designers. Perhaps we need a Keeper, like you suggest. Or perhaps pass
this role onto a project manager to maintain.. seems like more their
area in a way.

A resource site is something we've considered, it just comes down to
allowing development resources, and in a way, it seems it's for reasons
like this that Version Cue was invented. What added benefits can you
foresee a Resource site having..?

Re: PDF Delivery
PDF is not our company standard, so I'm up against a huge amount of
resistence in that area (we've resorted to offering annotated, sliced
(pdf exported).png's inside a word .doc to overcome it!). But the
advantages far outway the extra time taken to produce the word doc, so
thats where we're headed. Hopefully development and internal resistence
will grow to love the review features as much as we love staying inside
the joys of CS2.

Anyone else out there inside large firms requiring a similar workflow..?
I'd love to hear how you tackle the issues.

Many thanks,
Jim

>
> So far, I am the keeper of the master Photoshop prototyping template
> that contains all our widgets on different layers in the psd. We are a
> small team though. I have used just simple version control to monitor
> the progress of the prototyping template: "template v3.4.psd". As time
> permits, I make updates to the template that includes visual
> representations of coded widgets we have used, and variations of
> existing widgets.
>
> We are in the middle of creating a "resource site" for us UI designers,
> to better manage the different versions of our widgets we use. Similar
> to your email, we have standard widgets and controls, but many times we
> have to customize them to a specific project. We have one "calendar
> popup" widget, but many variations to account for the specific
> requirements for a project. We want to track all of this on our resource
> site (internal for us only).
>
> We deliver our screens and documentation in pdf form, because you can
> add some simple security to the document. We want people to be able to
> print our pdf's, but not be able to change any of the content. We can
> add editability security in the pdf. I just do a "save as" in Photoshop
> to create the pdf's of my screen designs.
>
> Does this help? Or answer your questions?
> Rob

----------------------
http://www.sentient.sprocket.co.nz
jimorrison at mailcan.com

--
http://www.fastmail.fm - One of many happy users:
http://www.fastmail.fm/docs/quotes.html

Comments

16 Mar 2006 - 5:01pm
Rob Nero
2005

We have much larger plans for our resource site, than just managing the
prototyping templates. It will be more of a central repository of
information we need to do our jobs efficiently and quickly. We'll be
using it to manage:
-design patterns
-"widget" javascript code
-design standards
-html templates
-branding colors
-icon libraries
-etc. etc...

Rob

-----Original Message-----
From: discuss-bounces at lists.interactiondesigners.com
[mailto:discuss-bounces at lists.interactiondesigners.com] On Behalf Of Jim
Morrison
Sent: Thursday, March 16, 2006 11:38 AM
To: discuss at lists.interactiondesigners.com
Subject: Re: [IxDA Discuss] How to manage a large control library?

[Please voluntarily trim replies to include only relevant quoted
material.]

Thanks for the insights Rob and good to know I'm not alone in the chaos.
Your process sounds much the same as what we have in place currently,
yet whats also proving difficult to manage within our team of six Visual
Designers. Perhaps we need a Keeper, like you suggest. Or perhaps pass
this role onto a project manager to maintain.. seems like more their
area in a way.

A resource site is something we've considered, it just comes down to
allowing development resources, and in a way, it seems it's for reasons
like this that Version Cue was invented. What added benefits can you
foresee a Resource site having..?

Re: PDF Delivery
PDF is not our company standard, so I'm up against a huge amount of
resistence in that area (we've resorted to offering annotated, sliced
(pdf exported).png's inside a word .doc to overcome it!). But the
advantages far outway the extra time taken to produce the word doc, so
thats where we're headed. Hopefully development and internal resistence
will grow to love the review features as much as we love staying inside
the joys of CS2.

Anyone else out there inside large firms requiring a similar workflow..?
I'd love to hear how you tackle the issues.

Many thanks,
Jim

>
> So far, I am the keeper of the master Photoshop prototyping template
> that contains all our widgets on different layers in the psd. We are a
> small team though. I have used just simple version control to monitor
> the progress of the prototyping template: "template v3.4.psd". As time
> permits, I make updates to the template that includes visual
> representations of coded widgets we have used, and variations of
> existing widgets.
>
> We are in the middle of creating a "resource site" for us UI
designers,
> to better manage the different versions of our widgets we use. Similar
> to your email, we have standard widgets and controls, but many times
we
> have to customize them to a specific project. We have one "calendar
> popup" widget, but many variations to account for the specific
> requirements for a project. We want to track all of this on our
resource
> site (internal for us only).
>
> We deliver our screens and documentation in pdf form, because you can
> add some simple security to the document. We want people to be able to
> print our pdf's, but not be able to change any of the content. We can
> add editability security in the pdf. I just do a "save as" in
Photoshop
> to create the pdf's of my screen designs.
>
> Does this help? Or answer your questions?
> Rob

----------------------
http://www.sentient.sprocket.co.nz
jimorrison at mailcan.com

--
http://www.fastmail.fm - One of many happy users:
http://www.fastmail.fm/docs/quotes.html

________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... discuss at ixda.org
List Guidelines ............ http://listguide.ixda.org/
List Help .................. http://listhelp.ixda.org/
(Un)Subscription Options ... http://subscription-options.ixda.org/
Announcements List ......... http://subscribe-announce.ixda.org/
Questions .................. lists at ixda.org
Home ....................... http://ixda.org/
Resource Library ........... http://resources.ixda.org

This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation.

Syndicate content Get the feed