Hey, you know a feature which I would love to see (and maybe it's already in there) -- would be the ability to "orchestrate" Java code. In other words, to be able to add external event hooks from functions/procedures/methods -- at runtime...
These event hooks, when encountered, would be able to do such things as:
* Print/pipe a debug message to an external program or log or log viewer;
* The debug printer should contain the function/procedure/method name, parameter names, and parameter values automatically (there should be functionality to have them in both the invocation and after the function/procedure/method's code is complete, prior to returning to the caller, so two possible places per function/procedure/method...);
* The ability to selectively turn on/off such events at runtime;
* The ability to add additional code which could be evaluated for every such event (also at runtime), and make the determination if the event should be processed or skipped;
* The ability to do all of the above programmatically, via API...
* Some sort of GUI which automatically imports all function/procedure/method names of a running Java program at runtime, then gives the user the ability to track/log whichever ones they want, by simply selecting them to a secondary listbox of tracked function/procedure/methods...
Now, maybe some or all of that -- is already baked in there. I didn't look at the codebase long enough to know...
But if it is in there, that's awesome! And if one or more of those features are missing, then maybe a future version maintainer or forked version maintainer might be persuaded to add them in there...
(Side note: It would be nice to have the above functionality for all programming languages!)
Hey, you know a feature which I would love to see (and maybe it's already in there) -- would be the ability to "orchestrate" Java code. In other words, to be able to add external event hooks from functions/procedures/methods -- at runtime...
These event hooks, when encountered, would be able to do such things as:
* Print/pipe a debug message to an external program or log or log viewer;
* The debug printer should contain the function/procedure/method name, parameter names, and parameter values automatically (there should be functionality to have them in both the invocation and after the function/procedure/method's code is complete, prior to returning to the caller, so two possible places per function/procedure/method...);
* The ability to selectively turn on/off such events at runtime;
* The ability to add additional code which could be evaluated for every such event (also at runtime), and make the determination if the event should be processed or skipped;
* The ability to do all of the above programmatically, via API...
* Some sort of GUI which automatically imports all function/procedure/method names of a running Java program at runtime, then gives the user the ability to track/log whichever ones they want, by simply selecting them to a secondary listbox of tracked function/procedure/methods...
Now, maybe some or all of that -- is already baked in there. I didn't look at the codebase long enough to know...
But if it is in there, that's awesome! And if one or more of those features are missing, then maybe a future version maintainer or forked version maintainer might be persuaded to add them in there...
(Side note: It would be nice to have the above functionality for all programming languages!)
Anyway, as said previously, looks very cool!