2011/11/25 Tomasz Finc <tfinc(a)wikimedia.org>rg>:
On Thu, Nov 24, 2011 at 2:41 AM, Strainu
<strainu10(a)gmail.com> wrote:
Thanks!
It's a shame we have to go through some
not-so-nice hacks to make the
content for mobiles different than the one for desktops. Perhaps the
architecture is too iPhone/American oriented? Not all mobile users
Are XML DOM parsers that American and iPhone centric? I sure hope not as
the rest of the Internet is going to have to be informed ...
Somehow, I find myself unable to laugh at that joke. You quoted that
out of context, the question goes together with the following phrases.
Plus, the XML DOM parser is the implementation of the architectural
decision, which was to parse the HTML and not the wikitext.
have unlimited traffic. Many people around me
disable images on mobile
internet.
Yup, and thats why we've had the option to disable images for many months
now. It lowered the payload by half. Lots of people use it. If you see
other data heavy features on pages that we can get rid of then please file
a bug. Were always eager to lower our payload.
Disabling images by the user is cool, but it leaves behind references
to images, which might make the text sound a little awkward. All
images in the ro.wp main page are referenced in the text. Removing
them cripples the page. This is why we had a custom webpage for mobile
and we would like to be able to use that as we go forward.
Hope you will give that some serious thought when the time comes.
We already have and would love to drop it down even more. Next interesting
step would actually be to load sections only when people want them. That'll
drop down the payload even more.
Turn on the webkit network profiler and let us know whats really slowing us
down.
Isn't webkit specific to the iPhone? I was not aware it was available
on normal platforms.
As to suggestions on how to drop the load, it's the same as above: let
the users do the micromanagement of the mobile sites, they're much
better than you (i.e the WMF, not you personally) at this.
Going back to the original issue, is there any other way to display
something else for the mobile site than including the divs on the main
page and making them invisible from the desktop site by CSS and JS?
This is what I called "an ugly hack" because it might very well fail
for text browsers or screen readers.
Thanks,
Strainu