Update: This problem has been resolved in version 0.4.9, which has just been submitted to the Beta Catalog, and should be available within a few hours.
The release of webOS 1.4 today seems to have caused some problems with the DnD 4e Compendium - it seems to be hanging while retrieving the filters from the Wizards.com website.
I'm doing what I can to fix the issue, but until it's resolved the app is sadly likely to be unusable.
Saturday 27 February 2010
Thursday 11 February 2010
Almost ready?
Over the last couple of days, I've made some good progress on the next release of the Compendium.
In addition to fixing a couple of bugs with the previous iteration, I've tidied up the validation on the new XP and Cost filters to avoid a problem with the Wizards.com API.
I'll be putting the current version - 0.4.8 - through its paces over the next couple of days, and hopefully should have a date in mind for the next release by the end of the weekend, pending any further issues.
In addition to fixing a couple of bugs with the previous iteration, I've tidied up the validation on the new XP and Cost filters to avoid a problem with the Wizards.com API.
I'll be putting the current version - 0.4.8 - through its paces over the next couple of days, and hopefully should have a date in mind for the next release by the end of the weekend, pending any further issues.
Thursday 4 February 2010
XP and Cost filter progress
After taking some time away from the development of the app, mostly just to start seeing it more like an end user might, I've started back on the code to get cost and experience fields added to the filter searches for items, monsters and rituals.
I spent a significant amount of time tonight working on the layout - unlike the level filters, the cost and XP fields have a huge number of potentially infinite values, and the kind of granularity that might be required when searching is much higher. With that in mind, I couldn't just use the same integer picker widgets as before. I had to arrange two text fields in a way that made sense and didn't take up too much space - which is more awkward than it first sounds when you're working mostly with pre-defined widgets.
I've come up with a solution that will hopefully work, although it still needs some tweaking - making it obvious where to tap to highlight the field is the first order of business now that the fields exist at all.
I'm not going to make any promises about when the next iteration will be available, but hopefully it'll be soon.
I spent a significant amount of time tonight working on the layout - unlike the level filters, the cost and XP fields have a huge number of potentially infinite values, and the kind of granularity that might be required when searching is much higher. With that in mind, I couldn't just use the same integer picker widgets as before. I had to arrange two text fields in a way that made sense and didn't take up too much space - which is more awkward than it first sounds when you're working mostly with pre-defined widgets.
I've come up with a solution that will hopefully work, although it still needs some tweaking - making it obvious where to tap to highlight the field is the first order of business now that the fields exist at all.
I'm not going to make any promises about when the next iteration will be available, but hopefully it'll be soon.
Subscribe to:
Posts (Atom)
