Hi,
Today i tried to use the QRpedia codes form my android phone. the QR code
scanner app asked me to open the link on the Wikipedia Android app or on
the browser. When i select the wikipedia app, the app shows me an empty
page, but the browser can open the link properly.
I think it would be great if is it possible to update the Wikipedia app, to
open the qrpedia links.
regards
user:nasir8891
--
*Nasir Khan Saikat <http://profiles.google.com/nasir8891>*
Hi,
Yesterday on IRC I invited a few people to start writing an FAQ about
the Wikipedia mobile app, with the hope that it will make using the
app easier, and will also make the feedback process more efficient.
Quite a lot was already written by :
http://etherpad.wikimedia.org/mobile-users-faq
Please, take a look there, correct and enhance the current answers
(search for TODO) and add more questions if I forgot anything.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Some new approaches to search:
The article below is about Handwrite, a new way to enter search terms in
Google.
This is significant in at least two respects: 1) It helps solve the
touchscreen typing fiasco that has proliferated on iPhones and Android
devices, and 2) it makes it even easier to search in Google relative to our
own search.
Why they (or some third party) can't add arrow keys in the onscreen
keyboard is beyond me...
Handwrite works fairly well, in my limited experience.
Also worth noting is AskWiki, an app that was originally released in
Germany. It features voice recognition and the following logic:
The focus is to find short and smart answers for direct questions, e.g.
"Wann wurde Einstein geboren?" (When was Einstein born?) or "Wer ist der
Leiter von BMW?" (Who's the head of BMW?).
This is done by analyzing the tables and subchapter headlines that appear
in Wikipedia articles.
This App uses Google Speech Recognizer for recognition of voice and the
database of Wikipedia. AskWiki runs on the mobile phone without using an
additional server.
**
The Handwriting is on The Wall for Google Mobile
Search<http://feedproxy.google.com/~r/MobileMarketingWatch/~3/1LLZ_jxEBp0/?utm_sou…>
Posted: 27 Jul 2012 01:37 PM PDT
[image: The Handwriting is on The Wall for Google Mobile Search]Internet
search giant Google is pushing its mobile search capabilities to new
heights this week.
As announced by the company on the Official Google
Blog<http://googleblog.blogspot.com/2012/07/make-your-mark-on-google-with-handwr…>,
there’s a new way for you to interact with Google: Handwrite for web search
on mobile phones and tablets.
Say you’re standing on a busy street corner, in a bumpy taxi ride, talking
with a friend, or sitting on the couch with your tablet. Handwrite enables
you to search by just writing letters with your finger most anywhere on
your device’s screen—there’s no keyboard that covers half of the screen and
no need for hunt-and-peck typing.
To get started, Google says, simply go to Google.com in your mobile
browser, tap on “Settings” at the bottom of the screen and enable
“Handwrite.” Refresh the homepage and then the feature is all yours to
enjoy.
Handwrite has, for the time being, been enabled for iOS5+ devices, Android
2.3+ phones and Android 4.0+ tablets, with support offered in 27 languages.
For more tips and tricks on how to use Handwrite, check out Google’s Help
Center guide here<http://support.google.com/websearch/bin/answer.py?hl=en&p=sbw_help&answer=2…>
.
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
On both the mobile website and in our Android app (both current
release and latest beta) I see wide tables truncated. For example, the
climate table on <http://en.m.wikipedia.org/wiki/Washington,_D.C.>,
where I can only see up to June. (on the same article, even the
right-hand end of the infobox is missing).
I haven't seen this discussed previously; and it's such a significant
loss of content that I think resolving it should be a high priority.
I'm using an HTC Desire HD, with the default browser.
--
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
On Fri, Jul 27, 2012 at 8:47 AM, Jon Robson <jdlrobson(a)gmail.com> wrote:
> This would be best answered by Brandon.From a personal point of view if the
> mobile site still looks like a mobile site in a desktop browser at the
> start of next year I will be somewhat disappointed with myself.
+1
> I personally believe that mobile is the likely method for accelerating
> athenas development as there are less blockers to do that.
We should be looking at Athena (and other projects like it) as
guidance for how were going to approach contribution projects on
mobile. Our focus for the next year is to not just grow the readership
base but to also grow the contributor base. We've never had as many
eyes on Wikipedia as before who can't contribute. Mobile users can't
be second class citizens within the Wikimedia projects. We have to
build all new pipelines on mobile devices to make this happen. These
contributor methods may look drastically different then their desktop
counterparts.
Responsive design is an interesting technique for layout but it breaks
down for functionality. A mobile phone, a tablet, and a desktop/laptop
are used very differently. Mimicking the exact same functionality
means your failing to understand what's best for each device.
> A lot of the existing bottle neck from my perspective is due to a lack of
> volunteer developers in the many mobile projects which slows important
> things like this down. Aside from the new design we are also planning some
> cool stuff for Wiki loves monuments with image uploading via mobile phones
> to commons. Poke me off list if you are keen to give time/expertise to help
> accelerate important initiatives like this.
I'm going to re-iterate what Jon said here. We have numerous projects
going on now and we've been actively mailing, blogging, and tweeting
to get new testers/developers/etc. Were always eager to get more
people involved. If you need to catch up with what were working on
just check the mobile projects pages.
http://www.mediawiki.org/wiki/Mobile
--tomasz
Ok, good feedback. To some degree this is determined by the admins of each
language, though in English we exercised some discretion.
Copying mobile-l to see if this generates more discussion.
Phil
On Mon, Jul 16, 2012 at 6:51 PM, Imzadi1979 <imzadi1979(a)gmail.com> wrote:
>
> On Jul 16, 2012, at 2:02 PM, Philip Chang wrote:
>
> Thanks for your feedback. It was a conscious choice to include only TFA
> and ITN, because of the restrictions of mobile screens.
>
> Do you feel strongly about any of the other content you mentioned?
>
> Phil
>
>
> On Mon, Jul 16, 2012 at 4:55 AM, Imzadi1979 <imzadi1979(a)gmail.com> wrote:
>
>> Just a quick comment, but the display of the Main Page only shows TFA and
>> ITN. What about DYK, OTD, TFL and TFP?
>>
>> -Imzadi1979
>> _______________________________________________
>> Mobile-feedback-l mailing list
>> Mobile-feedback-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-feedback-l
>>
>
>
>
> --
> Phil Inje Chang
> Product Manager, Mobile
> Wikimedia Foundation
> 415-812-0854 m
> 415-882-7982 x 6810
>
>
> Well, that's only 40% of the sections of the real Main Page (33% on
> Mondays). I'm sure the people who work hard to get TFP and TFL would be
> upset knowing that their hard work is only visible on computers and
> third-pary apps, not the one app that carries the WMF "seal of approval".
> Sorry, but I don't buy the "restrictions of mobile screens" argument when
> Wikipanion or Wikiamo, two apps I downloaded before the "official" app was
> available, show the whole Main Page. In short, the Main Page isn't the Main
> Page without all of its sections. The other apps don't display it as
> gracefully as possible, but they do show all of the sections.
>
>
> Imzadi1979
> imzadi1979(a)gmail.com
>
>
>
>
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
On Sat, Jul 21, 2012 at 2:04 AM, Derk-Jan Hartman <d.j.hartman(a)gmail.com>wrote:
>
> On 17 jul. 2012, at 21:23, Jon Robson wrote:
>
> > The way we deal with main pages on mobile is a big mess in my opinion.
> > It also seems during Wikimania that various people share my view on
> > this. We should show the same content on mobile as on desktop and stop
> > special casing it (There's a bug about this -
> > https://bugzilla.wikimedia.org/show_bug.cgi?id=30405)
>
> Agreed
>
> > I think the problem here is we'd need to clean up every MediaWiki
> > homepage in existence so that they do not use inline styles and have
> > mobile specific styles as otherwise if we stop special casing the main
> > page these pages will appear broken.
>
> Yes this is the problem.
>
> > I would suggest we
> > 1) set a deadline for a switch over where we stop the special casing
> > on the main page - we can work together during that day to ensure
> > pages are mobile ready 2) we change the code so that a querystring
> > specialcase=no shows what the main page will look like after the
> > switchover
> > 3) community works together to move inline styles into a stylesheet
> > e.g. MediaWiki:Common.css and alter homepages
>
> I don't see this as a requirement. We just need to provide alternate CSS
> and HTML layout (without fundamentally breaking IE6) and it needs to be
> implemented.
I'll rephrase this. " community works together to make homepage styles
mobile friendly"
The problem is that we currently use 50% width boxes and float them on the
home page. We **cannot** adapt this for mobile without using stylesheets
rather than inline styles... Currently there is already a mobile proof
definition in MediaWiki:Common.css for these kind of layouts that we can
reuse.
> I still don't agree with your comments on removing inline styling. If we
> move all inline styling we have on en.wp, we will have a style file of over
> 1 MB easily. We need to be more sensible about it.
Derk I completely agree with your concerns. My continuous moans about
inline styling are simply that we use inline styles rather than stylesheets
/ style tags which mean we currently mix content with styling and prevent
ourselves from doing things
>
> Perhaps we need transcluded internal stylesheets for these kinds of pages,
> so only pages that need this css get this css.
>
Exactly. However at the current time there is no mechanism for this - hence
why I suggested MediaWikiCommon.css as a potential location for these
styles for the time being - as this is the only place where we could do it
in the current setup. As a side note could we imagine adapting resource
loader so that we can use annotations to only serve certain to rules to
specific pages? e.g. * @only:Category:Portal */
--
Jon Robson
http://jonrobson.me.uk
@rakugojon
New app from the mobile team!
---------- Forwarded message ----------
From: Maarten Dammers <maarten(a)mdammers.nl>
Date: Sun, Jul 15, 2012 at 2:26 PM
Subject: [Wiki Loves Monuments] WLM Mobile app alpha3
To: Wiki Loves Monuments Photograph Competition
<wikilovesmonuments(a)lists.wikimedia.org>
Cc: Yuvi Panda <yuvipanda(a)wikimedia.org>
Hi everyone,
Thanks to the hard work of the mobile team the first Wiki Loves
Monuments mobile app is available now. The application works on your
android phone (not iphone yet) and is in alpa state. Alpha state means
that it's far from finished yet, but ready for people to start testing
with it. You can download the app from
https://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feed…
. That's also the place to leave feedback about the application.
Have fun and I hope you'll like it!
Maarten
_______________________________________________
Wiki Loves Monuments mailing list
WikiLovesMonuments(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikilovesmonumentshttp://www.wikilovesmonuments.org
--
Yuvi Panda T
http://yuvi.in/blog
@Brion, try to open the link of the QR code in the browser not the app, and
the article will be opened.
thanks
nasir
On Sun, Jul 22, 2012 at 12:20 PM, Brion Vibber <brion.vibber(a)gmail.com>wrote:
> That qr code does not contain a Wikipedia link; it links to en.qrwp.org.
>
> This presumably redirects to Wikipedia, but wouldn't be recognized itself
> as a URL that the app can handle.
>
> -- brion
> On Jul 20, 2012 3:53 PM, "Philip Chang" <pchang(a)wikimedia.org> wrote:
>
>> Interesting - thanks for your feedback. I'll open a bug. In any case, we
>> have to consider how prevalent this use case is.
>>
>> Any other opinions out there? Just to be clear, QRpedia is great, it's
>> just that we have limited resources and must prioritize tasks.
>>
>> Phil
>>
>>
>> On Fri, Jul 20, 2012 at 10:57 AM, Nasir Khan <nasir8891(a)gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Today i tried to use the QRpedia codes form my android phone. the QR
>>> code scanner app asked me to open the link on the Wikipedia Android app or
>>> on the browser. When i select the wikipedia app, the app shows me an empty
>>> page, but the browser can open the link properly.
>>>
>>> I think it would be great if is it possible to update the Wikipedia app,
>>> to open the qrpedia links.
>>>
>>> regards
>>> user:nasir8891
>>>
>>> --
>>> *Nasir Khan Saikat <http://profiles.google.com/nasir8891>*
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mobile-l mailing list
>>> Mobile-l(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>>
>> --
>> Phil Inje Chang
>> Product Manager, Mobile
>> Wikimedia Foundation
>> 415-812-0854 m
>> 415-882-7982 x 6810
>>
>>
>> _______________________________________________
>> Mobile-l mailing list
>> Mobile-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
--
*Nasir Khan Saikat <http://profiles.google.com/nasir8891>*
The way we deal with main pages on mobile is a big mess in my opinion.
It also seems during Wikimania that various people share my view on
this. We should show the same content on mobile as on desktop and stop
special casing it (There's a bug about this -
https://bugzilla.wikimedia.org/show_bug.cgi?id=30405)
I think the problem here is we'd need to clean up every MediaWiki
homepage in existence so that they do not use inline styles and have
mobile specific styles as otherwise if we stop special casing the main
page these pages will appear broken.
I would suggest we
1) set a deadline for a switch over where we stop the special casing
on the main page - we can work together during that day to ensure
pages are mobile ready 2) we change the code so that a querystring
specialcase=no shows what the main page will look like after the
switchover
3) community works together to move inline styles into a stylesheet
e.g. MediaWiki:Common.css and alter homepages
4) we turn of the special casing on the deadline date
5) we deal with broken main pages on a case by case basis.
I've added a note saying the above here:
http://www.mediawiki.org/wiki/Deprecating_inline_styles#Deprecating_inline_…
If this seems like a good course of action I'm happy to coordinate.
Please reply suggesting how much of a timeframe for such a switchover
would be necessary and of course speak up if you object strongly.
Feel free to forward to other mailing lists that make sense.
On Mon, Jul 16, 2012 at 7:09 PM, Philip Chang <pchang(a)wikimedia.org> wrote:
> Ok, good feedback. To some degree this is determined by the admins of each
> language, though in English we exercised some discretion.
>
> Copying mobile-l to see if this generates more discussion.
>
> Phil
>
>
> On Mon, Jul 16, 2012 at 6:51 PM, Imzadi1979 <imzadi1979(a)gmail.com> wrote:
>>
>>
>> On Jul 16, 2012, at 2:02 PM, Philip Chang wrote:
>>
>> Thanks for your feedback. It was a conscious choice to include only TFA
>> and ITN, because of the restrictions of mobile screens.
>>
>> Do you feel strongly about any of the other content you mentioned?
>>
>> Phil
>>
>>
>> On Mon, Jul 16, 2012 at 4:55 AM, Imzadi1979 <imzadi1979(a)gmail.com> wrote:
>>>
>>> Just a quick comment, but the display of the Main Page only shows TFA and
>>> ITN. What about DYK, OTD, TFL and TFP?
>>>
>>> -Imzadi1979
>>> _______________________________________________
>>> Mobile-feedback-l mailing list
>>> Mobile-feedback-l(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-feedback-l
>>
>>
>>
>>
>> --
>> Phil Inje Chang
>> Product Manager, Mobile
>> Wikimedia Foundation
>> 415-812-0854 m
>> 415-882-7982 x 6810
>>
>>
>> Well, that's only 40% of the sections of the real Main Page (33% on
>> Mondays). I'm sure the people who work hard to get TFP and TFL would be
>> upset knowing that their hard work is only visible on computers and
>> third-pary apps, not the one app that carries the WMF "seal of approval".
>> Sorry, but I don't buy the "restrictions of mobile screens" argument when
>> Wikipanion or Wikiamo, two apps I downloaded before the "official" app was
>> available, show the whole Main Page. In short, the Main Page isn't the Main
>> Page without all of its sections. The other apps don't display it as
>> gracefully as possible, but they do show all of the sections.
>>
>>
>> Imzadi1979
>> imzadi1979(a)gmail.com
>>
>>
>>
>
>
>
> --
> Phil Inje Chang
> Product Manager, Mobile
> Wikimedia Foundation
> 415-812-0854 m
> 415-882-7982 x 6810
>
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
--
Jon Robson
http://jonrobson.me.uk
@rakugojon