![script debugger lite script debugger lite](https://windows-cdn.softpedia.com/screenshots/CMDebug_3.png)
It only applies to nodes that have been loaded locally. Tree Navigation Filter (binocular icon): enables you to filter the nodes in the repository for which the name contains the input text.
![script debugger lite script debugger lite](https://windows-cdn.softpedia.com/screenshots/CMDebug_8.png)
After clicking a node, you can select an action in the toolbar. If you want to search the whole repository, use Tools, then Query.ĭisplays a tree of all the nodes in the repository.Ĭlick a node to display its properties in the Properties tab. Note that it only works for the nodes currently loaded into the CRXDE client application in browser. If a given node or nodes is loaded into the explorer pane, the list will be displayed, and you can select the path and hit Enter to navigate to it. You can try entering, e.g., the string oak into the widget to see how it works. Enter the name of the node you would like to find, and wait (or hit the search symbol on the right-hand side). It also provides support for looking for nodes with specific node name. You can also use it to jump to a node, by entering the path by hand, or pasting it from somewhere else, and hitting Enter. Overview of the User InterfaceĬRXDE Lite offers the following functionality: Top switcher barĪllows you to quickly switch between CRXDE Lite, Package Manager, and Package Share.ĭisplays the path to the currently selected node. You can now use CRXDE Lite to develop your application. The CRXDE Lite User Interface looks as follows in your browser: To get started with CRXDE Lite, proceed as follows: If you are debugging your own application and see strange behavior, look at the logs from Vega-Lite.It is recommended to use the AEM Developer Tools for Eclipse and the AEM HTL Brackets Extension during project development. The Vega Editor automatically collects and displays logs. However, sometimes it can be useful to use non-minified sources, which you can load from the jsDelivr CDN.įor example, to use non-minified sources with Vega-Embed, load the following scripts. You can even debug minified JavaScript sources since Vega and Vega-Lite provide source maps.
![script debugger lite script debugger lite](https://flatredball.com/migrated_media/ScriptDebugExpanded.png)
When debugging Vega and Vega-Lite in the browser, it can be useful to step through the execution in the Firefox, Chrome, or Safari developer tools. Follow the debugging guide in the Vega documentation to debug the Vega runtime.
![script debugger lite script debugger lite](https://img.magimg.com/uploads/script-debugger.png)
Therefore, to debug runtime behavior, you have to understand the behavior of the Vega runtime. This means that at runtime there is no difference between a chart that comes from a Vega-Lite specification and a chart that comes from the compiled Vega specification. Vega-Lite specifications compile to Vega and are executed by the Vega runtime. Make sure that you are using the version that is provided by the editor if you see inconsistent behavior. The Vega Editor shows warnings if the schema has a valid $schema reference and the specification is not valid according to the schema for the version specified in the $schema. The first step to debugging a problem with Vega-Lite is to make sure that the specification is valid.