Re: Why PHP?
- From: Thomas Miller <tmiller@xxxxxxxxxxxxxxxx>
- Date: Thu, 08 Feb 2007 13:50:16 -0500
http://sourceforge.net/projects/uopl/
Universal Object Pascal Library
After doing the ground work for such a beast, the way to go is with namespaces. This way you can have anything you want. For example,
clx/delphi/delphi12/*
clx/delphi/uopl/*
clx/delphi/gtk/*
clx/delphi/qt/*
clx/delphi/chrome/*
clx/delphi/aspnet2/*
clx/delphi/carbon/*
etc. (fyi, I think carbon is the native stuff for Mac OS X, or does it have a new name).
With conditional compiling, I can choose which library branch I want to base my exe on.
The uopl could be the beta / bleeding edge of the fully tested supported version of the VCL shipped with Delphi (in this example delphi12). Much like you have Fedora and openSuse for RedHat and Novell Suse Enterprise.
Base it on a license like Qt, free for open source use, pay a license for commercial. Obviously, you get a full use license if you buy Delphi, but you would still make money off those entities using Lazarus if they develop commercial software.
Using the method above, you should be able in a not to distant future, rebuild Delphi for all of these platforms.
Unfortunately I gave up when there were to many issues with needing to change private stuff in a lot of the base classes. Which means I would be using copyrighted stuff, which was a non starter.
Michael Swindell (CodeGear) wrote:
Dynamic languages such as PHP and Ruby new areas where we will be going. Some products will be more in the RAD camp, aligned with Delphi and VCL, and others will be more in the Open Source/Eclipse/Enterprise world. As a developer focused company we cannot be just the Object Pascal, C++, Java development company... there is way too much happening in the world of programming and languages and frameworks for us to stand still. Phillippe was willing to try different languages and products, some didn't stick (turbo modula), and others were wildly successful and decendents are still here today (Turbo Pascal, Turbo C++).
I can't yet comment or confirm leaks on future PHP products (that Swedish announcement was a no no), but *anything* we do in the Delphi world has be centered around a VCL framework, visual design, and allow component development. By PHP extensions, do you mean extensions for the IDE written in PHP?
Re cross-platform Delphi and the comments about CLX (VCL for Linux) in the paper. I'd like to see more discussion and thoughts around CLX and Qt and Gtk... what would a second generation CLX look like? Could it be completely open source and community developed with CodeGear support? How long would it take to develop? For CLX we did a mechanical port of VCL, then "hand wired" it from GDI to Qt - it was very manual and time consuming, took a loooong time.
"Simon Kissel" <kissel@xxxxxxxxxxxxxx> wrote in message news:45cb2a7c$1@xxxxxxxxxxxxxxxxxxxxxxxxxMichael,
let me take this chance to point out something that isn't mentioned
in my proposal document, simply because at that time your PHP
plans had not yet been known.
Personally I'm a bit sceptical about that PHP venture due to it
being a market you've got zero reputation in etc.
But if you do the PHP stuff and are considering also going cross-
platform with Delphi, I see a huge synergy effect in there:
If CodeGear comes up with a PHP IDE, wouldn't it be great if Delphi
allowed you to create PHP extensions for it? Keep in mind, PHP is a
scripting language, "components" (=extensions) need to be written in
a native code language to give usuable performance. Combining these
two would allow you to test your PHP extensions directly inside the
PHP IDE - it would even make sense to have Delphi and PHP personalities
in BDS this way.
This would be even greater for CodeGear's partners/component vendors:
Components from once-Delphi-only component vendors could be shipped
together with the PHP IDE product (maybe some licensed, others as
trial on the partner CD).
Selling just another PHP IDE without anything new doesn't sound that
interesting - how about selling a PHP IDE that provides a benefit
over other PHP IDEs, because it already includes PHP components and
allows you to add new ones?
I don't know how that fits into your PHP concept, but possibly
this is something worth thinking about, as it appears to be a
win-win for Delphi and the PHP IDE.
Simon
--
Thomas Miller
Chrome Portal Project Manager
CPCUG Programmers SIG Chairperson (formally Delphi)
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
http://www.bss-software.com
http://programmers.cpcug.org/
http://sourceforge.net/projects/chromeportal/
http://sourceforge.net/projects/uopl/
http://sourceforge.net/projects/dbexpressplus
.
- References:
- Why PHP?
- From: TObject
- Re: Why PHP?
- From: TObject
- Re: Why PHP?
- From: Michael Swindell \(CodeGear\)
- Re: Why PHP?
- From: Cesar Romero
- Re: Why PHP?
- From: Michael Swindell \(CodeGear\)
- Re: Why PHP?
- From: Simon Kissel
- Re: Why PHP?
- From: Michael Swindell \(CodeGear\)
- Why PHP?
- Prev by Date: Re: Delphi Spacely and Delphi Astro
- Next by Date: Re: My Vista/Delphi/Dev experience
- Previous by thread: Re: Why PHP?
- Next by thread: Re: Why PHP?
- Index(es):
Relevant Pages
|
Loading