# Perspective vs Vision **URL:** \ **Category:** Ignition\ **Tags:** vision, perspective\ **Created:** [January 26, 2023, 12:44am UTC](https://forum.inductiveautomation.com/t/perspective-vs-vision/69028 "2023-01-26T00:44:06Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [January 27, 2023, 1:50am UTC](https://forum.inductiveautomation.com/t/perspective-vs-vision/69028/19 "2023-01-27T01:50:21Z")
> [@WillMT10](#): > > Styling is not as easy to handle as Nick mentioned, but I personally never had too many headaches with it. This might help: > [@Perspective Symbol States](https://forum.inductiveautomation.com/t/perspective-symbol-states/69055/6): > > This is what I use for my style classes bindings. Device symbol binding on style.classes: view.custom.status here is the Status Desc tag below (I never refer to the Status tag in graphics, so I drop the "Desc" in my references to it) Style Class Maps/Device Status dataset tag data: (someone should really re-order these...) The StyleClass column has the path to my Perpective Styles. Using a dataset essentially as a map transform allows the transform to be centrally locate… > [@WillMT10](#): > > I feel like then CSS is then more like Java in Vision I completely disagree. JS injection is like Java in Vision. CSS is a cornerstone of Perspective, but perhaps because it's overshadowed by Perspective Styles configuration that this isn't made inherently obvious. Perspective Styles create CSS style rules. The Perspective Style editor, however, contains only a subset selection of the full array of available CSS properties though, and it's extremely useful to know some of the more useful CSS properties that _aren't_ included in this, such as `gap` --- _[View the full topic](https://forum.inductiveautomation.com/t/perspective-vs-vision/69028)._