Closed Beta: All conversations regarding the beta test group - My Forums

Re: Closed Beta: All conversations regarding the beta test group

charless — Aug 12, 2013, 06:20 AM

It's finally here.... an all new mxFormBuilder learn more and get a pre-release. Note that with RTFM being migrated limited docs until I can get logged back into RTFM to add the associated documentation.

See what to get excited about at description and registration.

Thanks for all your support and patience.

Cheers

Re: Closed Beta: All conversations regarding the beta test group

charless — Apr 03, 2013, 12:10 AM

I hope to get a new release back out in the next couple weeks, there are still external factors that I can not fully gauge at this time. Again apologies for the delay caused by the unforeseen circumstances.

Quote from: exside at Mar 13, 2013, 05:33 PM

May a donation help you to overcome these external factors =D? How are the links to the newest release distributed? Was there another link somewhere than the one in the first (and only?) email?

Donations are always welcome as the biggest hurdle is getting the time to work on items that are not paying bills.

Cheers

Re: Closed Beta: All conversations regarding the beta test group

exside — Mar 13, 2013, 12:33 PM

May a donation help you to overcome these external factors =D? How are the links to the newest release distributed? Was there another link somewhere than the one in the first (and only?) email?

Re: Closed Beta: All conversations regarding the beta test group

charless — Mar 13, 2013, 11:09 AM

No not abandoned, just some serious delays do to external factors regarding the project as a whole. More to come soon. Apologies to everyone.

Cheers

Re: Closed Beta: All conversations regarding the beta test group

exside — Feb 20, 2013, 05:50 AM

Hi charles,

are there any news or emails I missed regarding mxFormBuilder? Just have seen that the RTFM pages were deleted...hope ou didn't abandon the project (it has bigtime potential!)?!

Re: Closed Beta: All conversations regarding the beta test group

charless — Feb 02, 2013, 05:25 PM

@bennyb

Thanks for the feedback and as you mentioned some of your items are already in development and almost ready. Then for the bugs, yep the windows got all whacked somewhere however that's all about to change anyway

To the specifics in your list:

1) HTML5 input types.

2) Custom Inputs.

These are both going to be addressed in the ability to fully mange all input types including their content inside the mxFormBuilder manager, so full customization coming very soon.

3) Ability to add custom class or id to div wrap of each label/input. Not only for styling but allowing a bit more customization with JS so can hide certain field depending whats field in. I notice you do have conditional groups but not sure how these work.

Already done, just waiting on a few other changes for the next release before pushing out to everyone.

4) Should include in the RTFM on how to set a TV up to list the forms.

Agreed, once I get past releasing the next build I'll be revising the RTFM docs as some of lit is already going to be outdated with the next build.

Thanks again!

Cheers

Re: Closed Beta: All conversations regarding the beta test group

bennyb — Feb 01, 2013, 05:47 AM

Hi Charles,

I've not managed to test this as much I would of like so apologies there. But from what I've seen so far it looks really nice and looking forward to implementing into some of my projects.

I'll start with some thing I think the form could benefit from, so of which have been mentioned by others.

1) HTML5 input types. There's a few so would clog up the list a bit. So maybe having a more genetic term for text inputs and having a 2nd drop down list with the different types.
I thinking maybe as this is likely to be used by a client with no html experience you could group together some of the options which have a sub drop down, something like:

Text
- Single Line
- Multi Line
- Email
- Url

Number
- Number
- Date
- tel

2) Custom Inputs. Be good if it was possible to add our own option. I see you have the state lists, but here in the UK we'd want something different. So be good if we could create our own instead of having to add a field for every option. Possibly even remove the state list so they are added as custom input as that would keep the type list shorter.

3) Ability to add custom class or id to div wrap of each label/input. Not only for styling but allowing a bit more customisation with JS so can hide certain field depending whats field in. I notice you do have conditional groups but not sure how these work.

4) Should include in the rtfm on how to set a TV up to list the forms.

Bugs

1) I had a similar issue to Susan where the Saving overlay just hang after saving a newly created form. But i refreshed the page and it had actually created the form. This only happened a couple of times.

2) If you refresh the browser when view the component. Right click and duplicate nothing happens. But if you then refresh it's actually duplicated it. This seems to only happen on the initial load of the component.

3) Similar thing if your in a form adding fields. Refresh on the table view, right click to edit. The overlay appears but nothing populated. Close this, then edit again and its fine.

4) If I've added a multi checkbox as a previous field. When i go to add another field say for select box. Then the "create new option" is already pre populated with what was added in the multi checkbox. I had a few issues with this. I'd refreshed it and then none of the "options" were displaying even on ones i'd already created. They still somewhere as if I tried to create a new one with the same name I got the following error "a item with that name already exists, rename the new one or modify the existing item".

5) I selected the number type and the max and min input fields didn't display so was unable to add these. I tried again and this didn't happen again. So not 100% sure what caused this. There's some errors in the error log (pasted below) which i think maybe related.

6) On submission the submission text was displaying but with the following above:
array(0) { }

[2013-02-01 11:22:15] (ERROR @ /modx-2.2.6/assets/components/mxformbuilder/connector.php) forms: Attempt to set NOT NULL field closedate to NULL
[2013-02-01 11:22:15] (ERROR @ /modx-2.2.6/assets/components/mxformbuilder/connector.php) forms: Attempt to set NOT NULL field owners to NULL
[2013-02-01 11:23:29] (ERROR @ /modx-2.2.6/connectors/security/user.php) Error caching lexicon topic lexicon/en/core/user
[2013-02-01 11:57:01] (ERROR @ /modx-2.2.6/assets/components/mxformbuilder/connector.php) forms: Attempt to set NOT NULL field opendate to NULL
[2013-02-01 11:57:01] (ERROR @ /modx-2.2.6/assets/components/mxformbuilder/connector.php) forms: Attempt to set NOT NULL field closedate to NULL
[2013-02-01 11:57:01] (ERROR @ /modx-2.2.6/assets/components/mxformbuilder/connector.php) forms: Attempt to set NOT NULL field owners to NULL

Thanks

B

Re: Closed Beta: All conversations regarding the beta test group

charless — Jan 30, 2013, 06:38 PM

Quote from: nmweb at Jan 30, 2013, 09:16 PM

Furthermore, perhaps you could redesign the manager page into something resembling common ModX resources. That is, the form properties on top (open date, owners, name etc.) where page properties such as Title, Description, Cacheability etc. are.
And the form fields below (where the content field of a ModX resource usually is)

Yes, thats the ticket... I think thats would be brilliant but we still have one page in front of that where you actually create the form though or some interface maybe just a simple bar across the top with a drop down (or expandable panel) of current forms with of course a button to create a new one.

Re: Closed Beta: All conversations regarding the beta test group

charless — Jan 30, 2013, 06:34 PM

Quote from: sottwell at Jan 30, 2013, 08:18 PM

I wonder if this could be a pre-hook for Formit?

What could be a pre-hook for Formit??

I am planning on extending a snippet that extends just the validation type rules like an API just for validation, not sure if that was the direction you were going.

Cheers

Re: Closed Beta: All conversations regarding the beta test group

nmweb — Jan 30, 2013, 03:16 PM

What events (double-click, single-click, buttons) would make the most intuitive solution for navigating the elements of the form?

Update
Remove
Manage Fields
View Submissions
Duplicate

I like how the Articles component does it with a list of articles and underneath the buttons. See screenshot.

Furthermore, perhaps you could redesign the manager page into something resembling common ModX resources. That is, the form properties on top (open date, owners, name etc.) where page properties such as Title, Description, Cacheability etc. are.
And the form fields below (where the content field of a ModX resource usually is)

Btw, great that you are so open to input! It's what makes ModX so cool.