Fair enough. A plugin allows us to iterate a little faster to start with.

I don't think I want an HTTP request class with isMobile since HTTP
requests don't have tiny screens.
On Mar 26, 2013 11:08 AM, "Cash Costello" <notifications@github.com> wrote:

> In engine/lib/views.php:
>
> > @@ -1465,5 +1465,42 @@ function elgg_views_boot() {
> >  	}
> >  }
> >
> > +/**
> > + * User agent detection
> > + *
> > + * @since 1.9
> > + */
> > +function elgg_is_mobile(){
>
> I'd rather not throw in arbitrary classes without thinking about the
> design for handling HTTP requests. For example, do we want an HTTP request
> class that has a isMobile() method? How about something like
> https://github.com/serbanghita/Mobile-Detect
>
> Overall, I'd rather see this developed as a plugin and we identify the
> pain points along the way and fix them in core. Eventually, we pull this
> whole thing into core. Otherwise, I fear we end up with a partial
> implementation that we either ship (not again!) or strip out before the 1.9
> release.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Elgg/Elgg/pull/5284/files#r3536682>
> .
>