![]() It doesn't stop hereīut we've also got a lot planned for the plugin already, including some cool javascript code, and support for SMTP. Even though we've had some very generous people either contribute code or pay for changes to code, that has been less than one tenth of the total spend to date. Acknowledging the work done so farĪll of the plugin development has been done by an outside contractor, so everything we do has a cost. So all of that has been shelved, and we're back to a single set of open source code, but we need to consider now what to do with the Xero work and then whether we can recover any of the costs of development to date. And the whole point of this at the beginning was to have a single plugin, with no complex registration. It quickly became apparent that this would only create more work for the people who have paid, who we are trying to improve things for. So they have to have the same names and function names. For example you want to be able to update from the free to the paid. Seems simple enough, even with our model of not having registration functions, until you get into real world questions. The paid version would just contain the free functions plus extras. We spent a fair bit of time looking at how we could have two versions of the plugin, one paid and and one free. This was something beyond the plugin, but that really only has value alongside the plugin.Īt this point, we had the plugin as a set of functions that were free, open source and contributed from lots of different people, and a second set that we'd spent way more time and money on, and that also requires a FileMaker sync framework to be useful, that in our mind could be a product on it's own. So we also set to work to write a Xero sync framework that can push and pull data from Xero to a set of local FileMaker tables. After a lot of back and forth and development work at our end, we finally got something working, but realised the function itself is just the beginning. ![]() It turns out the Xero interaction is OAuth like but not the same as what we'd developed. Xero is becoming one of the big new things for online accounting, we use it ourselves and it's growing worldwide.Īt first it seemed like we would need OAuth in the plugin to make this work, so we started down that path. ![]() One of the big new things we added in this release is a simple ( on the outside ) function to authenticate against the Xero API. Lots of new features in this that are very exciting, but there's been a lot going on behind the scenes here as well which hasn't been public and I'd like to go through for all those interested. You may have noticed a new version of our free FileMaker plugin was released in the last few weeks, bringing the version number to 3.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |