From quanta-devel  Tue Mar 01 11:29:31 2005
From: Andras Mantia <amantia () kde ! org>
Date: Tue, 01 Mar 2005 11:29:31 +0000
To: quanta-devel
Subject: [quanta-devel] .webprj changes
Message-Id: <200503011329.31255.amantia () kde ! org>
X-MARC-Message: https://marc.info/?l=quanta-devel&m=110967653823939
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0948309368=="

--===============0948309368==
Content-Type: multipart/signed;
  boundary="nextPart3338730.LrO50buKNy";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3338730.LrO50buKNy
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

  An important change was committed right now to the CVS HEAD. From now=20
on the .webprj file does not contain user specific settings, like=20
upload profiles, preview prefix, treeview status and debugger settings.=20
The reason is that when working in a team, you may want to share the=20
main webprj file, but not the above listed ones, from which some are=20
clearly specific for a single user (eg. the username in the upload=20
profiles), others would cause unneeded conflicts in the webprj file=20
(the treeview statuses) and so.=20
 So from now on there will be a .webprj file with the list of files=20
belonging to the project and some other common settings and a .session=20
file with the rest.
  If Quanta does not find a .session file, it will read the information=20
the old way from the .webprj file and create the .session file from=20
there. So the transition should be transparent for users who use the=20
CVS HEAD.=20
 The problem appears if somebody from a team is using CVS HEAD others=20
are using 3.4 or older. Right now the user specific informations are=20
NOT removed from the .webprj file, so users of 3.4 will not loose=20
anything, but if a CVS HEAD user makes a modification which affects an=20
user setting, it will not be written back to .webprj, so 3.4 users will=20
not notice it.
 I'm wondering if I should keep this behavior or once the new behavior=20
is tested and it works correctly to remove the user settings=20
from .webprj once a .session file was created for it. I'm wondering=20
before if I don't clean the .webprj file it will contain after some=20
time information that nobody uses, but if I clean, 3.4 users will loose=20
their setting. Any opinion?

Andras

=2D-=20
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org

--nextPart3338730.LrO50buKNy
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCJFIbTQdfac6L/08RAqP5AJ4rWmBkXFPb7flH2lpAZyBgYoYpVQCfZirP
cY44mvgdALWnk++yc9shv7Q=
=K4na
-----END PGP SIGNATURE-----

--nextPart3338730.LrO50buKNy--

--===============0948309368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel

--===============0948309368==--