Hi,
I gave it a try, too. MacOS X 10.10, Python 2.7.9 from MacPorts.
> Everything worked fine.
>
Great! Thanks for your feedback and congratulation, you are the first
official MacOS user of Ringo :) If there is anyone else who want to be the
first one on other OS too then go for it. There are plenty options left ;)
> pcreate -t ringo foo
>
> The doc says "pcreate -t ringo Foo" ("Foo" with a capital "F").
>
> You have to remember that the filesystem on a Mac is case-insensitive
> (but case-remembering). So, "foo-admin" and "Foo-admin" would be the
> same on a Mac, but "foo-admin" wouldn't exist on e.g. Ubuntu Linux.
>
Thank your for the hint but I can not confirm this. This also works for me
on Ubuntu Linux. Internal the lowercase Version of the application name
will be used.
> I believe the initial instructions were created on a Mac, because I saw
> Omnigraffle files (a Mac-specific drawing app) when I did the "hg clone"
> yesterday.
>
No. It was some Linux System. Which files do you mean?
> > ImportError:
> > /home/xxx/.local/lib/python2.7/site-packages/lxml/etree.so: undefined
> > symbol: PyUnicodeUCS4_DecodeLatin1
>
> I believe it depends on whether Python was compiled with UCS2 or UCS4
> Unicode strings. In that particular case, I suppose UCS2 was chosen. I
> compiled lxml a number of times (on FreeBSD, Linuxes and OS X, and never
> came across that error)
>
Ah again thanks for helping here out! Unfortunately lxml is a dependency of
iirc py3o.template which I need for a nice printing feature in ringo. A
planed to replace it as the xml part does not seems to be that difficult.
But as always: There is simply to much work for too less time. But this
dependency is actually somewhat annoying.
> Anyway, anything went fine for me, I was able to launch the app, and
> from there I didn't know where to go... :D
>
That's fine. Did you follow the instructions on the webpage or the ones
from Steve?
Did the creation of the modul work for you? There is currently a issue with
that which i noticed in the instructions.) Do you seethe created module
entry on the header menu of your application after logging.
The next step is to add fields to the module to actually save something
useful and build a nice form for it. This is described in the documentation:
http://ringo.readthedocs.org/en/latest/development.html#adding-new-fields-to-the-model
This is quite easy and you can develop the form and model on the fly.
Modify the form definition, reload the page, do some changes and if you are
finally ready generate the model and apply the migration to actually safe
things in the database. For me this is one of the most helpful parts of
ringo. You should give it a try :)
If you or anyone else is interested in trying out more things I like to
help you of course. I expect there will be some points which need to be
better explained or are missing at all in the documentation.
As I did not want to spam the pylons-discuss group here with ringo related
things more than necessary you can either contact me on my private email or
(even better) subscribe to the new created group:
https://groups.google.com/forum/#!forum/ringo-framework.
PS: I have my own development environment too, but I'm afraid it's not
> ready for prime time...
>
:) Release often and release early. That the slogan often related to FOSS.
But I can understand you :) I was, and I am also afraid to make it public.
Torsten
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
