05/30/2010, 12:16 PM
|
#21 (permalink) |
|
Member
![]() ![]() ![]() Join Date: Jun 2009
Posts: 608
Likes Received: 7
Thanks: 25
Thanked 90 Times in 59 Posts
|
There is a minor problem, but it is not your fault and I don't know, if it can be fixed:
3 of our apps have localized app names. But Mojo.Controller.appInfo.title always gives the english app name, so that is what's being displayed in the update dialog. |
05/31/2010, 10:35 AM
|
#22 (permalink) |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
Do you have separate appinfo.json files for each localization, ala https://developer.palm.com/distribut...t=5802&start=0
If you do that, does it still always show English? |
05/31/2010, 10:45 AM
|
#24 (permalink) | |
|
Member
![]() ![]() ![]() Join Date: Jun 2009
Posts: 608
Likes Received: 7
Thanks: 25
Thanked 90 Times in 59 Posts
|
Quote:
|
|
06/01/2010, 03:37 PM
|
#28 (permalink) | |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
Ok, here's a simple solution. I'm not happy with it, and I wish the Mojo call worked, but this will work for the time being. I will commit this update later.
In your strings.json file for each localization, you'll have to manually enter the localized title in place of #{title} in the update dialog string. Here's a sample Spanish translation strings.json: Quote:
|
|
06/03/2010, 04:38 PM
|
#29 (permalink) |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
Okay, another commit today. This one brings better localization.
I decided that since it was confirmed by unwiredben that Mojo.Controller.appInfo.title always returns the English app title, it would be wise to localize the title globally within the app. So I localized it separately from the message string. I also decided to use keys for the localization files, prepended with puchk_ so that's in the commit, as well. |
06/21/2010, 09:59 PM
|
#30 (permalink) |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
Fixed an issue with app updates failing to install (bug with webOS that causes install failures when the older version is still open). More info in this article:
puchk updated to v0.6.1 |
09/20/2010, 12:10 PM
|
#33 (permalink) |
|
Member
![]() ![]() ![]() Join Date: Jun 2009
Posts: 608
Likes Received: 7
Thanks: 25
Thanked 90 Times in 59 Posts
|
window.close() does not quit my app anymore (when pressing the update button to launch the App Catalog).
Either it's webOS 1.4.5 or the fact that my app is now a multi-stage app. |
12/14/2010, 01:18 PM
|
#36 (permalink) |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
Good news and bad news!
Bad news - you're going to have to edit your code, but only once ![]() Good news - puchk is updated! In this update: I made this -much- easier to add to your apps, and to update puchk in the future. There is now a "never ask me again" functionality built-in http://www.jdf-software.com/software...k/puchk.tar.gz or http://www.jdf-software.com/software...k/puchk.tar.gz ----- Instead of copying + pasting the code into your assistant file, puchk is now a separate file, puchk.js. You can put this anywhere in your directory structure (I chose app_folder/js/puchk.js) 1) include the file in index.html <script type="text/javascript" src="js/puchk.js"></script> 2) in your first scene's setup() method (or wherever you want the check to happen - make sure it's a scene the user will be on long enough for the check to occur!) var update = new puchk(hours, this); update.check(); where "hours" is the MINIMUM number of hours between update checks, and "this" is just "this" It's as simple as that, now! You can delete all the old code that's clogging up your assistant! And now if puchk gets updated, it'll be as simple as replacing the puchk.js file with the new copy. |
12/22/2010, 06:21 PM
|
#37 (permalink) |
|
Member
![]() Join Date: Jan 2010
Posts: 115
Likes Received: 0
Thanks: 7
Thanked 24 Times in 17 Posts
|
MINOR update.
There was a spelling error - in the code for the update dialog, one of the keys ways spelled wrong - "nevel" instead of "never". It doesn't affect the text displayed in the dialog, but if you are using the key with localization files, you'll want to correct the error or your other languages won't show there. Plus I did a little tidying of the code to make it run a bit faster. The github repo is updated now. |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|



