I think the need for a powerful CLI is now more important than ever. I have been using MLO for many years, but I feel it is lagging behind competitors because it does not support AI. If there were a comprehensive CLI support, I could connect my Claude Code to the MLO CLI and build all sorts of custom workflows. But without this capability, I can only edit access MLO tasks using the user interface. I hope we get some sort of answer soon, or I will have to abandon this tool, which I love and is a cornerstone of my productivity system. Let me know if there are any updates on this and your thoughts on the importance of CLI support as well as other alternatives. Thanks
On Friday, August 2, 2024 at 9:12:59 PM UTC-4 Hugo González Castro wrote: > Hello all, > > Although this conversation was long ago, I might add some information in > case anyone finds it useful. There is also another related thread here: > https://groups.google.com/g/mylifeorganized/c/MPEDQQ8mwCE/m/A14_HyVpHgAJ > > There is no public API nor dev documentation, which is a pity. In MLO for > Windows I personally use the "mlo.exe" *batch command line*, which is > very useful for automation. I particularly automate the export to XML, > which is a very convenient format for me. There are more possibilities, > which includes adding subtasks by command line. > > Apart from that, the WiFi Sync is done with a separate library called "" > *MLOWiFiSync.dll*" which is dynamically loaded from the main executable > "mlo.exe". That libary implements some functions that could be called from > a different utility, which names are: > > > > > > > > > > > > *GetActiveSessionCountGetLastSynchronizationErrorGetLastSynchronizationErrorCodeSetLogFileNameSetOnDataNeededSetOnDataReceivedSetOnPairRequestedSetOnServerErrorStartListeningStopListening* > > The problem is the library is not specifying the arguments to those > functions, which is a problem without the source headers or API > documentation, which is unavailable. But, it is possible to create a fake > library to replace it and debug the process, and having a possibility to > get the arguments when the fake library is called by the MLO executable. > One that is done, then it would be possible to directly call the library > from a different app or utility. For example, it would be possible to > create a WiFi Sync of the AbstractSpoon ToDoList with the MLO for Android > app, which would be really cool. The user would still need to buy the MLO > for Android Pro version to be able to use that feature. Of course that > would be a kind of reverse engineering that would require a lot of work, > but seems feasible... MLO might not approve that kind of development > anyway... > > > El martes, 14 de enero de 2020 a las 11:24:24 UTC+1, Marco escribió: > >> I'm currently evaluating MLO. I would also like to see some API >> implemented. Don't mind what is the way to interact with it, whether it's a >> REST or CLI - doesn't matter as long as I'm able to create some >> integrations with my 3rd party. Not having this is a major drawback and >> potential stopper. >> >> On Thursday, August 16, 2018 at 8:01:03 AM UTC+2, Jan Thomä wrote: >>> >>> Hi, >>> >>> I would like to interface some automated tasks with MLO, so the >>> automation could create tasks in my MLO file. Is the MLO file format >>> documented somewhere or is there an API that I could use to read/write MLO >>> files? >>> >>> Kind regards, >>> Jan >>> >> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/mylifeorganized/bd8c4f7f-47a8-48c8-9941-a643ed1eaf62n%40googlegroups.com.
