My favorites | Sign in
Logo
                
Details: Show all Hide all

Today

  • 22 hours ago
    issue 3 (Crash on Moto CLIQ) Status changed by captainspam   -   Sweet. That'll be in the next version, once we've got wiki features ironed out. Thanks!
    Status: Fixed
    Sweet. That'll be in the next version, once we've got wiki features ironed out. Thanks!
    Status: Fixed
  • 22 hours ago
    issue 3 (Crash on Moto CLIQ) commented on by jebler   -   Very nice. I see a blue dot, with an a circle around it to indicate accuracy. I think we can call this fixed.
    Very nice. I see a blue dot, with an a circle around it to indicate accuracy. I think we can call this fixed.

Yesterday

  • 37 hours ago
    issue 3 (Crash on Moto CLIQ) commented on by captainspam   -   Oops. My mistake, I wasn't defining a value right (or, well, at all), and it was clipping out the indicator by accident. But this oughta fix it. Now in SVN r298.
    Oops. My mistake, I wasn't defining a value right (or, well, at all), and it was clipping out the indicator by accident. But this oughta fix it. Now in SVN r298.
  • 37 hours ago
    r298 (Oops. My mistake, I was never really defining mIndicatorHei...) committed by captainspam   -   Oops. My mistake, I was never really defining mIndicatorHeight, so if the accuracy was less than the size of the indicator icon, it was getting clipped out.
    Oops. My mistake, I was never really defining mIndicatorHeight, so if the accuracy was less than the size of the indicator icon, it was getting clipped out.
  • 42 hours ago
    issue 3 (Crash on Moto CLIQ) commented on by jebler   -   Almost fixed, it doesn't crash anymore. However when I turned my gps on the my location indicator shrank and (occasionally) vanished. I found that at AutoZoomingLocationOverlay.java:245 the variable radius would sometimes reach zero, no circle drawn. If you bypass the checks and force mBugged = true you should be able to see this. I added: if(radius < 2)radius=2; But that is still pretty small. 3 or 5 might be better minimum radius value.
    Almost fixed, it doesn't crash anymore. However when I turned my gps on the my location indicator shrank and (occasionally) vanished. I found that at AutoZoomingLocationOverlay.java:245 the variable radius would sometimes reach zero, no circle drawn. If you bypass the checks and force mBugged = true you should be able to see this. I added: if(radius < 2)radius=2; But that is still pretty small. 3 or 5 might be better minimum radius value.
  • 45 hours ago
    r297 (Fixed a bug where MainMap would spin endlessly if the user i...) committed by captainspam   -   Fixed a bug where MainMap would spin endlessly if the user is on the 30W line (actually, any 29W graticule), has Nearby Points turned on, it's a day when the 30W and not-30W hashes are different, and the user doesn't have yesterday's stock in the cache. Put simply, I forgot to increment mNextNearbyY in that loop when it comes across the zero point. Oops. Also fixed a slight bug where it drew multiple flags on the same nearby point, which I think is a bit wasteful.
    Fixed a bug where MainMap would spin endlessly if the user is on the 30W line (actually, any 29W graticule), has Nearby Points turned on, it's a day when the 30W and not-30W hashes are different, and the user doesn't have yesterday's stock in the cache. Put simply, I forgot to increment mNextNearbyY in that loop when it comes across the zero point. Oops. Also fixed a slight bug where it drew multiple flags on the same nearby point, which I think is a bit wasteful.
  • 46 hours ago
    issue 3 (Crash on Moto CLIQ) Labels changed by captainspam   -   All right, I've got the fix in SVN, r296. As far as I know, it should work properly, but I can't test it for sure, as I don't have a CLIQ. If it works for you, I can go ahead and mark this one fixed. Enjoy!
    Labels: DeviceSpecific
    All right, I've got the fix in SVN, r296. As far as I know, it should work properly, but I can't test it for sure, as I don't have a CLIQ. If it works for you, I can go ahead and mark this one fixed. Enjoy!
    Labels: DeviceSpecific
  • 46 hours ago
    r296 (Added in a workaround to make the location overlay work on t...) committed by captainspam   -   Added in a workaround to make the location overlay work on the Motorola CLIQ (and presumably, anything else that doesn't implement the MyLocationOverlay drawables properly).
    Added in a workaround to make the location overlay work on the Motorola CLIQ (and presumably, anything else that doesn't implement the MyLocationOverlay drawables properly).
  • 47 hours ago
    issue 3 (Crash on Moto CLIQ) commented on by captainspam   -   Yep, that's roughly the same change I found somewhere on the Android discussion groups. :-) I'll get that (or something similar) in as soon as I can! Thanks!
    Yep, that's roughly the same change I found somewhere on the Android discussion groups. :-) I'll get that (or something similar) in as soon as I can! Thanks!

Last 7 days

  • Jan 03, 2010
    r295 (Changed WikiUtils.getHttpPage to use StringBuilder instead o...) committed by captainspam   -   Changed WikiUtils.getHttpPage to use StringBuilder instead of concatenating Strings, the former of which is a lot more efficient in the end when it comes to arbitrary-length input like this.
    Changed WikiUtils.getHttpPage to use StringBuilder instead of concatenating Strings, the former of which is a lot more efficient in the end when it comes to arbitrary-length input like this.
  • Jan 02, 2010
    issue 3 (Crash on Moto CLIQ) commented on by jebler   -   Thanks! I was able to find and use a workaround as described at http://community.developer.motorola.com/t5/Android-App-Development-for/Google-Maps/m-p/3421#M396 It extends MyLocationOverlay, try-catch the error, if there is an error the it uses a overridden drawMyLocation(), if not it uses the default drawMyLocation(). Works for me (:
    Thanks! I was able to find and use a workaround as described at http://community.developer.motorola.com/t5/Android-App-Development-for/Google-Maps/m-p/3421#M396 It extends MyLocationOverlay, try-catch the error, if there is an error the it uses a overridden drawMyLocation(), if not it uses the default drawMyLocation(). Works for me (:
  • Jan 02, 2010
    r294 (Revamped WikiPictureEditor's Gallery list. Now it should so...) committed by captainspam   -   Revamped WikiPictureEditor's Gallery list. Now it should sort out the most recently-taken camera pictures first. This isn't done yet. Not by a long shot.
    Revamped WikiPictureEditor's Gallery list. Now it should sort out the most recently-taken camera pictures first. This isn't done yet. Not by a long shot.
  • Jan 02, 2010
    issue 4 (..is not 30W compliant for earlier dates) changed by captainspam   -   There. As per r293, Info.makeAdjustedCalendar has been updated to account for dates on or before May 26, 2008, which should bring it up to compliance. I tested it with the dates given in the wiki, and it appears to work properly. Assuming this works right, this will go into 0.7.1 once the wiki features are finished. Of course, if you tested it before r293, you would want to clear the stock cache in the Settings screen before testing it again.
    Status: Fixed
    Cc: thomas.hirsch
    There. As per r293, Info.makeAdjustedCalendar has been updated to account for dates on or before May 26, 2008, which should bring it up to compliance. I tested it with the dates given in the wiki, and it appears to work properly. Assuming this works right, this will go into 0.7.1 once the wiki features are finished. Of course, if you tested it before r293, you would want to clear the stock cache in the Settings screen before testing it again.
    Status: Fixed
    Cc: thomas.hirsch
  • Jan 02, 2010
    r293 (Updated Info.makeAdjustedCalendar to properly handle the 30W...) committed by captainspam   -   Updated Info.makeAdjustedCalendar to properly handle the 30W Rule for dates on or before May 26, 2008 (that is, ignore the 30W Rule for those dates, as it wasn't coined before then).
    Updated Info.makeAdjustedCalendar to properly handle the 30W Rule for dates on or before May 26, 2008 (that is, ignore the 30W Rule for those dates, as it wasn't coined before then).
  • Jan 02, 2010
    issue 3 (Crash on Moto CLIQ) changed by captainspam   -   I think I've heard of this happening with other phones, too, with most Market apps that go to the map and use a MyLocationOverlay indicator like Geohash Droid does. I'll have to look it up again, but I think there's something related to the CLIQ not having the location image that Android's looking for (that is, Motorola doesn't have it in their custom build and skin of the OS), which causes it to crash internally. But yeah, this isn't Geohash Droid code causing it. However, when I can get to it, I think there's a workaround I can use.
    Owner: captainspam
    Labels: Component-UI
    I think I've heard of this happening with other phones, too, with most Market apps that go to the map and use a MyLocationOverlay indicator like Geohash Droid does. I'll have to look it up again, but I think there's something related to the CLIQ not having the location image that Android's looking for (that is, Motorola doesn't have it in their custom build and skin of the OS), which causes it to crash internally. But yeah, this isn't Geohash Droid code causing it. However, when I can get to it, I think there's a workaround I can use.
    Owner: captainspam
    Labels: Component-UI
  • Jan 02, 2010
    issue 4 (..is not 30W compliant for earlier dates) commented on by captainspam   -   Ah, I see. I completely forgot the 30W rule only applies after they came up with it. This shouldn't be too hard. I'll get right on it.
    Ah, I see. I completely forgot the 30W rule only applies after they came up with it. This shouldn't be too hard. I'll get right on it.
  • Jan 02, 2010
    issue 4 (..is not 30W compliant for earlier dates) commented on by thomas.h...@gmail.com   -   I have marked the application as "PARTIALLY" 30W-compliant in the wiki for now.
    I have marked the application as "PARTIALLY" 30W-compliant in the wiki for now.
  • Jan 02, 2010
    issue 4 (..is not 30W compliant for earlier dates) reported by thomas.h...@gmail.com   -   What steps will reproduce the problem? 1. lookup a 30W geohash prior to 2008-05-27 e.g. 2009-05-20 52 13 yields 52.24047842, 13.12366119 (another issue: trying the same with 68,-29 results in a black screen, the message "trying to determine your location" and a frozen application) What is the expected output? What do you see instead? http://wiki.xkcd.com/geohashing/30W_Time_Zone_Rule#Testing_for_30W_compliance and 2009-05-20 52 13 should yield 52.630990585392, 13.618945982091
    What steps will reproduce the problem? 1. lookup a 30W geohash prior to 2008-05-27 e.g. 2009-05-20 52 13 yields 52.24047842, 13.12366119 (another issue: trying the same with 68,-29 results in a black screen, the message "trying to determine your location" and a frozen application) What is the expected output? What do you see instead? http://wiki.xkcd.com/geohashing/30W_Time_Zone_Rule#Testing_for_30W_compliance and 2009-05-20 52 13 should yield 52.630990585392, 13.618945982091
  • Jan 02, 2010
    issue 3 (Crash on Moto CLIQ) reported by jebler   -   What steps will reproduce the problem? 1. Pressing "Go!" What is the expected output? What happened instead? Then the map begins to load, "Trying to determine your location..." is usually displayed. Then the sorry app stopped unexpectedly dialog appears. What version of Geohash Droid are you using? On what phone? I experienced the crash with 0.7.0, 0.7.1-pre1, and current svn. Moto CLIQ, 1.5 Please provide any additional information below. I don't get the error on the emulator, but on my CLIQ the debugger tells me: Thread [<3> main] (Suspended (exception ClassCastException)) ViewRoot.draw(boolean) line: 1256 ViewRoot.performTraversals() line: 1049 ViewRoot.handleMessage(Message) line: 1518 ViewRoot(Handler).dispatchMessage(Message) line: 99 Looper.loop() line: 123 ActivityThread.main(String[]) line: 3977 Method.invokeNative(Object, Object[], Class, Class[], Class, int, boolean) line: not available [native method] Method.invoke(Object, Object...) line: 521 ZygoteInit$MethodAndArgsCaller.run() line: 782 ZygoteInit.main(String[]) line: 540 NativeStart.main(String[]) line: not available [native method] As far as I can tell this isn't very useful (I don't think geohashdroid code is referenced here). What can I do to get better debugging information?
    What steps will reproduce the problem? 1. Pressing "Go!" What is the expected output? What happened instead? Then the map begins to load, "Trying to determine your location..." is usually displayed. Then the sorry app stopped unexpectedly dialog appears. What version of Geohash Droid are you using? On what phone? I experienced the crash with 0.7.0, 0.7.1-pre1, and current svn. Moto CLIQ, 1.5 Please provide any additional information below. I don't get the error on the emulator, but on my CLIQ the debugger tells me: Thread [<3> main] (Suspended (exception ClassCastException)) ViewRoot.draw(boolean) line: 1256 ViewRoot.performTraversals() line: 1049 ViewRoot.handleMessage(Message) line: 1518 ViewRoot(Handler).dispatchMessage(Message) line: 99 Looper.loop() line: 123 ActivityThread.main(String[]) line: 3977 Method.invokeNative(Object, Object[], Class, Class[], Class, int, boolean) line: not available [native method] Method.invoke(Object, Object...) line: 521 ZygoteInit$MethodAndArgsCaller.run() line: 782 ZygoteInit.main(String[]) line: 540 NativeStart.main(String[]) line: not available [native method] As far as I can tell this isn't very useful (I don't think geohashdroid code is referenced here). What can I do to get better debugging information?

Last 30 days

  • Dec 29, 2009
    r292 (Added in DOMUtil from an old project of mine. Much of this ...) committed by captainspam   -   Added in DOMUtil from an old project of mine. Much of this was based off of a Learning Java book.
    Added in DOMUtil from an old project of mine. Much of this was based off of a Learning Java book.
  • Dec 29, 2009
    r291 (Forgot to add the string in.) committed by captainspam   -   Forgot to add the string in.
    Forgot to add the string in.
  • Dec 28, 2009
    r290 (Did an awful lot to WikiPictureEditor. - Converted it to a ...) committed by captainspam   -   Did an awful lot to WikiPictureEditor. - Converted it to a WikiBaseActivity. - Converted its wiki running thread into a WikiConnectionRunner. - Changed its error handling to pop up a dialog. - Fixed the gallery list so that it's in sync with the pictures (thumbnails and images use a different ID space, apparently). Unfortunately, I still want to make sure camera pics come first and that all of them are sorted by the time the picture was taken, since that's what is most likely to be uploaded. I'm still researching that one.
    Did an awful lot to WikiPictureEditor. - Converted it to a WikiBaseActivity. - Converted its wiki running thread into a WikiConnectionRunner. - Changed its error handling to pop up a dialog. - Fixed the gallery list so that it's in sync with the pictures (thumbnails and images use a different ID space, apparently). Unfortunately, I still want to make sure camera pics come first and that all of them are sorted by the time the picture was taken, since that's what is most likely to be uploaded. I'm still researching that one.
  • Dec 28, 2009
    r289 (Created WikiBaseActivity, featuring the methods WikiMessageE...) committed by captainspam   -   Created WikiBaseActivity, featuring the methods WikiMessageEditor and WikiPictureEditor share in common. Turned WikiMessageEditor into one, too.
    Created WikiBaseActivity, featuring the methods WikiMessageEditor and WikiPictureEditor share in common. Turned WikiMessageEditor into one, too.
  • Dec 28, 2009
    r288 (Converted WikiMessageEditor to use WikiConnectionRunner and ...) committed by captainspam   -   Converted WikiMessageEditor to use WikiConnectionRunner and the new error-reporting popup. I'll commit the new WikiPictureEditor, too, once I have a bunch of local debug changes removed from it.
    Converted WikiMessageEditor to use WikiConnectionRunner and the new error-reporting popup. I'll commit the new WikiPictureEditor, too, once I have a bunch of local debug changes removed from it.
  • Dec 27, 2009
    r287 (Created WikiConnectionRunner as a separate class, as there's...) committed by captainspam   -   Created WikiConnectionRunner as a separate class, as there's a lot of basic functionality shared between WikiMessageEditor's and WikiPictureEditor's threads. They'll be melded into this once I have a better error handler for them.
    Created WikiConnectionRunner as a separate class, as there's a lot of basic functionality shared between WikiMessageEditor's and WikiPictureEditor's threads. They'll be melded into this once I have a better error handler for them.
  • Dec 27, 2009
    r286 (fixing login recognition in WikiUtils. POSTing wiki pages re...) committed by thomas.h...@gmail.com   -   fixing login recognition in WikiUtils. POSTing wiki pages remains broken.
    fixing login recognition in WikiUtils. POSTing wiki pages remains broken.
  • Dec 26, 2009
    r285 (Set the message areas in both the picture uploader and the m...) committed by captainspam   -   Set the message areas in both the picture uploader and the message editor to capitalize sentences automatically. Also removed the timestamp checkbox from the picture uploader. Turns out the MediaWiki Gallery extension doesn't interpolate ~~~~~ for some reason, so that can't do anything.
    Set the message areas in both the picture uploader and the message editor to capitalize sentences automatically. Also removed the timestamp checkbox from the picture uploader. Turns out the MediaWiki Gallery extension doesn't interpolate ~~~~~ for some reason, so that can't do anything.
  • Dec 23, 2009
    r284 (Fixed apostrophes in strings.) committed by captainspam   -   Fixed apostrophes in strings.
    Fixed apostrophes in strings.
  • Dec 21, 2009
    GeohashDroid-0.7.1-pre1.apk (Geohash Droid version 0.7.1-pre1 (beta)) file uploaded by captainspam   -  
    Labels: Featured Type-Installer OpSys-Android
    Labels: Featured Type-Installer OpSys-Android
  • Dec 19, 2009
    r283 (Resourceified the strings in WikiPictureEditor. Also made i...) committed by captainspam   -   Resourceified the strings in WikiPictureEditor. Also made it so that the first thing PictureEditor does is grab the URI to the image so that the cursor isn't as important to keep (it'll get destroyed during a config event). There might be a better way to do this. Next, I have to figure out why it seems to be picking the same picture every time no matter what I select from my phone.
    Resourceified the strings in WikiPictureEditor. Also made it so that the first thing PictureEditor does is grab the URI to the image so that the cursor isn't as important to keep (it'll get destroyed during a config event). There might be a better way to do this. Next, I have to figure out why it seems to be picking the same picture every time no matter what I select from my phone.
  • Dec 17, 2009
    r282 (Reverted the dummy wiki I was using from WikiUtils, reset it...) committed by captainspam   -   Reverted the dummy wiki I was using from WikiUtils, reset it back to the real Geohashing Wiki.
    Reverted the dummy wiki I was using from WikiUtils, reset it back to the real Geohashing Wiki.
  • Dec 17, 2009
    r281 (WikiPictureEditor will now respond properly to canceling. W...) committed by captainspam   -   WikiPictureEditor will now respond properly to canceling. WikiMessageEditor will, too. Come to think of it, I'm not sure how it WAS canceling in the first place when I put that fix in... WikiPictureEditor will NOT, however, behave properly with orientation shifts. That's next up. Then resourceizing the strings and adding in a menu option to call the preferences screen, and I think we have a winner.
    WikiPictureEditor will now respond properly to canceling. WikiMessageEditor will, too. Come to think of it, I'm not sure how it WAS canceling in the first place when I put that fix in... WikiPictureEditor will NOT, however, behave properly with orientation shifts. That's next up. Then resourceizing the strings and adding in a menu option to call the preferences screen, and I think we have a winner.
  • Dec 17, 2009
    r280 (String resourceized the strings used in the wiki dialogs.) committed by captainspam   -   String resourceized the strings used in the wiki dialogs.
    String resourceized the strings used in the wiki dialogs.
  • Dec 17, 2009
    r279 (Fixed MainMap's Location Intent sending as it relates to pic...) committed by captainspam   -   Fixed MainMap's Location Intent sending as it relates to picture uploading (else it'll crash if it hasn't found a lock yet). Also, minor WikiPictureEditor cleaning.
    Fixed MainMap's Location Intent sending as it relates to picture uploading (else it'll crash if it hasn't found a lock yet). Also, minor WikiPictureEditor cleaning.
  • Dec 17, 2009
    r278 (Updated WikiMessageEditor so that it respects the coordinate...) committed by captainspam   -   Updated WikiMessageEditor so that it respects the coordinates and timestamp checkboxes from the interface.
    Updated WikiMessageEditor so that it respects the coordinates and timestamp checkboxes from the interface.
  • Dec 16, 2009
    r277 (Some cleanup to WikiPictureEditor to bring some of WikiMessa...) committed by captainspam   -   Some cleanup to WikiPictureEditor to bring some of WikiMessageEditor's bulletproofings to it. More to come. This isn't complete yet.
    Some cleanup to WikiPictureEditor to bring some of WikiMessageEditor's bulletproofings to it. More to come. This isn't complete yet.
  • Dec 16, 2009
    r276 (Changed the logic behind the anonymous warning label. Now i...) committed by captainspam   -   Changed the logic behind the anonymous warning label. Now it has fixed text and is set to View.GONE when not needed.
    Changed the logic behind the anonymous warning label. Now it has fixed text and is set to View.GONE when not needed.
  • Dec 15, 2009
    r275 (Changed the message areas in the wiki editors to have hint t...) committed by captainspam   -   Changed the message areas in the wiki editors to have hint text.
    Changed the message areas in the wiki editors to have hint text.
  • Dec 14, 2009
    r274 (Changed it so that MainMap sends out two doubles, not a Loca...) committed by captainspam   -   Changed it so that MainMap sends out two doubles, not a Location object, because, strangely, Locations aren't serializable. Odd. This makes the location uploader work properly. This is really a stopgap measure until I make GeohashLocationService later.
    Changed it so that MainMap sends out two doubles, not a Location object, because, strangely, Locations aren't serializable. Odd. This makes the location uploader work properly. This is really a stopgap measure until I make GeohashLocationService later.
  • Dec 13, 2009
    r273 (Removed unused imports from WikiPictureEditor.) committed by captainspam   -   Removed unused imports from WikiPictureEditor.
    Removed unused imports from WikiPictureEditor.
  • Dec 13, 2009
    r272 (As it turns out, if the Geohash Droid app is terminated in a...) committed by captainspam   -   As it turns out, if the Geohash Droid app is terminated in any way (most likely via low memory errors when it isn't active), the static mStore value in HashBuilder is rendered null. However, the only time it's initialized is during the main GeohashDroid class. Meaning, if, for instance, the user is in MainMap (a somewhat memory-heavy Activity due to it being a MapActivity), navigates to another app (i.e. the View Wiki Page option, or an incoming phone call), and the OS thinks memory is low, it could terminate Geohash Droid, expecting to start it back up from a retained state when it comes back in. Unfortunately, if MainMap or whatnot needs the database at that time (such as the Nearby Points feature), this will crash, as mStore will be null, seeing as how HashBuilder.initialize won't have been run. This fix is a quick hack that ensures mStore is always defined at any point it's needed by encapsulating it in an accessor that can create it from scratch if need be. This does mean all calls that refer to mStore now need a Context, which has also been addressed here. Later, a REAL fix would be to wrap all database access into a Service that knows to initialize HashBuilder without the hackish Context requirement every time.
    As it turns out, if the Geohash Droid app is terminated in any way (most likely via low memory errors when it isn't active), the static mStore value in HashBuilder is rendered null. However, the only time it's initialized is during the main GeohashDroid class. Meaning, if, for instance, the user is in MainMap (a somewhat memory-heavy Activity due to it being a MapActivity), navigates to another app (i.e. the View Wiki Page option, or an incoming phone call), and the OS thinks memory is low, it could terminate Geohash Droid, expecting to start it back up from a retained state when it comes back in. Unfortunately, if MainMap or whatnot needs the database at that time (such as the Nearby Points feature), this will crash, as mStore will be null, seeing as how HashBuilder.initialize won't have been run. This fix is a quick hack that ensures mStore is always defined at any point it's needed by encapsulating it in an accessor that can create it from scratch if need be. This does mean all calls that refer to mStore now need a Context, which has also been addressed here. Later, a REAL fix would be to wrap all database access into a Service that knows to initialize HashBuilder without the hackish Context requirement every time.
  • Dec 13, 2009
    r271 (WikiMessageEditor will now properly respond to configuration...) committed by captainspam   -   WikiMessageEditor will now properly respond to configuration changes (i.e. orientation shift). THAT should settle THAT! Note to self: I really should put that into LocationGrabber and StockGrabber, instead of each of them stopping cold during onPause. Next, WikiPictureEditor. Most of this will be the same.
    WikiMessageEditor will now properly respond to configuration changes (i.e. orientation shift). THAT should settle THAT! Note to self: I really should put that into LocationGrabber and StockGrabber, instead of each of them stopping cold during onPause. Next, WikiPictureEditor. Most of this will be the same.
  • Dec 13, 2009
    r270 (Changed the message handler part to use Message's obj field....) committed by captainspam   -   Changed the message handler part to use Message's obj field. This makes it a bit simpler for sending data than using Bundles, since we only need one object for the time being.
    Changed the message handler part to use Message's obj field. This makes it a bit simpler for sending data than using Bundles, since we only need one object for the time being.
  • Dec 09, 2009
    r269 (Added an abort() method to WikiUtils. This will attempt to ...) committed by captainspam   -   Added an abort() method to WikiUtils. This will attempt to abort whatever connection, if any, is in progress. Likewise, WikiMessageEditor will now attempt to abort itself if the dialog gets canceled (i.e. the user presses Back). Next, making sure everything continues working right and the dialog updates properly if the user switches screen orientations (etc, etc) during this time.
    Added an abort() method to WikiUtils. This will attempt to abort whatever connection, if any, is in progress. Likewise, WikiMessageEditor will now attempt to abort itself if the dialog gets canceled (i.e. the user presses Back). Next, making sure everything continues working right and the dialog updates properly if the user switches screen orientations (etc, etc) during this time.
  • Dec 06, 2009
    r268 (Converted the strings in WikiMessageEditor into string IDs f...) committed by captainspam   -   Converted the strings in WikiMessageEditor into string IDs for (maybe) easy translation later.
    Converted the strings in WikiMessageEditor into string IDs for (maybe) easy translation later.
  • Dec 06, 2009
    r267 (Moved WikiConnectionHandler creation and execution out of di...) committed by captainspam   -   Moved WikiConnectionHandler creation and execution out of dialog creation and into button-pressing. Under Android, the dialog is only created once per Activity instance, so if the user were to attempt to re-send a message, it would fail the second time, as the dialog's already created by that point. Also, WikiConnectionHandler now just implements Runnable instead of fully extends Thread. Simpler that way.
    Moved WikiConnectionHandler creation and execution out of dialog creation and into button-pressing. Under Android, the dialog is only created once per Activity instance, so if the user were to attempt to re-send a message, it would fail the second time, as the dialog's already created by that point. Also, WikiConnectionHandler now just implements Runnable instead of fully extends Thread. Simpler that way.
  • Dec 06, 2009
    r266 (Fixed a crashing problem caused by MainMap not passing the r...) committed by captainspam   -   Fixed a crashing problem caused by MainMap not passing the right string key for the Info bundle to WikiMessageEditor (which I think I put in... whoops). Also set it so that the "View Wiki Page" function reads from WikiUtils's WIKI_BASE_URL variable, which is really handy with my testbed wiki.
    Fixed a crashing problem caused by MainMap not passing the right string key for the Info bundle to WikiMessageEditor (which I think I put in... whoops). Also set it so that the "View Wiki Page" function reads from WikiUtils's WIKI_BASE_URL variable, which is really handy with my testbed wiki.
  • Dec 06, 2009
    r265 (Added a method to WikiUtils to get the wiki base URL.) committed by captainspam   -   Added a method to WikiUtils to get the wiki base URL.
    Added a method to WikiUtils to get the wiki base URL.

Older

  • Nov 22, 2009
    r264 (Extracted the URL of the wiki (the CGI access method) into a...) committed by captainspam   -   Extracted the URL of the wiki (the CGI access method) into a private static string. In addition to being cleaner to begin with, this'll also make it a lot easier to test things on my own private wiki without dumping pages all over the real wiki.
    Extracted the URL of the wiki (the CGI access method) into a private static string. In addition to being cleaner to begin with, this'll also make it a lot easier to test things on my own private wiki without dumping pages all over the real wiki.
  • Nov 16, 2009
    r263 (Tagging up the 0.7.0 release.) committed by captainspam   -   Tagging up the 0.7.0 release.
    Tagging up the 0.7.0 release.
 
Hosted by Google Code