Hi Kellie,
I'm so sorry for the long response time! You posted right when I left town for a few days...
I'm afraid I don't know about the WYSIWYG editor... the implementation for Form Tools was very basic and doesn't allow much customization beyond what appears in the UI. However, this is going to change in the next release. First, the Settings -> WYSIWYG tab is going to be removed and all options for the editor moved to a Custom Fields module. The WYSIWYG field will continue to be available and customizable, but in a different way. The /global/script/wysiwyg_settings.js file won't exist any more - I'll be moving that to a field editable via the module.
Blah blah blah - sorry, all very technical and not very useful. What I mean is that everything will change and will allow more customization without fear of breaking it for future releases. The first version will probably just provide the same options that exist right now, but later on I'll make it more configurable.
For the full-screen popup, presumably that needs some backend work to link to the appropriate HTML/PHP file containing the appropriate markup. I'll definitely keep this in mind when working on the module. If it's not too much work, I'll include it - (I can see it being very useful!)
Again, sorry I couldn't give more concrete help.
Yes, absolutely. First off, the existing Form Tools date-picker (which appears when editing the Submission Date and Last Modified Date) is being replaced with a jQuery calendar popup. The "official" one doesn't contain an option to select time as well, so I'm leaning towards this customization:
http://trentrichardson.com/examples/timepicker/
Secondly, The Custom Fields module will contain a new generic "Date / Time" field type. This will let you assign that field to any of your own form fields, so they'll be editable with the calendar / calendar+time / time popup (depending on what settings you choose for your field).
Sorry for the long response.
- Ben
I'm so sorry for the long response time! You posted right when I left town for a few days...
I'm afraid I don't know about the WYSIWYG editor... the implementation for Form Tools was very basic and doesn't allow much customization beyond what appears in the UI. However, this is going to change in the next release. First, the Settings -> WYSIWYG tab is going to be removed and all options for the editor moved to a Custom Fields module. The WYSIWYG field will continue to be available and customizable, but in a different way. The /global/script/wysiwyg_settings.js file won't exist any more - I'll be moving that to a field editable via the module.
Blah blah blah - sorry, all very technical and not very useful. What I mean is that everything will change and will allow more customization without fear of breaking it for future releases. The first version will probably just provide the same options that exist right now, but later on I'll make it more configurable.
For the full-screen popup, presumably that needs some backend work to link to the appropriate HTML/PHP file containing the appropriate markup. I'll definitely keep this in mind when working on the module. If it's not too much work, I'll include it - (I can see it being very useful!)
Again, sorry I couldn't give more concrete help.
Quote:Also any chance in your 2.5 release to provide date/time fields as options with the new JQuery calendar / date / time picker as an option. This is for your internal views, not via the api.
Yes, absolutely. First off, the existing Form Tools date-picker (which appears when editing the Submission Date and Last Modified Date) is being replaced with a jQuery calendar popup. The "official" one doesn't contain an option to select time as well, so I'm leaning towards this customization:
http://trentrichardson.com/examples/timepicker/
Secondly, The Custom Fields module will contain a new generic "Date / Time" field type. This will let you assign that field to any of your own form fields, so they'll be editable with the calendar / calendar+time / time popup (depending on what settings you choose for your field).
Sorry for the long response.
- Ben