3 ms·
I ran through the guided demo/walk-through and was sad to see that the export to HTML/CSS contained a crap ton of ID selectors. I only played with it for 5 or 1
by jqueryin 13y ago
I ran through the guided demo/walk-through and was sad to see that the export to HTML/CSS contained a crap ton of ID selectors. I only played with it for 5 or 10 minutes, but I found this:
Say you remove the id tag of #signup-form and change it to some arbitrary classname. The styling immediately goes away on the element! Somewhere there's a hard-coded style on the ID selector for the purposes of a pretty demo. This doesn't sit well with me.. You can see this is true when you click on the "Edit Project CSS" from the top menu item. I should've been able to change that ID to a class or combination of classes and not affect the styling on the fly.
Likewise, I'm a bit concerned what would happen by adding several classes. It doesn't appear as though they're each uniquely and independently tied to their own styles via the right adjusted area. If you want to do anything non-trivial, I believe you're stuck with manually entering the CSS in the "Edit Project CSS" pane on your own, which is worse than using your own IDE with automated updates in the browser via LESS, SCSS, SASS, HAML, Stylus, etc.
All I'm trying to say is better handling of classes would be much appreciated for those of us who prefer to try and widgetize and create reusable components. Beyond that, it looks nice :)
- ryanSrich 13y agoThat's really the issue with most new wysiwyg editors. FWIW Macaw seems to attack this problem head on (http://macaw.co/ http://macaw.co/)
- callmevlad 13y agoRelevant discussion on Macaw's use of absolute positioning: http://forum.macaw.co/discussion/64/absolute-positioning-and-margins http://forum.macaw.co/discussion/64/absolute-positioning-and...