That will definitely void your warranty big time, buddy, will be a lot of work, easily breaks whenever TWS is updated, and inherits all kinds of other problems.
I think @frodfrog's comment about display groups is a good one. The interface is simple but allows the TWS API client:
Beyond that, Richard King's IBC may possibly be the base for a more involved TWS/IBGW automation (Groups.io, ). It is very reliable, but Richard needs to maintain it frequently when new TWS updates arrive.
And finally, there are several JavaFX automation frameworks. TWS/IBGW are built on-top of the JavaFX GUI framework which provides hooks for automation (usually for automated application testing). There are several "robot" libraries out there that can query the current structure of the display and mimic all user input (typing, mouse movement, clicking).
But anything other than the TWS API display groups requests will definitely require much more effort than "a weekend and a few six packs".
´³¨¹°ù²µ±ð²Ô
On Thu, Aug 3, 2023 at 03:04 PM, buddy wrote:
The IntelliJ Java de-compiler also seems to be pretty robust if you're that determined. I took a gander at the jar files and there isn't as much obfuscation going on as I expected.
find ~/Jts/1019/jars/ -type f | xargs -I% unzip -l % | grep -Po 'com/ib/.*?/[^/]+' | sort | uniq | grep -v '\.class$'
So, I'm not sure you couldn't re-arrange your class path in an order such that TWS is effectively wrapped by a custom Java application.
Practically speaking however, I'm not in favor of this idea... strikes me as a potentially fun academic exercise though. I'd just stick to using the API as intended.
