Jaakko, I'm glad we still have this conversation and I do acknowledge your attempts to understand, collaborate and point the right way.
>From time to time I drink tea with Noah Webster, Ambrose Bierce and others known to be authors of explanatory dictionaries. Guess why did they spend time this way? For example, thanks to them you know schooner is not an overseas fruit, it's a sailing vessel, i.e. schooner remains to be a part of marine slang, but you understand its meaning now without going to shipyard or university — you can imagine a boat or at least a floating duck in the bathroom. Returning to IT, why top-level of hierarchy is called root and everything else is its tree? Or why each leave of that tree is called a file not a byter (container of bytes)? Because there was no need to complicate things with new words — just look outside the real windows or at your desk with plastic folders and paper files. KISS principle, right? Olympic geeks invented MVC paradigm keeping developers in mind whereas swiss physicist Tim Berners-Lee thought of ordinary people inventing HTML that's why even... hell, everyone could use it today. Then other geeks developed frameworks upon MVC, again keeping developers in mind. And now Prometheus is awaited. The one who will translate or give a familiar explanation about that accurate geek terminology — call it 'MVC for dummies' if you wish. For example, 'scalpel' is a medical knife (everybody cook so 'knife' is a better choice than 'metal sharp stick'). And what is a front controller? Is there a rear controller? And how to think of a model if yesterday all your pals referred this word to posing or high fashion? By the way, come to Switzerland, you'll be amazed with the 'views'. I see at least three ways how to cover this gap. 1. Extend the glossary with real-life analogies. 2. Add an extra guide 'for dummies' to Symfony2's Book. 3. Craft a downloadble demo of mid-size project covering such topics: - add page - add folder - split markup and content - link without hard-coding - use Twig for inheritance - include 3rd party tools like SCSS or HAML for intermediate tasks - add common error pages - (optionally) add more languages so foreign users feel like at home visiting one's site I see, many of you are excited about being 'internet assembler', being large-scale oriented and so on. But is there one to lend a helping hand in my case or it's so time consuming? Please. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
