Show HN: a web-based xkcd-style comix editor
cmx.io
cmx.io
For a weekend project, this guy created a UI that deals intuitively deals with angles, bezier curves, dependent relations between objects, and turns it all into HTML, and you guys are that butt hurt it only works in Chrome?
Think about the endless possibilities. On top of that it will be possible to build a library of objects like: "NormalGuy", "Ninja", "Tree" and so on.
Then it will be cool to programmatically move them. No Idea if that is feasible or not. Maybe not, but I will say otherwise.
Then we could describe an environment in which they could act in a declarative way. We could add simple behaviours shaped on top of simple goals. Those goals could be described in a similar way as the environment. If we tie a behaviour to an animation we have small drones of "Ninja" that act on themselves (well..kind of).
Or we could move those animation with the keyboard. I mean, at this point possibilities are just to be enumerated.
At the end it will be like a DSL to describe animation and behaviour and environment. Like an engine for videogames, animation, even smart behaviour (not mentioning AI and similars)
I don't know, I smell something really great behind that think that you built.
WebKit - the new IE.
If it's using -webkit prefixed CSS, that's pretty unlikely.
> What if I want to look at the web console to see just what breaks in case I know what the issue is?
Anyone interested in doing that should be well aware of how to spoof a user agent.
Unsupported CSS features should not affect the functionality of a web app, only its appearance. Emphasis on "should"; far too many web apps end up fundamentally broken when this happens.
If you're building a fun hobby project, you can do whatever you like, including building it in a specific environment.
However, it does limit feedback for any of us not using Chrome. Author is probably cool with that though as it appears and I commend them for not making us jump through hoops to try it anyways by switching user agent.
You are not answering the question. Why block a user-agent, if the check can be easily worked around?
Edit: I mean why block as opposed to display a simple warning ("this site is known to not work well with your browser").
A: "If it's using -webkit prefixed CSS, that's pretty unlikely."
There's actually been talk of non-Webkit vendors supporting the webkit prefix. Opera already does, Microsoft and Mozilla have said they need to support it in at least some cases.
"Non-WebKit browser vendors first started talking about implementing the -webkit prefix [in February of 2012] during a CSS Working Group meeting. Microsoft, Mozilla and Opera all said they felt the need to support -webkit, lest their users be relegated to an inferior browsing experience (because so many sites are using only the -webkit prefix)."
http://www.webmonkey.com/2012/04/opera-forges-ahead-with-pla...
Tantek Çelik of Mozilla: "At this point we're trying to figure out which and how many webkit prefix properties to actually implement support for in Mozilla. Currently we have zero. Zero is no longer an option for us."
Florian Rivoal (Opera), Sylvain Galineau (Microsoft): "Zero is not an option for us anymore either."
http://lists.w3.org/Archives/Public/www-style/2012Feb/0313.h...
I'm going to push new version which will allow you to continue over that warning.
For what it's worth, though the visual editor doesn't work in Nightly, the code editor + saving does work! It was really fun to mess around with the source and edit your sample comic. Great work!
IE was an attempt to aggressively eject the competition and kill the open web. When the web stubbornly refused to buy into IE-only technologies, it became Microsoft's dog in the manger, holding back the day that web apps made the OS irrelevant. It was good, technically, and then it was bad, technically, but it was always always evil.
We're doomed to repeat the same mistakes over and over again.
You can run Chrome on Linux, Mac and Windows! And at least in theory you can have a go at trying to port the Chromium browser to other platforms, as well.
It works, fairly well. But I spent about 15 minutes doing one panel, trying to figure out the minor nuances. I kept thinking to myself "I could do a whole comic in about 5 minutes in photoshop" as I adjusted the person's location, arm, speech, etc (and that was just modifying the characters that were already in the scene). In the end it was just not worth it in my mind.
Also, imagine creating something like Randalls "Click and Drag" comic (xkcd.com/1110/) -- how would you create all these custom objects in the editor without changing it into something similar to an HTML5 web-photoshop, at which point you might as well do that?
I think it has some upsides too. You may treat comix source as html code and apply tools we have for coding today, eg. diffs, version control, collaboration via github. People may also collaborate on library of items, actors and their poses, so you don't have to re-create them or copy&pase all the time. Also localisation will be a snap. And it will possibly allow animations in the future.
Actually I built this for a bigger project. I want to explain Bitcoin technically in the form of XKCD comix. This won't be one-off comix strip. This will be something like wiki/book which will evolve and I hope it will attract other contributors (not necessarily graphic designers).
But I think you're strongest element is the WYSIWYG editor, as most people aren't going to be coding from only the HTML view (unless they know what pose="-11,9|-5,117|-11,99" will look like in their heads). But the WYSIWIG interface is still pretty anemic, meaning I'm going to run into roadblocks faster (such as -- how do I create something like a tree? How can I add a hat to the man?).
Heads should be customizable in the future: https://github.com/darwin/cmx.js/blob/master/app/lib/cmx/ent...
Actually the system already supports attach points, so you can attach items to hands, foots and necks (right now the bubble is attached by default to a head bone).
The last generic piece which is missing will be <drawing> element. Right now it just allows you to specify lines. In the future it will enable you to insert any SVG which is convertible down to paths. I will just resample them and convert them into XKCD-style lines while keeping other styling. This will enable you to insert arbitrary SVG drawings in the scene. I won't create web-based photoshop for SVGs, I will let you import SVG created in other tools as long it is convertible to paths. Imagine it as embedding bitmap images into HTML files. This will be similar idea.
The WYSIWIG will come in it's million forms later and you shouldn't focus on it.
I just need comix.vim and I'm good.
I'm imagining real time comics. Chat comics. Comic discussion forums. It's endless! ;)
It'll be 1996 all over again: http://en.wikipedia.org/wiki/Microsoft_Comic_Chat
That was my first thought when I saw the markup. Brilliant work!
But on another hand, some things are more complicated that one expects. Can you really draw well enough? Can you share an example of a xkcd-style comic?
Perhaps I need to get back to doing some actual work...
Have you considered this as an educational tool? This is a fun and useful introduction to HTML and markup languages in general.
Would it be possible to highlight the relevant markup node when you've selected an object in the visual editor? That would be neat from a learning perspective.
Those who have seen it will know what I'm referring to.
Unfortunately, the editor does not work for me. It makes Chrome crash the page :(
I'm running Chrome 24.0.1312.69 on one of those new Dell XPS 13 Ubuntu machines running 12.04.2 LTS. Is there any other information you'd want for debugging, or pages to try?
http://yuml.me/diagram/scruffy;/usecase/edit/[Bob]-(This%20i...
T
http://my.opera.com/ODIN/blog/300-million-users-and-move-to-...
I feel uncomfortable with the use of non-namespaced tags and squatting on common terms. For example, cmx.io uses tags like <scene>, <label>, <drawing> and so on. I really would prefer it used something like <cmx:scene> or <c:scene>, so that it would be possible to mix CMX tags with other libraries that use similar tag names.
For anyone interested, here's my play: http://cmx.io/#4949114
It reminds me I have to build some feed with published comics :)
Hey K., do you remember? You interviewed me back in 2009 for a Bespin position :-) The world is pretty small. Hope you are doing well.
I just get an error message saying that the page script was taking too much memory and was stopped.