I suspect the things I'd like to have in some release of the VSCode environment "real soon now" may be beyond 1.2.0.
They're pretty much aligned with the roadmap/wiki document, so are suggested there for releases past 1.2.0. On Tue, Nov 8, 2022 at 9:10 AM Steve Lawrence <slawre...@apache.org> wrote: > > The only change to the CLI debuggers capabilities form 3.3.0 to 3.4.0 > was making is so the "info parser" and "info unparser" commands only > output information when you are parsing or unparsing, respectively. So > you now need to know if you are parsing or unparsing to know which > debugger command to use (note that DAFFODIL-2709 proposes an "info > processor" command so you don't need to know). I'm not sure if VSCode > even exposes those commands, so it might not matter. > > The only way to output the infoset with the CLI debugger is with the > "info infoset" command, and that always outputs using the > XMLTextInfosetOutputter (i.e. XML text). > > Daffodil (not the debugger) for many releases has supported a number > different input/output methods (e.g. SAX, JSON, etc), so depending on > how the DAP layer retrieves the infoset it might be able switch to a > different infoset type. That could be a nice feature, especially for > people that like to avoid XML as much as possible, though I wouldn't say > it's needed for the VS Code 1.2.0 release. > > Note that the 3.4.0 release supports a new EXI ype, but that's really > just a wrapper around the SAX outputter. And tha probably isn't that > useful from a debugger perspective because it's densely packed binary > that needs extra steps to visualize. > > > On 11/8/22 8:25 AM, Shane Dell wrote: > > This makes sense to me. Will this be update to use 3.4.0 not incorporate > > some features into the debugger right? For example with 3.40 (maybe before) > > you can now export the infoset as different data types correct? So the > > debugger and extension will need an update to allow the user to set the > > format they would want the infoset saved as, this would be in the > > .vscode/launch.json so that when they would use the infoset views those are > > in the correct format as well, does this sound right? > > > > On 2022/11/07 19:48:43 Steve Lawrence wrote: > >> Only thing I can think of is to update to Daffodil 3.4.0 once it's > >> released: > >> > >> #336 Update the extension to use Apache Daffodil 3.4.0 > >> > >> On 11/7/22 2:19 PM, Shane Dell wrote: > >>> It has been over 3 months since the last Daffodil VS Code release. We've > >>> had a > >>> number of bug fixes and features added since then, so I think it's about > >>> time for another release. > >>> > >>> Does anyone have any other changes they'd like to make it into 1.2.0? > >>> > >>> Once these issues are fixed I propose that we start the 1.2.0 release > >>> process. > >>> > >>> - Shane Dell > >>> > >> > >> >
