Hello Folks, I have been otherwise engaged battling Internet Explorer 8 in my spare dev time for the last two weeks so I am completely out of the loop as to where the form component is currently at.
Last week Fabien said he would put his issues on the mailing list, but we've yet to have this. It would be really good to have an idea of Fabiens issues with it, especially if they are the same issues I have. Internally we have issues with the whole "getParent()" thing, when defining a form, I may not understand the problems this solves but writing a string that defines your parent feels wrong to me. Its hard to debug for a start. I think an explanation of this area might help, so at least I can argue against it with more information if I still feel it is wrong. It is functional and does its job, but it is a little bit unclear look at the code what it is done. I feel if you can't figure it out by looking at the code then something is wrong...that is just my opinion of course... I know people have issues with the Type name thing also, I'm not that bothered it is just a name, however it would be good for people to debate this openly a bit more. It would be good if other people using it could list any issues they have too? >From my point of view I think its fine for my use and if it doesn't get put into 2.0 we will be using the code anyway in our application. Cheers John -- 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
