Hi list,
I recently helped shepherd a new skin into Mediawiki;
https://www.mediawiki.org/wiki/Skin:Erudite
I would like to think it is perfect in every way, but one area it
hasn't had any love is making sure it works well on mobile devices.
To the best of my knowledge it shouldn't do anything particularly
heinous, but I don't have any such devices to test it on. If anybody
has a few minutes and could have a play, and see if anything could
be improved, please do and let me know on list.
A live example of it is at
https://www.dur.ac.uk/nick.white/erudite-demo/mediawiki-current/
which should have full editing etc rights enabled. It's a dummy
wiki, so add whatever you like.
Thanks in advance!
Nick White
<brion> and <tfinc> told me that the "Wikimedia Mobile" product in
Wikimedia Bugzilla is rather dead and that bugs should be reported
either against "Wikipedia App"/"Wiktionary App"/"WikiLoves Monuments
Mobile" for apps, or "MediaWiki extensions" -> "MobileFrontend" for the
mobile website.
Is this general consensus? (Silence means agreement.)
If so:
1) There are 56 open tickets that need retriaging
(your help is welcome):
https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&resolution…
2) I am going to close "Wikimedia Mobile" product for new bug
entries, and edit its product description to state where to
file tickets instead.
Thanks for your input!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
I noticed we now have a mf-enwp.css for style overrides for english
wikipedia, which has been split off from mf-hacks.css.
Can't we just move this to Mobile.css on enwiki?
--
Yuvi Panda T
http://yuvi.in/blog
You may enjoy this piece of feedback given on the WLM survey :)
> What was the main obstacle, if any, for you to participate in the
> competition? WLM Android app drains my phone battery too fast.
> Please write down any further comments or suggestions about Wiki Loves
> Monuments: Best thing is the phone app, which should be further
> improved and expanded to handle articles that are not on monument lists.
I'm trying to build a version of WikipediaMobile and adapt it to be a
generic MediaWikiMobile app (https://github.com/hexmode/MediaWikiMobile)
I started by taking out all the Wikipedia-specific references that I
could find and thought wouldn't be too harmful.
After that, I tried "ant release" but ran into some problems. The build
wouldn't work, but I was able to get it to work after some searching
(see https://github.com/hexmode/MediaWikiMobile/commit/abc39e5).
I haven't had the chance to try it yet (this is my first Android app),
but I was wondering if this should be a change made in the main code.
Nark.
--
http://hexmode.com/
Any time you have "one overriding idea", and push your idea as a
superior ideology, you're going to be wrong. ... The fact is,
reality is complicated -- Linus Torvalds <http://hexm.de/mc>
Hello everyone!
Wikipedia for Android v1.3 beta2 was released to Google Play today. If
you already have the app, you'll be offered an update soon. If you
don't, you can install it from:
https://play.google.com/store/apps/details?id=org.wikipedia.beta
This is a relatively minor upgrade over beta1. The important changes were:
- RTL fixes
- Fix for references showing up twice
- Fix for not being able to type the character '9'
Since beta1 (which featured much faster page loading) has been out for
a few months, I'm hoping to push this release to stable with minimal
changes if no issues are found during testing. So do test and report
back!
Thanks!
--
Yuvi Panda T
http://yuvi.in/blog
It's difficult to promote events like:
http://uk.wikimedia.org/wiki/RBSA_Backstage_Pass
when mobile visits to that URL are redirected to:
http://uk.m.wikimedia.org/wiki/RBSA_Backstage_Pass
and errors are returned for all http://uk.m.wikimedia.org pages.
I'm told that this " affects all *.wikimedia.org addresses (at least
the ones of chapters hosted by the WMF);"
I'm assured that this has been raised with the devs responsible more
than once previously, but there's still no sign of a fix.
Can someone do something to resolve the matter, urgently, please?
--
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
> Thanks for the links. I always thought of using css media queries as
> cheating somehow, but I suppose it makes sense to create actually
> attractive and useful designs which can scale down elegantly.
Not at all! The most ideal way to use them is to design a site for
mobile, then using media queries to detect larger screen sizes and
adapt those for desktop - this will give you support for older mobile
browsers that do not support media queries. All modern browsers
support them and if you want to support IE8 and less you can resort to
using conditional if statements to serve non-media query based css.
>
> As for simulating a mobile device, thanks for the advice. I'm
> running Debian Squeeze at the moment, so I'll have to update my
> Chromium to get the developer tools with exciting device metrics
> options - thanks for pointing that out.
You'll probably be fine with Chrome developer tools. There are lots of
useful features tucked in it now for mobile development.
I'd also suggest testing in:
http://iphone4simulator.com/
You'll probably only need the simulator if you encounter very device
specific bugs.