I have taken a look at these URLs:
check if runtime installed
https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution
some sample code assuming newer Delphi
Using WebView (EdgeHTML) in Delphi / C++ Builder
some sample code assuming newer Delphi
WebView2 (TEdgeBrowser) updated Delphi interface (e.g. ICoreWebView2Controller2)
Yet even those seem to assume a newer Delphi version than I use (XE4) ... and preferably I would like Lazarus support as well. At the same time I really love being able to use "newest available patched system browser" which is why I am not jumping on https://github.com/salvadordf/CEF4Delphi albeit it may end up being the final solution.
Is there anyone else who has begun the undertaking of implementing webview2 on older versions or is this simply impractical due to type libraries not being importable etc? (i.e. major headache in converting, implementing and testing everything, furthermore on old Delphi versions)
I recently published WebView4Delphi at GitHub with an MIT license.
WebView4Delphi uses the WebView2 runtime to embed Chromium based browsers in Delphi and Lazarus applications.
It was developed in Delphi 11 but it also works with Delphi XE3.
I'm quite new to Delphi and I'm helping a team setting up a build server which are using Rad Studio 2005.
They have just bought DevExpress VCL and wants to use these. I would rather not have the component installed on the build server, but instead having them as a part of the source code and making sure that the project is using that version.
How is that done in Delphi?
We compiled all of our 3rd-party stuff into a BPL, then put that .bpl and corresponding .dcp and .dpr/.bdsproje into source control, so it gets delivered to the build server. Works well. In retrospect, it should have been a series of BPLs, divided by vendor, so that we could upgrade individual components/libraries without having to run regression tests on everything else.
My Win7 now installed RAD Studio 2010 with Delphi 2010, can I install Delphi XE3 separately? So both Delphi 2010 and XE3 work on the same Windows?
Thanks!
Yes you can. You can install all versions of Delphi side by side on a single machine. I'm currently sitting at a machine with D6, 2010, XE, XE2 and XE3.
Different people have different ways to organise side by side installations. I personally remove all references to Delphi from my system PATH variable. Then if I need to do anything at the command line I make sure I execute the rsvars.bat for the target version. That sets all the environment variables needed for that Delphi version. At that point executing dcc32.exe results in the target version of the command line compiler being invoked.
They should work. However some certain components might be buggy like different versions of BDE or maybe different versions of remote debugger core. But in general if you install lesser version with updates and then install more newer one - it should work. Unless some bugs happen.
But when you'd compile your projects or libraries, if you want to use both IDEs you should be very accurate about DCU and DCP paths, BPL names and such, so they would not be mixed in same place. DCU and DCP should be written into and searched in different folders. BPL names should have version-denoting suffix to them. and such.
Back when I used Delphi (win32), programs made with it would run on windows, with no need to install any runtime libraries like .NET or Java(?). Is this still the case? If not, which language can do that?
Delphi executables don't have any external dependency.
It's true since Delphi 1 up to Delphi XE.
I just wrote a post on my blog about this fact I like very much in Delphi.
http://blog.synopse.info/post/2010/09/20/Dll-hell%2C-WinSXS-directory-and-Delphi-paradise
No dll hell with Delphi applications!
Deploying a Delphi application is very easy.
If you need some database access, you could need some additional components, like the BDE, or the ODBC drivers, or whatever...
But there are a lot of stand-alone frameworks, with no external dependency, available for Delphi. We provide one Client/Server Open Source solution, using SQLite3 as database storage. And one of great feature of SQLite3 is that it doesn't need to install any client software. Our framework provide the Client/Server features, in pure Delphi.
Both the language and the IDE had some serious improvements from Delphi 1.
To name a few extentions for the language:
Support for interfaces
Records with methods
Record and class helper functions
Annonymous functions
Generics
Hinting directives
There are also some IDE improvements.
Unicode support
More integrated tools
Usage of identifiers (2011).
There are still some things missing:
64 bit support
generics still have some bugs.
It is still the case for the "normal" Delphi, i.e. Delphi for Win32. There is also Delphi Prism which targets .NET for which it is obviously not the case.
Currently there's Delphi for Win32 available, which doesn't require any runtimes and Delphi Prism (for .NET application development). Delphi for 64-bit native Windows development is promised next year.
Well, Lazarus obviously :-)
Seriously, Delphi is fine, but before you buy a recent one, if you need win9x support, check thoroughly. (since the unicode versions might no longer support that)
Is there any conflict?
All new versions of Delphi can always be installed safely /next/ to older version.
Each new version should be installed in its own directory.
If you are going to install multiple versions, always install the oldest version first, and then work your way to the newest.
We work very hard to make sure that all versions of Delphi coexist together. But again, never install one version directly on top of another.
I am running 2007 and 2009 on the same machine (this machine) just fine. The only problem you might have is if you are compiling components to the same directory - you will just need to rebuild all your DCU's and packages each time, or make version specific packages and directories.
Install them in their own directories, and make sure you keep package binaries separate, you should be fine. I've got 2009, 2007, 2006, 7 and 5 all on this machine with no issues.
I have at least 4 Delphi versions on one machine. They do not bite each other.
I always install older versions first because i had once problems if i did this the other way round.
Yes - as Rob said (Robsoft) I have both working here. Delphi has always been very good at co-existing with other versions.
Obviously you can only have one version as the default for opening Delphi files.
Should not conflict.
I did D2007 on the same machine as D2006 with absolutely no problems (I was shocked, actually).
I haven't tried D2009 yet, but it should be ok.
This guy had problems though. Hopefully his issues were due to the custom setup he describes in that article.
A colleague of mine (think he has an account on here as dcraggs now) has got them both running on the same machine just fine, I believe.
Certainly would be a huge own-goal from Embarcadero if installing D2009 broke an already-installed D2007, given the way that the components and DCUs are not compatible - I suspect a fair number of people will need to have both around for a while (some of us still need D5 and D7 too!)
CodeGear stated (don't have a link handy, sorry) that there should be no conflict. I haven't yet installed D2009 on my workhorse PC so I don't know if that is correct.
The settings in registry have different path and packages have different names so there really should be no problems.
I have Delphi 2007 and I have installed 2009 yesterday with no visible problems so far. Both seem to work fine.
Appears to be no problem. Installed D2009 with TurboDelphi and 2007 and 2, 5 and 7 all on the same Vista machine
Both 2007 and 2009 have Jedi JVC and JVCL installed on them. All appear to work fine. Hope that helps.
.. and if you compile existing packages make sure you give them a new name (e.g. suffix with D12) as each version's BPL directories are in the path.
Installed D2009 Enterprise on VMWare instance running Vista Business with an existing D2007 Enterprise installation. Perhaps I did something incorrectly, but I began to experience errors in the D2007 IDE, as well as a very strange error, unknown fieldtype, in exe files compiled with D2007. I uninstalled D2009, and the errors have gone away.
You should always install the older version first. I tried to install 2009 first and then 2007 but the setup of 2007 failed.
Uninstalling 2009, and starting with 2007 first fixed the install problems.
In theory, it's possible, but if you use many third-party (or your own) libraries, it can get hairy pretty fast. I tend toward developing on Virtual machines, for this and other reasons. But, YMMV.
Should be fine. I have Delphi 7, 2006, 2007, 2009 with 3rd party libs Dev Express and Rem Objects for all (except Dev Express for 2009 - is it out yet?) and all work flawlessly. As others pointed out the versions were installed oldest to newest.
The installations won't interfere with each other, although the Delphi 2009 and Delphi 2007 projects are not compatible, and can't be shared.
Moving along with the order of release is a must. Install older first. Uninstalling may get tricky though.
How to fix Delphi 2009 data explorer?