This will really be beneficial for all users when visually styling as a failsafe regarding the presence of inline styles in projects. So obviously the Pinegrow approach you have shown is far superior, along with its overall visual tools and entire app by this will really be nice revision for users and the Pinegrow visual workflow and so much for working to improve the features between the Visual Tools and CSS workflows. Which is a very intrusive approach by them towards the user and general workflow. Since our last discussion in that other thread a year ago, I looked at other apps and how they handle things.īlueGriffon for example puts a large bold color box around the input – but also actually locks the user out of doing anything further until they provide input. They seem like minor adjustments (UI and feature that already exists), each could further aid in strengthening this revision and enhancement of the workflow. ** Thanks for taking those 2 suggestions into consideration. This would provide another simple and elegant reminder for users to take action regarding input, while remaining appropriate to what you have shown via your screenshot. Otherwise if something is assigned it goes back the standard UI look:.If an Inline Style is present for the selected item then its orange:.Another minor suggestion that would prove to be beneficial, is to change the “stroke color” or “background color” of the “Class, ID, Selector Input” field to the UI orange also. Seems only logical, if you can utilize the hide/show feature and target the opposite collection of page items “without” inline styles via the “Show only: Inline styles”. That would likewise be beneficial as another visual representation method on the actual page itself. Will doing so also visually toggle the other items on the live page - like via the “Hide / show in Pinegrow” ?īasically like using the “Hide / show in Pinegrow” feature, but for everything that “does not” have inlines styles. Showing the inline style icon in the Tree panel, with the ability to display just the elements with inline styles (among other filters) So what to do, or what can be done to help prevent this inline CSS fragmentation? ![]() But having said that you can use it effectively, to create HTML emails which may require inline CSS, etc. ![]() Of course we know inline styles are largely frowned upon in general within the industry as it fragments the CSS workflow across locations and makes maintenance a nightmare to search for all the corresponding CSS instances in multiple locations. The user can then save the file without warning and these inline styles will remain in place. You can do this on as many items you like and Pinegrow will amass a list of “Classes without rules” which translates to all these visual edits placing inline styles on items. ![]() You can go into Pinegrow and start using the new Visual CSS Editor, which by default creates a “inline style attribute” for the selected item you are working on. CSS Properties - Direct user manipulation on page of basics properties - via Drag etcĪs it stands right now I believe this type of fragmented CSS can still presently occur and still remains to be considered even with the workflow as it currently stands at this moment.
0 Comments
Leave a Reply. |