hi Bob and Max
its been a while.
Until the damn iXXXX was released, CF was running really well and there was zero issues from the user community. Since then, the use of jEditor and other WYSIWYG features that could be called by CF are not working, and the upwardly mobile members of my user community are complaining that they can;t fill in a simple form that leverages and instance of jeditor (JCE is the actual editor but TinyMCE is also affected).
Now the issue does NOT reside with CF. Its actually the way Apple have implemented the mobile instance of Safari. (its not a complete implementation).
As a feature in the new version 4, could we have a way of identifying the user agent, independently of Joomla which would then show or not show certain form elements. This would help us keep up with new UA's as they appear and allow us to control what happens next.
I am having to hard code a solution into the exiting version of CF to ID the uaProf and then render jEditor or a std text box. This makes for long term supportability issues as I upgrade to the latest CF and beyond.
Can you guys help?
Thanks
-anthony
its been a while.
Until the damn iXXXX was released, CF was running really well and there was zero issues from the user community. Since then, the use of jEditor and other WYSIWYG features that could be called by CF are not working, and the upwardly mobile members of my user community are complaining that they can;t fill in a simple form that leverages and instance of jeditor (JCE is the actual editor but TinyMCE is also affected).
Now the issue does NOT reside with CF. Its actually the way Apple have implemented the mobile instance of Safari. (its not a complete implementation).
As a feature in the new version 4, could we have a way of identifying the user agent, independently of Joomla which would then show or not show certain form elements. This would help us keep up with new UA's as they appear and allow us to control what happens next.
I am having to hard code a solution into the exiting version of CF to ID the uaProf and then render jEditor or a std text box. This makes for long term supportability issues as I upgrade to the latest CF and beyond.
Can you guys help?
Thanks
-anthony
Hi Anthony,
What does "independently of Joomla" mean here? Joomla! has moderately good browser sniffer code that could be used to create a conditional form.
It would be fairly easy to do this with Custom Form HTML, more difficult to build with custom actions or elements I think as there is no concept of a conditional flow.
As I write though it might be possible to add some conditional switches into a Custom SHow HTML action.
Can you give me a few specifics to test.
Bob
What does "independently of Joomla" mean here? Joomla! has moderately good browser sniffer code that could be used to create a conditional form.
It would be fairly easy to do this with Custom Form HTML, more difficult to build with custom actions or elements I think as there is no concept of a conditional flow.
As I write though it might be possible to add some conditional switches into a Custom SHow HTML action.
Can you give me a few specifics to test.
Bob
Hi Bob,
Below is a piece of code I use in CF to leverage the inbuilt WYSIWYG editor via JFactory::getEditor();
By independently of Joomla I mean that Joomla is not up to date on all the User agent profiles out there in out there land, hence leveraging the "good browser sniffer code" may not achieve the necessary outcome (really happy if I am wrong BTW)
What we need to be able to test for is the use of the iPad or iPhone browser (mobile safari) wihin the CF form environment and only call out the text box, rather than calling the getEditor function. The alternative is to test for desktop FF, IEx, safari, Chrome, opera etc. and display the WYSIWYG editor for them and the text box for all others.
Let me know if you need any more info.(happy to provide the entire form code in if necessary)
-anthony
Below is a piece of code I use in CF to leverage the inbuilt WYSIWYG editor via JFactory::getEditor();
By independently of Joomla I mean that Joomla is not up to date on all the User agent profiles out there in out there land, hence leveraging the "good browser sniffer code" may not achieve the necessary outcome (really happy if I am wrong BTW)
What we need to be able to test for is the use of the iPad or iPhone browser (mobile safari) wihin the CF form environment and only call out the text box, rather than calling the getEditor function. The alternative is to test for desktop FF, IEx, safari, Chrome, opera etc. and display the WYSIWYG editor for them and the text box for all others.
Let me know if you need any more info.(happy to provide the entire form code in if necessary)
-anthony
<div class="form_item">
<div class="form_element cf_textarea">
<div class="cfclear"> </div>
<?php
$editor =& JFactory::getEditor();
echo $editor->display( 'matchReport', '' , '80%', '300', '55', '20', false ) ;
?>
</div>
<div class="cfclear"> </div>
</div>
<div class="form_item">
<div class="form_element cf_text"> <span class="cf_text">Instructions: Upload a Picture for use in the Article (check info for max file size)</span> </div>
<div class="cfclear"> </div>
</div>
This topic is locked and no more replies can be posted.