Any known issue with Chromium? I just get an error message saying that the page script was taking too much memory and was stopped.
Same here (Version 24.0.1312.56 Ubuntu 12.10 (24.0.1312.56-0ubuntu0.12.10.3))
Show HN: a web-based xkcd-style comix editor
71–80 of 116 posts
Re: Show HN: a web-based xkcd-style comix editor
#72I think its brilliant. I love the balance you've created between the visual editor and the markup.
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.
Re: Show HN: a web-based xkcd-style comix editor
#73"STOP! WebKit is required here. The Comix Editor was tested under Chrome. It uses some webkit-specific tricks." WebKit - the new IE.
The main problem with IE wasn't that it was an exclusive product incompatible with other browsers. The problem was that it was bad. I'm not a fan of people only supporting WebKit, but at least WebKit browsers are good .
Actually, for a while, IE was the best browser available. It was lighter weight, faster than Netscape, and had better web standards support. Mozilla, with its new Gecko engine, took a long time to mature, and was still fairly slow and bloated until Firefox (née Phoenix) came around. Remember, IE was where several features that now form the basis of the modern web came from. Heard of something called XMLHttpRequest? That came from IE.
Re: Show HN: a web-based xkcd-style comix editor
#74Earlier quoted context omitted.
A warning is fine, but I just hate it when a site doesn't even let me try in another browser. I use Firefox Nightly, maybe it fixed the issues that are breaking your app? If you're detecting via user agent, what if I use an odd user agent? What if I want to look at the web console to see just what breaks in case I know what the issue is?
> I use Firefox Nightly, maybe it fixed the issues that are breaking your app? 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.
Q: "I use Firefox Nightly, maybe it fixed the issues that are breaking your app?"
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...
Re: Show HN: a web-based xkcd-style comix editor
#75Earlier quoted context omitted.
"Anyone interested in doing that should be well aware of how to spoof a 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").
So non technical users go "oh, I'll take a look in Chrome", not "this thing's stupid, nothing works".
The same thing can be achieved by displaying a simple warning that lets users bypass it ("oh, I was warned it might not work in my browser, and indeed it doesn't, I will take a look in Chrome").
Re: Show HN: a web-based xkcd-style comix editor
#76Marry me.
Re: Show HN: a web-based xkcd-style comix editor
#77Here's my problem. 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 somet…
Yes, this a prototype and definitely not for everyone. It has many downsides. I agree Photoshop gives you full pixel control. 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…
> And it will possibly allow animations in the future.
That was my first thought when I saw the markup. Brilliant work!
Re: Show HN: a web-based xkcd-style comix editor
#78Earlier quoted context omitted.
OP is missing the point - the markup idea is brilliant. 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! ;)
> Chat comics. It'll be 1996 all over again: http://en.wikipedia.org/wiki/Microsoft_Comic_Chat
Damn, good memories of that, forgot what it was called!
Re: Show HN: a web-based xkcd-style comix editor
#79"STOP! WebKit is required here. The Comix Editor was tested under Chrome. It uses some webkit-specific tricks." WebKit - the new IE.
Yep. HTML Standards webkit Chrome proposed standards.
We're doomed to repeat the same mistakes over and over again.
Re: Show HN: a web-based xkcd-style comix editor
#80Earlier quoted context omitted.
> I use Firefox Nightly, maybe it fixed the issues that are breaking your app? 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.
They should at least include the non-prefix css (or other prefixes) as well for when a feature becomes available on other browsers in case they forget to update it or if they're not aware of what other browsers support.
or use something like this