> I concede that if the components arent available, you wont be able to port
> your app using those components. But whats the alternative if you want a
> mac version? The only alternative is a complete re-write in another
> language. And you'd still not have those same components. I'm under zero
> impression that I'll be able to take any of my apps and 'simply' re-compile
> them for macs. Thats not going to happen. But, if Delphi can get me 90% of
> the way there....
Yeah, that's what I'm thinking. I may have to "dumb-down" some of the
screens, but that won't keep me from re-using A LOT of code, when
releasing a lite-version of Product X for the Mac.
>
> Plus, if a Delphi compiler for macs/linux/whatever is available, what makes
> you think DevEx, TMS, etc wouldnt port their components?
Believe me, I'm counting on it. I already have declarations from Marc
Hoffman that I'll have TDAMemDataTable's equivalent on the Mac.
> Esp when we're
> talking non visual components. Unless their components are specifically
> designed for integrating into windows (something like D2D or shell
> integration), it should certainly be possible for most of them. A grid is a
> grid... why wouldnt it be possible to port it?
Well, a grid is a grid, until you start using DevEx's QuantumGrid.
That's when you realize there are 2 classes of citizens in that world.
Of course I would want them to port it. I'm sure it COULD be ported. The
question is how much work would it take DevEx, and what is the ROI?
And by extension, what is my ROI for extending my apps to the Mac space?
In the past 12 years, our company has had only 1 demo where having a Mac
version was stated to be part of the decision making process. That fact
doesn't negate that we could start actively pursuing that market, however.
Loren sZendre