How about PNG? Is it just me here using Fireworks for web design?
We have plans to do Fireworks as well, but the usage numbers are too low.
Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
71–80 of 129 posts
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#72is there a offline version available ?
We don't have a offline version.
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#73When I click on "Try now" I get a "Bad Request Error 400". Could it be because of me being signed into multiple google accounts?
No, it shouldn't be. Could you please try in incognito window?
It works in incognito window. It does look like it's an issue with multiple account signed in. Yours is not the first site on which Google auth is failing for me when I'm signed into multiple accounts.
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#74Earlier quoted context omitted.
No, it shouldn't be. Could you please try in incognito window?
It works in incognito window. It does look like it's an issue with multiple account signed in. Yours is not the first site on which Google auth is failing for me when I'm signed into multiple accounts.
Ah, ok. When we are signed in into multiple accounts, it allows us to select a specific account to sign in with.
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#75Does Markupwand use scripted Photoshop instances in the background? And if so, how did you manage to work around the fact that the standard Photoshop license does not permit such use?
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#76Earlier quoted context omitted.
As a designer, I've never "implemented" in Photoshop. Ever. Illustrator, yes (a long time ago), but there's nothin' like coding your own design. In fact, I design entirely with HTML/CSS (using the Live CSS Editor feature of the Web Developer add-on for FireFox) and use Illustrator to mix and pick colors.
I cannot tell you how much I wish all designers worked this way. I spend more time cutting PSDs than I do building the backend of the site (which is what I am actually hired to do).
Yep, every web development job I've ever had has required me to get Photoshop installed, usually sooner rather than later. Then the company moans and drags their feet about licensing costs etc. My current Mac has one old cracked version of Photoshop, one version with an expired trial, and the Gimp...
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#77Earlier quoted context omitted.
>divs are not semantic HTML This is very wrong, divs are as semantic as you want them to be. If you have an element that looks like this: Hello World Then yeah sure it's not semantic because you have two unnecessary divs holding a paragraph, but if it was just the one div holding a paragraph tag it would be perfectly acceptable in HTML 4.x onwards. The only cases I can see a div being non semantic are the silly examp…
> divs are as semantic as you want them to be. Then they are not semantic at all. , , all have semantic CSS class names. But they are not semantic HTML names. Remove the CSS, and all you have is , , and . This makes it difficult for screen readers (and web surfers who don't use CSS (are these people even real?)) to understand what the page is saying. However , , and all have semantic meaning that can be discerned whe…
You cannot use ONLY these "meant to be" semantic tags (, , ...) to describe semantically all the content you have.
Divs is then the only way to go I know.
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#78Earlier quoted context omitted.
As a designer, I've never "implemented" in Photoshop. Ever. Illustrator, yes (a long time ago), but there's nothin' like coding your own design. In fact, I design entirely with HTML/CSS (using the Live CSS Editor feature of the Web Developer add-on for FireFox) and use Illustrator to mix and pick colors.
I cannot tell you how much I wish all designers worked this way. I spend more time cutting PSDs than I do building the backend of the site (which is what I am actually hired to do).
Still better than having to work with 3000x3000 PDF's exported from InDesign...
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#79As the developer of www.psd2html.co.uk I can honestly say I am very happy that someone else out there is doing something similar to me...you might ask why?
When I launched Psd2Html in late 2010, I was unable to get on the front page of HackerNews, or any other website for that matter, I was down-voted to oblivion. I had insulting, slanderous comments posted on the Mac App Store which were untrue.
I was ridiculed by "hand coding only" services like www.psd2html.com, the employee lots of people and don't want to make people redundant, but the problem with this approach is that they will never move forward.
I was certain, and I'm still certain hand-coding will go the way of the Dodo.
So Markupwand, thanks for re-validating the idea, and I'm glad I'm not the only one who thought the idea was worthwhile.
I can see that I need to enhance my service/business model/add relative CSS positioning as an option.
I hope we'll be good competition for each other.
Thanks
Chris
Re: Show HN: Markupwand, magically convert your photoshop files to HTML & CSS
#80Earlier quoted context omitted.
How on earth are div's non-semantic? Most things on a page are just "boxes" -- not lists or links or images or paragraphs, just boxes. And div's are the correct thing to use in this case. Also, "class soup" is a proper CSS programming practice in many people's opinion -- many CSS style guides explicitly state that it's preferable to use descriptive class names in CSS rules, rathen than element names. Mainly because,…
> How on earth are div's non-semantic? Most things on a page are just "boxes" -- not lists or links or images or paragraphs, just boxes. And div's are the correct thing to use in this case. Because most things on a page are not "just boxes". , , and are not "boxes" -- they have semantic meaning. > Also, "class soup" is a proper CSS programming practice in many people's opinion -- many CSS style guides explicitly stat…
Semantic html is overrated in my opinion. As if every web page or application could semantically fit the header, article, footer, summary, section, nav, menu paradigm. I'm not against it, but probably, we will have another set of semantic tags in 5 years, and 10 years later yet another set of semantic tags.