Hey,

JonoB thanks for explaining the issue to eliminator2009.

I have added this as a issue (bug) on github at https://github.com/ollierattue/FormIgniter/issues/14

Will fix it when I next have some free some open source time.

Thanks,

The ‘You are using a variable called $data, but you have not defined it yet.’ bug has now been fixed.

Bug fix available on https://github.com/ollierattue/FormIgniter/ and the live application at http://formigniter.org

This app looks great. I’ve just did a quick test. For the people who likes fast solutions…

My notes…

I think that there could be option whether user wants to get output in html or in CI functions (dynamic).

Just one more idea… Maybe it would be hard, but… what if you would press the button ... “See the form” instead “build this form” and with JQuery drag&drop; user could to organize elements into Fieldsets .... And Fieldsets into Divs… Just to get a good look.

4ever - 19 May 2011 08:10 PM

This app looks great. I’ve just did a quick test. For the people who likes fast solutions…

Thanks for your kind words.

4ever - 19 May 2011 08:10 PM

I think that there could be option whether user wants to get output in html or in CI functions (dynamic).

I personally favour html. The CI helpers are great, but tend to confuse frontend developers (who I collaborate with). Still a helper/html option could be added relatively easily.

4ever - 19 May 2011 08:10 PM

Just one more idea… Maybe it would be hard, but… what if you would press the button ... “See the form” instead “build this form” and with JQuery drag&drop; user could to organize elements into Fieldsets .... And Fieldsets into Divs… Just to get a good look.

I think it is quiet a lot of work for little benefit. FormIgniter isn’t about producing a pretty form. This would be handled by the developer afterwards using CSS etc.

The source code for FormIgniter is available at https://github.com/ollierattue/formigniter - Give me a shout if you develop either of these two ideas.

Cheers.

Can you put an option to name the forms/controllers instead of just “myform”

great work by the way.

Ollie Rattue - 19 May 2011 09:02 PM

I personally favour html. The CI helpers are great, but tend to confuse frontend developers (who I collaborate with). Still a helper/html option could be added relatively easily.

Cheers.

I agree with you that CI helpers and forms solution generaly is still very complicated. But I prefer doing dynamic solutions even it is a little bit slower then clear html. Problem with html start that if you decide later to change some parts of elements then it could be more work then on the dynamic solution.

I already try some symplifing solutions for forms. I thought about adjusting the form_validation to my_form_validation library and validation and form_helper.php to MY_form_helper.php to get simpler solutions… I thought up how to get and use simpler format of configuration array for my_formvalidation. And I think it could be possible to remake or to add methods that could simplify the configuration for both creating form and validation. Having config fields without keys.

luke holder - 20 May 2011 03:38 AM

Can you put an option to name the forms/controllers instead of just “myform”

great work by the way.

Thanks - This ‘feature’ has been requested before and is down for future development - https://github.com/ollierattue/FormIgniter/issues/4

hey,
i just like your app but i hav a question ...
is it a common way to produce an extra controller for each form i hav?
for example when i want a user to register on my page i would have the signup (where the register form should be called), show etc in one controller
so should i c&p the code from your app to my controller or is it common to seperate form from the other stuff?

greetings

felix_ - 22 May 2011 09:59 AM

hey,
i just like your app but i hav a question ...
is it a common way to produce an extra controller for each form i hav?
for example when i want a user to register on my page i would have the signup (where the register form should be called), show etc in one controller
so should i c&p the code from your app to my controller or is it common to seperate form from the other stuff?

greetings

This is a personal decision on how you like to structure your application. I tend to keep all related functions in the same controller e.g.

Project (controller name)
-> Add
-> Edit
-> Delete
-> Save
-> Publish
-> Preview

felix_ - 22 May 2011 09:59 AM

for example when i want a user to register on my page i would have the signup (where the register form should be called), show etc in one controller
so should i c&p the code from your app to my controller or is it common to seperate form from the other stuff?

Yes I copy and paste the outputted code from FormIgniter into my controllers and rename the functions as applicable.

Ollie Rattue - 22 May 2011 11:28 PM

felix_ - 22 May 2011 09:59 AM

hey,
i just like your app but i hav a question ...
is it a common way to produce an extra controller for each form i hav?
for example when i want a user to register on my page i would have the signup (where the register form should be called), show etc in one controller
so should i c&p the code from your app to my controller or is it common to seperate form from the other stuff?

greetings

This is a personal decision on how you like to structure your application. I tend to keep all related functions in the same controller e.g.

Project (controller name)
-> Add
-> Edit
-> Delete
-> Save
-> Publish
-> Preview

felix_ - 22 May 2011 09:59 AM

for example when i want a user to register on my page i would have the signup (where the register form should be called), show etc in one controller
so should i c&p the code from your app to my controller or is it common to seperate form from the other stuff?

Yes I copy and paste the outputted code from FormIgniter into my controllers and rename the functions as applicable.

ok thanks… thats the way i would prefer also