alexeld

Hi Chaps, First of all: thank you all ever-so much for getting back to me! There's a mountain of great advice from each of you for me to start working through, and I really do appreciate it. I had started to get a sense that ProcessWire was accommodating of various development methods, and it's actually quite refreshing to find a framework which *doesn't* enforce a strict development methodology. Suffice it to say, I'm looking forward to getting stuck in to developing my little test application to figure out which method here best suits my needs. You guys have been great. Thanks again for all the input! Cheers!

Hi folks, I'm new to ProcessWire, and I'm currently evaluating it for use in an upcoming project. The reviews and write-ups I've read online have said great things about it, and from what I've seen so far, I'm really rather impressed. I've spent a lot of time using Laravel, CodeIgniter, and CakePHP, all of which make use of the MVC pattern, however, PW doesn't do this, and therefore I'm looking for some advice on how best to structure my PW applications... Reading around, I've found some write-ups which cover form handling and validation, but I'm unsure quite *where* these files should live, and I'd love some advice on how best to structure my application. Do I create a template which contains form-handling code *and* HTML (all in the same file -- like "classic PHP"), or can I separate my form handler/validation code from my markup (and have the HTML form post to a PHP script somewhere else)? Or maybe there's another way (perhaps using Modules) that I'm unaware of? If it helps, I'm /usually/ the "backend guy" on the projects I tend to work on, and I work closely with front-end chaps (designers mostly) who throw together the HTML, so if there is a way to keep the markup and processing logic loosely coupled, I'd love to hear about it! Anyway, thanks for taking the time to read this, and I really would appreciate any wisdom you kind people have to offer. Many thanks!