Hi Mollye,
What program are you using to track your graphics? Thanks.
Rick Quatro
Carmen Publishing Inc.
585-659-8267
r...@frameexpert.com
*** Frame Automation blog at http://frameautomation.com
Depends on functionality... I use a graphics tracker for file management
with thumbnails for
Hi Rick,
I've used Extensis Portfolio for years. Also used the older version of
ACSee and, while very good, it did not provide all the relational data
needed.
Several years ago, I worked with programmers at Ken Cook Company to
develop a Graphics Tracker
Hi Mollye,
What program are you using to track your graphics? Thanks.
Rick Quatro
Carmen Publishing Inc.
585-659-8267
rick at frameexpert.com
*** Frame Automation blog at http://frameautomation.com
Depends on functionality... I use a graphics tracker for file management
with thumbnails for
Hi Rick,
I've used Extensis Portfolio for years. Also used the older version of
ACSee and, while very good, it did not provide all the relational data
needed.
Several years ago, I worked with programmers at Ken Cook Company to
develop a Graphics Tracker
Hi Eduardo,
Seems like the answering messages got hijacked with wistful desires for
features and specifications...
To get back to your request, I intuit that you are documenting standard
work policies, either already existing or possibly needed. To support
the creation of your library, you can
On 22/06/2010 12:53 AM, Combs, Richard wrote:
I'm reminded of those software engineers I've dealt with who, _after_
they've completed a new feature, write requirements to match what
they've done. :-)
Popular saying among engineers:
Build to fit. Draw to match. Paint to cover.
(Too, too
Richard G. Combs wrote:
I'm reminded of those software engineers I've dealt with who, _after_
they've completed a new feature, write requirements to match what they've done.
:-)
At least you get (or got) written requirements. There are days I'd settle for a
written new feature list. :-)
.
-Original Message-
From: framers-boun...@lists.frameusers.com [mailto:framers-
boun...@lists.frameusers.com] On Behalf Of Lief Erickson
Sent: Tuesday, June 22, 2010 8:55 AM
To: framers@lists.frameusers.com
Subject: RE: A Graphics Library...Why?
Richard G. Combs wrote:
I'm reminded of those
: A Graphics Library...Why?
Eduardo F. Cidade, Sr., wrote:
I've built a specification for a Standard Operating Procedure (SOP)
regarding building a Graphics Library (call it a database, tracker,
whatever).
One thing that gnaws at this old writer is the standard question: Why?
I could use reasons
I've worked in the Engineering, Software Engineering, and Engineering Software
fields, and change history has been the preferred term. FWIW
Jack DeLand
___
You are currently subscribed to framers as arch...@mail-archive.com.
Send list messages to
Thanks Edward. You and fellow Frame Templars have given me a bit to go on.
The procedure is therethat's not the voidit's the why behind it.
Why am I doing it?
Is there a regulatory requirement?
Is this auditable (is that a word?)
Is there a Return on Investment (ROI)?
Again, so many
On 22/06/2010 12:53 AM, Combs, Richard wrote:
>
> I'm reminded of those software engineers I've dealt with who, _after_
> they've completed a new feature, write requirements to match what
> they've done. :-)
>
Popular saying among engineers:
"Build to fit. Draw to match. Paint to cover."
(Too,
Richard G. Combs wrote:
<< I'm reminded of those software engineers I've dealt with who, _after_
they've completed a new feature, write requirements to match what they've done.
:-) >>
At least you get (or got) written requirements. There are days I'd settle for a
written new feature list.
ank you for your cooperation.
> -Original Message-
> From: framers-bounces at lists.frameusers.com [mailto:framers-
> bounces at lists.frameusers.com] On Behalf Of Lief Erickson
> Sent: Tuesday, June 22, 2010 8:55 AM
> To: framers at lists.frameusers.com
> Subject: RE: A Graph
t lists.frameusers.com
Subject: RE: A Graphics Library...Why?
Eduardo F. Cidade, Sr., wrote:
> I've built a specification for a Standard Operating Procedure (SOP)
> regarding building a Graphics Library (call it a database, tracker,
> whatever).
>
> One thing that gnaws at this old
I've worked in the Engineering, Software Engineering, and Engineering Software
fields, and "change history" has been the preferred term. FWIW
Jack DeLand
Thanks Edward. You and fellow Frame Templars have given me a bit to go on.
The procedure is therethat's not the voidit's the "why" behind it.
Why am I doing it?
Is there a regulatory requirement?
Is this "auditable" (is that a word?)
Is there a Return on Investment (ROI)?
Again, so
Hi Eduardo,
Seems like the answering messages got hijacked with wistful desires for
features and specifications...
To get back to your request, I intuit that you are documenting standard
work policies, either already existing or possibly needed. To support
the creation of your library, you can
Good evening fellow Framers and Frame Templars
I've built a specification for a Standard Operating Procedure (SOP)
regarding building a Graphics Library (call it a database, tracker,
whatever).
One thing that gnaws at this old writer is the standard question: Why?
I could use reasons such as:
Depends on functionality... I use a graphics tracker for file management
with thumbnails for accurate identification and a format conversion
generator for multiple formats. Powered by a database, each graphic has
searchable metadata, automated file numbering and version control. This is
especially
Eduardo F. Cidade, Sr., wrote:
I've built a specification for a Standard Operating Procedure (SOP)
regarding building a Graphics Library (call it a database, tracker,
whatever).
One thing that gnaws at this old writer is the standard question: Why?
I could use reasons such as:
Good evening fellow Framers and Frame Templars
I've built a specification for a Standard Operating Procedure (SOP)
regarding building a Graphics Library (call it a database, tracker,
whatever).
One thing that gnaws at this old writer is the standard question: Why?
I could use reasons such as:
Depends on functionality... I use a graphics tracker for file management
with thumbnails for accurate identification and a format conversion
generator for multiple formats. Powered by a database, each graphic has
searchable metadata, automated file numbering and version control. This is
especially
Eduardo F. Cidade, Sr., wrote:
> I've built a specification for a Standard Operating Procedure (SOP)
> regarding building a Graphics Library (call it a database, tracker,
> whatever).
>
> One thing that gnaws at this old writer is the standard question: Why?
>
> I could use reasons such as:
>
24 matches
Mail list logo
