#Mac/Win crosspltform Dev
11 messages in this thread
Yes, there is the Code Fragment Manager (CFM), currently available
under PowerPC _only_, but eventually available under 680×0 (with the
Apple Shared Library Manager (ASLM) available in the interim).
However, that's not going to help when it comes to a dynamic-link
library (DLL). You simply cannot take DLL code which exists under
Windows today and use MSVC 2 (when it's released) to produce a
Macintosh version via the CFM or ASLM. Yes, it's possible to design
_new_ code which takes the considerations of DLLs and the CFM, but the
MSVC 2 solution can take _current_ code and provide a cross platform
solution.
So, I meant DLLs as they exist under Windows, not that the Macintosh
did not have an equivalent technology. But it is a _different_
technology which is not compatible with Windows DLLs. The MFC with
MSVC 2 is a solution, while DLL with MSVC 2 is not.
Just a clarification.
P.S. Sorry I missed you at the conference! Thanks for the free
MacTechs!
David,
>> Just a clarification.
Aha! Now I understand what you meant. FYI: I believe that Apple will
be abadoning the ASLM stuff and going for the newer stuff from IBM
(which I'm lapsing and can't remember the name to right now).
>> Sorry I missed you at the conference! Thanks for the free
MacTechs!
Me too. You're quite welcome. Did you like the issues?
>> FYI: I believe that Apple will be abadoning the ASLM stuff and going for
>> the newer stuff from IBM (which I'm lapsing and can't remember the name
>> to right now).
God, I hope so. ASLM stinks. SOM (System Object Model), on the other
hand, is cool, or so I've been told (haven't studied it myself…)
>> God, I hope so. ASLM stinks.
That's what I've heard as well. The OpenDoc team is moving from ASLM
to SOM in one of their upcoming pre-release versions.
>> SOM (System Object Model), on the other hand, is cool, or so I've been told
(haven't studied it myself…)
Yep. That's what I've heard as well.
Time will tell,
>>Despite what people claim about Microsoft apps dominating on the Mac,
>>the simple fact is that MS would make more $$$ if they could convince
>>Mac users to use the same MS apps under MeSs-Windows. And every little
>>slowdown will convert a few people.
Like Excel's macro evaluation speed on the Mac? (a p-code emulator in a Mac
app? — I called MS on that issue last year and they grudgingly admitted that
the Mac versions macro evaluator was not native Mac code.)
>>I really hate the idea of being totally dependent upon a Microsoft tool
>>to develop a mac app. What happens if they're slow to implement new
>>versions as the mac evolves?
What if they never implement something? Mac apps made via that platform won't
be scriptable, eh? I gathered that from earlier msgs, even with extensive
#ifdef-ing the code won't be structured/factored to support it. And that
knocks voice control out of the running, right? I understood that scripting is
used to enable that.
* * * * * * * * * * ** * * * * * *
Y A H O O ! P O W E R P C T O D A Y ! ! !
Al;
Neil,
"FYI: I believe that Apple will be abadoning the ASLM stuff and going for the
newer stuff from IBM (which I'm lapsing and can't remember the name to right
now)."
Do you mean the Code Fragment Manager, or something else. If the lattter,
please elaborate!
"Did you like the issues?"
I've actually not had time to look at the issues as yet. However, I'll be
looking at them soon and will then decide whether to resurrect my ancient
subscription!
David
David,
>> Do you mean the Code Fragment Manager, or something else.
Apple is going to be getting rid of the Shared Library Manager in favor of SOM
(an object manager) from IBM. OpenDoc will make this move in one of its next
prerelease versions.
Good luck,
Neil Ticktin
Editor-in-Chief
MacTech Magazine
(formerly MacTutor)
>>I believe that most Macintosh developers are not interested in
>>developing commodities — otherwise they would have been developing
>>for Windows. Macintosh is about doing things better
>> — not like everyone else.
Got that right!!
And it works that way (sort of) in the Windows world also! A friend (who does
that stuff) told me that the word is: "If you want to make money use Microsoft,
if you want to develop software use Boreland".
>>Apple is going to be getting rid of the Shared Library
>>Manager in favor of SOM (an object manager) from IBM.
>>OpenDoc will make this move in one of its next prerelease versions.
I was really impressed with the ASLM, although I didn't get to use it, compared
to DLLs. I liked the thought of DLLs that could be used with C++. Will DSOM
work with C++?
Al;
Nick,
"Apple is going to be getting rid of the Shared Library Manager in favor of SOM
(an object manager) from IBM. OpenDoc will make this move in one of its next
prerelease versions."
Interesting, yet _another_ change by Apple. I'm now glad I didn't waste my
time learning the ASLM!
David
>> Interesting, yet _another_ change by Apple. I'm now glad I didn't waste my
time learning the ASLM!
Since you insist on being so critical of Apple, I'd like to remind you of
Microsoft's fabled "TrueImage". I have two clients with TrueImage printers,
both are now sitting in a corner on the floor. Apple is not infallible, and
Microsoft stumbles just as often.
As for ASLM, it works and there are a few critical products in the market using
it. Sitting on your hands will not get your product shipping any time soon.
And then looking at the other side of the fence, I sure a LOT of people will be
overjoyed to hear that they will have to rewrite their VBXs in order to work
with OLE2… (isn't that a change about to hit soon…)
malam
Mehboob,
"Since you insist on being so critical of Apple, I'd like to remind you of
Microsoft's fabled "TrueImage". I have two clients with TrueImage printers,
both are now sitting in a corner on the floor. Apple is not infallible, and
Microsoft stumbles just as often."
I don't like or dislike Microsoft any more than Apple — I work for _neither_.
However, I, as a developer, feel I'm getting more of what I want and need from
Microsoft than Apple. You choose to criticize Microsoft, I choose to criticize
Apple. Microsoft has _never_ let me down (yet, of course!) whereas Apple
continues to find new ways to do so.
"As for ASLM, it works and there are a few critical products in the market
using it. Sitting on your hands will not get your product shipping any time
soon."
I don't find myself "sitting on my hands". If I needed ASLM I would have been
into it. I'm just glad that I _didn't_ need it so I've not invested time in
something that had no long term gain.
"And then looking at the other side of the fence, I sure a LOT of people will
be overjoyed to hear that they will have to rewrite their VBXs in order to work
with OLE2… (isn't that a change about to hit soon…)"
No more overjoyed then the Macintosh folks who need to do the same for the
ASLM->SOM decision.
David