On Sep 18, 2:50 pm, "Francois Zaninotto" <[EMAIL PROTECTED] project.com> wrote:
> Try to avoid using "we". I know the original tutorial has some of > these, but either the reader is doing the tutorial (and that's "you" > or "do that"), or we're doing it together, but then it should be "we" > everywhere. Since the symfony book uses the first form, I advise > removing all "we" instances. Note that "Let's" works fine. No problem, I can make that change. > Keep the tutorial fast and simple. Add more references to the doc (for > instance about forms). > > I think the security part at the end of the tutorial should teach the > user how to install and configure sfGuardPlugin rather than explain > another form object. Forms have already been introduced before at that > time, so it's not worth talking about it again. Incidentally, that > would introduce plugins, which are a great strengh of symfony, and you > could include a link to the plugins page. Last but not least, sfGuard > is used in a large majority of projects, so showing how to use it in a > First Project tutorial makes sense. I am happy to add something in about plugins (and sfGuardPlugin would be a good candidate). However I am concerned that we would not be illustrating that forms can be created manually as well (in the forums people sometimes ask if a form can be created that does not map to a table). Perhaps I can just mention that this is possible, and add a link to the forms docs, as you suggest. > As for the sfForms part itself, I got lost reading it. I think you try > to explain too many things. You should just tell that a form is > automatically generated for Propel objects and that you can already > use it (show a screenshot), then explain how to customize it in a very > simple way - and in the right order. Don't show the code of > BaseBlogCommentForm. Pass the FK argument to the form before showing > how the form constructor can use it. Show a screenshot of the form > before and after your changes. If you can, cut this part by 50%, or > users might run away. I will try to trim it down, and you're probably right that I can swap some words for pictures. If I managed to lose you whilst explaining things, then a PHP developer of beginner or intermediate ability stands no chance! I will rethink this a bit. > I'd even encourage you to remove all mention of the new form system > from this tutorial, because this part of the framework is way too > complex for a beginner. But that's only my personal opinion. On a related note, I chose not to use plugins as MFP for 1.0 also avoided them - I suspect at the time a simple form was easier than introducing a new concept. However I'd agree that plugins are less complex than the new form system, so perhaps a different approach makes more sense for 1.1. I will take your advice on board and go from there. On that basis, if anyone was thinking of helping with some screens, perhaps it would be best not to, since the illustration requirements are likely to change. Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
