At 0:52 Uhr +0100 10.03.2005, Quentin Mathé wrote:
Le 8 mars 05, à 17:58, M. Uli Kusterer a écrit :
At 21:41 Uhr +0100 07.03.2005, Stefan Urbanek wrote:
How it should be? Instead of creating an application, create a
framework. Self-sufficient application should be considered a prototype
and proof of concept for given functionality. Application should be only
an user interface for a framework. The application should be as thin as
possible.
(...)
Moreover, the framework should be split into two: UI and non-UI part.
(...)
Thoughts?
1) Installation hassles: This would mean one
would have to install three parts, in three
different locations, and uninstall them to get
rid of the app: Framework, App and Tool.
I think we could extend make_services crawler
tool to discover Framework and Tool packaged in
application bundles, then no need to have such
install process. A Spotlight-like crawler would
be proably later the best solution to provide
transparent installation by drag/drop (Mac OS X
Library folders are a real pain to clean when
you add/remove applications on your system
often, even when you consider this situation has
improved a lot compared to Mac OS classic)
OTOH, a crawler would be a security risk. MacOS
X already does that for file types and URL scheme
handlers defined in an Info.plist. You'd need to
keep track of what frameworks have been loaded
before and warn the user when a new framework is
first loaded...
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
