[eluser]Jonathan Ledbetter[/eluser]
xwero,
I'll admit that I have reservations about using CI's browser class, mostly from other people's experiences/frustrations with it. The big drawbacks I see with it is that it doesn't appear to have been updated for a long time (it still lists "Windows Longhorn"!), it lacks mobile recognition support for both browsers on my phone, and it doesn't mention Opera for Wii (or any other browser for standalone consoles)
anywhere. The only gaming console I saw was PSP (and possibly Nintendo DS, I don't have it in front of me). Also, I didn't just want to add Opera for Wii in one of the lists; it's not quite a normal browser, and it's not quite a mobile browser, it really just needs its own category.
That, and because I'm trying to target only a specific number of current devices, have led me to decide to forgo the browser class and roll my own quick-and-dirty helper function. Until CI catches up to the browser list game, I'm sticking with my own functions.
Your suggestion was actually what I was trying to say I'd do in option #3. That's the way I'm leaning, more for a code-saving standpoint, so that I only need to call models from a minimal number of controllers and controller methods.
However, from a curiosity (and possible adaptation) standpoint, my question remains: Is there a way for CI to reroute to different controllers automatically based on what my functions return? You could even substitute the browser class calls, as long as they can be interchanged in the example.
I look forward to your responses, and thanks again.