Because Habari is a commit-then-review project and alway has been. The changes are being made in a branch, which allows people to jump in and help if they can, review if they want and offer informed pushback if necessary.
I think you make some valid points. We really don't need to break APIs willy nilly, that has bitten me on the butt more than once. Owen sent this to the list so we could have discussion about it, and it is in a branch so that it doesn't affect trunk until it's ready. One of the major pushes for the update to formUI was me, and my very vocal hate of trying to use it in non-bloggy projects, which is 90% of what I do with Habari today. I have real world, incredibly frustrating experience trying to use the system. It doesn't support AJAX well, which most of the forms I create today need to be able to handle, and it makes intricate, in depth styling impossible. These are two major, major stumbling blocks to its adoption outside of hardcore developers, and I say hardcore since I am a core dev, a founder and pretty good at the whole PHP thing and I don't take the time to create custom templates to solve the problems in formUI, because I don't have the time or energy to do it. It is less effort to just create the forms I need and the code that backs them from scratch. And there in lies the rub. FormUI should make it easier and safer to create forms than rolling them yourself, and today it just doesn't do that. On Feb 8, 2013, at 8:16 AM, Morgante Pell <[email protected]> wrote: > I'm not convinced FormUI is such a bad system. It's one of the > beautiful bits of Habari. > > I'm not saying we need to keep the API. I'm just asking what > specifically about the changes necessitates breaking the API. > > Why do things like this go ahead with minimal discussion? > > ~Morgante > > Le Feb 8, 2013 à 18:10, Owen Winkler <[email protected]> a écrit : > >> On 2/8/2013 8:58 AM, Morgante Pell wrote: >>> Those all seem like worthy goals, but I'm very concerned about >>> significantly changing the API for FormUI. >> >> The current system is in the poor state it is currently precisely because we >> altered it while keeping backward compatibility. While we're still in >> pre-1.0, we have every reason to make it right so that we have a stable API >> instead of a rickety one we keep using. >> >> It's not just a change for change's sake. It's a change because what's >> there now isn't good enough and prior to 0.10's other massive changes is the >> time to properly fix it. >> >> Owen >> >> -- >> -- >> 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/habari-dev >> --- You received this message because you are subscribed to the Google >> Groups "habari-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > -- > 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/habari-dev > --- > You received this message because you are subscribed to the Google Groups > "habari-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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/habari-dev --- You received this message because you are subscribed to the Google Groups "habari-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
