On Nov 5, 2005, at 5:37 PM, Jeff Lowrey wrote:
Again, it kind of depends. Web based applications are usually
different in scope and usage patterns than standalone applications.
If your app really makes more sense as a standalone desktop app, then
you should probably go to the trouble to refactor it to use
CamelBones. If it makes more sense as a web app, you should maybe
look into distributing it in a "hosting" manner, rather than an
installer manner.
This also changes if you're planning on selling this, or merely making
it available.
Let me move the focus a little...
If there were a perl module that could let perl CGI scripts interact
with a native Mac OS X window, that displayed web formated content like
Safari (or perhaps a hacked FireFox), but also gave you access to the
"Main Menu", then any web programmer could port their work to a native
Mac OS X (like) application with little effort.
Now, if you consider the different aspects of current web apps and the
features that you can use now on OS X with the built-in Apache, like
MySQL, DHTML, CSS, AJAX, Graphics Libraries (GD), accessing local or
remote data for use in your application, you have a rich collection of
APIs that leverage a huge base of existing programmers skills to create
Native Mac OS X apps, for sale, or free. If they could just package it.
It's just something that feels so close...
--
Bill Stephenson
