CSS Shapes Editor for Chrome
razvancaliman.com
razvancaliman.com
I think dev-centric vector tools present a really good opportunity to improve the workflow between devs and designers and change the way many of us design web UI/animations. My main goals and interests:
- modular tools that are not encased within a monolithic editor
- animation/key frames
- renderer agnostic (for use with canvas/WebGL/CSS/etc)
- publishing path/animation state as a npm module, so that others could just "npm install spinny-preloader"
- ultimately building a suite of tools for more fluid motion graphics that render in real-time in the browser, but look just as good as something from After Effects
I wonder if some aspects of your tool could be reused for some of these goals.
https://github.com/artursapek/mondrian
The original idea was also to create an animation tool which could export to canvas code and/or SVG files with embedded JS. Ended up just being a generic SVG editor.
I eventually couldn't keep committing the time to develop it, but it was a fun project for a long while. Really got interesting when I started thinking about algorithms for something like Pathfinder (unfinished work: http://artur.co/pathfinder.html) and a freehand drawing tool which outputs cubic beziers (the crayon tool in my example). Also fun was coming up with data structures for undo/redo (mine still kind of suck).
Anyway, have fun with your project.
I always find "monolithic remakes" to be doomed from the start. So my current goal isn't to create the full app, but focus on it's different parts. Eg. the path-illustrator should be modular and standalone, and easily integrated into larger tools with perhaps different agendas. Same with timelines, SVG import/export, etc.
Off-topic: I'm looking for a remote part-time job as JavaScript Developer, if anyone is interested write me an email (ivanca@gmail)
There's also a polyfill, incidentally: http://blogs.adobe.com/webplatform/2014/05/12/css-shapes-pol...
[0]: http://bit.ly/blinkintents
[1]: http://9to5mac.files.wordpress.com/2014/06/screenshot-2014-0...
Even chrome and firefox, which auto-update their browsers in order to keep everyone on the latest version - which should let websites use new features earlier - seem to have around 1/4 to 1/3 of their users on old versions,
http://cdn.arstechnica.net/wp-content/uploads/2014/09/chrome...
http://cdn.arstechnica.net/wp-content/uploads/2014/09/firefo...
which is worrying.
hyphens: auto
https://developer.mozilla.org/en/docs/Web/CSS/hyphensor is it still better to rely on adding soft hypens via script? Like hyphenator.js https://code.google.com/p/hyphenator/
With no version of chrome supporting it it seems like a bad idea to rely on it.
It's still a neat effect for creating little asides, blurbs, etc. though
Sounds pretty flexible to me.
Defining the length of each line of text is a backward-facing solution and should be discouraged.
It's the same reason why we don't use absolute positioning in pixels to do all our CSS layout.
Custom shapes can be very finicky in when they break or don't break certain lines. Designing such a breaking-shape for a print magazine depends not only on the shape of the image, but is tweaked considerably depending on whether it breaks on a particular word on a particular line, and how this looks in the context of the page, spacing, readability, etc. Sometimes you can see this went wrong when a text has been edited without adjusting the shape. On the web with different mediums, resolutions, fonts and rendering, you can pretty much expect this to turn out wrong a significant part of the time.
But note that this is a general spec for adding shapes to HTML elements. Wrapping text around images is just one of many possible use cases.
But if you're asking why the shape is being defined with text, inline in the CSS, that's because defining shapes with SVG was postponed to level 2 of the CSS Shapes spec.
http://dev.w3.org/csswg/css-shapes-2/#referencing-svg-shapes