Re: Version 0.7.1-pre2
Thomas Hirsch
not enough, we might link to the current location on geohash.org
instead. I'm using this in the IRC channel currently.
Also: A bug. The expedition page was duplicated, i.e. the whole old
page appended to the edited version.
http://wiki.xkcd.com/wgh/index.php?title=2010-01-12_52_13&diff=198574&oldid=198573
I'll have to look into that later today.
Best regards,
Thomas
CaptainSpam
part is isn't working anymore. I thought I was feeding the same data
in that was coming out before, but I might be mistaken. I'm using the
XML interface via the API, which may be returning slightly different
data.
I guess it never showed up in testing on my end because the only
testing I did was on my private wiki, one which didn't have the
Expedition template, so it wasn't plugging it in. But once I added
the template in, I'm seeing the same problem.
I'll see what I can figure out, too, next time I have the chance.
Unless you can get it solved before then. :-)
On Jan 12, 9:27 am, Thomas Hirsch <thomas.hir...@gmail.com> wrote:
> The location stamps work nicely. If the coverage of openstreetmap is
> not enough, we might link to the current location on geohash.org
> instead. I'm using this in the IRC channel currently.
>
> Also: A bug. The expedition page was duplicated, i.e. the whole old
> page appended to the edited version.
>
> http://wiki.xkcd.com/wgh/index.php?title=2010-01-12_52_13&diff=198574...
Thomas Hirsch
> Unless you can get it solved before then. :-)
I have removed the section=0 parameter in the api call. That caused it
to replace only section 0 (i.e. everything above the first section
header) with the whole content of the new page, instead of replacing
the whole page.
Best regards,
Thomas
Thomas Hirsch
web interface is noticeable. That makes it much more usable with
unreliable connections.
CaptainSpam
> I have removed the section=0 parameter in the api call. That caused it
> to replace only section 0 (i.e. everything above the first section
> header) with the whole content of the new page, instead of replacing
> the whole page.
Oops. My mistake. I guess I misread that part of the API. That'd
also explain why it wasn't doing that before I added the template to
my test wiki; until I added the template, the pages had no sections.
The API is really useful in that regard. Since all what's being sent
is the page data and useful information about the page (and not the
rest of the design and such), it really does speed things up. The
only exception right now is the upload mechanism; that one isn't using
the API yet, since that's a 1.16 feature and the Geohashing Wiki is on
1.15. Fortunately, the cookies obtained from the API's login function
work on non-API uses.
Well, with this, we should be able to get 0.7.1 released soon. Thanks!
Thomas Hirsch
Yay!
I have made one more change:
The option "include local timestamp" now uses the system time on your
phone, if checked. It uses the wiki time stamp (~~~~~) if unchecked. A
time zone will always be provided.
I have some more suggestions:
- move the options "include local vs. wiki timestamp" and "include
location" to the settings. I don't think (anymore) that people will
have to change their opinion about that on a per-message basis. That
will leave a bit more space for message editing, too.
- the option "include me in the participant list" aka "I will be
there!". There are a few places where we could add this, and I'd like
to hear your opinion:
* As a checkbox below the message, like we used to do it for the options above.
* In the settings, in the form of "Add me to the participant list, if
I send a message."
These two would force you to actually send a message with details (and
maybe an estimated time of arrival). Possibly resulting in less false
claims.
* As a separate entry in the "Update wiki" menu.
That would encourage the immediateness of participation. Possibly
resulting in more false claims.
I would start tinkering in that general direction, and commit any
major changes into a branch.
CaptainSpam
> I have some more suggestions:
> - move the options "include local vs. wiki timestamp" and "include
> location" to the settings. I don't think (anymore) that people will
> have to change their opinion about that on a per-message basis. That
> will leave a bit more space for message editing, too.
I like that one. That sounds fairly simple, too; I can probably add
that in tonight at some point.
> - the option "include me in the participant list" aka "I will be
> there!". There are a few places where we could add this, and I'd like
> to hear your opinion:
>
> * As a checkbox below the message, like we used to do it for the options above.
> * In the settings, in the form of "Add me to the participant list, if
> I send a message."
> These two would force you to actually send a message with details (and
> maybe an estimated time of arrival). Possibly resulting in less false
> claims.
>
> * As a separate entry in the "Update wiki" menu.
> That would encourage the immediateness of participation. Possibly
> resulting in more false claims.
>
> I would start tinkering in that general direction, and commit any
> major changes into a branch.
While I like this idea, it might take a bit more thought to decide how
to do it. That we might put off until 0.7.2, but it's something
that'd be nice. In my opinion, I'd go towards automatically adding
yourself to the participant list via something in the settings screen.
CaptainSpam
Preferences, and I've removed the checkbox from the message editor.
On Jan 13, 12:05 pm, Thomas Hirsch <thomas.hir...@gmail.com> wrote:
CaptainSpam
Though I'd like to make a better About screen at some point, I think
what we've got is good to go. Unless anyone else turns up any serious
bugs, I'll push it out to the Market this weekend some time.
For 0.7.2, I'm going to start with making it behave better with phones
of different sizes, since I noticed that a co-worker with a smaller-
resolution phone can't download GHD from the Market, and my brother
and I now have higher-resolution phones (the Droid/Milestone and the
Nexus One, respectively). I've got some work to do. :-)
Thomas Hirsch
downward compatibility with building the app for android 1.5.
("invalid resource directory name") Is there a workaround or is it
just how things are meant to be?
CaptainSpam
The workaround should already be in place, actually. After the
multiple screen size support was added, the app should now only build
under Android 1.6 (or higher). However, since there's no 1.6-specific
API calls in the code, the manifest's minVersion attribute should
allow the app to be installed and run on 1.5 phones (assuming the
documentation is correct; I can only test this on the emulator, and
that was working last I knew).
1.5 can't understand the dpi and size-specific resource directories,
but the -v4 qualifiers should work around that.
Long story short: You can't build it for 1.5 anymore, but that
shouldn't be necessary.
Thomas Hirsch
> shouldn't be necessary.
I see. Thanks a lot for the details!