[Building Sakai] How to support proliferation of new tablets in CLE

[David Horwitz]

Just a point for people looking at making a feature 
available/unavailable it is far better to query the service (being WURFL 
or Mobile detect based) for capabilities rather than specific devices. 
Part of the fragility of the current use is that it ask "is this an 
iPhone" rather than "does this device support feature x".

D

On 01/09/2012 01:01 AM, Steve Swinsburg wrote:
> Hi Keli,
>
> The portal currently uses the WURFL library to detect mobile devices, however recent license changes means we cannot upgrade, so I am looking at switching it to an alternative project called Mobile Detect, which is based on MobileESP and available in the maven repositories. It is Apache2.
>
> https://jira.sakaiproject.org/browse/SAK-21334
>
> Once the code is cleaned up then tools will be able to check the mobile device easier, and via an entityprovider.
>
> cheers,
> Steve
>
>
> On 07/01/2012, at 11:42 AM, Keli Sato Amann wrote:
>
>> Hello,
>> We are running 2.6 locally, but we added the patch that suppresses the rich text entry of the fckeditor and replaces it with simple text entry that comes with 2.8. We have manually updated that patch to do this switch when it detects additional useragents (iphone, and now Android phones and iPad).
>>
>> I was hoping this also covered Android tablets, but we just tested it on a Nook and we still see the non-responsive rich text options. So we will have to manually update this to include the useragent for the Nook and I guess the Kindle Fire if we can find one to test.
>>
>> My questions are this:
>> 1) Is the rich text entry of the ckeditor (which I think comes with 2.9) supported on iOS and Android devices or will we need to continue this workaround?
>>
>> 2) If we have to continue this workaround, is there a different string we can search on that isn't quite so specific that would cover all iOS and Android devices so we can stop updating this?
>>
>> 3) We created another dependency: in Forums, we hid the Delete and Setting options for Topics so that they only show during a hover. We want to completely hide these options on touch devices (while it is possible to get this to display with a double click, this is confusing). So now we need to do the useragent check in two locations. Is there a way to maintain the approved list in just one location?
>>
>> I may not understand any of your answers, so I'm cc'ing Lydia ;-)
>>
>> Thanks,
>> Keli Amann
>> User Experience Specialist
>> Academic Computing Services
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"