Something I thought of recently. Can't recall if I mentioned it already. The data display capabilities of the data editor are advancing, but the debugger does not benefit from those yet. (I think.)
Is there a place in the roadmap where these are converged so that the debugger user can also visualize and search the data these same ways? I reviewed it and did not see this. It seems to conceptualize the data editor as distinct from the debugger. I prefer to think of the editor as exactly what the debugger has, plus the ability to modify the data also. E.g., in the debugger, it would be useful to be able to point at any byte, and an unobtrusive display in the corner somewhere to show you some combination of big/little endian signed/unsigned integer for 2, 4, 8 bytes, float/double, and charset decode of 8 bytes in iso-8859-1,and utf-8. (Ideally the list of these types and encodings could be specified as part of the launch.json or other sticky project settings that the user could modify per schema project.) I think of this as being a lot like when using a spreadsheet, you can highlight any rectangle of cells, and in the lower-right there is a sum of those cells. You don't even notice it unless you want to see that sum. It's really unobtrusive. With the exception of modifying data, I think anything the data editor has for display of data would make sense on the data display while debugging. Other than needing to manage the screen real-estate differently, I think the data debugger's data display really could be another instance of the data editor, but in a read-only mode. Arguably, you could punt on trying to crowd everything into the same multi-panel UI frame for debugging, and pop open another window for the data view during debugging, and have it actually BE an instance of the data editor. You would just need the ability for the debugger to give it new highlighting positions as the debug position moves. On Tue, Aug 15, 2023 at 12:35 PM Davin Shearer <da...@apache.org> wrote: > +1 from me. To help inform the discussion, here are some draft > release notes for the possible v1.3.1-RC1 release: > > Data Editor > > · Add support for large file editing and "infinite" scrolling > > · Added support for editing in several Data Editor simultaneously > > · Implement Incremental Search and Replace and Save As functionality > > · Consolidate single-byte and multi-byte view and edit modes > > · Values are now editable in the Data Inspector > > · Content-type discovery using Apache Tika > > · Initial implementation of a Data Profiler > > · Implement “overwrite only” mode that will keep the file size > the same, even when performing operations like Search and Replace where the > token sizes aren’t the same > > Debugger > > · Changed debug server to more secure local interface > > · Update to debugger log levels > > · Update debugger build and extraction > > · Resolved debugger issues in Java 17 > > · Added additional configurations for the debugger > > IntelliSense & DFDL Diagnostics > > · Add additional/missing attribute completion snippets > > · Refine snippet suggestions for specific element tags > > · Refine the handling of auto-complete closing tags for multi-line > attributes (attribute split on multiple lines) > > · Add semantic highlighting for XPath expressions > > TDML > > · Resolved bug fixes in Windows > > > -Davin > > On Tue, Aug 15, 2023 at 12:07 PM Mike Beckerle <mbecke...@apache.org> > wrote: > > > +1 from me. I looked at the changes/fixes, and there is quite a lot in > > 1.3.1. Definitely worth a point release. > > > > On Tue, Aug 15, 2023 at 10:27 AM Shane Dell <shaned...@apache.org> > wrote: > > > > > Hello all, > > > > > > The Apache Daffodil VS Code Extension development team believes we are > > > ready to create a release candidate for 1.3.1 of the Apache Daffodil VS > > > Code Extension. The list of issues for the VS Code extension can be > found > > > here https://github.com/apache/daffodil-vscode/issues. Closed issues > for > > > 1.3.1 can be found at > > > https://github.com/apache/daffodil-vscode/milestone/10?closed=1. Are > > there > > > any problems, complaints or concerns? > > > > > > This discussion thread will be opened for at least 72 hours before > moving > > > forward. This will be Friday August 18th at 10:30 AM. > > > > > > Thank you, > > > > > > Shane Dell > > > > > >
