The Importance of Design-Mode for Client-Side MVC
Join the DZone community and get the full member experience.Join For Free
synopsis: design mode (the same view but without angular or knockout loaded) is a great way to see the multiplicity of the view as you develop.
here’s a screenshot:
and here’s the link, which is a better way of quickly seeing the shrunken picture above.
moustache or handlebar style template fields everywhere.
you can see them everywhere – things that would be output text in the final version, but are now just model references in design mode. some are simple field references, some are more compex expressions, or have formatters attached.
only one row versus many in the running version.
there are three rows in the running version, and only one row in the design mode.
multiple alternates concurrently shown in design-mode
the passed or failed icon in in the running version, is now passed and failed (side by side) in design mode:
for each column in the table, according the the design of the jbehave storynavigator, there are three possibilities in respect of sort order:
- this column is the sorted one in descending order
- this column is the sorted one in ascending order
- this column is not the one being sorted
all three of those realities are shown for each column, and it is that which forces the columns far out to the right of the view. there’s an obvious improvement that someone could make to that – as there is no need for me to repeat the text of the column name as it does not change.
hopefully you get to see the beauty of of angular and knockout: you get to see a design preview of the finished page, with all of the components visible, and with css hooked up as it would be in the finished product.
Published at DZone with permission of Paul Hammant, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.