This looks incredible. Eagerly awaiting a beta invite. I can't wait to try this out. Great job Divshot team!
Divshot
101–110 of 113 posts
Re: Divshot
#102Interesting that the tagline is Interface Builder for web sites. One of the big powers of IB is that it ties back into your code so directly. This seems somewhat separated from whatever underlying code I'm creating. I think the killer app is really an IB-for-the-web that plugs into Rails/Django/Symphony/etc so you can start building a web app visually, without sacrificing code quality.
+1 for integration with a template system or CMS, Definitely a killer app.
Re: Divshot
#103Re: Divshot
#104Re: Divshot
#105Interesting that the tagline is Interface Builder for web sites. One of the big powers of IB is that it ties back into your code so directly. This seems somewhat separated from whatever underlying code I'm creating. I think the killer app is really an IB-for-the-web that plugs into Rails/Django/Symphony/etc so you can start building a web app visually, without sacrificing code quality.
I was lucky enough to use the Divshot beta several months ago during a hackathon, and my team's process was indeed to copy the generated HTML into Rails ERB files at the end of initial design. But what was really powerful was the ability to WYSIWYG our way through discussions about what our product would do, and then just publish easily consumed code when we were ready to hack. Our alternative would have been an analogous process in Photoshop (slower and doesn't produce the base code) or to iterate the HTML during the discussion (much slower and requires the designer/developer to switch mental contexts quickly). It worked very well for our purposes and I see it being invaluable during client discussions.
Re: Divshot
#106Nice - I made a prototype of something similar half a year ago - drag&drop designing of bootstrap-based sites :) http://www.screenr.com/vjo8
Re: Divshot
#107For teams where you have non-coding interaction designers and backend designers AND separate marketing teams this could be an awesome accelerator simply because everyone uses the same tool (Bootstrap) but interacts with it in different ways. That's awesome.
Re: Divshot
#108Why is there such a strong focus on "responsive" CSS? It has never made much sense to me, because my desktop will never turn into a tablet, and my tablet will never turn into a smartphone. It seems as though creating a better server-side abstraction that lets me produce different markup that shares much, but not all, of the CSS would be more effective from a development time perspective. If you use responsive CSS, wh…
One issue with server side solutions in general is caching becomes really hard or ineffective. With the client side solutions, like responsive CSS, you're serving one cached, distributed, minified set of data to every client.
What? Really? Having several version of the CSS would not be hard to do in most frameworks.
Also only sending the needed CSS for mobile browsers makes it that much faster.
Re: Divshot
#109How are you getting such clean html from the WYSIWYG, pre or post html processing?
Re: Divshot
#110Earlier quoted context omitted.
Bootstrap creator here. * .navbar is for positioning/sizing. * .navbar-inner is required for the gradient because `overflow: visible;` is not respected by IE when `filter` is present. * .container is for centering the content within the navbar No idea what .navbar-content is—that's not part of the Bootstrap navbar component. We also use a `ul.nav`, not `div.nav`. So, close to the core, but not 100%.
Hey Mark, you're right on every count. The div.nav is a mistake that I thought I had fixed already, as for the rest let's just say it'll be fixed post-haste. Obviously we're HUGE fans of Bootstrap over at Divshot :)
This is why HN is great. Someone (me) posts some constructive criticism, albeit snarky, and within a short time the project founder is getting feedback from Mark Dotto.
I should have also said I think Divshot is pretty cool, even if I didn't like how many nested divs I saw.