> 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 ;)
OK, first on FreeBSD too, then ;) More precisely, FreeBSD 9.3-RELEASE for amd64, and python 2.7.9. > 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? I'm not 100% sure, but I think I noticed one *.graffle file during the "hg clone". But maybe it was in the "develop" phase, and I saw it in another module... > 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. Personally I use lxml very often, either directly (especially the xpath function) or indirectly (e.g. via BeautifulSoup), and I like it :) It's supposed to rely on the libxml2 C++ libraries, which provide high-quality, high-performance processing of XML and HTML files :) > That's fine. Did you follow the instructions on the webpage or the ones > from Steve? >From the webpage, http://ringo-dev.intevation.de/ > 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. No particular issue, meaning creation worked, and the app still runs, but I can't see the bar module. So it seems it didn't work after all... (just tested on FreeBSD). > 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 Thanks, I'll have a look at it :) > 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. I tried to integrate different services, as in other dev environments: - Users, groups and permissions, of course (loosely based on the tutorial) - Bootstrap CSS/JS, - "Utility" languages - Sass stylesheets, Jade templates (thanks to Fanstatic) - localisation (via Babel/Lingua), including in Jade templates - Lots of dogpile caching (python code, rendered HTML, SQLAlchemy queries, etc.) - Through-the-web editable content - Form generation/validation (Colander, Deform) - Solr indexing (not light, but nothing beats it, I suppose) - Static resources handled by Fanstatic (providing bundling, precompilers, minification, etc.) - An e-commerce module provides the basis for building e-shops Currently I'm runing into a few issues, among which : - Some of my localisation modules are not compatible with Pyramid 1.5, I'm "stuck" with 1.4 for the moment. - The platform is dependent on PostgreSQL, because I used some advanced data types such as Arrays and Hstores (for extended attributes indexed by Solr). I'd like to have a "lite" version able to run e.g. on a Raspberry Pi with SQLite, and without Solr... Hopefully I'll find time to fix these issues in the coming months... Laurent. -- 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.
