On May 4, 9:24 pm, mdipierro <[email protected]> wrote:
> Just take the web2py binary distribution. Unzip, start it, upload your
> app via admin (as "init"), stop web2py.
>
> Copy web2py.app on the USB drive and you are done.

Just want to report on this:

--- Indeed, this worked well (but - there is some story around it, and
therefore a request / quesion):

My app imports a library not generally installed.

I tried placing the library in the mac.apps   area where the site-
packages are, BUT the app only contains *.pyc files, and comtimes all
those archived up).   Merely placing a library in there didn't work
In fact, ONLY opening up this area of the mac.app, and trying to re-
package it ... resulted in a "didn't work" situation.

The good news:  Massimo's solution ( use web2py to load a new app, and
then save the result - new app is in web2py).

Converting the library to an app specific module didn't require very
much (just had to be sure to not to heck for compiled library versions
from this API - since I want a "universal" mac app, i.e. running on
intel _or_ powerpc macs, I can't be letting the app look around like
this - python only).

NOW - the reason I wanted this:  stuff (demos) going on a USB to hand
out at a conference.

PROBLEM:  this gives admin.
QUESTION:  What is a way to set startup settings so the app "just
starts" from the usb - i.e. no query for password, pre-set port
number, BUT still launch a browser?

REQUEST:   Since I think making a universal mac app must not be
trivial (or I would have done it), this method is good --- but for
"hand me out at the conference"  here's a couple of things that would
be nice:

-  script to remove the *.py files of your app before packing up ---
similar to what happens (apparently) when you make a mac app anyway.
I'm not sure if PACK will be able to do that, but I'll contribute this
- it should be fine for my conference.... I'll test;

-  potentially, a "demo" exeutable of web2py - just for handing out at
conferences, clients, etc. (and - tell me if you think this isn't
necessary, and why) - that is:  enable database administration (so
people can play with select data), but not source, or any of the other
"peek at what my demo is doing" stuff.

Thoughts?
Thanks,
- Yarko
>
> On May 4, 9:01 pm, Yarko Tymciurak <[email protected]>
> wrote:
>
> > I'm trying to build a distributable version of an app for mac (and
> > it's my first time trying to do this for a mac).
>
> > I've tried "make app"  from the web2py install directory;
> > I've tried "python setup_app.py py2app"  (which I think should work);
>
> > I am missing some step - has anyone built a web2py mac distributable?
>
> > I've pretty much got the entire she-bang development setup on a mac -
> > Wing, several versions of python, all the necessary libs installed
> > accross all the various versions (my app pulls in some extra libs),
> > and all running fine on the app.
>
> > I've read thru the Makefile  app: section (which looks to me like it's
> > tryingn to take the place of py2app's actions...),   installed py2app,
> > readhttp://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html...
>
> > Thanks for any pointers, hints,
>
> > - Yarko

Reply via email to