New at creating extension - workflow, testing incremental changes?
I am new at this: creating MoneyDance extension. I just download
and tried the dev package and it appears that the workflow is:
1. change codes 2. package extension jar file 3. re-install above
package 4. Test and repeat
Am I correct on that? If yes, it would really helpful to be able
to work in "expanded directory" mode:
. Have a file pointer to a working directory (save steps #2, #3)
FYI, I am looking into being to provide an extension to fully import MS Money (*.mny) file content into MoneyDance (via sunrrise).
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ben Spencer on 21 Aug, 2011 09:02 AM
Hi
I am super excited that you are embarking on this project. I had not heard of the sunrise project until you mentioned it the other day on this forum. I looked into directly opening .mny files for importing into Moneydance about a year ago when I read that they were little more than slightly modified .mdb files. It turned out to be a fairly involved process and I abandoned it very early on. I am so glad you are interested in working on this, the process of exporting each account to a QIF file and importing into Moneydance is really terrible.
I agree the work flow is quite laborious. I have emailed the lead developer asking if he has any recommendations.
Ben Spencer
Moneydance Support
hleofxquotes closed this discussion on 29 Aug, 2011 01:28 AM.