![]() Of course this requires diligence with updates, which have to be done manually. I've actually been doing something like this just using the "save as" feature of my browser, and editing the form action attribute of the page to give it a non-relative URL. I suppose that if skins are fairly easy to make, then a stripped down skin for the client might be in order, thought I'm not sure that would be necessary so long as the form elements are named consistantly between the skins. My idea is for the client to interface with the server just using the perfectly normal HTTP, just like all other user agents which communicate with Wikimedia so as to keep this as simple as possible and to avoid the range of possible bugs that can come from making drastic changes in server features. The client would probably need some kind of conflict resolution behavior as well. The commit function would either have to insist on an update first, or perhaps better, would be smart enough to do one automatically. While the pagename would pretty much obviously have to be the URL page name of the article. So if this command were called "wix" (a name pulled totally out of thin air) the user could type something like 'wix checkout pagename.wiki', or 'wix update pagename.wiki' or wix commit pagename.wiki'. What I have in mind at least for now is something kind of like the cvs client command line software, but with a much simpler set of functions and behaviors. I've noticed that there's been some discussion of this sort of thing on the Wikimedia meta site, but I think I would propose to do something a bit different (and hopefully simpler) than the stuff I've seen proposed there. The advantages would include the possibilities of working on a laptop, while actually traveling and of giving the traveler a choice of the full range of text editors. I've been thinking that it would be really nice to have a way to work on wikivoyage articles offline. The following bit was moved here from the Traveler's pub: This has already been done for wikipedia. The Aarddict project can easily be used to allow offline reading on many devices, including the N800, windows, linux, apple.Ī database dump would be all that is required. Is the HTML generated by the Wikimedia software viewable on mobile devices? This probably isn't necessary for offline reading, but perhaps it's a place to start? - (WT-en) Dawnview 02:43, (EST) This group should also consider the new class of devices dubbed internet tablets, like the Nokia N800. wikivoyage is already available in plucker format? - /ebook/.Why can't I simply take wget ( ) and make my offline copy? - (WT-en) Hansm 05:10, 2003 Nov 4 (PST)Ĭause it'd be very crude and take way too much space of your valuable PDA memory. I don't see what's the goal of this expedition. Yeah, I posted to the plucker users mailing list, and got some off-list responses along the lines of "that sounds cool". Oh, and if I do have a PDA it will definitely run Linux, so then I have to think of tweaking Plucker, which only runs on PalmOS for the moment (fortunately it's free software :). But I guess that there is room for some kind of cooperation between Wikivoyage (or even Wikimedia) people and Plucker developers. 49 Offline Wikivoyage: Available for every language as ZIMĭid somebody contact the Plucker developers already? I don't have a PDA myself (yet.), so I won't delve into this.48 Content erroneously posted in Wikivoyage:Tourist Office.47 New data for your smartphone or mashup.45 Click on a POI to open in your favorite Android navigation/GPS app.41 Android app released! Wikivoyage offline.40 OxygenGuide: Bring Wikivoyage offline on your smartphone. ![]() 37 OxygenGuide updated: first database since transition to Wikimedia!.35 Two great tastes that taste great together.34 Software tools for easy edit / offline. ![]()
0 Comments
Leave a Reply. |