Cameron Cole wrote:
,1895,2000205,00.asp
This looks like good news :)
>This makes so much sense. It is going back to the formula
that built
>the name Borland in the first place with tools like Turbo Pascal.
>Tools that are very reasonable in cost but powerful at the
same time.
I read up on two crippling changes though. No native support for
larger commercial databases namely SQL Server and (not
including MSDE) and you can only have one Turbo version on
a machine
at one time so no Turbo C++ and Turbo Delphi on at the same time.
The first I can see if there's a (possibly pricey) add-on to
provide the DB functionality; and there's always the
aftermarket tools.
The latter is ridiculous, I sincerely hope they're not
seriously considering doing that.
Stephen Posey
slposey (AT) concentric (DOT) net
That is apparently a function of the design (you can't install Delphi 06 Pro and Enterprise on the same machine either) rather than marketting. You can always use vmware.
Regards
Sean
Sean Cross
Systems Development
Catalyst Risk Management
P Box 230
Napier
Phone:** 06 834 0362
Mobile:* 021 270 3466
Email:** sean.cross (AT) crm (DOT) co.nz
http://www.crm.co.nz/
in Auckland, Napier, Wellington & Christchurch
Disclaimer:
"The information contained in this document is confidential to the addressee(s) and may be legally privileged. Any view or opinions expressed are those of the author and may not be those of CRM. No guarantee or representation is made that this communication is free of errors, viruses or interference If you have received this e-mail message in error please delete it and notify me. Thank you."
Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Sean Cross - CRM wrote:
>Cameron Cole wrote:
I read up on two crippling changes though. No native
support for larger commercial databases namely SQL Server
and (not including MSDE) and you can only have one
Turbo version on a machine
at one time so no Turbo C++ and Turbo Delphi on at the
same time.
>Stephen Posey Wrote:
>The first I can see if there's a (possibly pricey) add-on to
>provide the DB functionality; and there's always the
>aftermarket tools.
>
>The latter is ridiculous, I sincerely hope they're not
>seriously considering doing that.

That is apparently a function of the design (you can't install
Delphi 06 Pro and Enterprise on the same machine either)
rather than marketting. You can always use vmware.

I might buy that as an excuse if historically it had been
impossible to install concurrent versions of Delphi, C++Builder,
and JBuilder all on the same machine, which is clearly NT the case.

Anyway, I've successfully had all versions of Delphi 16 and
C++Builder 1&35 installed on the same machine; which I realize
isn't quite the same thing, but what's stops you from installing
both Pro and Enterprise?

Not that I ever tried (never had occasion to) and it admittedly
seems a bit silly (why bother with Pro if you have Enterprise?);
but if you install them to different locations what keeps them
from working?

I'm pretty familiar with Delphi's registry usage and I'd expect
both would end up reading from the same keys obviously, but that
shouldn't present any particular problems that I can think of off
the top of my head, just changes in one IDE would show up in the
other.

Stephen Posey
slposey (AT) concentric (DOT) net

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Stephen Posey wrote:
Sean Cross - CRM wrote:

Cameron Cole wrote:

I read up on two crippling changes though. No native
support for larger commercial databases namely SQL Server
and (not including MSDE) and you can only have one
Turbo version on a machine
at one time so no Turbo C++ and Turbo Delphi on at the
same time.

>Stephen Posey Wrote:

The first I can see if there's a (possibly pricey) add-on to
provide the DB functionality; and there's always the
aftermarket tools.

The latter is ridiculous, I sincerely hope they're not
seriously considering doing that.

>That is apparently a function of the design (you can't install
>Delphi 06 Pro and Enterprise on the same machine either)
>rather than marketting. You can always use vmware.
>
>
I might buy that as an excuse if historically it had been
impossible to install concurrent versions of Delphi, C++Builder,
and JBuilder all on the same machine, which is clearly NT the case.

Anyway, I've successfully had all versions of Delphi 16 and
C++Builder 1&35 installed on the same machine; which I realize
isn't quite the same thing, but what's stops you from installing
both Pro and Enterprise?

Not that I ever tried (never had occasion to) and it admittedly
seems a bit silly (why bother with Pro if you have Enterprise?);
but if you install them to different locations what keeps them
from working?

I'm pretty familiar with Delphi's registry usage and I'd expect
both would end up reading from the same keys obviously, but that
shouldn't present any particular problems that I can think of off
the top of my head, just changes in one IDE would show up in the
other
Since both versions of D6 would read from the same registry entry they'd
need to be located into the same directory structure! The registry
contains stuff about paths as well as info about colors, components and
other less important things. So installing two editions of the same
product on the same machine would fail - but I think that's true for ANY
software product with multiple editions for the same version.

the other hand different Borland products (including different
versions of the same product: D5 / D6) use different registry keys. Sure
they'll all routed into the same big tree but they do use different keys.

In the end I think installing different Turbo XXX products would be
similar to installing different current Borland products not similar to
installing different editions of the same product. If there is such a
limitation (only allow one version of Turbo XXX on any given machine)
I'm sure it's a beta-bug R some well-crafted Borland feature, not a
side-effect of registry storage.

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

I have D5, D7 and D2005 on the same machine. The registry entries
for *.dpr, *.pas, *.dfm and so on are set to one of them - D2005 I think
since that was the last one I installed.

But mostly I use D7, which is my favorite.

When I want to launch a DN, I right click on the *.dpr file and a list of
options
pops up which includes "open with" as a submenu. Left clicking again on
the one I want at that moment chooses the DN I want to use. So the registry
entries don't affect me in any way other than that I have to right click and
choose before launching.

Alternatively, all DN are on the "Start|All Programs" menu sequence, so
I can get to any of them that way, and use "File| Project" once some
DN has been launched to get going.

So I don't find registry entries to be a problem at all, not even an
inconvenience,
and unless Borland marketing got in the act, I would expect the Turbo line
to
follow the same design lines.

JMH,
Rich

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Hi All,

I have a TWebBrowser successfully downloading html pages
and displaying them. When I right click on the TWebBrowser,
I get the standard IE6 menu (Back, Forward, Save Background as )
which I don't want. I'm using XP HE, D7.

I built a popupmenu and added the click features I do want the
TWebBrowser to show the user, and I set the TWebBrowser's
"PopupMenu" property to that popup menu.

It doesn't work. When I right click on the TWebBrowser at run time,
I still get the IE6 menu!

The "PopupMenu" property box has a "+" in the object inspector, so
I checked the sub items and they all look K to me:

AutoPopup True
Items has the menu items on my popup menu
TrackButton tbRightButton

So none of those are obvious problems.

Does anyone know how to change the IE6 popup menu to another
popup menu of my own design?

Thanks,
Rich

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Marvelous! Thanks, Corey! I don't begin to understand all the hook and
unhook things going on here, but as long as it works, it solves the
immediate
problem of disabling the standard TWebBrowser right click menu.

Now I have to figure out how to call the popup menu instead. Does anyone
have an idea on how to do that?

Thanks,
Rich

Cory wrote:

Rich, this article describes how to disable TWebBrowser's context menu

8/11/06, Rich Cooper -
rcooper15 (AT) comcast (DOT) net<+#comcast.net@
spamgourmet.comwrote:
>>
>Thanks Rob,
>>
>>From that MSDN web site material, it appears that the way to eliminate
>the
>standard
>context menu and implement a Delphi popup menu is to override what MSDN
>calls
>
>>
>Does anyone have a sample (or article) about how to do that? Surely lots
>of
>people must have faced that issue before and solved it?
>>
>Thanks,
>Rich
>>
>>
>Rob Kennedy wrote:
>>
>Rich Cooper wrote:
>>Does anyone know how to change the IE6 popup menu to another
>>popup menu of my own design?
>>
>See the following MSDN article.
>>
>>
>#Controlling_the_Cont
>>
>--
>Rob
>>
>
>Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org
>
>>

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org

Hi All,

Using D7 and Indy 9, I have a THttpServer that supports a
thick client program. The client program is sent to customers
and I want to provide an automatic update service, like MS
does with WinXP.

I've used the InstallShield Express version that ships with
D7 to create a 'setup.exe' file. That works fine, but if I try to
install over a previous version, WinXP objects. The user is
forced to uninstall the previous version, though it seems the
user can uninstall the previous one AFTER installing the
new version!

My question is this. How can I make my thick client D7/Indy9
program uninstall the previous version, and install the new
version?

is that impractical in practice? Should I just download and
store a new .exe over the old one? Is there a way to do that?

Suggestions appreciated,
Rich

Delphi-Talk mailing list -Delphi-Talk (AT) elists (DOT) org