#8093 Developing Mobile Web View

Rohan Verma


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)


Tickets: #8204


  • Dave Brondsema

    Dave Brondsema - 2016-06-22

    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.

  • Nozze foto

    Nozze foto - 2016-07-19

    Is SourceForce going also to be avaiable as mobile view?


    Last edit: Nozze foto 2016-07-21
  • Ingo

    Ingo - 2017-12-27

    I don't think that such a detection is necessary. A good and pragmatical alternative might be a floating layout. Beside some.finetuning it is mainly the widths which need to be changed.


Log in to post a comment.