These are general thoughts - and they aren't complete - so try to read between the lines a little :)
I've been wondering for a while on how the GUI side of things can be reworked to make things more fluid for devs while also allowing the Dev/Designer team to be more effective. I've been thinking along the lines of GUI based behaviors - that can be applied to views/widgets/components/forms/data-sets. It's best explained by an example that I've suggested in other places (hi J.Wage :)): Take translation - it's something we apply to models and templates. Imagine a Translation behaviour for the UI - you apply it to the view/form/page and it supplements the output with style and JS that displays a GUI helper for inline translation of the page elements. On Fri, 18 Sep 2009 17:33:55 +0200, Sid Ferreira <sid....@gmail.com> wrote: > Actually, each advent callendar could have a small "client" > application.For > instance, in jobeet, an affiliate website. > > On Fri, Sep 18, 2009 at 12:31, Sid Ferreira <sid....@gmail.com> wrote: > >> David: up! >> >> >> On Fri, Sep 18, 2009 at 12:29, david <da...@inspiredthinking.co.uk> >> wrote: >> >>> >>> The forms side of things is complex and cumbersome - but mostly due to >>> the >>> nature of PHP itself. >>> Lacking a decent WYSIWYG IDE does symfony and PHP in general a >>> disservice >>> - but the flip argument is that you're an engineer not a photoshop >>> monkey. >>> >>> From the tutorial perspective Sid's right - there needs to be more - >>> and >>> probably a minimum of 3: >>> 1) Simple, uncomplicated - show the speed and power of sf >>> 2) Jobeet - simple but has the background >>> 3) Complex - detailed >>> >>> The API documentation of SF should be linked back to the tutorials - >>> giving examples of usage and allowing people to refer to examples. >>> >>> On Fri, 18 Sep 2009 17:20:45 +0200, Sid Ferreira <sid....@gmail.com> >>> wrote: >>> >>> > It kinda makes sense... but is also hard how to handle that... Maybe >>> a >>> > small >>> > intro about Doctrine, but you must remember that using >>> > About forms, well, they are classes, if you dig up you find >>> everything, >>> > but >>> > without any IDE, it's madness... >>> > >>> > Maybe a 'Symfony for Dummies' was needed, in order to hookup people >>> that >>> > doesn't have the minimum knowledge (as Prieto just said) >>> > >>> > On Fri, Sep 18, 2009 at 12:04, bghost <bggho...@gmail.com> wrote: >>> > >>> >> >>> >> Hi Fabien, >>> >> >>> >> - With the introduction of the Doctrine ORM, number of parameters >>> >> and configuration options are increased manifold. Therefore, the >>> >> developer >>> >> must first learn all about the Doctrine ORM. Is that good? Doctrine >>> >> ORM >>> >> already providing a fairly good possibilities and options without >>> >> Symfony. >>> >> >>> >> - Symfony WEB forms are a bit too complicated and their relations >>> >> with the rest of a Symfony application is often unclear. >>> >> >>> >> WBR, >>> >> Ghost3D >>> >> >>> >> >>> >> >>> >> On Sep 18, 4:43 pm, Fabien Potencier <fabien.potenc...@symfony- >>> >> project.com> wrote: >>> >> > You say that symfony became too complicated, which implies it was >>> not >>> >> > before. >>> >> > >>> >> > Can you give us some examples of what became more complicated? >>> That >>> >> will >>> >> > help us improve the framework. >>> >> > >>> >> > For instance, we have less and less configuration files. Since >>> 1.0, >>> we >>> >> > removed a lot of them, and removed some parameters also. >>> >> > >>> >> > Thanks, >>> >> > Fabien >>> >> > >>> >> > -- >>> >> > Fabien Potencier >>> >> > Sensio CEO - symfony lead developer >>> >> > sensiolabs.com | symfony-project.org | fabien.potencier.org >>> >> > Tél: +33 1 40 99 80 80 >>> >> > >>> >> > bghost wrote: >>> >> > >>> >> > > First, I would like to say that Symfony framework is not too >>> bad, >>> >> > > because I follow its development from the first version. But I >>> think >>> >> > > it became too complicated because it is evident exaggeration >>> >> > > with the introduction of countless parameters and configuration >>> >> > > files in order to automate all possible tasks. This entails that >>> the >>> >> > > programmer spends more time dealing with the Symfony framework >>> >> > > than with the real problem. >>> >> > >>> >> > > P.S. I did nothing special but just followed the Jobeet >>> tutorial. >>> >> > >>> >> > > WBR, >>> >> > > Ghost3D >>> >> > >>> >> > > On Sep 18, 4:24 pm, Sid Bachtiar <sid.bacht...@gmail.com> wrote: >>> >> > >>> It is necessary to invest so much effort to do a relatively >>> simple >>> >> > >>> application. >>> >> > >> If you're just learning Symfony, then yes of course you'll >>> find it >>> >> too >>> >> > >> much effort. This is true with any other framework/technology. >>> >> > >>> >> > >> But for those of us who have invested our time in Symfony, we >>> find >>> >> > >> great leverage in using Symfony. >>> >> > >>> >> > >> So what is the relatively simple application you're trying to >>> >> build? >>> >> > >>> >> > >> On Sat, Sep 19, 2009 at 1:58 AM, bghost <bggho...@gmail.com> >>> wrote: >>> >> > >>> >> > >>> It is necessary to invest so much effort to do a relatively >>> simple >>> >> > >>> application. >>> >> > >>> Productivity and profitability of such work is very >>> questionable. >>> >> > >>> So, Symfony - Goodbye >>> >> > >> -- >>> >> > >> Blue Horn Ltd - System Developmenthttp://bluehorn.co.nz >>> >> > >>> >> >>> > >>> > >>> >>> >>> -- >>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >>> >>> >> >>> >> >> >> -- >> Sidney G B Ferreira >> Desenvolvedor Web >> >> > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
