November 8, 2013
There is a new survey meant for Delphi developers who still have applications build in old, pre-Unicode versions of Delphi. If you are still using old versions of Delphi, you are invited.
There is a new survey meant for Delphi developers who still have applications build in old, pre-Unicode versions of Delphi (not specifically tow two mentioned in the title, but also Delphi 4, 5, 6, 2005, 2006, and so on). The idea behind the survey it to understand if we can do something more (or something different) to help developer migrate to newer versions of the product.
If you are part of this group of developers still using older versions (even if you also bought a newer one you are using for some of your projects), we'd appreciate your input. And if you know any other Delphi developers using older versions of Delphi and can send them the link to the survey, tweet, blog, or email about this initiative, thanks in advance.
The survey has 16 questions, mostly quite simple, and should take about 5 minutes to complete:
https://www.surveymonkey.com/s/MF6RZMG
Update: There was a problem with the 8th question taht is now fixed. Sorry my bad for trying it out, but not trying to post my own answers. It was a multiple choice with cumpulsory answer, seems this doesn't work in SurveryMonkey.
posted by
marcocantu @ 12:24AM | 15 Comments
[0 Pending]
15 Comments
Delphi 7 and Delphi 2007 Migration Survey
Survey does not work! Says: unanswered question. Not
true.
Comment by Peter on November 8, 13:36
Delphi 7 and Delphi 2007 Migration Survey
Your survey question no. 8 is broken; it forever
demands: "This question requires an answer" despite
answer given.
Comment by Matthias B on November 8, 13:44
Delphi 7 and Delphi 2007 Migration Survey
Sorry but the survey seems bugged!
At the question 8 I answered two NO, but the survey on
exit ask me to aswer to this question!?
Comment by on November 8, 13:44
Delphi 7 and Delphi 2007 Migration Survey
Unable to finish survey because of an error. Question 8
requires an answer. Even if an answer is given, the
error persists.
Comment by Leif Uneus
[http://www.opsis.se]
on November 8, 14:00
Delphi 7 and Delphi 2007 Migration Survey
Question 8 seems to be broken. Even when a value is
filled in, I can't submit the survey.
Comment by Bruce McGee on November 8, 14:01
Delphi 7 and Delphi 2007 Migration Survey
Marco,
It's something wrong with the survey. I see the message
"This question requires an answer" every time I try to
post answers.
http://postimg.org/image/xmxizm233/
Comment by Kryvich
[https://sites.google.com/site/kryvich]
on November 8, 14:11
Delphi 7 and Delphi 2007 Migration Survey
Question #8 insists I did not answer it...though I
did. Finally got the survey accepted by checking all
the choice boxes, though I only wanted to check the first.
Quality control here is about as good as with XE2
Styles..yuk.
Comment by SteveJG on November 8, 14:11
Delphi 7 and Delphi 2007 Migration Survey
I can suggest one thing right off the top of my head, that is to make the
latter versions of Delphi stable and functional. I have never received an
out of memory error when compiling a project group in D7 but I get it all
the time in XE3 and it's still there in XE4.
If QC bugs aren't going to be addressed, and new features are for mobile
development, why would a desktop developer upgrade their Delphi
version when they have something stable that meets their needs?
Comment by Larry Hengen
[http://www.tpersistent.com]
on November 8, 14:21
Delphi 7 and Delphi 2007 Migration Survey
Sorry for the issue with question 8. It is now resolved.
Comment by Marco Cantu
[http://www.marcocantu.com]
on November 8, 15:01
Delphi 7 and Delphi 2007 Migration Survey
- Older Delphi starts faster.
- I don' need all supplied components from newer delphi
- i'd prefeur a customer specific choice of components.
if i order a newer delphi version, i'd like a choice
of components, which i can order for my purpose with
the new delphi version.
- the bad integrated help of newer delphi versions
get's public. But why buy new components if i cannot
use them because of bad help?
- for me as hobby programmer the price of a new delphi
version.
Comment by Thomas Schönfelder on November 11, 13:32
Delphi 7 and Delphi 2007 Migration Survey
I took the survey but thought I would mention the major
reason here for keeping code in D2007 (we use delphi
2007 and XE 5): 1) Unicode migration; 2) Code bloat
(which is related to 1 - for code we did port our
executables immediately doubled in size).
Probably too late now, but would be nice if you could
identify at the project level or even at
installation/instance whether "string" means ansi string
or unicode string. Or figure a way to reduce code bloat
with unicode exes and provide a project migration tool
to move code from ansi to unicode
Comment by Charlie Vinal on November 13, 15:08
Delphi 7 and Delphi 2007 Migration Survey
I answer in the survey... but finally...
THINK ABOUT THE PRICES... THE PRICES ARE TO HIGH...
ALSO THE PRICES TO UPGRADE BETWEEN 2 VERSIONS...
1.486,31 € FOR THE UPGRADE XE5 ENTERPRICE to XE5
ENTERPRICE... A JOKE
Nils Bödeker
Comment by Nils Boedeker
[http://www.ulmer.de]
on November 14, 13:25
Delphi 7 and Delphi 2007 Migration Survey
Hi,
for me there is three reasons that i'll not migrate
to XE5 for full development at the moment.
First, to much .Net"ism" in the IDE make it too
heavy for my taste ..., second even with the .Net i
could use it if the IDE could use mono for support in
Linux or OS X and third i really don't like Firemonkey
and units namespaces.
regards,
Dimitrios Chr.
Comment by Dimitrios CHr. on November 17, 11:41
Delphi 7 and Delphi 2007 Migration Survey
For me, the key to get me to upgrade my projects is to
make the changes needed to allow...
UNICODE: TURN OFF/ON by UNIT
I'm sure there's tons of reasons on why this is really
hard. But, I have lots of old network code that EXPECTS
a char/string to be 1-BYTE. I have spent months porting
my biggest project to XE2, successfully, but I'm not
going to do it for the FOUR other Delphi 2007/7 projects
that I have.
Comment by Vin Koglin on November 22, 03:52
Delphi 7 and Delphi 2007 Migration Survey
Vin,
there is not unicode on/off option, but there is the possibility to to a
search replace of string/char/pchar to ansistring/ansichar/ansipchar per
unit.
I know, not the same thing.
-Marco
Comment by Marco Cantu
[http://www.marcocantu.com]
on November 22, 18:01
Post Your Comment
Click
here for posting
your feedback to this blog.
There are currently 0 pending (unapproved) messages.
