TurboExplorer

[WILL]

What is wrong with putting delphi and delphi .net in one package

Well on the technical side is makes sense and is a VERY attractive concept. BUT in the corporate world the companies easily see the idea of a huge multi-purpose do-it-all compiler/ide suite as an excuse to overprice it. Seperate them and that excuse is gone. In fact to get someone to purchase them together they're more likely to offer a bundle deal.

The other reason is that the Delphi development team of the recent past, has shown it's inability to take on too many new technologies and innovations. (Bull-headedness on the part of the project planners/bosses if you ask me...)

It's the corporate theme to make everything marketable and only hand out little pieces at a time so that they don't exhaust their fat juicy cash cow. (To be honest this is the 'evil' approach that Google employees talk about in their mission statement.)

This is the problem that has become Borland. Having 2 projects running side-by side, it's possible that neither team would have the excuse that they are adding enough to justify a new version and a new product to sell, when we developers know that thats complete bull.

Pascal programmers want to develop in Linux, Mac and Win32/64. But we don't get that. We want to do mobile devices too. But we don't get that either. We did get code refactoring and other similar enhancements, yes. We did get .NET ok fine. But we also got husstled into a higher priced do-it-all suite that ran like crap and half of it we didn't need nor want.

Breaking things down and simplifying it is a good thing in a way. The DevCo is not Borland, thats clear, but I think that from a corporate vs the consumer side of things, it's a better bet than these mega-super suites that Borland has been pumping out for an underfunded department is crap.

It is nice in fact to see(well hear) the opposite of that for a change.

[FNX]

I've just received an email from an italian delphi newsletter with attached
this link. Most of you should already know how to but it can be useful for
medium-range users not so familiar with non-vcl coding

have a look!
http://www.danielstools.de/downloads...ponents_en.pdf

[Legolas]

Hacking a bit it is possible to compile things for PDA too
All you have to do is:

1) download CF preview compiler from borland site
2) extract all stuff from .msi package
3) add DCCIL.exe to the delphi "Borland\BDS\4.0\Bin" folder
4) replace all .dcuil and .dcpil files in "Borland\BDS\4.0\lib\cf" folder (well, making a backup copy should be nice )
5) follow this guide

The bad thing is that DCCIL.exe is expired, so you need to move back your windows clock to 2005... :roll:

Well, it's a bit tricky, but it's good enough to make some testing :lol:

[WILL]

Francesco, you keep this up and you're liable to be nicknamed the 'Port King'.

[Legolas]

Francesco, you keep this up and you're liable to be nicknamed the 'Port King'.

:king:

Not really a port though. I think that at Borland have not devoted too much in turbo release engineering, because with some tricks (see the previous one by FNX too) it is possible to bypass all turbo limitations

[size=7px]Well, it is even too easy to patch DCCIL.exe to bypass the expiration date check...[/size]

[Legolas]

Oh my... At Borland should post correct infos, imho... Well, I have discovered that turbo delphi for .net is capable to natively compile CF apps, without external compilers... The only thing to do is going here:

Project->Options...->Directories/Conditionals/

and adding "D:\your_path_to_borland\Borland\BDS\4.0\lib\cf" to the search path. :roll:

More infos

[FNX]

This two lines from Marco Cantu say it all...

"...However, this is not the case. Delphi works better than Borland is telling the world and this is a pity."

"PS. I did get in contact with some people at Borland mentioning the problem but I didn't receive a positive reply"

I just wonder WHY?!?

[Chebmaster]

After doing a lot of minor corrections, writing a perverted utility for converting all my code that was based on the macros, making more conversions, discovering that Win32 API support in Turbo is a complete crap, getting a bundle of AVs for free, I got my engine running.

What should I say?.. It's free, it works, it looks promising.
But after having to put this
[pascal]{$ifndef fpc}
Const
WM_ACTIVATE = 6;
WM_KEYDOWN = 256;
WM_KEYUP = 257;
WM_SYSKEYDOWN = 260;
WM_SYSKEYUP = 261;
WM_LBUTTONDOWN = 513;
WM_LBUTTONUP = 514;
WM_RBUTTONDOWN = 516;
WM_RBUTTONUP = 517;
WM_MBUTTONDOWN = 519;
WM_MBUTTONUP = 520;
WM_MOUSEMOVE = 512;
WM_MOUSEWHEEL = 522;
WM_SYSCOMMAND = 274;
WM_SIZE = 5;
WM_CLOSE = 16;
WM_DESTROY = 2;
{$endif}[/pascal]
to make my program work I am a bit wary. Is it really stable?.. Wil it stay free for long?.. Questions, questions... :?

[savage]

I'm surprise by that, usually all those messages are found in the "Messages" Delphi Unit. Do you have Messages as part of you uses clause?

[Chebmaster]

"messages"...? Not in the "windows" unit as in Free Pascal...?
Last time I worked with Delphi, it was 3 or 4 years ago, and that was Delphi 4. Since then I use only Free Pascal.