Thanks Jerad! That's good to know. It looks like there might be a way to turn off WYSIWYG on mobile devices and enable BUEditor without changes to the two modules. It would be a pretty hacktackular method of invoking a custom handler for textarea and weighting the module heavier than BUEditor and TinyMCE and then putting the teaser element back in on a form_alter for mobile devices. I can see what I'll be playing with today. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 11/3/2010 9:05 AM, Jerad Bitner wrote:
FWIW, we use BUEditor on Lullabot.com and it works really well on an iPad.
On Wed, Nov 3, 2010 at 6:53 AM, Daniel F. Kudwien <news@unleashedmind.com <mailto:news@unleashedmind.com>> wrote:
> However a better solution would be in Drupal to disable > Wysiwyg on iOS devices and enable BUEditor. That's actually > something I need to work on myself over the next couple of > days for a client.
Limiting editors to media queries and/or dynamically switching to a more suitable editor per user agent sounds like an ideal use-case for the Wysiwyg module. BUeditor is not supported yet, but markItUp is very similar (and much more bullet-proof, AFAICT).
Thanks for sharing this idea! Would be happy to discuss details and required steps in Wysiwyg's queue.
sun
-- ~Jerad Bitner Lead Developer and Drupal Trainer at Lullabot http://lullabot.com | http://sirkitree.net | http://jeradbitner.com