Sueetie is one of the few if not the only Online Community Application that supports mobile devices across all applications: blogs, media gallery, forums and wiki. This Patterns and Origins document describes the mobile architecture used in Sueetie.
Sueetie Framework Mobile Architecture: Patterns
What follows is the top-level mobile architecture used by the Sueetie Framework and shared with individual Sueetie applications. See the following for information about mobile architecture changes for the core Sueetie applications.
Dynamic Theming at the Heart of Sueetie Mobile
Sueetie Mobile displays one of two themes based on the user device: Sueetie Current Theme or Sueetie Current Mobile Theme. A MobileDevices SueetieConfiguration Core property is located in the Sueetie.config file. Using a RegEx match statement, if select strings located in the SueetieConfiguration.Core.MobileDevices is found in the browser User Agent description, the Sueetie Current Mobile Theme is used, along with its specific pages, master files and all themed objects.
Here is the current MobileDevices property.
MobileDevices="(android|iphone|ipod|nokia|sonyericsson|blackberry|samsung|sec\-|windows ce|motorola|mot\-|up.b|midp\-)"
Because we are using dynamic theming based on the device we do not need to employ a http://mobile.sueetie.com strategy, with two different urls per page. All urls are shared identically between mobile and desktop devices. Dynamic theming reduces duplication, improves SEO reporting and prevents any SEO penalties of identical content on multiple URLs.
Chiclet: Default Sueetie Mobile Theme
Chiclet is the name of the Sueetie Mobile Theme. It is the default mobile theme (coming) in Sueetie 1.4 along with the default Lollipop desktop theme. Chiclet has the contents of any other Sueetie theme as you see here.
The Sueetie UrlRewrite HttpModule for Full Theme Independence
With the release of Sueetie 1.3 we had a rock solid global theming model in place with nearly complete independence of theming objects, specifically, a model that employed unique master pages, style sheets and user controls for each theme. Yet there was still sharing of certain pages like the site home page, login page, aggregate blogs page and a few others. It was clear that to provide dual mobile and desktop support that we could no longer share pages either. So a new SueetieUrlRewrite HttpModule was created.
SueetieUrlRewrite reads the contents of the urls.config file which is cached. Here is a working urls.config file excerpt.
<?xml version="1.0"?>
<urls>
<!-- common -->
<!-- rewrittenurl denotes location typically in /themes/CurrentTheme of physical page -->
<url name="home" path="/default.aspx" rewrittenurl="/themes/{0}/pages/default.aspx" />
<url name="contact_us" path="/blog/contact.aspx" />
<url name="search_home" path="/search/default.aspx" />
<!-- members -->
<url name="members_login" path="/members/login.aspx" rewrittenurl="/themes/{0}/pages/login.aspx" />
<url name="members_logout" path="/members/logout.aspx" />
<url name="members_myaccountinfo" path="/members/myaccountinfo.aspx" />
<url name="members_register" path="/members/register.aspx" rewrittenurl="/themes/{0}/pages/register.aspx" />
<url name="members_message" path="/members/message.aspx" rewrittenurl="/themes/{0}/pages/message.aspx" />
<url name="members_activate" path="/members/activate.aspx" rewrittenurl="/themes/{0}/pages/activate.aspx" />
SueetieRewrite inspects the url path of the current request. If it matches any of the paths in urls.config and that url has a rewrittenurl property, a context.RewritePath() loads the rewrittenurl page. The pages in the original path locations for those urls are treated as IIS placemarkers with little more than a note on where to find that file's actual location.
Here is a screenshot of the new /theme/THEME/pages folder and some of the site pages which are no longer shared. Keep in mind that because SueetieRewrite is used globally across a Sueetie Community, we'll be seeing it used in other applications as well. In other words, both the path and rewrittenurl can exist anywhere needed to break-out shared files to their specific theme's /pages location.
All pages with the exception of the root default.aspx page share codebehind in the Sueetie WebApplication CodeFiles area, though you can of course create your own codebehind files per theme.
Sueetie Mobile Architecture: Origins
Sueetie Mobile Architecture was based on that employed in BlogEngine.NET. Rather than duplicate that content here, please see
Mobile BlogEngine.NET Architecture.