the bot that started it all (for me) [[tg-bots/mtfutilsbot]] literally a page about modularizing functions i guess, in practical sense [[tg-bots/modules]] types and data structures that need to be considered [[tg-bots/objects]] contracts between classes, for abstraction [[tg-bots/interfaces]] like interfaces, but here we have an implementation. The catch is, they run OUTSIDE of a bot context. [[tg-bots/runners]] So here's the general idea right now. 1. I try to identify some objects and interfaces to implement 2. I implement a couple in a "plugin-like" configuration, in native code 3. I create a little task-runner that can load one up and process data with it on CLI 4. I convert whatever mtfutilsbot is doing over to use the little runner instead 5. When I've got a few of them sorted, I'll have a better idea of how to hook them better into a native bot, and I can work a bit on the other side 6. gradually migrate all the little runners over to libraries for the new bot

the bot that started it all (for me) [[tg-bots/mtfutilsbot]] literally a page about modularizing functions i guess, in practical sense [[tg-bots/modules]] types and data structures that need to be considered [[tg-bots/objects]] contracts between classes, for abstraction [[tg-bots/interfaces]] like interfaces, but here we have an implementation. The catch is, they run OUTSIDE of a bot context. [[tg-bots/runners]] So here's the general idea right now. 1. I try to identify some objects and interfaces to implement 2. I implement a couple in a "plugin-like" configuration, in native code 3. I create a little task-runner that can load one up and process data with it on CLI 4. I convert whatever mtfutilsbot is doing over to use the little runner instead 5. When I've got a few of them sorted, I'll have a better idea of how to hook them better into a native bot, and I can work a bit on the other side 6. gradually migrate all the little runners over to libraries for the new bot I'm also thinking..... tdlib has a lot of great stuff. And I know how to use dlopen or whatever to load and run plugins... But what I might do is develop against Qt5 the whole while. That'll make me a bit slower and heavier, but it'll also give me a smoother ride with possible future problems such as windows deployment and blah blah. Why not boost? Never tried it lol

the bot that started it all (for me) [[tg-bots/mtfutilsbot]] literally a page about modularizing functions i guess, in practical sense [[tg-bots/modules]] types and data structures that need to be considered [[tg-bots/objects]] contracts between classes, for abstraction [[tg-bots/interfaces]] like interfaces, but here we have an implementation. The catch is, they run OUTSIDE of a bot context. [[tg-bots/runners]] So here's the general idea right now. 1. I try to identify some objects and interfaces to implement 2. I implement a couple in a "plugin-like" configuration, in native code 3. I create a little task-runner that can load one up and process data with it on CLI 4. I convert whatever mtfutilsbot is doing over to use the little runner instead 5. When I've got a few of them sorted, I'll have a better idea of how to hook them better into a native bot, and I can work a bit on the other side 6. gradually migrate all the little runners over to libraries for the new bot I'm also thinking..... tdlib has a lot of great stuff. And I know how to use dlopen or whatever to load and run plugins... But what I might do is develop against Qt5 the whole while. That'll make me a bit slower and heavier, but it'll also give me a smoother ride with possible future problems such as windows deployment and blah blah. Why not boost? Never tried it lol