| Github | https://github.com/scottcorgan |
| https://twitter.com/scottcorgan |
- 2 Followers
- 53 Following
- 17 Posts
moved to @scottcorgan because this one is always down
@elly just stumbled on this. AppreNtly it’s all CSS and HTML, not canvas.
@davekarpf perhaps!
But my timeline full of music, sports and FE Dev is as busy as ever. It’s kind of irritating to navigate it with all the bugs on Twitter now.
Most of the people in that circle that have left still find more of an audience and value on Twitter it seems.
@tomsherman it’s surprising how many scaffolds and templates use “*”
@elly From working on InVision Freehand, I can mostly confidently say that the complexity and performance requirements to allow a user to create anything anywhere on an infinite canvas is very difficult to achieve in html/css only.
@elly The biggest headache we had back then wasn't so much performance, but forks; "many roads lead to the same result", and which fork to choose. Performance wasn't an issue because we were working with a much smaller subset of html/css and what type of graphics would need to be generated (because it was constrained to Bootstrap components).
@elly I can't find any old blog posts, but here are two apps from back in Bootstrap's heyday.
https://designshack.net/articles/css/divshot-an-awesome-way-to-design-and-build-bootstrap-pages/
https://designshack.net/articles/css/easel-a-wysiwyg-bootstrap-page-builder/
I was a main dev on the Divshot builder linked above. It was all html/css based because it generated bootstrap compatible code from the WYSIWYG.
Divshot: An Awesome Way to Design and Build Bootstrap Pages
Recently, we took a close look at Easel, a web-based site builder that leverages Twitter Bootstrap. Today we’re following that up with a tour of a very similar tool: Divshot. With Divshot, you can quickly and easily build clean, responsive web page layouts using a combination of visu...
@elly for sure the right question.
Not a proven fact, but it would seem like most design tools use tech optimized for performance of large documents (I worked on InVision Freehand for years and can confirm that WebGL was chosen because it was fast for large documents, not because it was easy to translate from design to code).
A lot of early in browser design tools started with the DOM, then moved to SVG, and most eventually end up in WebGL land.
@Gigawatt121 at least please drop the intros to the videos