🚀 go-pugleaf

Hi Robert and all MacApp 3.0 lovers,
 
Robert, receiving your link (on Xmas) is encouraging ...
 
> MADA could not undertake a project of that scope without a significant
increase ...
 
All is depending on the amount of a separate fee for the members subcribing the
MacApp upgrade.
IF (!) Apple will cease maintenance of MacApp, MADA is in the best position to
coordinate the bug fixes, submitted and tested by members.
Indeed we can submit implementation of new features also to MacApp.
The new versions of MacApp can be distributed on a CD (personally i will
subcribe!) or/and ETO (there are allmost no differences between ETO #8 and #9).
 
> So how can MacApp live on? It probably can't as the commercial framework that
it is today. But it would be a shame to let the technology wither and
die.
 
As i mention in my previous link, Apple should upgrade MacApp with bug fixes
and new features as QuickTime, OSL, AppleScript, QuickDraw GX ....
Indeed it would be a big shame if Apple will 'drag MacApp into Trash'!!!!
MacApp is very good and allmost complete, and used by a lot of developers.
BTW i have experimented a while with MS C++ 7.0. I added a lot of basic coding
to my subclasses to make it complete!
 
> This simple act would likely make MacApp the overnight favorite framework
among students and tiny developers.
> MacApp would become a learning tool for aspiring object-oriented Mac
programmers
 
A lot of students and developers (*tiny* and others) are developing without a
framework because working flexible with a framework, a fast Mac with minimum 16
Mb and a *huge* harddisk is a must, which means a *big* investment for a
student (plus the cost of subcribing the software).
MacApp (and other frameworks) aren't easy, it take some time (a few months?)
learning OOD, OOP and understanding the structure of the framework (where and
how to overwrite) by *browsing* the framework code.
BTW i learned a lot of *tricks* for my non-MacApp applications.
 
---
 
Something else to consider: what about the cost of
    - the conversion of a lot of MacApp applications
    - learning a new framework
    - fixing first version bugs
    - overhead of a multi-platform framework.
 
We know that Apple is reading these links, by sending links to the group is the
only way to convince Apple to keep MacApp as our favorite Mac framework.
 
I give my answer on Eric's title in one of the issues of FrameWorks 'Is MacApp
3.0 Dead?' No way, but it is still stagnant, and that is also a shame!!!!
 
Xmas (without snow) Regards
Willy
 
ps: still learning MacApp ...