Changed documentation. ddg.source is still not tested because I'm planning on creating a new ant target which performs a ddg.source test on the currents tests - since the DDG through .source and through normal execution should be the same
In the process of improving ddg.source so that the DDG Created is as similar as possible to the one created by ddg.console. Further, note that any script that is sourced, if ddg calls are not ignored and those calls attempt to make console nodes, then issues will arise because the commands are not inserted into history
ddg.source works on simple cases, but abstraction nodes are not yet created
Fixed issue with abstracting sourced scripts. Currently working on fixing the issue with abstractions that occur within the call to ddg.source. Have abstracted away a bit of the functionality for abstraction console nodes in the hopes that this will be helpful later on
Testing a new method of creating console nodes that no longer relies on the assumption that the user is acting interactively with the script
Factoring out more code. Getting close to fixing console node creation and ddg.source
Fixed minor error with logic in .ddg.proc.node
Fixing boolean errors
Fixing boolean errors
Further attempts at solving the issue with nested abstract node. Also remove initialization checks for ddg.debug.on and ddg.debug.off
End of day. Still not working as expected, but getting closer