Hi, Francois! Thanks for your feedback. That is interesting news. As for MMEx, there are reasons for all those decisions and it usually narrows down to limitations in resources (time, developers). In respect to the Android app, Google keeps changing its rules for Play Store, and CloudRail - which was used to communicate with cloud services - dropped its support for storage services.
I'm currently using MMEx on mobile devices and it serves the purpose. The benefit is that I can modify the code and add the features that help me out. Disregard at the moment the data structure, we can leave that as an implementation detail which is irrelevant for exporting the data to beancount. The asset allocation actually works well but is not documented at all. I've moved the asset allocation code to Python - https://github.com/MisterY/asset-allocation - as it better suits my purpose there and is easier to maintain. Well, it now works and there is no need to adjust it. On my todo list is a task to try out the Asset Allocation functionality in ledger. I have all the parts for creating just the balance records (to avoid processing) which would be used with the asset allocation definition in a separate file. I also created a Python lib -https://gitlab.com/alensiljak/moneymanagerexlib - which can read MMEx database (the version which is currently supported by the Android app). This works fine and I used it for CSV generation for GnuCash. I'd assume that all that's needed is the BeanCount format definition, and a mapping for transactions/posting. I will, actually, move forward with this at some point as I intend to continue using MMEx on the phone but I also need that data in my main application. Whether the functionality ends up in the mobile app or in the Python library that reads the SQLite database directly, I don't know yet. Probably Python, since it can now run on Android, too. It is unfortunate that you are no longer using MMEx for Android, as additional manpower would be really handy in enhancing any of the parts of the chain. One thing that would be handy is the transaction definition (i.e. a class) which accepts all the Beancount supported properties, that I could fill out from MMEx entities, and it would give me a string representation back, which I could save into the resulting file. If you have this part, then please do share it somehow. I have most of the pieces laid out, just need the time to put them together. Cheers! On Wednesday, 24 April 2019 12:43:47 UTC+2, francois PEGORY wrote: > > Hello there, > I created some time ago two scripts in order to import and export data > from mmex to beancount. > > I left mmex since they remove the sync with Dropbox . > > Nonetheless, I found that mmex has less functionality than the beancount > format. For example, a transfer should be always a separate transaction. > This is not the case in beancount. > In addition, I didn't understand all the asset management part of mmex. > But if you want I can clean my code and send my GitHub . > > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/7724a8d4-7a91-4e9f-880f-4a4493bc9dc6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
