Board index » cppbuilder » Re: Community Open Letter Nonsense

2004-10-20 04:54:28 PM
cppbuilder93
OK, when Diamondback comes out, my BCB 5 pro SP1 projects had better port over
to it as smoothly as a Venezuelan maiden's thighs. Or else! Here is the
transcript of the posting in this noisegroup (Thanks Chris!) subject VCL :-
===============================================
Mark Jacobs wrote:
in the .NET framework. A form may be a form, but when you want to
set properties on the form, they're often called different things
between .NET and VCL/VCL.NET. VCL.NET offers some abstractions
that may be better, or just plain easier for VCL experienced folks
to use.
With the Avalon/XAML transformation coming up, I don't have a wish
to convert to .NET, just to dump it for the next MS framework
either. VCL.NET allows me to leverage my VCL comfort, who knows if
it will translate to Avalon/XAML too, but at least I can eliminate
one framework transformation.
There's arguments on both sides. I'm just more comfortable in
VCL.NET.
-Brion
===============================================
--
Mark Jacobs
DK Computing
www.dkcomputing.co.uk
"Jeff Overcash (TeamB)" < XXXX@XXXXX.COM >wrote in message
|
| Mark Jacobs wrote:
|>
|>In another thread, someone (who knows these things) was saying that there
are
|>necessary design changes required to get BCB VCL working inside Db.
|
| Since I write more than 25 of the components on the pallet (IBX) I can tell
you
| that there was absolutely no changes I had to make from the Win32 version
(run
| time or design time) to get them to work in Diamondback. Who ever told you
this
| did not know what they were talking about, contrary to your statement.
 

"Mark Jacobs" <www.jacobsm.com/mjmsg?Borland%20Newsgroup>wrote in
message news:417627c4$ XXXX@XXXXX.COM ...
I don't think anyone's ever implied that you should be able to port any BCB5
project to using VCL.NET without a single line of code changing.
What *IS* being said, and said quite reasonably, is that there is no reason
why a BCB5 project wouldn't compile and run pretty much untouched FOR WIN32
with a Diamondback version that included BCB support. There's no more or
less of a paradigm shift there than moving from BCB4 to BCB5.
Moving to .NET, as I said, is likely a different story.
- Roddy
 

"Rudy Velthuis [TeamB]" < XXXX@XXXXX.COM >writes:
 

{smallsort}

Then I heartily look forward to the release of a BCB Win32 supporting
Diamondback product. However, considering the work I had to do to get BCB3
projects up and running in BCB5 ... mmmmmm.... huh! Oh well. So BCB and VCL's
future depends on its implementation in Diamondback? Does anyone know what the
odds of it being included in Diamondback's next (or forthcoming) release?
100-1 or 10-3 on? And when abouts is that likely to be released? Just
curious...
--
Mark Jacobs
DK Computing
www.dkcomputing.co.uk
"Roddy Pratt" <roddy at spam fritter dot com>wrote in message
| I don't think anyone's ever implied that you should be able to port any BCB5
| project to using VCL.NET without a single line of code changing.
|
| What *IS* being said, and said quite reasonably, is that there is no reason
| why a BCB5 project wouldn't compile and run pretty much untouched FOR WIN32
| with a Diamondback version that included BCB support. There's no more or
| less of a paradigm shift there than moving from BCB4 to BCB5.
 

Mark Jacobs wrote:
get the infamous letter (just under two months to go :-/ ) we don't
really know. Borland /might/ decide BCB should continue as a separate
product. I doubt it though - too costly and too little return I think.
within the next significant release of its host environment. FWIW if
the forthcoming letter says that BCB is to continue as part of another
product I will be pushing Borland to make it a priority. My ideal would
be to have Borland issue a point release consisting solely of BCB as an
additional personality.
Even if they just gave us BCB6 incapsulated within a new IDE it would
be a good first step. My biggest complaint at present is the IDE. Once
they've done that they could look at compiler and VCL updates.
Unfortunately I suspect that all three are linked and that you couldn't
have Builder projects using their own versions of the VCL.
--
Andrue Cope [TeamB]
[Bicester, Uk]
info.borland.com/newsgroups/guide.html
 

"Harold Howe [TeamB]" < XXXX@XXXXX.COM >wrote...
chooses to ignore the community of developers ("we will never abondon the
developers"), then that will speak just as loudly as if they do. Can't make
that determination unless we knock on the door and see if they answer. If
they don't, we must move on.
the number of folks who stand at their door and knock. 350+ so far. If they
want to attribute that group directly to a newsgroup communitiy which, in
their mind, is not reflective of a typical borland customer, then perhaps
they should shutdown the newsgroup.
users and receive input. But what other mechanisms exists other than word
of mouth, and OPBs (other people's Blogs). I think though, in the end, the
views received extend beyond what could be attributed to this newsgroup.
Consider that some of these views include those who sponsor and/or pay for
software develped using BCB.
- Paul
 

Mark Jacobs wrote:
announced as expecting to ship in November 2004. It has support for
Delphi/Win32, Delphi.NET and C#.
The press release is here:
www.borland.com/news/press_releases/2004/10_12_04_delphi2005_boos
ts_windows_productivity.html
or
tinyurl.com/3jktr
As far as the release after that goes, nothing is set in stone yet.
--
Leo Saguisag
Delphi l10n engineer
About the Borland newsgroups: info.borland.com/newsgroups/
"Luke, you're going to find that many of the truths we cling to depend
greatly on our own point of view." -- Obi-Wan Kenobi (Return Of The
Jedi)
 

Andrue Cope [TeamB] wrote:
*zero* clue how hard it would be to move a C++ BCB project into
Diamondback, regardless of whether your eventual platform target
will be Win32, .NET via VCL.NET, or .NET (raw?).
-Brion
 

"Andrue Cope [TeamB]" < XXXX@XXXXX.COM >wrote:
it more of a suite.
 

Mark Jacobs wrote:
importantly converting a Win32 component to a .NET component. IBX users in D8
did not have to change a line of IBX code in the Win32 VCL apps to port them to
.NET. Most apps needed only minor changes to get them running under .NET. The
major work was done under the hood at the component level. Component developers
had a lot of work, component consumers (application writers) had much much less.
Also your complaint was about moving your BCB6 app to Diamondback, which the
natural assumption would mean Win32 to Win32. You don't seem to understand what
Diamondback contains (even though the information is easily available), yet have
a lot of negative assumptions (mostly wrong) about it.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
A human being should be able to change a diaper, plan an invasion, butcher
a hog, conn a ship, design a building, write a sonnet, balance accounts, build
a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act
alone, solve equations, analyze a new problem, pitch manure, program a computer,
cook a tasty meal, fight efficiently, die gallantly. Specialization is for
insects. (RAH)
 

Ahmmm... A Rudy, shouldn't you set an example about t{*word*220} quotes?
Or at least not posting at the end of it please ;-) .
Rudy Velthuis [TeamB] wrote:

Boian Mitov wrote:
Shows I'm human after all, though. <g>
--
Rudy Velthuis [TeamB]
"Don't let it end like this. Tell them I said something."
- last words of Pancho Villa (1877-1923)
 

"Rudy Velthuis [TeamB]" < XXXX@XXXXX.COM >writes:
 

Thomas Maeder [TeamB] wrote:
--
Rudy Velthuis [TeamB]
"Give me chastity and continence, but not yet."
-- Saint Augustine (354-430)
 

Alright, stroppy. I am just nosing around, trying to get a feel from people
who may have been privileged enough to have tried Diamondback out. I have now
seen a short video clip on code folding in Db, and very impressive it was too,
but I suspect they were running the demo on a huge 4,000 hectare estate of IBM
Big Blues to achieve the performance speed they demonstrated!
--
Mark Jacobs
DK Computing
www.dkcomputing.co.uk
"Jeff Overcash (TeamB)" < XXXX@XXXXX.COM >wrote in message
| No, that is a transcript for converting a Win32 app to a .Net app, more
| importantly converting a Win32 component to a .NET component. IBX users in
D8
| did not have to change a line of IBX code in the Win32 VCL apps to port them
to
| .NET. Most apps needed only minor changes to get them running under .NET.
The
| major work was done under the hood at the component level. Component
developers
| had a lot of work, component consumers (application writers) had much much
less.
|
| Also your complaint was about moving your BCB6 app to Diamondback, which the
| natural assumption would mean Win32 to Win32. You don't seem to understand
what
| Diamondback contains (even though the information is easily available), yet
have
| a lot of negative assumptions (mostly wrong) about it.