Thanks for posting; that seems like a reasonable development approach. I did some hacking on the sheet a few months ago because I was going to try reading the portfolio directly by using JS in the browser, hoping to be able to get items' container ship information (turns out the information isn't there, so it can't be reported correctly; everyone interested in this sheet supporting containers should file a bug report with LW!).
The biggest issues I saw in the sheet were how it determined that something was a weapon or an amor... There's a list of text strings and it looks for those strings. That means "new" weapons won't be recognized as such -- perhaps the kineticist's blast falls into this category? It would be nice if those strings could be externalized (step 1) and then generated (step 2) so that the sheet could support more items with a simple build/deploy process. Perhaps the d20pfsrd databases would help? (Don't know if they have a database for weapons and armor, though.)
The biggest issues I saw in the sheet were how it determined that something was a weapon or an amor... There's a list of text strings and it looks for those strings. That means "new" weapons won't be recognized as such -- perhaps the kineticist's blast falls into this category? It would be nice if those strings could be externalized (step 1) and then generated (step 2) so that the sheet could support more items with a simple build/deploy process. Perhaps the d20pfsrd databases would help? (Don't know if they have a database for weapons and armor, though.)