Board index » delphi » Re: Delphi 8 doesn't work with some Developer Express components

2004-01-08 02:25:59 AM
delphi160
"Anders Ohlsson (Borland)" <XXXX@XXXXX.COM>writes
hard time reconciling that kind of accusation, and the inference that lies
behind it, with a calm state of mind. The use of the word "immediately" also
implies impertinance rather than calm.
However, I will admit I am tired of dealing with the repercussions of this
thread, and if this led me to infer agitation where there was none, I
apologize.
 

Don't say that. C#Builder may be not the best IDE to work with, but it's
lightweight, and quite stable (for v1).
If Borland fix some (many) of C#Builder's well known bugs, i see no reason
to use a beast like VS.
regards
Sakis
"jordan smith" <XXXX@XXXXX.COM>writes

Captain Jake writes:
poorly wording it. I ask that you read my original message again. These
were my points I was trying to get across:
1. Borland wants this problem resolved ASAP.
2. Whoever DevEx reported the issue to did not put it into our tracking
system, so the problem was never discovered by someone who could do
something about it. This was primarily Borland's fault, because that
employee should certainly have reported it. It was therefore never
worked on. This unfortunate event has made it clear that Borland needs
to provide an "escalation procedures" guide to our BTPs. This is to
help prevent something like this from happening again in the future. I
am already working on this document, and we will be sending it out to
all our BTPs ASAP.
3. I want to know who the Borland recipient of the information from
DevEx was so we can make sure that person *does* know the proper method
of reporting bugs so they are tracked.
4. I have never doubted that Developer Express reported the issue.
Unfortunately, it was not reported through the proper channels, so it
did not get tracked and fixed.
The only sensible thing to do right now is:
- find and fix the problem (which Corbin did, about 2 hours after he
had the test case)
- get it out as a public beta after receiving verification from DevEx
that it fixes the problem
- get it out as a public beta so it can be verified for other
components and solve the problem immediately for other people who may
encounter it
- release it as an officially supported patch
The rest of this "Borland said/DevEx said" argument benefits no one.
Can we please move on to more productive discussions? Thanks.
--
John Kaster, Borland Developer Relations, bdn.borland.com
Don't miss the best BorCon ever! info.borland.com/conf2003/
Add a feature/Fix a bug: qc.borland.com
Get source: codecentral.borland.com
 

"Rudy Velthuis (TeamB)" <XXXX@XXXXX.COM>writes
anyone doing serious work in C# Builder is necessarily using third-party
.NET components at design-time.
 

John Kaster (Borland) writes:
resolved. "Move along folks, nothing to see here."
--
John Kaster, Borland Developer Relations, bdn.borland.com
Don't miss the best BorCon ever! info.borland.com/conf2003/
Add a feature/Fix a bug: qc.borland.com
Get source: codecentral.borland.com
 

"John Kaster (Borland)" <XXXX@XXXXX.COM>writes
pipeline. I apologize if I anything I said or implied made you look bad.
But I have one small suggestion, if I may be permitted to tarry just a bit.
It is all well and good to have put into place the plan you outlined in your
post, but it seems to me that one additional step would be in order and that
is implementing a plan whereby bugs discussed in the newsgroups get
escalated or added to the tracking system by someone internal to Borland. It
is fine to tell BTP's how to escalate issues, but in this case there was
also plenty of newsgroup banter about the bug long before Corbin was finally
alerted to the issue. It might not be the way Borland currently operates but
there seems to be a general expectation that if a bug gets discussed here on
the newsgroups that Borland thereby knows about it. It would have quickly
defused the issue discussed at the head of this thread if there had already
been in place a mechanism to escalate newsgroup-discussed bugs without any
further action on the part of customers or BTP's. Asking people to vote on
QC is all well and good but it is easier to discuss bugs here on the
newsgroups than it is to install the QC client, and I think Borland really
ought to consider the newsgroups as yet another bug-tracking and discovery
device. Perhaps Borland needs to have somebody on staff full time whose job
is solely to patrol the newsgroups looking for bugs that are worthy of entry
into the big-tracking system. I bet if you ask around here that few people
would disagree with that suggestion.
 

Captain Jake writes:
*must* be. I'd never buy another Delphi32 release (and I would
advice everyone else to do the same), if they didn't release at least
one (hopefully BIG) sp for the current D32.
After that, there would be a major update to get some of the language
changes from D.NET.
David
 

jordan smith writes:
www.c-sharppro.com/features/2003/11/cs200311jm_f/cs200311jm_f.asp
David
 

David Smith writes:
would cost about a half to a third of normal upgrades (prefer a
third...).
I see this as a possibility because of the changes that were mentioned
to the compiler to aid its integration with delphi 8.
I can not see them moving the released product to the new BDS IDE just
yet so they are going to have to duplicate a couple of fixes in both
IDE's as well.
Purely speculation, but I would be happy with a 7.5 release.
cheers,
JED
 

"David Smith" <XXXX@XXXXX.COM>writes
thing. I wouldn't be very surprised if the same update or service patch or
whatever anyone wants to call it, covers both bug fixes for Delphi 7 and the
addition of .NET-compatible language features all in one.
 

Wayne Niddery [TeamB] writes:
which only Borland could access and enter details into (and I assume
some trusted, experienced developers like TeamB also had access to at
least enter bugs). Some people were screaming that this was good
enough, and so QC was created so that everyone could enter and view bug
reports. Why would we want to go back to the previous position of
Borland and TeamB entering all bug reports?
Personally, I'd much rather Borland spend time in development,
fixing bugs and adding new features, TeamB spend time in the newsgroups
helping people, and the person who has the experience and test case for
a bug to be the person who enters it so that the person fixing the bug
can followup to the correct person.
Christopher Latta
 

Captain Jake writes:
responsibility of Borland and/or TeamB to mine these groups for things to
add to QC? It is extremely wasteful to spend time wading through hundreds of
newsgroup posts every day looking for those few posts that warrant being
added. Moreover, even assuming someone spent the time to do so, in *most*
cases that person would have to follow up with the person(s) that posted in
the groups to get sufficient information to make it worth entering into the
system anyway. This is *extremely* counter-productive and would be a waste
of a salary.
QC was created *precisely* to make it reasonable for customers to enter bugs
directly. If you can take the time to report a bug in the newsgroup, why
can't you report it yourself in QC? You are the one with the information.
Chances are you will *not* post all the information you could or should in a
newsgroup posting whereas QC presents the fields needed in order to help you
do just that, thus asking to have someone else mine the newsgroups is, on
average, going multiply the effort involved by at least a few times.
The Win32 client is easy to install, but if you really don't like that you
can enter bugs via the Web client too. Furthermore, in future releases of
Delphi, etc (already in the current version of JBuilder) you will be able to
enter bugs directly from the IDE (which means some here will apparently
demand that a Borland rep come to their office and enter the bug for them
via the IDE interface!).
Borland is doing all they can to make this an easy and *effective,
efficient* process. At some point, the customers have to take a little
initiative and *use* the system provided to them.
--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: www.logicfundamentals.com/RADBooks.html
"It is error alone which needs the support of government. Truth can
stand by itself." - Thomas Jefferson
 

RandomAccess writes:
 

"Wayne Niddery [TeamB]" <XXXX@XXXXX.COM>writes
really about. In reading it I see that my idea has already been scuttled.
Nuts to me.
(I thought it was triggered by some TeamB bashing and the inevitable
hullaballoo that would inevitably ensue. I am tired of seeing TeamB and
their detractors go back and forth about what TeamB is supposed to do, so I
tune out any threads where I see that going on. Usually I'd be able to
use the "Top of Thread" button and then the "Back" button to quickly see
what post triggered a particular discussion but until I fix a {*word*193} bug I am
stuck with OE.)
 

"Andrew Rybenkov" <XXXX@XXXXX.COM>writes
Actually, neither do I.
Best Regards