Thread View: comp.sys.mac.oop.macapp3
1 messages
1 total messages
Started by De Waele Willy - Gent,BE,IHD
Tue, 29 Dec 1992 02:38
The Takeover ...
Author: De Waele Willy - Gent,BE,IHD
Date: Tue, 29 Dec 1992 02:38
Date: Tue, 29 Dec 1992 02:38
57 lines
3077 bytes
3077 bytes
Hi all,
First to Kent:
> And what are the real bottlenecks of the Macintosh today?
Real multiprogramming (multitasking) with priorities and time-slicing setup via
CDEV or something else. Perhaps with PowerPC?
I believe that there will be no or minor penalty for todays 7.x Mac
applications running on a PowerPC: the penalty is compensated by higher speed
of the RISC. I refer to "Blueprint for the Decade" (an Apple document) p. 8:
"Smooth Migration Path", and an article in "Apple Direct".
Running SoftPC on a Mac is very slow, even on a Mac IIfx: that's real
emulation. But there is a market for this product.
But ... on p. 10 in the same document:
### i quote "MacApp - Speeding Application Development"
...
"MacApp provides a timely way to incorporate new features when new versions
of system software are introduced. When MacApp began shipping, developers who
had created their programs with MacApp 2.0 were able to gain full support for
System 7 features in a matter of days instead of months."
"MacApp will track advancements in the System 7 platform, including
QuickTime, OCCE and user interface enhancements. MacApp gives in-house and
commercial software developers the ability to track these capabilities as well,
while also providing a head start toward programming for Pink."
### end quote
The analysis:
1. "new features when new versions of system software are introduced":
---> Indeed MacApp 3.0 supports some new Sysatem 7.0 features:
AppleEvents, Balloons. But there was a big conversion from MacApp
2.0.
2. "QuickTime, OCCE and user interface enhancements":
---> de nada.
3. "providing a head start toward programming for Pink":
---> smooth migration to Bedrock? (see below)
So what???
Or, this article has no value (only commercial)
Or, framework software is moving too fast and we developers can't follow.
We can't change every year to another framework.
In any case, i work 23+ years with IBM and one thing is sure: When a product
WILL BE obsoleted, we receive an official letter specifying that 1 year from
now it will be obsoleted and AFTER that date no more maintenance. In the
meantime (during 1 year) we received support and official bug fixes.
Thus, ETO subscribers received no official document about MacApp obsolete.
We expect that Apple fix the bugs until Bedrock is released and give us a
smooth migration to it, otherwise we can better develop as in *the old days*:
vinala C(++)/Pascal and create our own *framework* and using MacApp as a base
for trivial procedures or find another solution ...
Regards,
Willy "WDW" De Waele
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads