[Date Prev][Date Next][Thread Prev] [Thread Next][Date Index] [Thread Index]

Modifications [was: Data Storage]


  • From: Gunnar Hjalmarsson  
  • Date: Sun, 11 May 2003 11:45:15 +0200

James S. Huggins (Ringlink) wrote:
==========================
Another advantage might be upgrading to the latest version while
retaining all your customizations?

Don't think so. Modifying the code means modifying the code irrespective of which programming language - or technique for
storing data - that is used.
==========================


No. But it does have to do with the separation of "code" and
"data".

To the extent that modifications/customizations can be made in
files that are separate from the code and which work "in the next
version" like they did in the prior version OR which have simple
modification instructions, installing new versions requires less
and less "reapplication" of custom code modifications.

That's undoubtedly true. But I believe that the _data_ (at least what I mean by "data") is well separated from the code already, and that you are actually thinking of structuring the code so that e.g. the HTML markup is separated from the Perl code.

So, how is the status in that respect? The HTML _is_ to a large extent
separated from the rest of the program, but I believe that the
_documentation_ leaves a great deal to be desired in that respect. You
mentioned the need for "modification instructions", and I do agree on
that. The lack of clear guidance about which modifications are easily
done, how they preferrably should be done, and what you should refrain
from doing if you want to avoid upgrading problems, is one of the
shortcomings in the current docs and/or FAQ IMO. Last December there
was a discussion on this list about certain modifications, and that
discussion showed the need for a docs revision in this respect.

Nevertheless, irrespective of the status of the program and the docs,
it will always be important that the users communicate their thoughts.
We are very interested in knowing about both modifications that have
actually been done, and desired changes. That way we can consider to
either make similar changes in the original program, or make changes
in the original program that make common customizations easier.

/ Gunnar


Follow-Ups from:
James S. Huggins (Ringlink)

References to:
James S. Huggins (Ringlink)

[Date Prev][Date Next][Thread Prev] [Thread Next][Date Index] [Thread Index]