I used this module (some) for 6.x, and it was absolutely perfect...
I'm really hopeful to see this push forward into D7 quickly. I've just started testing out the 7.x dev version, and most things seem "okay" at the moment. (haven't dug in too far)...
BUT... my biggest issue... is that the tool set here is limiting, and it could be possible to make this MUCH more powerful by integrating with the 7.x context/ctools setup so that the device detection is in a condition, and the theme switching is in a reaction.
I've recently built the Delta module that integrates with my Omega theme. Delta gives a contextual reaction so that when whatever condition is met, I can render a completely different layout via the SAME theme through contextual theme settings.
I'd love to see this workflow move into context (and can help if the feature is agreed upon) so that this moves to a more flexible implementation.
If device detection is in context as conditions, and the theme switching/other settings move into reactions, I think adoption would really grow as it would be possible to do MANY more things on mobile devices than mobile_tools currently allows for/has functionality for.
Thoughts?!?! I'd love to help with this progress if possible, but it would take a bit of a rewrite to integrate the way I see it.
Comments
Comment #1
twom commentedHi Himerus,
Thanks for this feedback. I am trying to find find some time to get the D7 version ready. However, I currently have not enough time to push it quickly.
Your idea sounds great, and I think that some rethinking of the Mobile Tools module for D7 is appropriate.
I'll see if I can setup a roadmap page, to bundle some of the ideas and look around for help. In meantime, if you feel the urge for writing a D7 patch, feel free! I'll commit it.
Thx,
Comment #2
himerus commented@twom
Thanks for the quick response... My work in theming (Omega theme, Delta module) has come a long way, and one of my next major focuses is on mobile theming, and this module was a cornerstone of a few mobile sites I did in D6...
My main thoughts for integration of Context simply comes from the fact that I "think" with the current implementation, the condition/reaction of mobile detection/theme switching is kind of locked in, and doesn't allow for a lot of flexibility without a lot more coding.
The ability to integrate a condition for Context that says if browser = iphone OR android, then a reaction that says use theme Cool Mobile Theme will give the ability for MANY modules/site builders to interact in a LOT of ways with just selecting the mobile condition from Context... even changing block/region visibility based on those conditions, etc.
My thought is that it could just make things easier long term, and more flexible for advanced implementations that no one has really even considered yet. (I'm only thinking of my one need w/the Delta module)
My plate is pretty full as well, but for me this type of implementation is definitely a priority somewhere on my contrib side, so I'll see what I can do, and dig into the code you have in place currently in the 7.x and evaluate how some of those items can be moved into Context... It may be that it doesn't have to be MOVED... but could ALSO implement via context... So your interface could stay the same/give the same options... BUT there could/would also be the transparent Context integration that fires in addition to your current implementations...
Not really sure there, and wont be until I can understand the underlying code, but I definitely will take a look, and report back when I can...
RE: A Roadmap... it would be awesome (when you have the time) to do a brain dump of where you'd like to see the module go so I (and others) can help there!
Comment #3
attheshow commentedThe context integration in version 6.x-2.3 is awesome. Thanks so much for adding this and for the great module twom!
Comment #4
twom commentedIn meantime Context is also present in D7, however it will need some testing!
Comment #5
minoroffense commentedComment #6
Blooniverse commentedWow, this seems to be a good development direction ('Context'). As I understand @himerus, this would transform 'Mobile Tools' into what it already is in its core: a detection module.
I find this approach much more appealing than having to decide: "Mobile Tools – Themekey – Spaces" vs "Omega – Context – Delta"!!!
If you need my service, please let me know (checking code, patching, general testing).
Comment #7
Blooniverse commented... a brief question: Wouldn't it be better to disconnect the submodule 'Mobile Tools Context' from its dependencies ('Spaces', 'Themekey', 'Purl')? Without these dependencies 'Mobile Tools' would be more flexible to use! Maybe users want to make use of it, but without installing these mentioned additional three modules?
Comment #8
joemoraca commentedmobile tools context + context + delta + omega seems to be the holy grail
Comment #9
dddbbb commentedI have to say I agree with the_phi's comment in #7. I currently only intend to use Mobile Tools for detection and for providing contexts for Context and/or Panels to work from - I'm sure I'm not alone.
The 3 currently required modules for Mobile Tools Context effectively ends up totalling 4 if you include the fact that Spaces in turn requires Features. That's 4 modules I wasn't planning on installing otherwise...
Comment #10
devin carlson commentedMarked #1108530: context integration? as a duplicate.
Comment #11
minoroffense commentedContext triggers for device groups are in place.
Comment #12
minoroffense commentedThe Context condition is now available in the "mobile_tools_context" module. You can set a context to be active when device groups are activated.