10 Debugging - What the hell is going on? - Reference Documentation
Authors: Marc Palmer (marc@grailsrocks.com)
Version: 1.0.RC2
10 Debugging - What the hell is going on?
It can be a bit tricky to work out what is going wrong when a UI Set or Theme is not rendering as you would expect. Is there a problem in the UI set or the theme, what themes and UI sets are available etc?There are some tools to help you as a Theme or UI Set author and to help developers preview your themes.10.1 Troubleshooting UI Sets
UI sets provide the CSS, JS and markup for individual UI elements, separate from any theming.As such the best way to debug UI Sets is using the built in platform UI viewer - not the Theme previewer.Using the Platform UI UI Set browser
Viewing the full UI Sample page which demonstrates all the UI elements and checking your page loads correctly, JS works, and the various elements operate as expected is your best starting point.With your app or plugin running in "run-app" development mode, browse to:http://localhost:8080/<yourprefix>/platform/ui/uisetsThis will let you see each installed UI Set in action.Make sure your UISet renders all the widgets correctly in the UI Set viewer.
10.2 Troubleshooting Themes
Themes are responsible for only the structural layout and styling of a page.They may also choose to override styles provided by the UI Set on which they depend, for example to change colours.Using the Platform UI Theme browser
Viewing the content content in your Theme is the best way to isolate Theme issues from your app itself.With your app or plugin running in "run-app" development mode, browse to:http://localhost:8080/<yourprefix>/platform/ui/themesHere you can view each Theme's layout with default content supplied, with or without the full set of UI Set samples included.View the layout that you are having problems with and verify the structural markup is all correct, and that all your CSS and JS is loading and being applied correctly.