Daniel, your post could serve as a very basic explanation of Symfony to newcomers? Do you think you could re-write this and fix some of the grammar? Post it on a blog somewhere and I'll link to it, and maybe others, and maybe some of the bigger Symfony blogs, like Symfony Nerds, will link to it. It could be worthwhile for some.
On Sep 19, 10:01 am, Daniel Echalar <[email protected]> wrote: > Hi i'm studing and i'm newer, > well, one year ago i was trying to learn symfony by my way (well in those > times without internet), i could not do the hello world jaja , so i leave > symfony. now i need to finish a web system until 31 of December and alone. > two months ago i started to write the code of my application, my > abstractions were fine, my code were fine, but it took a long time, one > entire week, and nothing to see (no forms, or just a hello world), as i'm > fighting against the clock, and fortunately i remembered symfony (hoh the > damn symfony) this thing that is to dificult to learn XD but all people says > that it save a lot of time, so i thought , "well if i want to end until > December would have to lear the framework", so i started to read from > symfony website, and then started with jobeet. Ho, let me say that jobeet is > great , but after the some days it becomes boring, because, you read, copy > and paste, and then you run!, the best you can expect is that some error > occurs,then you need to realy re-read, and surf around the code, and you > finally are understanding the "framework". So i decided that if i continued > following with the bojeet tutorial i will become in a good copy-pastetor, so > i started my own mini-projects and leave the jobeet, and then the real > learning started. Now i'm happy, because i learned good programming > practices, i understand the folders structure, and i now where should i go > to fix something, and what to do for increase my application, the problem of > the sf start with many tasks i have solved by file with little notes, if it > is useful for somebody : > > Installation notes symfony project > ========================================= > > 1.-create folder named project > 2 .- create folders / lib / vendor / symfony / / within this symfony symfony > decompressed > 3 .- chekar if our server is fit through rootProyecto / lib / vendor / > symfony / data / bin / check_configuration.php, command line and browser. if > everything ok delete the check_configuration.php > 4 .- php lib \ vendor \ symfony \ data \ bin \ symfony-V, pa see if > improperly installed. OK FYMFONY INSTALLED. > BUILDING PROJECT > 5.-php lib \ vendor \ symfony \ data \ bin \ symfony generate: project > NombrProyecto > > 6.-copy / lib / vendor / symfony / data / bin / symfony.bat to project root > folder > BUILDING APPLICATIONS > 7.-symfony generate: app - escaping-strategy = on - csrf UniqueSecret > frontend-secret = (could be any other application, by convention for the > purpose MVC is a frontend > THE ROUTE > 8 .- changes in config / ProjectConfiguration.class.php line > require_once '/ > Users/fabien/work/symfony/dev/1.2/lib/autoload/sfCoreAutoload.class.php'; by > > require_once dirname (__FILE__ ).'/../ lib / vendor / symfony / lib / > autoload / sfCoreAutoload.class.php '; > Your project becomes portable change absolute path to relative > WEB SERVER CONFIGURATION > 9 .- Paste the following in / apache / conf / httpd.conf > > # Be sure to only have this line once in your configuration > NameVirtualHost 127.0.0.1:8082 <- listening port number > > # This is the configuration for NameProject > Listen 127.0.0.1:8082 <- listening port number > > <VirtualHost 127.0.0.1:8082> <- listening port number > DocumentRoot "" > DirectoryIndex index.php > <Directory "c:\sf\nameProject\web"> > AllowOverride All > Allow from All > </ Directory> > > Alias / sf "c: \ sf\ nameProject \ lib \ vendor \ symfony \ data \ web \ > sf" > <Directory "c:\sf\nameProject\lib\vendor\symfony\data\web\sf"> > AllowOverride All > Allow from All > </ Directory> > </ VirtualHost> > > save file, and restart apache > > 10.-creates a folder for your user stories and write in the gun ali file. > histories.txt > 11.-Reliz the data schema based on the stories. > 12 .- get an ER diagram > DATABASE > 13.-Diagram in config / schema.yml > CREATE DATABASE > 14.-mysqladmin-p create uroot-projectName > 15.-we tell symfony to use Db: symfony configure: database "mysql: host = > localhost, dbname = projectName" root mysecret > 16.-build the sqls of the tables: symfony propel: build-sql > 17.-run the sql script for the table ipmortar db: symfony propel: insert-sql > > 17 .- perform object mapping through the ORM (Propel): symfony propel: > build-model > 18 .- construct all homework: symfony propel: build-all - no-confirmation > 19 .- clean the cache: symfony cc > INTRODUCTION OF DATA > 20 .- we publish data to insert in / data / fixtures / archivos.yml > 21 .- enter the data: symfony propel: data-load > Creating modules. is now visible through web > 22 .- symfony propel: generate-module - with-show - non-verbose-templates > appname NombreMOdulo model. eg > symfony propel: generate-module - with-show - non-verbose-templates > frontend publication BlogPublicacion > > 23 .- __toString functions create () for each model class > ready, from now on, see APIs and tutorials > ==========finish installation notes============ > with this notes i have a project ready to increase actions in less than five > minutes. You can even do a .bat to automate the process :P. > > for the forms, i just read the froms book, it is a nice book. > the definitive guide is fine, but is hard to hard all, jeje. just little > parts > > now i'm finishing my first sf project, and it looks and works great, i have > added new functionalities and also modified the DB, and it still working > fine. soon i will deploy it, and then with a real experience , i will start > the real project that i must finish until december. jaj It was a real risk!! > to learn symfony, because now i have less time (one month less), but even > now , with a lot of questions and few knoledge about the many and many > features of symfony, i can produce software. and that's great! > > of course nothing is perfect, > > my feedback is: > > - the php documentation has a lot of examples(eg: for every function), > and that is really nice and useful > - maybe a specializated guide (like the forms book) for every > subframework.(please one of routing, and other that enable one to make or > generate css files XD ok it is a work of graphics designers, but symfony > generates lot of html code, and is hard to write a css file, for example to > know some 'Id' i need to read the generated code first) > - graphics, do more graphics showing the structures, configuration files > etc. you know, reading 10%, watching 30%, and doing 60% , watching is not > too negligible. > > So for me, symfony is a good way to start to do good software, fast, yes it > has a lot of configuration files, but if a parameter saves me one day of > work, i prefer to learn how the paremeter works, ask the list, read > somethings, and then use it. > > well, it is just my personal experience, hope to help the project. > and yes, i need to study english grammar XD. thanks > > 2009/9/19 Alexandru-Emil Lupu <[email protected]> > > > > > Well the symfony plugins part is the maintainer / creator job to keep it > > updated. But as there is no motivational thing involved (money or need to > > use it in sf 1.2 or something else that don't cross my mind atm ), i do not > > think the maintainer will do it. Instead, you might create an account on SF > > website, and become contributor to desired plugin, and create a sf1.2 > > compatible version. This way, you'll know that there is a SF1.2 plugin > > available. > > Instead of > > sfShoppingCartPlugin<http://www.symfony-project.org/plugins/sfShoppingCartPlugin>, > > you might wanna check sfShop project (google it). It has a "shoping cart" > > plugin and is written in 1.2 (if i recall right). > > > Alecs > > > On Sat, Sep 19, 2009 at 11:07 AM, mini_alexander <[email protected]>wrote: > > >> Symfony has the best documentation which I have ever seen. Jobeet > >> tutorial is very long but in this tutorial is almost everything - all > >> important things. > >> For me the worst thing in Symfony are plugins. Many good plugins are > >> old - for example shopping cart: > >>http://www.symfony-project.org/plugins/sfShoppingCartPlugin > >> This shopping cart is for symfony 1.0 and we now have symfony 1.2 and > >> soon 1.3. And there is many that plugins. I would like to see plugins > >> in compatybile version with the newest version of symfony. > > >> On 19 Wrz, 07:10, Lukas Kahwe Smith <[email protected]> wrote: > >> > On 19.09.2009, at 06:36, Jake Barnes <[email protected]> wrote: > > >> > > On Sep 18, 3:36 pm, Lukas Kahwe Smith <[email protected]> wrote: > >> > >> On 18.09.2009, at 21:27, bghost wrote: > > >> > >>> I think that the attempt of putting the entire WEB form within the > >> > >>> class > >> > >>> only unnecessarily complicate such a simple thing such is form > >> > >>> handling. > >> > >>> That's just forcing WEB developers to learn how to make simple > >> > >>> things > >> > >>> on the complicated way. > > >> > >> i think this is a valid criticism. there is a clear shift away from > >> > >> having just some html/css/js guru do the templates back in symfony > >> > >> 1.0 > >> > >> towards requiring a symfony expert to also handle the templates, but > >> > >> that person lacks the html/css/js guru knowhow. the pay off is > >> > >> however > >> > >> that a symfony expert can now do a lot more if he just sits down with > >> > >> the html/css/js guru to create the required widgets in pair > >> > >> programming. the quality of the site should also increase since reuse > >> > >> is done more on the widget side of things but more importantly you > >> > >> start to bring everything data related together in the models, so you > >> > >> have a single definitive source. > > >> > >> so what does it all mean? teach your symfony experts some more html/ > >> > >> css/js, teach your html/css/js guru some symfony .. or better yet .. > >> > >> facilitate paired programming .. and you should be off producing high > >> > >> quality more maintainable sites in less time .. but the old workflow > >> > >> of clear work separation isnt going to cut it anymore. > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
