17 Jun
2015
17 Jun
'15
6:49 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear all,
in R14.1.x and in the somehow upcoming R14.0.1 release, tdevelop has reverted to use
.kdevelop project files instead
of .tdevelop files. Also, the main entry in such file was reverted to "kdevelop"
instead of "tdevelop". This has been
done to improve compatibility with KDevelop3 project files.
When you switch to the "new" version, you will need the following renaming:
1) .tdevelop files -> .kdevelop
2) .tdevelop.filelist files -> .kdevelop.filelist
3) change <tdevelop> to <kdevelop> in any .kdevelop file
4) change </tdevelop> to </kdevelop> in any .kdevelop file
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVgRiSAAoJECp1t8qK3tXPPwoP/jciCGEv4z4kx581xI9X0iCr
WjiZrmQX+ZbQOYhtv2+ZFsIjy3MdPvp5uWU0nEkcRAk1a2B+YNlLF/Dc5wE2Hw4O
K328Xk6fIJ1WDq7sxH1lYOC6nB4I2rHShTZxf0gc8KV/F3ndsGwUHh/NPpyuWucx
xO3afbb8IFvsJ7rCCkJFYGSWwQPnwuXjSiC2ao+mZY/TPBPPetZs67RVwJtaukj1
M9jE97jvpus12EIUmMclAnKDXmZKuZWU1a4CiMpnGDsbYx2jTZG0dXRij9uO5/yj
slgVWbHLLECJWlj6HMYKRrSxQWK5QwkYkSOpn5OnOAgcZZd9EFwOokWfyGB973kg
4noc7pYuvEo0Tm18/jYJ8uzWECCOW+xFUoZTBSN3uSjj9h0d3302vzNsPzk/YPkX
RxbTFrsZUO8Ya6fahD91taqJJd3AIZFhDqfwhfavt0HtAaY/iAaZWc0dsLd2Ge54
+MZACWz/g0+j0lGVcgI4OkxJqY8k6RtqEvKWLoo+BIfIXnPKlVRToELjwozG5ZCE
On8Vkg/9BnIe17kWFei+UwlkwHB6t6z8hTDD/04gjeTK4UR5XyUYIjxfib4tLNbl
Mrq/q/C9zfva5BlZGiuyJKZ+T3yznbXGyNHgSVD+3udiVlQSbUeGM88r/RnnqJCS
8bmphkuelzaSj+za9nS3
=jWev
-----END PGP SIGNATURE-----
17 Jun
17 Jun
3:01 p.m.
New subject: [trinity-devel] Changes to tdevelop for R14.1.x and R14.0.1
I personally disagree with this move, because your initial idea was to make R14 tde
compatible and the rest was left for the KDE 3.15. Why moving back now?! What is the
benefit of this?I really dislike changing things back and forth and on top after TDE
stated that R14 will be TDE oriented.Could such things be discussed in the public please.
regards
On Wednesday, June 17, 2015 8:50 AM, Michele Calgaro <michele.calgaro(a)yahoo.it>
wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear all,
in R14.1.x and in the somehow upcoming R14.0.1 release, tdevelop has reverted to use
.kdevelop project files instead
of .tdevelop files. Also, the main entry in such file was reverted to "kdevelop"
instead of "tdevelop". This has been
done to improve compatibility with KDevelop3 project files.
When you switch to the "new" version, you will need the following renaming:
1) .tdevelop files -> .kdevelop
2) .tdevelop.filelist files -> .kdevelop.filelist
3) change <tdevelop> to <kdevelop> in any .kdevelop file
4) change </tdevelop> to </kdevelop> in any .kdevelop file
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVgRiSAAoJECp1t8qK3tXPPwoP/jciCGEv4z4kx581xI9X0iCr
WjiZrmQX+ZbQOYhtv2+ZFsIjy3MdPvp5uWU0nEkcRAk1a2B+YNlLF/Dc5wE2Hw4O
K328Xk6fIJ1WDq7sxH1lYOC6nB4I2rHShTZxf0gc8KV/F3ndsGwUHh/NPpyuWucx
xO3afbb8IFvsJ7rCCkJFYGSWwQPnwuXjSiC2ao+mZY/TPBPPetZs67RVwJtaukj1
M9jE97jvpus12EIUmMclAnKDXmZKuZWU1a4CiMpnGDsbYx2jTZG0dXRij9uO5/yj
slgVWbHLLECJWlj6HMYKRrSxQWK5QwkYkSOpn5OnOAgcZZd9EFwOokWfyGB973kg
4noc7pYuvEo0Tm18/jYJ8uzWECCOW+xFUoZTBSN3uSjj9h0d3302vzNsPzk/YPkX
RxbTFrsZUO8Ya6fahD91taqJJd3AIZFhDqfwhfavt0HtAaY/iAaZWc0dsLd2Ge54
+MZACWz/g0+j0lGVcgI4OkxJqY8k6RtqEvKWLoo+BIfIXnPKlVRToELjwozG5ZCE
On8Vkg/9BnIe17kWFei+UwlkwHB6t6z8hTDD/04gjeTK4UR5XyUYIjxfib4tLNbl
Mrq/q/C9zfva5BlZGiuyJKZ+T3yznbXGyNHgSVD+3udiVlQSbUeGM88r/RnnqJCS
8bmphkuelzaSj+za9nS3
=jWev
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
5:03 p.m.
New subject: [trinity-devel] Changes to tdevelop for R14.1.x and R14.0.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
I personally disagree with this move, because your
initial idea was to
make R14 tde compatible and the rest was left for the KDE 3.15. Why moving
back now?! What is the benefit of this?I really dislike changing things
back and forth and on top after TDE stated that R14 will be TDE
oriented.Could such things be discussed in the public please.
regards
Some of this might be due to the fact that I've been largely unavailable
for the past several months (life / putting food on the table), therefore
I think my original goals of migrating everything from KDE to TDE have
stalled.
Michele, what is the actual benefit of maintaining compatibility with the
obsolete KDE 3.5 series instead of automatically upgrading the kdevelop
files to a TDE format? There is no guarantee that KDE will continue to
use a compatible format in the future so I don't see how this is a good
idea?
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlWBqGQACgkQLaxZSoRZrGG4pQDfZ0DOjy8UEnSy5+ZnuH90okcn
8sLWDEvAqikIEQDgwsHmbpwKs7RsjwvFSMU3xfZWk4U+h6vrk4Cj3A==
=uL0u
-----END PGP SIGNATURE-----
11:09 p.m.
New subject: [trinity-devel] Changes to tdevelop for R14.1.x and R14.0.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 06/18/2015 02:03 AM, Timothy Pearson wrote:
I personally
disagree with this move, because your initial idea was to make R14 tde compatible and the
rest was
left for the KDE 3.15. Why moving back now?! What is the benefit of this?I really dislike
changing things back
and forth and on top after TDE stated that R14 will be TDE oriented.Could such things be
discussed in the public
please.
> regards
Some of this might be due to the fact that I've been largely unavailable for the past
several months (life /
putting food on the table), therefore I think my original goals of migrating everything
from KDE to TDE have
stalled.
Michele, what is the actual benefit of maintaining compatibility with the obsolete KDE
3.5 series instead of
automatically upgrading the kdevelop files to a TDE format? There is no guarantee that
KDE will continue to use a
compatible format in the future so I don't see how this is a good idea?
Thanks!
Tim
Hi there,
the details of the discussion prior the changes were made can be found here
(http://bugs.pearsoncomputing.net/show_bug.cgi?id=2308#c2).
The change was made to assure we could still autogenerate cmake-based projects. Without
doing so, it would render any
"cmake based" project template unusable due to the fact that there is no
TDevelop3 cmake generator available (and I
doubt the cmake guys would create one just for us).
Basically TDE is still going the TDE way, but had to concede on this point to preserve
some useful functionality.
Everything can be reverted if the majority of the users prefer so, but be aware that in
this case this would come at a
small loss of that extra functioanlity.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVgf4sAAoJECp1t8qK3tXPuJ8P/3lvCqSxCSA/JwYpVQdSw50L
JwpaQZ0RP63VJeoyN2ODf7oGhk8OICSZ41XfoLVk3I8Fu6y0NTS+yoOcnsueFQu0
q0U5XDuwIuFzzUnRUoazLRWsYsZGbP67fHf9AIRpn+SkCIewy1Q+NqH3YPVHQnz6
951i8OXjWBzaU3p39bZdVreAZlexP8rAqaV2vdhXaNr0tA8IUWDvK0RyauMfUyL/
v4i6tir44X8rVv68P9OOctzwsnF12/0W4rjO8WtlHlzTQcFShxWzOwpChzwrsgGH
3SS4vVX73JrxtREGLkuNQYoU6jRM8KX8kiul/IPePhm6RZrtde6w/z37ceEMTaug
nJ5jEti8LViP/eGz6i1ZEh07Kd5pi6U+RgDJB1IZskG7ncJu2kfZMRiFjlgDr2vA
FMbZTnu21+A+HWp8DHSoqC9ANUShMgjgpoSVd8MtUb1zkE5hO9J5IzbfkWTlgaNV
F59H184RM7f4/EsnFrvJFflHvnWD56IO8/of4GFjnMEocPv89A+pY4g/VflLxJr0
Jro91vVCnoR9pEXZ/kkGCSOdNFGzDUbxsC1/wVX0bN2rTOPEZ1eFvOQQXhnfzKQx
q7/H3RI+TfGhFVzV2+NAR2Yyc15QJUpIsc3icqw6bkXaZdywyrxc/353VkZijJVz
d/aIe6n5cWdA7QHhx0eQ
=Cqd2
-----END PGP SIGNATURE-----
18 Jun
18 Jun
3:10 p.m.
New subject: [trinity-devel] Changes to tdevelop for R14.1.x and R14.0.1
On Thursday 18 of June 2015 01:09:32 Michele Calgaro wrote:
On 06/18/2015 02:03 AM, Timothy Pearson wrote:
Hi there,
the details of the discussion prior the changes were made can be found here
(http://bugs.pearsoncomputing.net/show_bug.cgi?id=2308#c2).
The change was made to assure we could still autogenerate cmake-based
projects. Without doing so, it would render any "cmake based" project
template unusable due to the fact that there is no TDevelop3 cmake
generator available (and I doubt the cmake guys would create one just for
us).
Basically TDE is still going the TDE way, but had to concede on this point
to preserve some useful functionality. Everything can be reverted if the
majority of the users prefer so, but be aware that in this case this would
come at a small loss of that extra functioanlity.
Cheers
Michele
Preserving data compatibility seems to me useful.
For example, some time ago due to the renaming KWallet => TDEWallet was caused
incompatibility of data files with stored passwords. Therefore are reverted
portion of renaming data file header so that the data files could still be
compatible with KWallet. It seems like a good reason to have a compatible
files until will be necessary to change the stored data, which compels to
change format of data files.
--
Slávek
I
personally disagree with this move, because your initial idea was to
make R14 tde compatible and the rest was left for the KDE 3.15. Why
moving back now?! What is the benefit of this?I really dislike changing
things back and forth and on top after TDE stated that R14 will be TDE
oriented.Could such things be discussed in the public please.
regards
Some of this might be due to the fact that I've been largely unavailable
for the past several months (life / putting food on the table), therefore
I think my original goals of migrating everything from KDE to TDE have
stalled.
Michele, what is the actual benefit of maintaining compatibility with the
obsolete KDE 3.5 series instead of automatically upgrading the kdevelop
files to a TDE format? There is no guarantee that KDE will continue to
use a compatible format in the future so I don't see how this is a good
idea?
Thanks!
Tim
3234
days inactive
3235
days old
4 comments
4 participants
participants (4)
-
Emanoil Kotsev -
Michele Calgaro -
Slávek Banko -
Timothy Pearson