Sorry my first message was send before i finish it. here it is : _____
Naives Pyramids questions and remarks I hope this will be useful, it's just my questions about the future Pyramids. Just for info i consider myself a beginner programmer, because i know than i use things than i don't understand all the underground machinery (and i hope i will not need to understand it). I was most of the time adapting recipes from Pylons Book, Pylons Docs, TG2 docs and learning in the same time. Actually my mind is a bit separated in two parts : - Happy, because i see than the project have a direction, and than Pyramid have a extensibility design in mind witch i think was missing in Pylons (inherited from repoze.bfg). the 'transversal' think make me curious too. - Frightened because i am near to finish my first Pylons project, and it already take me a lot of time during the process just to begin with : choosing between Django/TG1/TG2/Pylons, then choosing Auth&Auth, buiding a lot of Mako templates, form validating, etc...) it's just now than i think than i begin to be productive than i see than i will probably need to learn a lot more. I have already made the 0.9.7 -> 1.0 move (and that was easy thanks to http://pylonshq.com/docs/en/1.0/upgrading/). So i will probably do this new move to before to release my project. But, now i still have a lot of (probably naives) questions and some few remarks about the pyramid docs. 1) I do not have seen in the Pyramid docs lines about logging. I do not see either in the default pylons_sqla template. I think than it was a great default idea in the Pylons1 templates. So : - do i will have to add it myself ? - is there another Pyramid way - this is planed in futures templates (or shabti) but not ready yet Alternaly a word about this in the Pyramid docs, even to say "do it yourself" would be useful. 2) If i have understand, Beaker is not set up by default but pyramid_beaker is available, and will probably be used by the majority of us. In my Pylons project i do not have to even think about it because the default template do it for me so : - is it planed to add it by default in a pyramid templates or will it be only a "do it yourself" ? (it's seems anyway than it's easy to do thanks to pyramid_beaker) 3) Pyramid is furnished with his own Auth&Auth mecanism. Actualy i am using repoze.what-pylons mainly because he have a database backend and a good user base (also TG2 give me an alredy done model for it). Actualy i can do what i want with it even if he give me too much (i use only users and permissions, but not groups). But it's working (even if it was a bit painful to setup) Francky i have find the Auth&Auth doc part of Pyramid dificult to understand for me. It's probably because i have use a someone else recipe for now and did not do it myself so : - Could we have a steep-by-steep of the Pyramid Auth&Auth working example in the doc (preferabily database oriented) I know than the objective is to be the more flexible as possible and to allow a bunch of differents mecanisms, but even if i need and want Auth&Auth i would prefere to concentrate on what do the application, so basicaly, take the common recomended recipe and go on. - What are the advantage or limitations of the pyramid Auth&Autho over others ? (repoze.who/what, AuthKit etc...) 4) Pyramid have herited the ZCML thing... I sure than you are already aware of the basic Pylons developer fear about it. My problem is not the Zope backgroun it's just than i don't like writing XML. I already know than i can use the Configurator to be pythonic and even do not think about XML. But it's well explained in the doc than if i want my project to be Expendable i will have to take the ZCML road so : - Is there any futures plan to allow apps to be expandable even if the are writed imperatively ? - if not could we have an ZCML example for each imperative example in the doc ? 5) When i has reading Django/TG2/Pylons docs and books, the more intersting part for me was form handling parts. Because my applications will have alooot of forms (they are database front-ends). Handling forms is bit painful with Pylons actualy (mostly because of validation part) but with the Pylons docs and the book i can manage them and create form nearly as they are in my mind. I would realy be happy to have an even very short form example in the doc. Particulary a set of CRUD opperations in the view handlers . Preferabily a plain html one with no validation just to understand well the basic flow process. (I have find the pyramid_formish page and quicly read it. But i have the same impresions than when i read/try ToscaWiget. This will do the job but i will lose a lot of template control and have a bunch of <table> or <div> forms instead of <fieldset> ones). 6) I will need internationalisation (my base user are all french but i try to write only english code because my english is so bad than i like to spread it). The docs are here but i have one question : - I have take a lot of time to painfuly write my string with _("string") or worstly ${_("makostring")} ... His this will work out of the box with a good imports (probably translationStringFactory as _ ) or did i will have to review all of them to take care of the 'domain' or more ? There is probably some more latter but they are the one who pop in my mind while reading the docs. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
