I get a network error when I try to edit on the Android app, and on moble
web only a small section loads in the edit window of the Signpost article I
want to edit, but I can read articles ok. Did something break for mobile
editing? Thanks, Pine
With Brion's help I now have symbolicated crash reports!
Based on my airport session this afternoon we have another crash fix patch
already merged and one more which we'll test on old iOS 6 devices over the
next few days :)
These crashes are going down!!!
Adam: Whilst we standardise on template languages we need to
distinguish between the types of template languages that currently
exist in the MediaWiki world e.g. handlebars and hogan
https://gerrit.wikimedia.org/r/149360 is in the code review queue and
basically makes it mandatory to include a template language file
extension (previously it would default to hogan when none was
specified).
Basically you have to rename all your template files from having a
.html extension to .hogan and update the ResourceLoader resource
modules.
Mobile has already done this as have Flow.
I think Zero is the only other extension that uses them and I'm keen
not to break it.
Next steps would be to get Gabriel's knockoff template language
integrated into the Mantle extension and allow extensions to give it a
go.
That then gives us a clear path to migrating this to core once we've
decided on a standard template language.
We got initial crash logs from Apple this morning -- it looks like the top
crasher is a failure in DownloadSectionsOp when creating a dictionary with
the downloaded info. Most likely something is coming up null in some corner
case we're not catching, and it should be failing out before that
gracefully.
-- brion
I stumbled upon genymotion.com when reading through this month's 'tech
radar' [0] put out by Thoughtworks. Anybody have experience with it?
Supposedly it's a fast android emulator that is intended to make it easier
to test against the fractured ecosystem. Looks like they offer a free
license for non-commercial use, though the feature set is not as robust as
their other license options.
[0] http://www.thoughtworks.com/radar/#/
--
Arthur Richards
Team Practices Manager
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hi everyone,
I just reviewed the work on wrapping up disambiguation and page issues into
buttons in the interface. I think we need to iterate more before it's ready.
Some thoughts on page issues:
- The "Page issues" dialogue that's opened up is a little bit large.
Ideally it'd be pretty much full screen, but there'd be just enough space
around the edges that I can tap outside it to close it without having to
resort to using the back button.
- Having just an icon is confusing for page issues. It's not clear what
a little blue flag means. Let's put "Page issues" next to the icon inside
the button.
Some thoughts on similar titles:
- The copy of "Similar titles" is ambiguous and doesn't adequately
convey the interaction that results from pressing it. I know we want to
keep it short, but right now it's not getting the point across.
- The interaction of the button itself also proved to be a little
problematic. When I place myself in the shoes of the user, and tap it with
curiosity, I'm flung to another page and I'm not really sure what happened.
It's quite jarring. It's not easy for me to connect "X (Disambiguation)"
with the "Similar titles" button I pressed.
Generally:
- The colouring of the buttons, in blue, makes them really stand out.
The colouring of the rest of the interface there, in black, really brings
those buttons to the foreground. I think this has made them too prominent.
These points are mostly raising more questions than they're answering, so
we'll still need to figure out solutions to the points.
Overall, I like the direction we're going with these features. They're
really bringing the content to the forefront of the experience. But they're
not quite ready yet. Let's keep iterating. :-)
Thanks,
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
Hi all,
I have some requests.
* Full text search functionality
* Compatibility with Signpost front page template
* Support interwiki linking such as to Meta
* Condense the options panels from the left and right hamburger icons to a
single icon
* More emphasis on encouraging people to edit
* VisualEditor fuctionality
Thanks,
Pine