This is a hard judgement to make, I don't know if its really possible to know which is best until you've tried both ways. So perhaps pick a direction and do a proof of concept for one page and see how it works. I would lean towards #1 so that you could re-use a lot more existing code, but there probably will be places where the HTML templates will need changes also, maybe even controllers. Many of the APIs only support read and not create/update/delete yet.
In a different turbogears app that I've worked on, we've used code from http://detectmobilebrowsers.com/ for detection. And if needed (but hopefully not) you can use a different template like `tg.decorators.override_template(self.index, 'jinja:other_template.html')` within an `index()` method for example. --- ** [tickets:#8093] Developing Mobile Web View** **Status:** open **Milestone:** unreleased **Created:** Mon Jun 20, 2016 12:40 PM UTC by Rohan Verma **Last Updated:** Mon Jun 20, 2016 12:40 PM UTC **Owner:** Rohan Verma Hello, As part of my GSoC project, I will be developing a mobile web view for Allura. I have thought about how to go about it but would love some suggestions on how to go about it. There are two ways to go about developing this: 1. Detecting it is a mobile/tablet screen and provide a different CSS file. This will be feature complete from the beginning. (Use existing templating engine) 2. Developing a seperate mobile website which we open if we detect a mobile viewport. This will not be feature complete and we will use API calls to asynchronously develop features. (Added benefit to this is that we improve the API) --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
