mrserv0
Member
Hi @Erel and the community. Thank you for the amazing work you do and all that has been created, and will be created on this platform.
I'm a contributor on the B4X Language Support Extension by @Jansen611 and lately have been considering the feasibility of adding a Debugger to it. This would likely be a lengthy task, but after observing the flow in the IDE and generated Java files, it seems that it could be possible, and be beneficial to the community and beyond.
How I approach VSCode debugging now (if you can call it that
), is that I use a combination of the B4A/JBuilder, to build a release package, and then rely on Log() statements to see results in the VSCode terminal, via ADB Logcat or otherwise. In the AI Age, the combination of Log Statements, and Run Tasks for installation / running, and screenshots, as well as ui testing with UIAutomator, is a pretty good workflow. But it does not expose the raw power of the IDE's Debugger, and lacks the control the IDE gives you. While it may not give you the same performance, the tools on VSCode's side to develop the Debugger component of the extension in VSCode is readily available, well documented and supported, and would be a suitable platform for this idea.
I understand Open Sourcing the IDE has not been realistic, and inviting community contribution would be really messy for a well rounded, mature, and polished product. So thats not what we would be after.
So my question is, would you consider open sourcing the B4A/JBuilder and required components to make a debugger for the extension? Or a version that could be used for this task? as it would be perfect to be able to get the Builders to build a Debug Package that could be communicated with in the extension.
Anyways, thankyou for considering the request! and Im curious to hear anyone elses thoughts about aftermarket debuggers!
Best Regards,
Michael.
I'm a contributor on the B4X Language Support Extension by @Jansen611 and lately have been considering the feasibility of adding a Debugger to it. This would likely be a lengthy task, but after observing the flow in the IDE and generated Java files, it seems that it could be possible, and be beneficial to the community and beyond.
How I approach VSCode debugging now (if you can call it that
), is that I use a combination of the B4A/JBuilder, to build a release package, and then rely on Log() statements to see results in the VSCode terminal, via ADB Logcat or otherwise. In the AI Age, the combination of Log Statements, and Run Tasks for installation / running, and screenshots, as well as ui testing with UIAutomator, is a pretty good workflow. But it does not expose the raw power of the IDE's Debugger, and lacks the control the IDE gives you. While it may not give you the same performance, the tools on VSCode's side to develop the Debugger component of the extension in VSCode is readily available, well documented and supported, and would be a suitable platform for this idea.I understand Open Sourcing the IDE has not been realistic, and inviting community contribution would be really messy for a well rounded, mature, and polished product. So thats not what we would be after.
So my question is, would you consider open sourcing the B4A/JBuilder and required components to make a debugger for the extension? Or a version that could be used for this task? as it would be perfect to be able to get the Builders to build a Debug Package that could be communicated with in the extension.
Anyways, thankyou for considering the request! and Im curious to hear anyone elses thoughts about aftermarket debuggers!
Best Regards,
Michael.
