Events/PluginDevsDay20081108: Plugin_Developers_Day_abridged_#symfony_2008-11-08.log

**** BEGIN LOGGING AT Sat Nov 08 06:53:29 2008

Nov 08 06:53:29 *   Now talking on #symfony
Nov 08 06:53:29 *   Topic for #symfony is: Welcome to #symfony | Stable: sf1.1 | sf1.2 in beta now | Site: http://www.symfony-project.org | Docs: http://www.symfony-project.org/doc/ | Blog: http://www.symfony-project.org/blog/ | Help also available on the mailing list: http://www.symfony-project.org/community | This channel is logged, please use #symfony-off for offtopic chat
Nov 08 06:53:29 *   Topic for #symfony set by fabpot at Sat Nov 01 19:21:18 2008
Nov 08 06:53:29 *   #symfony :http://www.symfony-project.com/

Nov 08 14:53:32 <kriswallsmith> SecureSymfony: hello -- i'll be here all day, so hopefully my session will serve as a transcript
Nov 08 14:58:19 <annis> so, I got sf12 setup *grins*
Nov 08 14:59:03 <kriswallsmith> if you're here for the plugin day, please take a look at the latest blog article
Nov 08 14:59:05 <kriswallsmith> http://www.symfony-project.org/blog/2008/10/22/plugin-developers-day
Nov 08 14:59:22 <kriswallsmith> oops... http://www.symfony-project.org/blog/2008/11/08/additional-tasks-to-streamline-your-workflow
Nov 08 15:01:13 <Garfield-fr>   kriswallsmith: http://trac.symfony-project.org/ticket/4868
Nov 08 15:02:36 <kriswallsmith> Garfield-fr: this works for me by running "export SYMFONY=/path/to/symfony/lib"
Nov 08 15:02:50 <kriswallsmith> Garfield-fr: i haven't tried that on windows yet though
Nov 08 15:02:59 <kriswallsmith> Garfield-fr: the technique may need adjusting
Nov 08 15:03:11 <Garfield-fr>   Not good solution because i have 3 versions on my laptop
Nov 08 15:03:23 <SecureSymfony> Garfield : SET SYMFONY
Nov 08 15:03:56 <SecureSymfony> Garfield-fr : You can set it in your APACHE
Nov 08 15:04:41 <Garfield-fr>   For basic user, this is not a good idea
Nov 08 15:04:55 <kriswallsmith> the first "session" lasts for two hours -- "Creating and releasing a plugin"
Nov 08 15:05:40 <kriswallsmith> before we get into that i'd like to chat a bit about when it's a good time to create a plugin
Nov 08 15:06:39 <kriswallsmith> i personally am creating many more plugins than i'm releasing to the community
Nov 08 15:07:18 <kriswallsmith> working with plugins more as packages of what i reuse between projects
Nov 08 15:07:45 <kriswallsmith> is anyone else working like this?
Nov 08 15:07:54 <kjaer_>    Yes.
Nov 08 15:07:54 <klemens_u> yes, I do
Nov 08 15:07:56 <fabpot>    yep, a lot
Nov 08 15:08:01 <nervo> also
Nov 08 15:08:11 <fabpot>    I never use the modules directory of the apps
Nov 08 15:08:15 <fabpot>    everything in a plugin
Nov 08 15:08:20 <pcahard>   I have never share my plugins, but I will
Nov 08 15:08:21 <fabpot>    or plugins for that matter
Nov 08 15:08:24 <klemens_u> especiall for reusable parts on multiple projects
Nov 08 15:08:34 <nervo> i also use plugins when a functionnal process need to shqre elements in many different places
Nov 08 15:08:37 <klemens_u> fabpot: same for me
Nov 08 15:08:39 <fabpot>    klemens_u: even without sharing things between projects
Nov 08 15:08:50 <fabpot>    it is a nice way to organize your projects
Nov 08 15:08:54 <klemens_u> pcahard: thats my idea for today as well
Nov 08 15:09:00 <kriswallsmith> yes, i think it's an excellent workflow
Nov 08 15:09:01 <Henrik|away>   kriswallsmith: yes a good idea, especially when you have more websites who share functionality and not design, ex. the plugin modules can be overwritten in the app module template folder
Nov 08 15:09:34 <kriswallsmith> so we are trying to streamline this for everyone with some new tasks in the sfTaskExtraPlugin
Nov 08 15:09:35 <quickdev>  kriswallsmith, I'm working like that. Have many unreleased plugins shared between my projects, too.
Nov 08 15:09:39 <digitalbase>   fabien told something on the symfony camp that for most applications he groups functionality into plugins, instead of putting everything in the application
Nov 08 15:09:55 <Henrik|away>   fabpot: nope that way you are using the plugin dir as a modules directory imo
Nov 08 15:10:01 <Nebelmann> digitalbase: that's what he just said :)
Nov 08 15:10:13 <digitalbase>   yeah, and that's what i am confirming :)
Nov 08 15:10:23 <kriswallsmith> there are only a few in there right now, but it will grow to ease some of the more cumbersome parts of this process
Nov 08 15:10:26 <nervo> it seems that we all undestand well the concept of "plugin" :)
Nov 08 15:10:33 <fabpot>    Henrik|away: not really, this way a plugin can nicely package the model, modules, libs, tasks, ...
Nov 08 15:11:13 <digitalbase>   one thing would be nice to talk about ( a downside of using plugins for grouped functionality) is using foreign keys between different schema.xmls
Nov 08 15:11:15 <Henrik|away>   yes but still if you are not gonna share it someway or anothen then i breaks the directory structure and you are just changing the directory structure
Nov 08 15:11:27 <klemens_u> kris: can you give a short introduction on the features of the sfTaskExtraPlugin please?
Nov 08 15:11:33 <Nebelmann> but why put everything in plugins if the business rules can't be applied to other apps?
Nov 08 15:11:39 <kriswallsmith> digitalbase: i'll make a note
Nov 08 15:11:48 <Henrik|away>   Nebelmann: my point exactly
Nov 08 15:11:58 <hal>   digitalbase, yes, that is something that I want to know about
Nov 08 15:12:16 <lukaswoj>  digitalbase: yea, me too
Nov 08 15:12:24 <klemens_u> digitalbase: is this a propel specific problem? I think so because it works well in doctrine
Nov 08 15:13:26 <digitalbase>   i think so, we'll talk about that later, because there are some workarounds, but i'll leave it up to kriswallsmith to start that discussion
Nov 08 15:13:33 <hal>   to be clear, digitalbase, are you also talking about , dependencies on other plugins, and making the new plugin work regardless of whether a specific plugin is installed?  Let me give an example...
Nov 08 15:13:33 <SecureSymfony> Klemens_u: there is a new blog of sfTaskExtraPlugin : http://www.symfony-project.org/blog/2008/11/08/additional-tasks-to-streamline-your-workflow
Nov 08 15:13:38 <klemens_u> kriswallsmith: taking notes is good idea. I think we need to focus on one theme at a time, or its gonna... (140 people!)
Nov 08 15:14:17 <kriswallsmith> the latest article in the plugins tag give a good introduction to the new tasks
Nov 08 15:14:26 <kriswallsmith> http://www.symfony-project.org/blog/2008/11/08/additional-tasks-to-streamline-your-workflow
Nov 08 15:14:33 <digitalbase>   hal, just linking a foreign key to another plugin. For example you create a NewsPlugin, in newsitem you want to define a FK to sfGuardUser.id. This will fail when building the model
Nov 08 15:15:07 <hal>   digitalbase, say you built a forum plugin, and you have a table with a createdby_user column which is a FK to the sfGuardUser table.  How do you make your plugin easily work with another user-management plugin?  (maybe the user already has his own custom user-management or auth module built into the app_
Nov 08 15:15:29 <digitalbase>   kriswallsmith, any thoughts/ideas on porting this plugin to 1.1 too ?
Nov 08 15:16:02 <digitalbase>   hal, i personally don't think this is something we should get into detail now. I am sure we can talk about this later today
Nov 08 15:16:08 <annis> you'd have to make that a config variable (user_id_FK_table.user_id_FK_name)
Nov 08 15:16:17 <Nebelmann> fabpot: I understand why you only use plugins, but then what can the apps/modules dir be used for?
Nov 08 15:16:23 <SecureSymfony> hal: This should be discuss later
Nov 08 15:16:24 <kriswallsmith> i need suggestions for a new plugin we can talk through the creation of
Nov 08 15:16:28 <kriswallsmith> any ideas?
Nov 08 15:16:49 <fabpot>    Nebelmann: it is just another way to code. Both have advantages
Nov 08 15:16:56 <digitalbase>   kriswallsmith, with or without the reference to a "foreign" schema.xml ?
Nov 08 15:17:06 <Henrik|away>   kriswallsmith: a faker like plugin to generate test data
Nov 08 15:17:09 <Henrik|away>   that are realistiv
Nov 08 15:17:12 <hal>   Nebelmann, I second that question - what would you leave in the app? 
Nov 08 15:17:20 <Henrik|away>   mayb inspired by Ruby Faker gem
Nov 08 15:17:29 <kriswallsmith> is everyone familiar with sfGuardPlugin?
Nov 08 15:17:29 <jamiel>    I think the apps/modules directory will always be neccessary, but I like the idea of packaging reusable components in plugins
Nov 08 15:17:50 <hal>   kriswallsmith, yes
Nov 08 15:17:51 <fabpot>    hal: app.yml and general settings, that's all
Nov 08 15:17:51 <digitalbase>   i think we should keep it simpler. maybe make a sfNews plugin or something ?
Nov 08 15:17:57 <quickdev>  kriswallsmith, I would have a plugin idea
Nov 08 15:18:03 <hal>   fabpot, ok, thank you 
Nov 08 15:18:08 <Nebelmann> but it's not easy to think of what *could* be reused in another project...
Nov 08 15:18:11 <SecureSymfony> Please, can we stay on track... Those are good questions, that we'll talk later!
Nov 08 15:18:22 <annis> kriswallsmith: building manageable navigations
Nov 08 15:19:00 <annis> but I'm familiar with sfGuardPlugin (how about adding the ability to explicitly removing privileges from users/groups?)
Nov 08 15:19:05 <digitalbase>   guys, this plugin will be used as a reference, it will not be a fully featured plugin, lets keep it simple
Nov 08 15:19:15 <quickdev>  KRISWALLSMITH, atm I'm trying to create a plugin for my test environment. The plugin should be able to load and save various 'scenarios' for application testing. For example "User is registered" or "User A is in State xy". To test some things in those situations.
Nov 08 15:19:16 <hal>   Whatever example app you build, please ensure it has multiple tables, with a mix of relations (ie 1-2-m and m2m
Nov 08 15:19:41 <KRISWALLSMITH> since it's an excellent example that we're all familiar with, let's talk through how we would write sfGuardPlugin if it didn't already exist
Nov 08 15:19:51 <annis> cool
Nov 08 15:20:00 <hal>   KRISWALLSMITH, ok
Nov 08 15:20:07 <digitalbase>   my suggestions : sfNewsPlugin, sfGuardSignupPlugin, sfGuardUserProfilePlugin
Nov 08 15:20:17 <hal>   KRISWALLSMITH, using doctrine or propel?
Nov 08 15:20:18 <pacogliss> is it possible to build a whole APP as a plugin ? (not a module or less)
Nov 08 15:20:34 <[MA]Pascal>    KRISWALLSMITH, with admin gen 1.2 compatability :)
Nov 08 15:20:35 <annis> see, two sfGuard things in there! (@digitalbase)
Nov 08 15:20:50 <KRISWALLSMITH> i am not on the doctrine bandwagon yet, so let's stick to propel for this first example
Nov 08 15:21:02 <SecureSymfony> Kris : Nice!
Nov 08 15:21:02 <annis> good, me too
Nov 08 15:21:20 <hal>   KRISWALLSMITH, be careful - the doctrine bandwagon will leave without you!!  ;-)
Nov 08 15:21:27 <KRISWALLSMITH> first -- since this is a propel plugin -- the name is not quite right
Nov 08 15:21:33 <digitalbase>   hal : -)
Nov 08 15:21:45 <Nebelmann> is a plugin some kind of app which can be embedded in any project?
Nov 08 15:21:50 <KRISWALLSMITH> if you use an ORM, include its name in your plugin's title
Nov 08 15:21:56 <annis> So, Kris... can we code along you? (sf1.2 sandbox?)
Nov 08 15:21:57 <hal>   Nebelmann, yes
Nov 08 15:22:38 <Nebelmann> so why should we package everything in an app if it's only designed for one project?
Nov 08 15:22:40 <annis> everyone, please stop talking and let Kris take the lead. :)
Nov 08 15:23:13 <Nebelmann> /app/plugin
Nov 08 15:23:25 <KRISWALLSMITH> so we'll call this plugin "myPropelGuardPlugin" ... agreed?
Nov 08 15:23:31 <hal>   Nebelmann, the only part worth putting into a plugin are parts that are useful in other apps
Nov 08 15:23:57 <digitalbase>   agreed
Nov 08 15:24:01 <KirilAngov>    ok
Nov 08 15:24:09 <SecureSymfony> Nebelmann : It's more a module that a complet app...  Usually.
Nov 08 15:24:34 <jamiel>    KRISWALLSMITH: If we were going to release this to the world later, would it be sfPropelGuardPlugin ?
Nov 08 15:24:51 <jamiel>    rather than my ?
Nov 08 15:24:58 <Nebelmann> jamiel: it's just an example...
Nov 08 15:25:06 <Nebelmann> I don't think it'll be released
Nov 08 15:25:13 <KRISWALLSMITH> yes, i'm using "my" for the purpose of this example
Nov 08 15:25:17 <Nebelmann> as sfGuardPlugin is already a good plugin
Nov 08 15:25:25 <KRISWALLSMITH> to avoid confusion
Nov 08 15:25:29 <jamiel>    I know ... I mean, is sf a requirement for plugins ? because there are some with different prefixes in the repo
Nov 08 15:25:42 <KRISWALLSMITH> anyway... i have a clean copy of the latest symfony 1.2 development checked using Subversion
Nov 08 15:25:54 <JPhilip>   Plugins now have a a Doctrine and Propel version, can we write plugins that are used for both like Symfony where a new data access layer could be added later?
Nov 08 15:26:46 <KRISWALLSMITH> so to create a new project on my mac, i open terminal and enter...
Nov 08 15:26:51 <KRISWALLSMITH> cd Sites
Nov 08 15:27:12 <KRISWALLSMITH> mkdir my_plugin_sandbox
Nov 08 15:27:21 <KRISWALLSMITH> cd my_plugin_sandbox
Nov 08 15:27:45 <KRISWALLSMITH> ~/Sites/symfony/1.2/data/bin/symfony init-project my_plugin_sandbox
Nov 08 15:28:09 <KRISWALLSMITH> i'll give folks a minute to do that...
Nov 08 15:29:47 <hal>   KirilAngov, I haven't used the sandbox before - is it fully self-contained
Nov 08 15:29:48 <hal>   ?
Nov 08 15:30:01 <hal>   KRISWALLSMITH, sorry, that was to you!
Nov 08 15:30:17 <annis> well, that doesn't work so well, since I only downloaded the sandbox from the site and don't have the latest svn version
Nov 08 15:30:19 <KRISWALLSMITH> next step is to install the sfTaskExtraPlugin
Nov 08 15:30:20 <hal>   KRISWALLSMITH, so I can run that alongside my other installations, and it won't affect them?
Nov 08 15:30:46 <annis> yes, you can
Nov 08 15:30:50 <jamiel>    @hal: this "sandbox" is just a fresh 1.2 project ..
Nov 08 15:30:56 <KRISWALLSMITH> ./symfony plugin:install sfTaskExtraPlugin --release=0.0.1 --stability=alpha
Nov 08 15:30:56 <annis> keep going Kris
Nov 08 15:31:21 <hal>   what is the svn url of the sandbox install?
Nov 08 15:31:38 <jamiel>    hal, just grab the latest 1.2 branch
Nov 08 15:31:44 <KRISWALLSMITH> the plugin's still an infant -- 0.0.1-alpha :)
Nov 08 15:32:36 <annis> damnit, I only have php 5.2.3 and not 5.2.4 :(
Nov 08 15:32:56 <pcahard>   about installation of plugins any solution for specify the release of symfony in argument than the release of the plugin ?
Nov 08 15:33:01 <KRISWALLSMITH> to step back -- you can checkout the symfony 1.2 branch where i have it (above) like so...
Nov 08 15:33:06 <KRISWALLSMITH> mkdir ~/Sites/symfony
Nov 08 15:33:09 <KRISWALLSMITH> svn co http://svn.symfony-project.com/branches/1.2 ~/Sites/symfony
Nov 08 15:33:54 <KRISWALLSMITH> do people have the sfTaskExtraPlugin installed?
Nov 08 15:34:02 <jamiel>    Yup
Nov 08 15:34:28 <lukaswoj>  me too
Nov 08 15:34:33 <KRISWALLSMITH> ./symfony list generate
Nov 08 15:34:38 <hal>   KRISWALLSMITH, nope - what's the url?
Nov 08 15:34:46 <JPhilip>   not yet
Nov 08 15:34:55 <annis> not yet
Nov 08 15:35:01 <KRISWALLSMITH> hal: ./symfony plugin:install sfTaskExtraPlugin --release=0.0.1 --stability=alpha
Nov 08 15:35:25 <hal>   KRISWALLSMITH, it would have been good to have a list of system requirements in the announcement, so that we could all have set our systems up before it started
Nov 08 15:35:26 <KRISWALLSMITH> hal: or svn co http://svn.symfony-project.com/plugins/sfTaskExtraPlugin/trunk plugins/sfTaskExtraPlugin
Nov 08 15:36:37 <KRISWALLSMITH> ok, let's generate our plugin now
Nov 08 15:36:58 <KRISWALLSMITH> ./symfony generate:plugin myPropelGuardPlugin
Nov 08 15:38:02 <KRISWALLSMITH> just found a bug in the pear version of the plugin -- you'll have to manually create your plugin's /lib folder
Nov 08 15:40:34 <KRISWALLSMITH> Nebelmann: correct
Nov 08 15:41:41 <KRISWALLSMITH> one thing we can do here, for instance, is check to make sure the propel plugin is enabled
Nov 08 15:44:10 <digitalbase>   could we briefly make a list of things that are considered 'good usage' in the configuration class ?
Nov 08 15:44:16 <KRISWALLSMITH> this can be done in the ->initialize() method by trying to call ->getPluginConfiguration('sfPropelPlugin')
Nov 08 15:46:33 <KRISWALLSMITH> the plugin configuration class replaces what was config.php in < 1.2
Nov 08 15:46:40 <KRISWALLSMITH> so this is where you'll connect to events ($this->dispatcher)
Nov 08 15:46:42 <KRISWALLSMITH> or register propel behaviors -- sfPropelBehavior::register(Methods|Hooks)
Nov 08 15:47:06 <digitalbase>   so : connect to events, checking/enabling other plugins, registering behavious, check for certain dependancies
Nov 08 15:47:22 <KRISWALLSMITH> digitalbase: right.
Nov 08 15:47:42 <KRISWALLSMITH> that list may grow as more devs begin to use these classes though
Nov 08 15:47:55 <JPhilip>   Can we create an ORM independent plugin instead of a propel specific? and add data access layers later.
Nov 08 15:48:11 <KRISWALLSMITH> fabpot: do you want to add to what belongs in a configuration initialization?
Nov 08 15:48:36 <digitalbase>   JPhilip, i don't think you can, if you really want ORM independancy (propel/doctrine) you could make a dbFinder plugin
Nov 08 15:49:15 <jamiel>    Maybe adding conditional routes can go in there?
Nov 08 15:49:23 <digitalbase>   no :)
Nov 08 15:49:28 <JPhilip>   It is just a pain to have 2 versions of each plugin that does data access
Nov 08 15:49:55 <KRISWALLSMITH> jamiel: yes, adding routes is done using $this->dispatcher->connect()
Nov 08 15:50:08 <digitalbase>   routing rules should go in : myPropelGuardPluginRouting.class.php
Nov 08 15:50:33 <digitalbase>   you only register those in the config
Nov 08 15:52:31 <KRISWALLSMITH> so our config class looks something like this: http://www.hashbin.com/td2
Nov 08 15:53:20 <KRISWALLSMITH> there's plenty more that can be done there, but let's move on for now
Nov 08 15:54:24 <KRISWALLSMITH> should we take a look at the test directory next, or start building the plugin?
Nov 08 15:54:44 <lukaswoj>  test first imo :)
Nov 08 15:55:52 <jamiel>    Yes please, I have two questions regarding the test directory
Nov 08 15:56:11 <jamiel>    Unless it's going to be covered later in functional testing your plugin
Nov 08 15:56:31 <Nebelmann> KRISWALLSMITH: I have problems accessing hashbin...
Nov 08 15:56:47 <KRISWALLSMITH> let's write a unit test to verify the exception we've added to the configuration class
Nov 08 15:57:45 <Nebelmann> well, www.hashbin.com works, but with /td2 it doesn't :)
Nov 08 15:58:13 <lukaswoj>  should'nt we add test first ? ;)
Nov 08 15:58:35 <KRISWALLSMITH> i've created a /test/unit/configurationTest.php in myPropelGuardPlugin: http://pastie.org/310145
Nov 08 15:59:35 <klemens_u> KRISWALLSMITH: @testing plugin: Bernhard Schussek and I would like to talk a bit more about this topic
Nov 08 15:59:49 <klemens_u> Can you take a note on that?
Nov 08 16:00:15 <KRISWALLSMITH> klemens_u: ok -- you guys can say some about testing plugins after we write this test?
Nov 08 16:00:20 <klemens_u> We can do this later
Nov 08 16:00:38 <klemens_u> It's more like questions not a speech :-)
Nov 08 16:01:00 <KRISWALLSMITH> klemens_u: after we write this test
Nov 08 16:05:28 <KRISWALLSMITH> here's the unit test i wrote -- http://pastie.org/310145
Nov 08 16:05:57 <KRISWALLSMITH> does this make sense to everyone?
Nov 08 16:06:06 <lukaswoj>  kris: where You put that code ?
Nov 08 16:06:45 <KRISWALLSMITH> that test is in /plugins/myPropelGuardPlugin/test/unit/configurationTest.php
Nov 08 16:07:15 <KRISWALLSMITH> you should be able to run this test successfully
Nov 08 16:07:29 <KRISWALLSMITH> php plugins/myPropelGuardPlugin/test/unit/configurationTest.php
Nov 08 16:07:43 <KRISWALLSMITH> or by using the harness provided
Nov 08 16:07:55 <KRISWALLSMITH> php plugins/myPropelGuardPlugin/test/bin/prove.php
Nov 08 16:08:10 <KRISWALLSMITH> any questions?
Nov 08 16:09:26 <JPhilip>   I get You must register some test files before running them!
Nov 08 16:09:56 <jamiel>    KRISWALLSMITH: Looks like we need to do your export SYMFONY=/path/to/1.2 ; trick
Nov 08 16:10:03 <KRISWALLSMITH> JPhilip: where did you add the pastie test?
Nov 08 16:10:07 <KRISWALLSMITH> jamiel: correct
Nov 08 16:10:35 <JPhilip>   plugins/myPropelGuardPlugin/test/unit
Nov 08 16:11:52 <KRISWALLSMITH> JPhilip: i'm not sure -- it's working for me
Nov 08 16:12:13 <JPhilip>   The command I ran is: symfony test:unit maybe this is wrong for a plugin
Nov 08 16:12:37 <KRISWALLSMITH> JPhilip: that command doesn't include the plugin tests
Nov 08 16:13:16 <KRISWALLSMITH> JPhilip: perhaps later... but not at this point
Nov 08 16:13:28 <klemens_u> JPhilip: that's one point we'd like to talk about later on.
Nov 08 16:13:44 <KRISWALLSMITH> you need to either run the test or the harness directly
Nov 08 16:14:00 <klemens_u> I've created a wiki entry about plugin testing, where I took some notes on what features would be nice:
Nov 08 16:14:02 <klemens_u> http://trac.symfony-project.org/wiki/PluginTesting
Nov 08 16:14:04 <KRISWALLSMITH> (the harness being bin/prove.php)
Nov 08 16:14:53 <SecureSymfony> Kris : plugin:runtest  should be add to sfTaskExtraPlugin
Nov 08 16:15:22 <KRISWALLSMITH> klemens_u: this looks like part of the roadmap for sfTaskExtraPlugin (which currently exists only in my head...)
Nov 08 16:16:07 <KRISWALLSMITH> anyone still working on getting configurationTest working?
Nov 08 16:16:15 <bschussek> kris: I guess this could perfectly be added to the core though
Nov 08 16:16:17 <KRISWALLSMITH> any questions about that script?
Nov 08 16:16:44 <klemens_u> KRISWALLSMITH: please add your ideas, or tell us if they are already written anywhere
Nov 08 16:16:52 <JPhilip>   So I did not get the command to run the test!
Nov 08 16:17:17 <KRISWALLSMITH> JPhilip: there's no command at this point. you need to execute the script directly
Nov 08 16:17:35 <KRISWALLSMITH> php plugins/myPropelGuardPlugin/test/unit/configurationTest.php
Nov 08 16:18:12 <KRISWALLSMITH> klemens_u: does this wiki page sum up what you wanted to discuss, or would you like to take a few minutes now?
Nov 08 16:18:36 <klemens_u> KRISWALLSMITH: in general it sums it up.
Nov 08 16:18:53 <klemens_u> I have to say, some is already done by the sfTaskExtraPlugin.
Nov 08 16:21:15 <klemens_u> KRISWALLSMITH: what is on your roadmap for the sfTaskExtraPlugin you mentioned before
Nov 08 16:22:48 <KRISWALLSMITH> i would like to connect to command.post_command and modify new model and form classes to be easily customizable in the project -- i haven't thought that through all the way yet.
Nov 08 16:23:19 <JPhilip>   The test bootstrap does not find the Symfony libs when I run the test script directly on my config:
Nov 08 16:23:20 <JPhilip>   PHP Fatal error:  Uncaught exception 'RuntimeException' with message 'Could not find symfony core libraries.' in C:\DATA\php\sf_sandbox\plugins\myPropelGuardPlugin\test\bootstrap\unit.php:5
Nov 08 16:23:24 <JPhilip>   Stack trace:
Nov 08 16:23:28 <JPhilip>   #0 C:\DATA\php\sf_sandbox\plugins\myPropelGuardPlugin\test\unit\configurationTest.php(3): include()
Nov 08 16:23:30 <JPhilip>   #1 {main}
Nov 08 16:23:32 <JPhilip>     thrown in C:\DATA\php\sf_sandbox\plugins\myPropelGuardPlugin\test\bootstrap\unit.php on line 5
Nov 08 16:24:18 <Garfield-fr>   JPhilip: Check this: http://trac.symfony-project.org/ticket/4868
Nov 08 16:24:33 <jamiel>    JPhilip: export SYMFONY=/path ... Path to where you checked out 1.2 to
Nov 08 16:24:52 <jamiel>    Ahh, windows ...
Nov 08 16:24:54 <klemens_u> KRISWALLSMITH: and regarding plugin testing? what are your ideas on that?
Nov 08 16:24:58 <KRISWALLSMITH> klemens_u: i'm also looking at using command.post_command to run plugin tests when when test:all is run, as you suggest on the wiki
Nov 08 16:25:11 <chrisk89>  well i have some more questions about functional testing of plugins
Nov 08 16:25:17 <klemens_u> (maybe we should move to a separate irc channel?)
Nov 08 16:25:22 <chrisk89>  how to test custom tasks?
Nov 08 16:25:40 <bschussek> KRISWALLSMITH: maybe we should ask fabien, I think this functionality could well go into the core
Nov 08 16:26:23 <KRISWALLSMITH> chrisk89: take a look at http://trac.symfony-project.org/browser/plugins/sfTaskExtraPlugin/trunk/test/unit/task/generatorTasksTest.php
Nov 08 16:26:51 <JPhilip>   OK, the test passes now
Nov 08 16:27:36 <KRISWALLSMITH> chrisk89: it uses the task_extra_lime_test class defined in the plugin's bootstrap/unit.php
Nov 08 16:27:49 <KRISWALLSMITH> http://trac.symfony-project.org/browser/plugins/sfTaskExtraPlugin/trunk/test/bootstrap/unit.php#L17
Nov 08 16:28:16 <chrisk89>  KRISWALLSMITH: hm k, I'll have a look
Nov 08 16:28:20 <KRISWALLSMITH> i may move that class into /lib/test so it can be reused
Nov 08 16:28:55 <KRISWALLSMITH> we have another 30 minutes in this "session" -- let's get back to building the plugin?
Nov 08 16:29:01 <KRISWALLSMITH> unless there are outstanding questions?
Nov 08 16:30:11 <rdeeb> One question
Nov 08 16:30:14 <annis> my test is failing
Nov 08 16:30:16 <rdeeb> sorry for beeing late
Nov 08 16:30:56 <rdeeb> just installed the sfTaskExtraPlugin and can access the tasks
Nov 08 16:30:57 <annis> Failed 1/1 test scripts, 0.00% okay. 1/2 subtests failed, 50.00% okay.
Nov 08 16:31:56 <jamiel>    annis: Run the test directly to see the failure message
Nov 08 16:32:02 <jamiel>    rather than using the harness
Nov 08 16:32:27 <annis> configuration throws an exception if sfPropelPlugin is not enabled
Nov 08 16:32:40 <annis> hmm, but I followed along you guys
Nov 08 16:32:46 <jamiel>    annis: did you skip the step of creating your project config file?
Nov 08 16:33:06 <annis> ah, that was it, because hasbin/td2 didn't work
Nov 08 16:33:10 <annis> damn
Nov 08 16:34:40 <jamiel>    annis: http://pastie.org/310167
Nov 08 16:35:26 <annis> now I'm with you, thanks!
Nov 08 16:35:27 <KRISWALLSMITH> here's the schema.yml i've created: http://pastie.org/310168
Nov 08 16:37:16 <KRISWALLSMITH> does this schema make sense to everyone? it's a basic users table.
Nov 08 16:37:25 <KRISWALLSMITH> any additions? removals?
Nov 08 16:37:26 <annis> where do we put that schema? I gues it's not config/schema.yml of the project?
Nov 08 16:37:48 <KRISWALLSMITH> annis: plugins/myPropelGuardPlugin/config/schema.yml
Nov 08 16:38:22 <jamiel>    KRISWALLSMITH: Should we not namespace the classes?
Nov 08 16:38:28 <jamiel>    Or does this happeny automatically?
Nov 08 16:38:44 <KRISWALLSMITH> jamiel: good point
Nov 08 16:39:22 <KRISWALLSMITH> updated -- http://pastie.org/310168
Nov 08 16:40:06 <mosez> kriswallsmith: write table name in singular.
Nov 08 16:40:35 <KRISWALLSMITH> mosez: personal preference. i prefer plural table names.
Nov 08 16:40:51 <KRISWALLSMITH> ./symfony propel:build-model
Nov 08 16:41:09 <SecureSymfony> Kris : Same here, but be sure to set the phpName
Nov 08 16:41:44 <KRISWALLSMITH> in this schema the class phpName is myGuardUser, the table name if my_guard_users
Nov 08 16:42:07 <KRISWALLSMITH> i'm using the new schema syntax introduced in symfony 1.1
Nov 08 16:42:27 <annis> cool, looks like "sf cc" can be left out starting with 1.2 when building the model?
Nov 08 16:44:27 <KRISWALLSMITH> moving on... you should see propel model classes in the plugin now
Nov 08 16:45:41 <JPhilip>   I get: You must create a schema.yml or schema.xml file, even though I have schema.yml in plugins/myPropelGuardPlugin/config
Nov 08 16:47:05 <KRISWALLSMITH> these model classes, as they are now, cannot be extended in both the plugin and the project
Nov 08 16:47:10 <KRISWALLSMITH> only one or the other
Nov 08 16:47:28 <KRISWALLSMITH> to fix this, we need to add a class to the heirarchy
Nov 08 16:48:02 <KRISWALLSMITH> so BasemyGuardUser > myGuardUser becomes BasemyGuardUser > PluginmyGuardUser > myGuardUser
Nov 08 16:48:27 <JPhilip>   There is an empty schema.yml in /config
Nov 08 16:48:42 <annis> Kris: Huh? ;) What do we need to change where?
Nov 08 16:49:57 <KRISWALLSMITH> mkdir plugins/myPropelGuardPlugin/lib/model/plugin
Nov 08 16:50:20 <annis> k
Nov 08 16:50:39 <KRISWALLSMITH> (this involves a few steps and is something i'd like to automate in the sfTaskExtraPlugin)
Nov 08 16:50:48 <annis> very good
Nov 08 16:54:28 <KRISWALLSMITH> create a file plugins/myPropelGuardPlugin/lib/model/plugin/PluginmyGuardUser.php with the contents http://pastie.org/310180
Nov 08 16:55:35 <KRISWALLSMITH> and edit myGuardUser.php so it reads http://pastie.org/310182
Nov 08 16:56:29 <KRISWALLSMITH> now you can add custom logic to you plugin's model class by editing PluginmyGuardUser.php
Nov 08 16:56:46 <annis> I guess, you're trying to install a sf1.0 plugin into a sf1.1 project
Nov 08 16:57:43 <KRISWALLSMITH> and the project can add custom logic by creating a myGuardUser.php in its lib/
Nov 08 16:57:59 <KRISWALLSMITH> is this making sense to everyone?
Nov 08 16:58:16 <annis> hmm, OOP is really cool
Nov 08 16:58:26 <KRISWALLSMITH> any questions about making a plugin model class customizable in the project?
Nov 08 16:58:49 <jamiel>    KRISWALLSMITH: So the plugin author shouldn't use myGuardUser ?
Nov 08 16:58:56 <jamiel>    Only PluginmyGuardUser ?
Nov 08 16:59:06 <annis> I guess
Nov 08 16:59:11 <KRISWALLSMITH> jamiel: correct
Nov 08 16:59:26 <KRISWALLSMITH> the myGuardUser.php file in the plugin should remain an empty class
Nov 08 16:59:55 <jamiel>    But why don't the developers just extend myGuardUser themselves if they want to override it?
Nov 08 17:00:21 <jamiel>    myCustomMyGuardUser extends myGuardUser
Nov 08 17:00:53 <annis> But then why have myGuardUser.php around? If in the project there's a class that inherits from PluginmyGuardUser then everything should be golden, right?
Nov 08 17:01:06 <KRISWALLSMITH> jamiel: propel restrictions -- myGuardUserPeer::doSelect() returns instances of myGuardUser
Nov 08 17:01:41 <jamiel>    Aha
Nov 08 17:01:58 <annis> And what do we want the respective classes to return?
Nov 08 17:02:24 <annis> if that's too low-level to explain then just move on :)
Nov 08 17:02:29 <KRISWALLSMITH> annis: we include stub class so the project doesn't have to unless it needs to be customized
Nov 08 17:02:45 <annis> alright, thanks
Nov 08 17:02:59 <KRISWALLSMITH> annis: i don't understand your question -- classes don't return, methods return
Nov 08 17:03:57 <KRISWALLSMITH> ok, if there are no more questions on this point i'd like to take a 15 minute break
Nov 08 17:04:05 <annis> Kris: sorry, I know. What I meant was: What do we want doSelect return in the cases where there are these inheritance hierarchies?
Nov 08 17:05:02 <jamiel>    annis: This way it "just works" ... and if you want to extend the propel classes in your project, you do so using myGuardUser extends PluginmyGuardUser .. and Propel will return your custom class
Nov 08 17:05:08 <jamiel>    because it has the name propel expects
Nov 08 17:05:27 <annis> ah, clear now, thanks
Nov 08 17:20:13 <hal>   sorry, guys, but where is myGuardUser.php located?
Nov 08 17:20:51 <jamiel>    hal : it gets generated in plugins/myPropelGuard/lib/model
Nov 08 17:21:18 <JPhilip>   OK, I finally built the model, I did not have myPropelGuardPlugin enabled in config class.
Nov 08 17:21:52 <annis> JPhilip: Hmm, I didn't do that... and it works.
Nov 08 17:22:57 <annis> Kris: Can I have another minute? ;)
Nov 08 17:23:43 <KRISWALLSMITH> how's this format working for everyone?
Nov 08 17:24:07 <jamiel>    wb, kris ... if you are going to cover it later then ignore this, but curious as to why an entire project stub gets created in test/fixtures
Nov 08 17:24:09 <JPhilip>   I have used only Doctrine so far, looks like the propel classes are very verbose
Nov 08 17:25:15 <KRISWALLSMITH> jamiel: a plugin's test shouldn't be dependent on an external project
Nov 08 17:25:32 <hal>   could someone tell me what I have done wrong here...  http://pastie.org/310201
Nov 08 17:26:12 <KRISWALLSMITH> hal: those methods need to be called from ProjectConfiguration::setup()
Nov 08 17:26:56 <hal>   KRISWALLSMITH, so do I replace initialize with setup?
Nov 08 17:27:22 <KRISWALLSMITH> no, you need to open ProjectConfiguration.class.php to enable plugins, not the plugin configuration
Nov 08 17:27:29 <KRISWALLSMITH> ^^hal^^
Nov 08 17:27:38 <jamiel>    KRISWALLSMITH: agreed, but then when is the stub project used? Because the sf_root_dir is still the main project dir
Nov 08 17:28:06 <hal>   KRISWALLSMITH, ah, thank you!
Nov 08 17:28:19 <KRISWALLSMITH> jamiel: take a look at the plugin's test/bootstrap/functional.php file
Nov 08 17:28:40 <KRISWALLSMITH> it uses the embedded project's ProjectConfiguration class
Nov 08 17:29:35 <KRISWALLSMITH> also of note is the embedded project's ProjectConfiguration class
Nov 08 17:29:52 <KRISWALLSMITH> it's been customized to work inside the plugin
Nov 08 17:30:20 <hal>   now I have the error, InvalidArgumentException: The plugin "sfDoctrinePlugin" does not exist.
Nov 08 17:31:24 <KRISWALLSMITH> hal: you don't need to disable the doctrine plugin b/c it's disabled by default
Nov 08 17:31:35 <hal>   KRISWALLSMITH, oops, ok, thanks
Nov 08 17:32:02 <KRISWALLSMITH> ok... let's take a look at creating plugin modules
Nov 08 17:32:42 <annis> cool. I'm getting the impression there are not so many of us following around anymore, or am I mistaken?
Nov 08 17:32:49 <KRISWALLSMITH> i'm not sure
Nov 08 17:32:54 <KRISWALLSMITH> who all's with us?
Nov 08 17:33:08 <JPhilip>   I am
Nov 08 17:33:12 <annis> me
Nov 08 17:33:19 <ksn135>    me
Nov 08 17:33:22 <jamiel>    yup, following
Nov 08 17:33:32 <lukaswoj>  me too
Nov 08 17:34:11 <KRISWALLSMITH> alright - let's create a module to handle login and logout
Nov 08 17:35:07 <KRISWALLSMITH> ./symfony generate:plugin-module myPropelGuardPlugin myGuardAuth
Nov 08 17:36:05 <KRISWALLSMITH> you should see a new /modules folder in your plugin
Nov 08 17:36:23 <JPhilip>   Yes
Nov 08 17:36:40 <annis> yes
Nov 08 17:37:05 <KRISWALLSMITH> this task creates a module just like the one created by generate:module with a few exceptions
Nov 08 17:37:38 <annis> there's no templates folder
Nov 08 17:37:55 <KRISWALLSMITH> annis: yes, that's a bug with the pear package that needs to be fixed
Nov 08 17:38:03 <annis> ah, okay
Nov 08 17:38:10 <annis> shall we create it now?
Nov 08 17:38:15 <KRISWALLSMITH> annis: yes
Nov 08 17:38:22 <annis> k
Nov 08 17:38:27 <KRISWALLSMITH> the module actions class should look like this: http://pastie.org/310208
Nov 08 17:38:29 <JPhilip>   Yes there is one from trunk
Nov 08 17:39:23 <KRISWALLSMITH> this class extends BasemyGuardAuthActions rather than sfActions
Nov 08 17:39:48 <KRISWALLSMITH> this is the same technique we used on the model classes
Nov 08 17:40:38 <KRISWALLSMITH> all your plugin actions should be defined in BasemyGuardAuthActions http://pastie.org/310211
Nov 08 17:41:22 <JPhilip>   This was done in a lot of plugins, nice to see it standardized in a task
Nov 08 17:42:05 <KRISWALLSMITH> updated to include stub action methods: http://pastie.org/310211
Nov 08 17:42:52 <JPhilip>   OK
Nov 08 17:43:23 <KRISWALLSMITH> a general rule of thumb for plugin actions is to create many small methods
Nov 08 17:44:04 <annis> so they can easily be overriden :)
Nov 08 17:44:10 <bschussek> KRISWALLSMITH: just a short question - why is the $_SERVER['SYMFONY'] var required when I generate plugins with your sfTaskExtraPlugin?
Nov 08 17:44:29 <bschussek> can't you just copy the location of symfony based on the ProjectConfiguration?
Nov 08 17:45:12 <KRISWALLSMITH> possibly something like this -- http://pastie.org/310211
Nov 08 17:45:36 <KRISWALLSMITH> bschussek: no b/c we need a customized ProjectConfiguration
Nov 08 17:45:39 <annis> erm, Kris, what exactly did change between the last two pasties for the action methods?
Nov 08 17:45:40 <quickdev>  KRISWALLSMITH, btw...many ppls are following your disicussion without taking part, just for info :)
Nov 08 17:45:43 <annis> the url is the same
Nov 08 17:46:40 <bschussek> KRISWALLSMITH: I didn't mean to use the project configuration, but to use the _path_ written in the ProjectConfiguration instead of relying on $_SERVER['SYMFONY']
Nov 08 17:47:31 <bschussek> another problem I see with this solution is that I cannot use multiple versions of symfony at once
Nov 08 17:48:06 <KRISWALLSMITH> annis: yes, i've been updating the same pastie
Nov 08 17:48:18 <annis> oh, I have to check
Nov 08 17:49:30 <KRISWALLSMITH> bschussek: you're suggesting we run a regex on that file?
Nov 08 17:50:24 <JPhilip>   bschusssek: http://trac.symfony-project.org/attachment/ticket/4868/sfTaskExtraPlugin.patch
Nov 08 17:51:32 <KRISWALLSMITH> does the structure of login methods here make sense to everyone? http://pastie.org/310211
Nov 08 17:51:57 <bschussek> KRISWALLSMITH: either that, or maybe there's a different solution (maybe using Reflection on symfony classes or stuff like that)
Nov 08 17:51:58 <annis> Kris: it wasn't updating in my browser, got it now. Makes sense.
Nov 08 17:52:08 <JPhilip>   Yes, similar to what was done in the 1.0 generators
Nov 08 17:52:50 <bschussek> ah sorry, forget the stuff about Reflection :-)
Nov 08 17:53:13 <KRISWALLSMITH> using this structure you can create some basic defaults and leave the more specialized code to the application developer
Nov 08 17:53:50 <KRISWALLSMITH> for instance, the application developer may want to handle login failures differently for ajax requests
Nov 08 17:54:16 <annis> so he could override handeLoginFailure?
Nov 08 17:54:36 <KRISWALLSMITH> annis: exactly
Nov 08 17:56:26 <KRISWALLSMITH> well, this discussion falls under "Writing a customizable plugin"
Nov 08 17:57:42 <KRISWALLSMITH> ok, so we've covered model classes and modules
Nov 08 17:57:50 <KRISWALLSMITH> any questions on either of those?
Nov 08 17:58:36 <JPhilip>   Yes, can you make it clear where we put the default action code?
Nov 08 17:58:56 <KRISWALLSMITH> JPhilip: in the modules's lib/Base*Actions.class.php
Nov 08 17:59:26 <jamiel>    KRISWALLSMITH: At this point do default routes exists now as /myGuardUser/auth/login ? Or does some routing config need to happen
Nov 08 17:59:38 <annis> What belongs then in the actions.class.php?
Nov 08 18:00:01 <jamiel>    annis: Nothing, like myGuardUser in the model .. its a stub to be extended in the project
Nov 08 18:00:09 <jamiel>    Erm, my wording was bad there ..
Nov 08 18:00:14 <jamiel>    its a stub to be used until it's extended
Nov 08 18:00:19 <KRISWALLSMITH> the plugin actions.class.php should be an empty class so it can be copied into the application and customized -- same technique we used for model classes
Nov 08 18:00:29 <annis> okay
Nov 08 18:00:42 <KRISWALLSMITH> jamiel: yes, default routes include plugin modules
Nov 08 18:01:02 <KRISWALLSMITH> jamiel: although each module will need to be enabled in the project or application's settings.yml
Nov 08 18:01:14 <jamiel>    k, thanks
Nov 08 18:01:42 <JPhilip>   I am rather new to PHP, so it seems a little strange that implementation code goes in an abstract class
Nov 08 18:02:24 <annis> hmm, you're right... I know that C# doesn't allow it.
Nov 08 18:02:33 <annis> Kris, PHP does?
Nov 08 18:03:06 <FabianLange>   yes, same as java. abstract classes are templates that already contain code but need to be extended by a class that provides remaining code
Nov 08 18:03:26 <FabianLange>   the ones that do not contain implementation are called interfaces
Nov 08 18:03:27 <jamiel>    Which is exactly what is happening in this case ....
Nov 08 18:03:40 <jamiel>    So seems fine to me
Nov 08 18:03:49 <KRISWALLSMITH> let's take a look at plugins/myPropelGuardPlugin/test/functional/myGuardAuthActionsTest.php
Nov 08 18:05:37 <KRISWALLSMITH> i've added a few lines to the generated file: http://pastie.org/310220
Nov 08 18:06:22 <KRISWALLSMITH> anyone know how to fix this test?
Nov 08 18:06:28 <jamiel>    KRISWALLSMITH: Why don't you generate that second line for us automagically with generate-module? ;)
Nov 08 18:06:47 <KRISWALLSMITH> jamiel: i agree
Nov 08 18:07:31 <KRISWALLSMITH> any ideas what needs to be fixed in the action for the test to pass?
Nov 08 18:07:39 <jamiel>    KRISWALLSMITH: we need a template
Nov 08 18:07:55 <KRISWALLSMITH> jamiel: yep
Nov 08 18:08:10 <KRISWALLSMITH> add a loginSuccess.php template and the test should pass
Nov 08 18:10:07 <KRISWALLSMITH> actually, i take that back -- looks like the module needs to be enabled in the embedded project application's settings.yml
Nov 08 18:10:53 <jamiel>    KRISWALLSMITH: again, generate-module could have done that for us couldn't it?
Nov 08 18:11:07 <annis> but there's no frontend app with an settings.yml
Nov 08 18:11:15 <KRISWALLSMITH> jamiel: yes, there are a few bugs here
Nov 08 18:11:29 <annis> or do you mean to create one the plugin config dir?
Nov 08 18:11:31 <jamiel>    annis: in plugins/myGuardUser/test/fixtures/project/
Nov 08 18:12:27 <KRISWALLSMITH> paste this into your plugins/myPropelGuardPlugin/test/fixtures/project/apps/frontend/config/settings.yml http://pastie.org/310223
Nov 08 18:13:07 <KRISWALLSMITH> *now* the test should pass -- sorry about that
Nov 08 18:14:43 <KRISWALLSMITH> success?
Nov 08 18:15:00 <chrisk89>  a little question about custom tasks in a plugin and application configuration, is it recommended/forbidden that tasks modify configuration files? if you want it can be discussed later
Nov 08 18:15:35 <KRISWALLSMITH> chrisk89: there are some tasks that do (ie configure:*) but it must be done w/ care
Nov 08 18:15:35 <annis> no success
Nov 08 18:15:36 <jamiel>    KRISWALLSMITH: getting unknown strategy 1
Nov 08 18:15:47 <annis> even after clearing the cache of the embedded project
Nov 08 18:15:51 <KRISWALLSMITH> yeah, that's another bug, but the pastie has that fixed
Nov 08 18:16:03 <jamiel>    tried turning off escaping_strategy in that config you gave us but no joy
Nov 08 18:16:43 <chrisk89>  KRISWALLSMITH: thx
Nov 08 18:17:21 <KRISWALLSMITH> jamiel: what do you see now?
Nov 08 18:17:47 <jamiel>     InvalidArgumentException: Unknown strategy 1. This is using the pastie config
Nov 08 18:18:19 <KRISWALLSMITH> jamiel: http://pastie.org/310223
Nov 08 18:18:58 <TjiefTjaf> Class 'sfGuardSecurityUser' not found
Nov 08 18:18:58 <TjiefTjaf> Heil sfAutoloader
Nov 08 18:19:42 <jamiel>    Same error kris :S hmm
Nov 08 18:20:55 <annis> erm, I just checked, the embedded project doesn't regenerate the module.yml compilation...
Nov 08 18:21:04 <annis> it's missing in the config folder
Nov 08 18:21:15 <KRISWALLSMITH> you may need to clear the cache for the test project
Nov 08 18:21:16 <annis> how do I clear the cache of the embedded project?
Nov 08 18:22:10 <KRISWALLSMITH> annis: this should be handled by the bootstrap script, but for now you can run this...
Nov 08 18:22:12 <KRISWALLSMITH> ./plugins/myPropelGuardPlugin/test/fixtures/project/symfony cc
Nov 08 18:23:52 <annis> Kris: my bash just tells me, Permission denied on the symfony script
Nov 08 18:23:55 <annis> hmm...
Nov 08 18:24:01 <annis> sudo... no luck
Nov 08 18:24:12 <jamiel>    do php plugins/my..
Nov 08 18:24:14 <jamiel>    instead of ./
Nov 08 18:24:19 <jamiel>    unless u +x it
Nov 08 18:24:57 <jamiel>    Clearing cache hasn't helped, maybe just move on Kris ... look into it later
Nov 08 18:25:29 <annis> yeah, just move on, it's now telling me, it can't find the AutoLoaderWhatEver...
Nov 08 18:26:13 <KRISWALLSMITH> annis: try php plugins/myPropelGuardPlugin/test/fixtures/project/symfony cc
Nov 08 18:27:05 <annis> no luck there, same error
Nov 08 18:27:07 <JPhilip>   I give up on the function test for now, I just get too many errors
Nov 08 18:27:31 <jamiel>    Oh wait, i got it
Nov 08 18:27:44 <annis> Huh? ;)
Nov 08 18:27:58 <KRISWALLSMITH> there are some bugs in the generated code that are complicating things
Nov 08 18:28:17 <KRISWALLSMITH> i will address these for the 0.0.2 release :)
Nov 08 18:29:01 <annis> no worries, it's still alpha... but we could work with it pretty much, I wouldn't call it 0.0.1-alpha
Nov 08 18:29:03 <jamiel>    Mine passes with that pastie sorry kris :) .. I was sticking in config/settings.yml instead of apps/frontend/config/
Nov 08 18:29:25 <KRISWALLSMITH> ok
Nov 08 18:30:15 <annis> mine passes now too
Nov 08 18:30:47 <KRISWALLSMITH> let's look at the plugin:package task, take another break, then get into the 3rd session "Ad hoc coding sprints on new and existing plugins"
Nov 08 18:31:54 <KRISWALLSMITH> so let's pretend we're ready to release myPropelGuardPlugin
Nov 08 18:33:19 <KRISWALLSMITH> go ahead and run ./symfony plugin:package myPropelGuardPlugin
Nov 08 18:33:53 <KRISWALLSMITH> you should see some interactive prompts
Nov 08 18:34:23 <KRISWALLSMITH> go ahead and complete the wizard
Nov 08 18:35:01 <jamiel>    Ahh, sexy
Nov 08 18:35:44 <KRISWALLSMITH> this uses the new sfTask::ask() methods
Nov 08 18:35:57 <jamiel>    KRISWALLSMITH: Is there a corellation between our plugin version number and symfony version number?
Nov 08 18:36:11 <KRISWALLSMITH> jamiel: no, your plugin version number is up to you
Nov 08 18:36:13 <JPhilip>   Cannot package, errors in package file
Nov 08 18:36:53 <annis> use a number like 0.0.1 as the version number
Nov 08 18:36:57 <annis> that had me too
Nov 08 18:37:16 <annis> run the same again, it will only ask you what's missing or wrong
Nov 08 18:37:25 <annis> pretty sexy, I'll have to admit
Nov 08 18:37:58 <KRISWALLSMITH> right -- some of those values are added to the xml template
Nov 08 18:38:29 <KRISWALLSMITH> if you get an error in the package file you should see a package.xml.error file
Nov 08 18:38:37 <KRISWALLSMITH> take a look at that
Nov 08 18:39:04 <KRISWALLSMITH> or run pear package-validate...
Nov 08 18:39:13 <KRISWALLSMITH> cd plugins/myPropelGuardPlugin
Nov 08 18:39:17 <KRISWALLSMITH> pear package-validate
Nov 08 18:40:26 <KRISWALLSMITH> you may need to mv package.xml.error package.xml before running package-validate
Nov 08 18:40:38 <KRISWALLSMITH> but that command should show you more information about what's wrong
Nov 08 18:41:24 <annis> maybe print out the package.xml.error?
Nov 08 18:41:44 <annis> And restart the process? So you don't have to run the command twice?
Nov 08 18:42:00 <annis> Can one restart the task from within the task?
Nov 08 18:42:45 <jamiel>    So what have we got here Kris? Our package all zipped up and ready to go and starting point for a package.xml that we need to edit?
Nov 08 18:42:50 <KRISWALLSMITH> annis: you can abort the task with ctrl-z
Nov 08 18:44:02 <hal>   KRISWALLSMITH, I'm afraid I have to go.  Thank you for your hard work today.  I can follow the tutorial tomorrow by using the log at http://colabti.org/irclogger/irclogger_logs/symfony but can you publish all the code somewhere later, so that we can access it, please? Can I suggest that when you post to a pastebin, to make sure it is a permanent pastebin, and to use different posts each time, so that we can always access each code-change as we follow through the tutorial at a later date?
Nov 08 18:44:06 <annis> Kris: no, I mean, when there are errors, just print out the package.xml.error and restart the task *automatically* :)
Nov 08 18:44:43 <hal>   kriswallsmithBRB, my above suggestion is for future seminars like this one.
Nov 08 18:45:59 <SecureSymfony> There will be other discussions today!
Nov 08 18:47:14 <SecureSymfony> Kris : Hal have a good comment; exactly what I wanted to say, especially because we log the chatroom
Nov 08 18:47:43 <hal>   SecureSymfony, thanks a lot - bye now!
Nov 08 19:02:58 <KRISWALLSMITH> hal_away: i'll try to recreate each paste and remove general discussion for the published log of today
Nov 08 19:02:59 <annis> kris is back :)
Nov 08 19:03:30 <KRISWALLSMITH> so this last session is a bit more free-form
Nov 08 19:03:36 <annis> Kris, before we start
Nov 08 19:04:04 <KRISWALLSMITH> annis: yes?
Nov 08 19:07:17 <KRISWALLSMITH> how many are here for the plugin developers day now?
Nov 08 19:07:24 <annis> me
Nov 08 19:07:37 <KRISWALLSMITH> (no need to be shy)
Nov 08 19:07:43 <FabianLange>   freeform means that kris drinks cofee while everbody asks questions
Nov 08 19:07:52 <phuson>    anyone knows why after I checkout the plugin into the plugins folder, running ./symfony generate:plugin gives me "Task "generate:plugin" is not defined."
Nov 08 19:07:54 <annis> :D
Nov 08 19:07:56 <FabianLange>   i am here because of that event as well
Nov 08 19:08:18 <jamiel>    Heh - I'm pretty sure most people are just catching up every 15-20 mins
Nov 08 19:08:21 <KRISWALLSMITH> phuson: sounds like you haven't enabled the plugin in ProjectConfiguration
Nov 08 19:08:45 <phuson>    ah
Nov 08 19:08:55 <JPhilip>   here, I had an error in package content generation with <?xml version="1.0"?> added before the content.
Nov 08 19:09:02 <jamiel>    KRISWALLSMITH: Still sitting with a package.xml template ... and a zipped up project ... how do we wrap that up to let the world know about our new awesome plugin?
Nov 08 19:09:14 <phuson>    KRISWALLSMITH: it's been a while since I mess around with plugins, let me look at the API docs for that
Nov 08 19:09:39 <KRISWALLSMITH> jamiel: now that you have the .tgz package you just need to upload it to http://www.symfony-project.org/plugins
Nov 08 19:09:44 <SecureSymfony> me
Nov 08 19:10:05 <jamiel>    But my package.xml is still an incomplete template it looks like
Nov 08 19:10:30 <jamiel>    Don't all the <files> need to be in there?
Nov 08 19:11:04 <KRISWALLSMITH> jamiel: delete the package.xml and run plugin:package again
Nov 08 19:12:39 <lukaswoj>  Is there any plugin which automates caching (for example: with memcached) of selected model objects ? If no - I could try to develope such plugin
Nov 08 19:12:43 <jamiel>    I just get a package.xml.tmpl
Nov 08 19:13:36 <KRISWALLSMITH> jamiel: good -- the task uses that template to create a package.xml, which it then deletes after the package.tgz is created
Nov 08 19:13:56 <JPhilip>   if I remove <?xml version="1.0"?> from content and build with pear, it works
Nov 08 19:14:10 <KRISWALLSMITH> if there's a package.xml file the task just uses that w/o asking any questions
Nov 08 19:14:30 <KRISWALLSMITH> JPhilip: pear doesn't like the xml declaration? really?
Nov 08 19:14:57 <JPhilip>   Not on my setup (windows)
Nov 08 19:15:08 <KRISWALLSMITH> interesting...
Nov 08 19:15:30 <SecureSymfony> JPhilip : Your PHP is set to accept small tag... VERY BAD!
Nov 08 19:15:56 <JPhilip>   What is that?
Nov 08 19:16:48 <SecureSymfony> in your php.ini it accept <? instead of <?php only
Nov 08 19:17:24 <FabianLange>   it is called "short tags"
Nov 08 19:17:40 <SecureSymfony> JPhilip : So you have an error with the XML
Nov 08 19:17:55 <SecureSymfony> FabianLange: Your right! My bad!
Nov 08 19:17:57 <KRISWALLSMITH> so, shall we decide upon a plugin to write/upgrade together? anyone want to take the lead here?
Nov 08 19:18:02 <FabianLange>   http://www.php.net/ini.core
Nov 08 19:18:15 <JPhilip>   I have asp_tags = Off in php.ini
Nov 08 19:18:38 <annis> I'm also in, but not so much as a lead
Nov 08 19:18:47 <SecureSymfony> JPhilip : short_open_tag = Off
Nov 08 19:18:47 <Henrik|away>   KRISWALLSMITH: hmm it should be something that uses tasks
Nov 08 19:18:58 <jamiel>    KRISWALLSMITH: Why dont we upgrade sfFeed2Plugin ? It's pretty basic
Nov 08 19:19:19 <annis> jamiel: sounds cool
Nov 08 19:19:25 <Henrik|away>   an idea of mine http://svn.symfony-project.com/plugins/sfPopulateDataPlugin/README
Nov 08 19:19:46 <Henrik|away>   or how about the DbFinder :)
Nov 08 19:19:50 <Henrik|away>   theres no release for 1.2
Nov 08 19:20:00 <skoop> whats with sfFeed2Plugin?
Nov 08 19:20:08 <JPhilip>   short_open_tag = Off is there
Nov 08 19:20:38 <skoop> Henrik|away: I think sfFeed2Plugin isn't even fully done for 1.1 yet
Nov 08 19:21:32 <annis> sfFeed2Plugin sounds good, anyone in?
Nov 08 19:21:36 <SecureSymfony> I'm at a conference at the same time...
Nov 08 19:21:43 <skoop> feel free to do the sfFeed2Plugin, but I have a nearly-done addition to the original plugin based on the ticket from Michael Nolan that I still need tocommit to it
Nov 08 19:21:53 <BoukeH>    Your configuration accepts besides <?php also <? as start tag (asp-style) which is considered a bad thing by some
Nov 08 19:22:03 <mirthlab>  KRISWALLSMITH: oh yeah, nice work on the sfTaskExtraPlugin though :) worth the lack of sleep
Nov 08 19:22:20 <jamiel>    Lets just do an easy one and get sfPHPUnitPlugin out the way :P
Nov 08 19:22:24 <KRISWALLSMITH> let's not work on sfFeed2Plugin if skoop has some pending commits
Nov 08 19:22:33 <skoop> oh no, please do
Nov 08 19:22:35 <skoop> it's an addition
Nov 08 19:23:08 <skoop> the only thing that may be a problem is the fact that the sfFeed2Plugin repository doesn't have trunk/branches yet
Nov 08 19:23:11 <KRISWALLSMITH> it's brand spankin' new
Nov 08 19:23:14 <skoop> but I can easily change that
Nov 08 19:23:20 <KRISWALLSMITH> but requires symfony 1.2
Nov 08 19:28:44 <mirthlab>  so have we decided? sfFeed2Plugin it is?
Nov 08 19:29:19 <mirthlab>  i think KRISWALLSMITH should just make a final decision :)
Nov 08 19:29:22 <Henrik|away>   whos in for openid for sfGuard ? :)
Nov 08 19:30:15 <KRISWALLSMITH> i like the openid idea
Nov 08 19:30:17 <jamiel>    OpenId for sfGuard sounds cool
Nov 08 19:30:31 <KRISWALLSMITH> can we leverage Zend's open id classes?
Nov 08 19:30:47 <SecureSymfony> Henrik : Too long to do... There is already 3 Plugin for it, and 2 with Zend!
Nov 08 19:30:47 <FabianLange>   there is a zend openid for sfguard plugin :-)
Nov 08 19:30:55 <annis> Anyone with me on sfFeed2?
Nov 08 19:31:00 <skoop> KRISWALLSMITH: perhaps stupid question: for plugins, do we put the versions for the different symfony versions into branches like branches/1.0 branches/1.1 and branches/1.2 ?
Nov 08 19:31:10 <Henrik|away>   yeah but its incomplete
Nov 08 19:31:12 <SecureSymfony> sfFeed2 seem good, and more simple!
Nov 08 19:31:22 <SecureSymfony> Yes, both of them!
Nov 08 19:31:26 <FabianLange>   skoop: ideally yes, but not all plugin authors did it like that
Nov 08 19:31:32 <Henrik|away>   KRISWALLSMITH: sure i guess they are pluggable
Nov 08 19:31:50 <skoop> FabianLange: well, I'm going to alter the sfFeed2Plugin repo for this specific purpose ;)
Nov 08 19:32:01 <FabianLange>   then please do so
Nov 08 19:32:02 <KRISWALLSMITH> skoop: most plugins use branches/{sf_version}
Nov 08 19:32:07 <skoop> ok
Nov 08 19:32:20 <KRISWALLSMITH> but it's up to the plugin dev to organized his or her repository
Nov 08 19:33:05 <Henrik|away>   KRISWALLSMITH: hmm guess openid should be a part of sfGuard and not an extra plugin so mayb too steep for now :/
Nov 08 19:33:29 <KRISWALLSMITH> FabianLange: where is the zend open id for sfguardplugin?
Nov 08 19:33:52 <Henrik|away>   http://www.symfony-project.org/plugins/sfZendOpenIdPlugin
Nov 08 19:34:13 <KRISWALLSMITH> i think group think is getting the best of us here... let's just get into sfFeed2Plugin
Nov 08 19:34:27 <mirthlab>  KRISWALLSMITH: i agree! let's just make a decision
Nov 08 19:34:53 <KRISWALLSMITH> skoop: can you take a lead here?
Nov 08 19:35:11 <skoop> KRISWALLSMITH: sure, what you want me to do? just help people with sfFeed2?
Nov 08 19:36:56 <KRISWALLSMITH> this is the practicum part of the day
Nov 08 19:38:01 <BoukeH>    okey I'll pay attention now since the discussed plugin, sfZendOpenIdPlugin, is the one I'm lead on :)
Nov 08 19:38:02 <KRISWALLSMITH> so folks could make edits to the plugin and send you patches for approval?
Nov 08 19:38:30 <KRISWALLSMITH> i haven't looked at sfZendOpenIdPlugin yet
Nov 08 19:39:11 <BoukeH>    it's very basic at this moment, only authentication (sfZendOpenIdAuth) and administration of identities is supported as of yet
Nov 08 19:39:19 <KRISWALLSMITH> BoukeH: can you share any challenges you faced writing this?
Nov 08 19:40:00 <skoop> ok, I have made the changes to the sfFeed2Plugin repo
Nov 08 19:40:15 <skoop> I'll copy the 1.0 version to the 1.2 branch
Nov 08 19:40:27 <skoop> KRISWALLSMITH: do people have access to the repo, or will they supply patches?
Nov 08 19:40:43 <skoop> sorry, I'm just in and haven't really been followeing PDD as I was in BHD
Nov 08 19:41:10 <KRISWALLSMITH> skoop: no one has commit access
Nov 08 19:41:34 <KRISWALLSMITH> who's still with us? who wants to work w/ stefan (skoop)?
Nov 08 19:41:41 <annis> me
Nov 08 19:41:59 <JPhilip>   me
Nov 08 19:42:01 <Henrik|away>   im on kinda :P (catching up on work stuff at the same time) but there none the less
Nov 08 19:42:19 <mirthlab>  me
Nov 08 19:42:24 <mirthlab>  i have commit access
Nov 08 19:42:28 <FabianLange>   me, but i am on 1.2 tickets :-)
Nov 08 19:42:46 <BoukeH>    It was my first plugin so I had to find everything out; particular challenges were the package.xml file for PEAR and integration of the Zend Framework
Nov 08 19:42:56 <Henrik|away>   why not merge the repo to git and everyone who wanna work on it can commit
Nov 08 19:42:58 <FabianLange>   so in case anyone has any patches for 1.2 besides plugins feel free to pm me
Nov 08 19:43:05 <Henrik|away>   and at the end well split some review parts up ?
Nov 08 19:43:12 <mirthlab>  Henrik|away: that's a little out of the scope for today ;)
Nov 08 19:43:19 <Henrik|away>   :)  sry :P
Nov 08 19:43:28 <mirthlab>  haha
Nov 08 19:43:38 <skoop> annis, JPhilip , mirthlab: ok, so from what I understood you want to migrate sfFeed2 to the 1.2 structure?
Nov 08 19:43:55 <annis> seems like it
Nov 08 19:44:19 <Henrik|away>   the tasks needs to be split up into tickets or something so peps dosent work on the same thing
Nov 08 19:44:25 <annis> Can we use the sandbox 1.2 from before for it? I kinda stumped how we are going to work together
Nov 08 19:44:54 <KRISWALLSMITH> annis: that's why i'm delegating :)
Nov 08 19:45:11 <annis> Kris: fine, thx
Nov 08 19:45:17 <skoop> annis: I wasn't in before so I don't know exactly what the 1.2 sandbox was, but it sounds like you could do it
Nov 08 19:45:17 <Henrik|away>   well we need some kind of project management ticket stuff
Nov 08 19:45:34 <Henrik|away>   skoop: the sandbox = clean 1.2 install
Nov 08 19:45:34 <skoop> Henrik|away: I agree
Nov 08 19:45:52 <skoop> ah, in that case annis, you can use the sandbox to work on the sfFeed2Plugin
Nov 08 19:46:30 <annis> skoop: We first need to know what's *not* working in the plugin now
Nov 08 19:46:35 <Henrik|away>   KRISWALLSMITH: assembla account with temp ticket trac ?
Nov 08 19:46:42 <annis> skoop: So, I'll just checkout the 1.0 branch to my sandbox?
Nov 08 19:47:02 <KRISWALLSMITH> Henrik|away: sorry, i'm english only...
Nov 08 19:47:11 <mirthlab>  the way i've worked on plugins before.... simple link the plugin to the plugins directory via svn:externals
Nov 08 19:47:12 <Henrik|away>   haha :) assembla.com :)
Nov 08 19:47:19 <skoop> annis: wait just a minute, and you can checkout the 1.2 branch instead
Nov 08 19:47:22 <Henrik|away>   so we wont clutter the symf trac
Nov 08 19:47:30 <FabianLange>   skoop, did you intend the svn copy that way?
Nov 08 19:47:42 <Marijn>    KRISWALLSMITH: Ok, something occurred to me the other day. I was thinking about naming conventions for plugin classes and I think that when it comes to action classes we should stick to the Plugin prefix there as well in favor of the Base prefix
Nov 08 19:47:43 <KRISWALLSMITH> why not just create trac tickets for sfFeed2Plugin?
Nov 08 19:47:43 <FabianLange>   ah you didnt :-)
Nov 08 19:48:17 <skoop> FabianLange: already fixing it ;)
Nov 08 19:48:17 <Henrik|away>   KRISWALLSMITH: hmm sure if its not gonna be confusing for people :P
Nov 08 19:48:23 <Marijn>    wow, just read the blog post about sfTaskExtraPlugin => NICE :D
Nov 08 19:48:39 <skoop> annis: ok, the 1.0 code is now available in the 1.2 branch, so you can check out the 1.2 branch of sfFeed2Plugin
Nov 08 19:48:41 <KRISWALLSMITH> Marijn: thanks
Nov 08 19:49:00 <FabianLange>   #3959 could be fixed :-)
Nov 08 19:49:19 <skoop> FabianLange: my fault for working directly in the repo with my copies. fixed it in a local checkout instead ;)
Nov 08 19:49:35 <Marijn>    thanks for my first comment or the second. I just started to see the advantage of developing certain logic in plugins and found myself in dire need of such a task :-)
Nov 08 19:49:51 <FabianLange>   yeah for directory copy and merge i prefer a gui over the cli :-)
Nov 08 19:49:59 <jamiel>     svn checkout https://svn.symfony-project.org/plugins/sfFeed2Plugin/branches/1.2 plugins/sfFeed2Plugin
Nov 08 19:50:09 <Pests> How do I use a projects symfony model classes outside of my symfony dir?
Nov 08 19:50:11 <JPhilip>   Got sfFeed2Plugin branch 1.2 checked out
Nov 08 19:51:49 <annis> doing the checkout now... done
Nov 08 19:52:05 <jamiel>    How about we start by getting the tests failing in a way we expect ... rather than throwing errors
Nov 08 19:52:27 <jamiel>    then we can make them pass one by one
Nov 08 19:52:45 <skoop> FabianLange: ticket 3959 is also related to this same thing: there is no sf1.1 package for the plugin yet
Nov 08 19:52:52 <FabianLange>   i know, thats why i was refering to this
Nov 08 19:53:58 <skoop> annis, JPhilip , mirthlab: perhaps you guys could work on both an sf1.1 and an sf1.2 version?
Nov 08 19:54:04 <bschussek> Klemens and I just implemented some new plugin testing goodies. We'll propose them to Fabien, maybe we will get them into the core
Nov 08 19:54:06 <Henrik|away>   one thing is that 1.2 supports multiple mime types so the asXml method should be cleaned up
Nov 08 19:54:21 <annis> jamiel: I'd do it the other way around first
Nov 08 19:54:27 <bschussek> symfony test:all --plugin=myCustomPlugin and such stuff ;-)
Nov 08 19:54:52 <bschussek> the documentation for it is just being written by Klemens
Nov 08 19:54:54 <annis> jamiel: create a new plugin with the new TaskExtraPlugin and integrate back from the original sfFeed2Plugin
Nov 08 19:55:09 <KRISWALLSMITH> bschussek: yes, either the core or the task plugin
Nov 08 19:55:34 <annis> jamiel: b/c the prove.php has changed since then, everything should be different now
Nov 08 19:55:42 <bschussek> kris: I think this as well as the generate:plugin task definitely belongs into the core, since symfony officially supports plugins
Nov 08 19:56:08 <Henrik|away>   annis: i second that
Nov 08 19:56:27 <Henrik|away>   but is there a lead on this so people arent gonna do all kind of things
Nov 08 19:56:50 <KRISWALLSMITH> bschussek: fabpot has told me tasks geared toward plugin developers should go in the task extra plugin.
Nov 08 19:57:06 <KRISWALLSMITH> bschussek: which is maintained by the core team
Nov 08 19:57:07 <bschussek> KRISWALLSMITH: ah, that's interesting
Nov 08 19:57:11 <annis> that's kinda hard to do Herik, b/c the feed plugin isn't working yet, we can't just add features, we'll have to rewrite pretty much
Nov 08 19:58:21 <annis> How about gathering ppl for the same plugin in another room?
Nov 08 19:58:26 <bschussek> KRISWALLSMITH: on the other hand, we made only small enhancements to the core test tasks, and I think writing separate tasks for this functionality would be way too complicated (for both devs and users)
Nov 08 19:58:27 <Pests> How do I use a projects symfony model classes outside of my symfony dir?
Nov 08 19:58:48 <KRISWALLSMITH> bschussek: can you use the command.* events?
Nov 08 19:58:49 <bschussek> just think of having to use different test:all and plugin-test:all tasks
Nov 08 19:59:14 <isleshocky77>  ok, I'm back. Had to grab some food.  For anyone who said that the taskPlugin is only for 1.2+  I made a small raw php only script which handles package.xml files pretty easily I don't know if I should post it somewhere.
Nov 08 19:59:36 <bschussek> KRISWALLSMITH: not really. Klemens will release the documentation for our changes in ~5 minutes, I suggest both you and Fabien look at it and tell us what you think about it
Nov 08 19:59:56 <KRISWALLSMITH> bschussek: sounds good
Nov 08 20:01:42 <JPhilip>   One more hour, are we going to learn how to transform helpers into widget classes?
Nov 08 20:01:44 <skoop> KRISWALLSMITH: do I need to be the lead on a plugin to change the installation instructions on /plugins?
Nov 08 20:02:41 <KRISWALLSMITH> skoop: under which tab?
Nov 08 20:02:52 <skoop> Under Installation
Nov 08 20:02:57 <KRISWALLSMITH> JPhilip: i'm not sure i understand what you're asking
Nov 08 20:03:20 <Henrik|away>   skoop: you cant
Nov 08 20:03:30 <Henrik|away>   its generate by the packages availible
Nov 08 20:03:46 <JPhilip>   Old plugins use helper functions, now we have widgets for the same functionality
Nov 08 20:03:55 <skoop> Henrik|away: ah ok
Nov 08 20:05:10 <KRISWALLSMITH> JPhilip: you're referring to form helpers and sfWidgetForm classes?
Nov 08 20:05:43 <Pests> How do I use a projects symfony model classes outside of my symfony dir?
Nov 08 20:05:57 <klemens_u> You can find the documentation of Bernhard's any my proposal here: http://trac.symfony-project.org/wiki/PluginTesting
Nov 08 20:06:35 <klemens_u> It describes the enhancement for 'symfony test:all' etc for plugins
Nov 08 20:06:49 <JPhilip>   I mean custom helper functions like in my plugin sfDoctrineTree plugin: get_doctrine_tree($model, $field, $root = 0, $options = array()) should now be a widget
Nov 08 20:07:48 <KRISWALLSMITH> JPhilip: why is that?
Nov 08 20:09:30 <JPhilip>   I guess you can still use the helper functions, but widgets seem to integrate into the new form framework
Nov 08 20:10:31 <isleshocky77>  Anyone know where this room is being logged to?  I have in my bookmarks that it was here: http://www.cpr.in-berlin.de/symfony/irclog.frontend.php
Nov 08 20:11:38 <bschussek> KRISWALLSMITH: if you have any feedback on our proposal, just write us here or add your comments on the wiki page
Nov 08 20:11:51 <Henrik|away>   a bit ot shouldnt JSON content type be text/x-json ?
Nov 08 20:12:13 <KRISWALLSMITH> bschussek: now i see it
Nov 08 20:12:34 <annis> Henrik|away: that's IE MIME-types at work... :D
Nov 08 20:12:39 <Henrik|away>   okay :P
Nov 08 20:12:55 <Henrik|away>   becuase safari just auto downloads application/json files
Nov 08 20:13:29 <annis> it should be text/json then
Nov 08 20:14:00 <Henrik|away>   ty
Nov 08 20:14:03 <fruit> q: does are avaiable any where #symfony channel logs?
Nov 08 20:14:43 <SecureSymfony> fruit : we will have a transcription
Nov 08 20:14:54 <SecureSymfony> I got to go!
Nov 08 20:17:23 <SecureSymfony> Hum, normal, we need to get them out there.... It will be on symfony-project.org
Nov 08 20:21:15 <KRISWALLSMITH> have PDD folks signed off?
Nov 08 20:22:01 <Henrik|away>   KRISWALLSMITH: dunno im still here on the sideline :P
Nov 08 20:22:06 <klemens_u> me too :-)
Nov 08 20:22:30 <KRISWALLSMITH> ok, let's wrap up.
Nov 08 20:22:39 <ringhio`>  KRISWALLSMITH: do you will post a complete log of this PDD somewhere?
Nov 08 20:22:55 <KRISWALLSMITH> do you guys think this is a good format for this sort of thing?
Nov 08 20:23:02 <martialmind>   doctrine:build-filters or propel:build-filters
Nov 08 20:23:06 <KRISWALLSMITH> would you like to see this type of event happen more often?
Nov 08 20:23:20 <ringhio`>  of course!
Nov 08 20:23:23 <klemens_u> KRISWALLSMITH: good questions. in general absolutely yes!
Nov 08 20:23:44 <KRISWALLSMITH> i'm very interested in growing the plugin community
Nov 08 20:23:45 <klemens_u> perhaps more focused - more specific on one topic
Nov 08 20:24:12 <klemens_u> and a 'prepare this and that' list perhaps (sf1.2 installation etc)
Nov 08 20:24:13 <KRISWALLSMITH> another idea i've had is to setup an established "peer review" process that a plugin dev can submit their work to
Nov 08 20:24:19 <ringhio`>  maybe it could be shorter and more focused
Nov 08 20:24:20 <KRISWALLSMITH> to add a level of legitimacy
Nov 08 20:24:41 <KRISWALLSMITH> ok, shorter and more focused. fair enough.
Nov 08 20:24:52 <klemens_u> KRISWALLSMITH: +1 for the peer review
Nov 08 20:25:11 <klemens_u> It's would be also a good way to learn from each other
Nov 08 20:25:16 <JPhilip>   Maybe ask people to prepare specific questions/problems to solve from their plugins
Nov 08 20:25:33 <annis> yeah, that would be good
Nov 08 20:25:42 <KRISWALLSMITH> JPhilip: i'm not following you
Nov 08 20:26:00 <ringhio`>  if you want to repeat frequently
Nov 08 20:26:01 <annis> anyone here still interested to help skoop and myself with sfFeed2?
Nov 08 20:26:25 <ringhio`>  annis: sfFeed2Plugin of Zaninotto?
Nov 08 20:27:05 <JPhilip>   Let plugin developers prepare and expose problems they have with their own plugins
Nov 08 20:27:17 <ringhio`>  i use it on http://miit.me are you looking for help to maintain?
Nov 08 20:27:21 <skoop> ringhio`: previously of francois, yes
Nov 08 20:27:37 <annis> ringhio: yes
Nov 08 20:27:39 <skoop> ringhio`: we are looking for help right now to port it to sf1.1 / sf1.2
Nov 08 20:27:41 <ringhio`>  yes I know about his departed
Nov 08 20:28:15 <annis> join us on #sfFeed2
Nov 08 20:28:18 <JPhilip>   I am not sure I understood the sf2Feed thing, I thought it was just an exercise we were doing
Nov 08 20:28:20 <FabianLange>   i really would like to see sffeed2 for 1.2 and could help, but i dont have anythin here on my mac yet
Nov 08 20:29:05 <klemens_u> KRISWALLSMITH: a question for sfTaskExtraPlugin:
Nov 08 20:29:12 <EBSMobile> annis: I am getting an array as a result but now sure how to extract the data from it?
Nov 08 20:29:12 <klemens_u> how is the fixtures project created?
Nov 08 20:31:06 <KRISWALLSMITH> klemens_u: it's directly copied from the core
Nov 08 20:31:10 <Henrik|away>   KRISWALLSMITH: should have our own channel so normal sf question is filtered from the actually event
Nov 08 20:31:37 <KRISWALLSMITH> Henrik|away: next time, yes
Nov 08 20:31:44 <Henrik|away>   #symfony-event or something
Nov 08 20:32:21 <KRISWALLSMITH> Henrik|away: that's exactly what i was thinking :)
Nov 08 20:32:36 <Henrik|away>   great minds think alike ^^
Nov 08 20:33:43 <klemens_u> KRISWALLSMITH: so it's similar to 'generate:project'?
Nov 08 20:34:57 <KRISWALLSMITH> yes, although it doesn't actually call the task
Nov 08 20:35:08 <klemens_u> I see. thanks
Nov 08 20:35:24 <KRISWALLSMITH> well, thank you to everyone who participated today
Nov 08 20:35:31 <KRISWALLSMITH> i'm glad we did this :)
Nov 08 20:35:53 <isleshocky77>  KRISWALLSMITH: Is there a log somewhere?
Nov 08 20:35:54 <KRISWALLSMITH> i'll have a transcript available shortly -- i'll probably announce it on the blog
Nov 08 20:36:03 <JPhilip>   Thanks
Nov 08 20:36:16 <klemens_u> KRISWALLSMITH: Any feedback from your side on our 'enhancment of the test tasks' RFC?
Nov 08 20:37:13 <isleshocky77>  Is there a new way of running tests, such as all tests including symfony and plugins, just all plugins, etc.  Or do we have do run php prove.php individually for each?
Nov 08 20:37:51 <klemens_u> isleshocky: we proposed that today: http://trac.symfony-project.org/wiki/PluginTesting+
Nov 08 20:38:00 <klemens_u> sorry: http://trac.symfony-project.org/wiki/PluginTesting
Nov 08 20:39:03 <klemens_u> isleshocky. Is that what you have in mind?
Nov 08 20:43:21 <KRISWALLSMITH> cheers, all
Nov 08 20:43:26 *   KRISWALLSMITH is now known as kriswallsmithAFK
Nov 08 20:43:43 <isleshocky77>  klemens_u: Yep.
Nov 08 21:00:16 <bschussek> Our result of the plugins developers day! :-) http://trac.symfony-project.org/ticket/4873
Nov 08 21:00:37 <bschussek> Rejoice all plugin developers, for the day of easy plugin testing has (nearly) come
Nov 08 21:00:54 <bschussek> :-)
Nov 08 21:01:04 <klemens_u> goodnight everyone!
Nov 08 21:01:19 <klemens_u> (at least in our timezone :-))