Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm starting a new project, and I want to use Delphi for the desktop GUI. I'll be doing mainly typical client/server stuff with it (probably with Firebird). I have Delphi XE6 pro, and the older versions that came with it. And these are some of my somewhat flexible requirements:
The app should work on Linux and OSX, by running on top of Wine. (This was confusing, so I reworded it)
The app should work on Windows XP.
I'm thinking I'll use the open source VirtualTreeView and Turbopower GUI components. Or I may consider an older version of Devex that I have, that officially works with XE, but may (I don't know) unofficially work on a later version?
This project won't generate income right away, so I'd rather not buy a newer version of Devex (I'm currently waiting for some new work to start up, but there's no guarantee it actually will). Also, I read that XE6 will work with XP, even though it's not officially supported:
http://blog.marcocantu.com/blog/2014_april_xe6avaialble.html
But I'm still not comfortable with the idea, since Embarcadero didn't actually test it. And 3rd party support could also be a problem.
What your question boils down to is whether or not the latest versions create executables that run on XP, and then on your targeted Wine versions.
Mostly that depends on what functions you call. If you call functions that aren't present in XP, then your program won't run on XP.
A plain vanilla VCL app from XE7 will run on XP. It's what you do then that counts. Simply, you'll have to take care, and test plenty.
My large app still runs on XP and is built with XE7. So it's perfectly possible. As Marco said in his comment, Embarcadero are not yet actively changing the VCL so that it breaks on XP. But they no longer test on XP.
Personally I'd sooner use the later versions so that I had access to generics. I know XE had generics, but the implementation was still a little buggy.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I have a Windows VCL app in Delphi XE5 that I'm looking to convert/rewrite for iOS. The current app uses a local Firebird database.
I'm looking for suggestions on whether to use a tool to convert the VCL app for iOS use, or whether rewriting is the best way to go.
You don't need to rewrite your application provided you made it using FMX (FireMonkey) instead of VCL. FMX was introduced with Delphi XE2. Old FMX (The one provided with XE5) will probably not work with recent iOS version. So upgrading Delphi to latest version is highly recommended.
If you wrote your application with VCL, then yes you have to rewrite it with FireMonkey (FMX). This could be not to much difficult as FMX components are close to VCL. The most difficult part is if you use 3rd party visual components. You have to get FMX version.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a legacy project written for Delphi 7. I'm about to integrate a bunch of new code into it which includes a test suite using DUnit. DUnit it not a part of Delphi 7 (it has been integrated later), so here's the question: should I include DUnit units into my project (check them into version control etc) or should I better require all the participating developers to maintain their separate DUnit installation?
The project is closed source and is written and deployed only within the enterprise I'm working for—that is, the project source code won't be delivered to any consumer.
The way you've worded your question, there may be some confusion as to what you're asking. So let's get that out of the way first.
It sounds like your asking whether to include DUnit units in your production application. This would be a very bad idea, and I'll avoid the details why in this answer.
However, I understood your question to be about whether you should treat this "third party" source like your own project source code (in terms of source control). And I've answered as such.
There are a number of principles that justify including DUnit source in your SC repository.
Whenever you have a new developer or new dev machine installation, you want to get up and running quickly, easily and with a minimum of fuss.
Only when all dependencies are managed within your source repository can the ideal be achieved. It's quite difficult to do better than: (1) Get Latest Source. (2) Build.
Even if you use a disk image with all required apps (including third-party libraries), it won't have 100% up-to-date source.
It is very important that all your developers are on the same version of DUnit.
Otherwise you risk having test cases that work on one machine, but might not even compile on another.
After you've made extensive use of DUnit, I'm sure you'll find various things (big and small) that you'll want to change. You'd best keep these changes in your repository.
My personal experience with DUnit is that parts of it are poorly designed. As a result some extensions are much more easily done by modifying the units directly.
I would even go a step further: Even though more recent versions of Delphi include DUnit, I'd still make a copy into Source Control. As much as DUnit is shipped with Delphi - it is really just third party source slapped into a folder.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I've been using Delphi (Turbo Pascal before that) and have always been a windows guy. My wife bought me one of the new iPads for my birthday and I used it for the first time last night. Wow!... I had no idea how addicting that thing can be.
So, now I need to think about writing an app or two for this iPad. I'm guessing I need to upgrade from Delphi 2010 to Delphi XE2 and I'm looking for a good Delphi resource on development and distribution of iPad apps.
If you want to go the Delphi way you have to upgrade to XE2.
Google for (FireMonkey iOS).
Some resources:
http://blogs.embarcadero.com/ao/2011/10/26/39188
http://www.embarcadero.com/coderage/sessions
http://www.andreanolanusse.com
http://www.felix-colibri.com/papers/firemonkey/firemonkey.html
Bob Swart has a course manual called 'Delphi XE2 native iPhone/iPad Development'. It is not free, I have no stocks in it, but I can recommend it.
Check out:
http://op4js.optimalesystemer.no/
and
http://www.unigui.com
I think to compile a program for an iPad, you either need Delphi Prism, which creates a .NET application that could be run in Mono, a cross platform .NET framework.
Or, if you want to write native code, I think you will need a MacBook to compile the last step and publish it to your iPad. I think there is no compiler included with Delphi XE2, that runs in Windows and creates an executable for the iPad. The compiler for iOS (the FreePascal compiler, which is shipped with Delphi 2) needs to run on a Mac.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have been at RAD Studio XE2 World Tour here in Poland in Cracov and I really love new features, so Im almost sure, Ill buy it. But now I downloaded trial version and I want to ask about two things:
Firstly: What can I do with it? I mean - can I build for example one free application and distribute it over Internet? It would be freeware application written within these 30 days. License is quite long and I cant find restrictions like that.
Secondly: If I install this trial anything bad can happen to my Delphi 2009 (Professional)? I have a lot of IDE experts, additional components, important projects etc etc - I dont want to lose anything. In short - is it better to install it on VM?
You are not allowed to distribute applications or components written with the trial edition of Delphi.
I've installed 'full' XE2 onto a VM which already had Delphi 7 and Delphi 2010 on, and haven't seen any adverse effects over the last couple of days. All 3 environments appear to get along fine, as has long been the Delphi tradition.
Once I get a chance I'll stick it on my 'main' development VM, which is currently Delphi 2007.
However, I don't know about the trial version aspect of it. I wouldn't expect it to behave any differently but if you're concerned about your production/work environment, I would strongly suggest that you isolate your trial explorations to a VM... - just to be safe. :-)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
If I stick with Ms Jet 4.0 (Ms Access 2000-2002) to develop my desktop database program, do you think my app will become obsolete pretty fast? That is from using old db engine that will not be available in the latest windows OS like Windows 7?
Or Ms Jet 4.0 is still a safe bet?
I'm using D5 and ADO.
Please share your thoughts and opinion :)
Thanks!
Ms Jet drivers are not supported on x64 bit OS so IMHO you should no longer use it. SQLite is a great choice for an embedded database.
I would rather try Firebird Embedded. There are plenty of components to access this database (like Zeos) and Firebird Embedded is very easy to deploy (just copy few dlls and database file to output directory).
Question was asked: "Is Ms Jet 4.0 still a good choice to develop Desktop Database App?"
The answer is No, it's a terrible choice. It's old, outdated, and basically unsupported.
Jet 4.0, DAO 3.6 and ADO are part of the Windows operating system since Windows 2000 and is present in Windows 7. I also don't see Microsoft removing those from the next version of Windows although I do't have any official or unoffical quotes on that.
Since SQL Server Express is free, I think it would be quite stupid to use JET for a multi-user network based application. It was only used in the past because there was no free version of SQL Server.
But if you want a simple database app that just runs on a single workstation then JET may well be an easy option considering ease of deployment etc.