TMG-L Archives

Archiver > TMG > 2009-11 > 1257375386


From: "Darrell A. Martin" <>
Subject: Re: [TMG] File storage - wish list
Date: Wed, 04 Nov 2009 16:56:26 -0600
References: <110220092355.16090.4AEF71590009F84700003EDA22218675169B0A02D29B9B0EBFC0CECBCC9D0A970E9D0A970E030C@att.net><12128B8EC32B47CD9A371CF348F7216C@CharlieXXI> <110420092110.145.4AF1EDE20006244F0000009122218683269B0A02D29B9B0EBFC0CECBCC9D0A970E9D0A970E030C@att.net><CB8C6628C74543D6A1085CCE15BAA56A@CharlieXXI>
In-Reply-To: <CB8C6628C74543D6A1085CCE15BAA56A@CharlieXXI>


Jim Byram wrote:
> Charles,
>
>> Another caveat, there's several files still hanging out in the
>> Users\\\Roaming\TMG7 folder, in particular *.lo layout files, custom
>> toolbar file and *.ini config files that affect how stuff looks onscreen.
>> I don't know what all those Roaming\TMG7 files do, but if they belong to
>> individual projects, they could be included in each appropriate project
>> folder. I could be in error, but it appears these files can not be
>> "moved" to a new default location and thus require additional steps to
>> include them in any project copy/move at the time of the project
>> copy/move. So part of my "separate" project folders would include the
>> approriate aforeementioned files, perhaps in the "config" folder of each
>> project.
>
> These are program level files that can be used with any project. They _must_
> be in the user program data folder.
>
> Jim

Jim:

I am of the opinion that the files discussed above do NOT, in any way,
affect the DATA in a project. Practically speaking, this means that even
if they were deleted or corrupted at the system level (for example, in
an ugly system crash) there would be no impact on the information
contained in the project. The impact would be visual, and possibly data
entry tools. Correct?

However, appearance and data entry tools are both key components of a
user's environment, and it may be possible to create e.g. a toolbar that
is "tied", even if only by user behavior, to a specific project.
Therefore, to the extent that a user has created one or more elements of
the environment that are specific to a project, and that elements of
that environment cannot be placed in a user defined "everything for a
project" folder, that project is not truly portable.

I intend this as an observation, not a criticism. I am occasionally
irritated by what happens when I transfer data from my desktop to my
laptop, but I understand what is going on and I don't have any real
trouble dealing with it.

That said, I am of the opinion that, hypothetically speaking, anything
*whatsoever* that can be modified by the user is user data. It should be
treated as such for purposes of backup and restoration, if nothing else.
However, one must deal with operating system and security constraints,
among other things that get in the way of implementing some
theoretically desirable features.

Comments?

Darrell


This thread: