Looks very nice, but i will never use something like this as SAS. This needs to be downloadable and embeddable in a private product (like a CKeditor), otherwise i'd never use it.
Could you explain a little more why you feel that way?
Divshot
71–80 of 113 posts
Re: Divshot
#72Looks very nice, but i will never use something like this as SAS. This needs to be downloadable and embeddable in a private product (like a CKeditor), otherwise i'd never use it.
The editor itself is completely static HTML and written in CoffeeScript/Spine which gives us a lot of flexibility. We're exploring different opportunities for integration and possibly a downloadable version.
Re: Divshot
#73Got any sample output? I'd love to compare notes on the HTML your tool creates. I'm interested in this type of app, as I've built a design prototyping tool called Edit Room, that also creates production-ready HTML and CSS from visual design tools. http://www.edit-room.com/ Good luck!
Here's some 100% unmodified output from a page I threw together in about a minute just to post here: https://gist.github.com/3743829
That's some serious divitus going on with the nav. 5 nested divs for top navigation? No HTML5 elements?
Re: Divshot
#74Earlier quoted context omitted.
Right, but which part of the dev/design process is it taking over? Do you guys see divshot taking over production ready front end development the way Balsamiq (and the likes, arguably) took over pen & paper? Given the predecessors to divshot in the WYSIWYG world, expect many developers and designers to be extremely open minded, yet very skeptical.
We definitely expect some skepticism given past WYSIWYG entries into the space, but we consider our prime directive to be "No matter what, the output is clean." We hope to be a tool that developers will use to rapidly prototype an interface at the beginning stages of an application and then continue to use it to experiment or quickly build new functionality throughout the app lifecycle. Hope that answers your questio…
It does, and I appreciate it. Thanks.
Re: Divshot
#75Earlier quoted context omitted.
Here's some 100% unmodified output from a page I threw together in about a minute just to post here: https://gist.github.com/3743829
That's some serious divitus going on with the nav. 5 nested divs for top navigation? No HTML5 elements?
We're following the exact docs for Twitter Bootstrap with regards to HTML output, and yeah it can sometimes get a little div-heavy. We will be supporting other UI frameworks as well as emphasizing semantic HTML as much as possible as we grow beyond Bootstrap.
Re: Divshot
#76I'm waiting for a beta invite for more than a month, I hope this hints of a upcoming release? The competition ( http://jetstrap.com/ ) is not waiting...
We rolled out our beta yesterday, sending out invites in short waves. You should get one very soon. Thanks for being patient!
Yeah I wanted to try it out too but never got an invite. I'll probably just forget about this site in a few hours.
You should let more people try it even if it means stumbling upon a few bugs than to turn away people who are genuinely interested in trying.
Re: Divshot
#77Earlier quoted context omitted.
That's some serious divitus going on with the nav. 5 nested divs for top navigation? No HTML5 elements?
We're following the exact docs for Twitter Bootstrap with regards to HTML output, and yeah it can sometimes get a little div-heavy. We will be supporting other UI frameworks as well as emphasizing semantic HTML as much as possible as we grow beyond Bootstrap.
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%.
Re: Divshot
#78Earlier quoted context omitted.
We rolled out our beta yesterday, sending out invites in short waves. You should get one very soon. Thanks for being patient!
Yeah I wanted to try it out too but never got an invite. I'll probably just forget about this site in a few hours. You should let more people try it even if it means stumbling upon a few bugs than to turn away people who are genuinely interested in trying.
I'm still reviewing comments and sending out invites to new followers, sorry you haven't received one yet! We opted for a private beta in short waves so we can learn more about our users and address their early feedback. I wasn't able to find your email so give us a shout if you're still interested. Click the "Contact" link in the footer. Thanks!
Re: Divshot
#79Earlier quoted context omitted.
We're following the exact docs for Twitter Bootstrap with regards to HTML output, and yeah it can sometimes get a little div-heavy. We will be supporting other UI frameworks as well as emphasizing semantic HTML as much as possible as we grow beyond Bootstrap.
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 :)
Re: Divshot
#80Why 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…
It's less about it being responsive in real-time and more about it being responsive across a wide array of devices with different size screens.