Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Divshot

divshot.com

Post reply on HN
Print view View original

61–70 of 113 posts

Re: Divshot

#61

Post by ckrailo »

jakejohnson wrote: post #11
cadab wrote: post #4

Any chance for some invites? I'd love to try.

We'll be reviewing comments here throughout the day and if we can easily find your email you might receive an early invite!

If I'm going to use this soon, now's the time since I'm prototyping out a web app. I'd love an early invite while the timing's good. (The email I signed up with is my username here at gmail.)

Edit: Either you saw me or I just got lucky. Thanks a bunch! I'll be sure to share feedback (even if it's just saying good job). :)

Re: Divshot

#62

Post by tharris0101 »

mbleigh wrote: post #19
tharris0101 wrote: post #10

I'm not sure I'd use something like this for production, but anything to let me do mock ups quicker is nice in my book. Can't wait for the invite.

We think you might be convinced to use it for production once you see the output HTML. Stay tuned!

I hope you're right! I got the invite so I'll try it tonight

Re: Divshot

#63

Post by TazeTSchnitzel »

tarr11 wrote: post #38
CGamesPlay wrote: post #24

Why 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…

Some examples: * Resizing your browser window. * Changing font-size for accessibility (Ctrl+, Ctrl-) * Moving your browser between multiple screens If responsive was server-side, each of these scenarios would cause a page reload in order to accomodate the adjusted layout. Responsive design doesn't just mean CSS media queries. It more commonly means using floating div/ul instead of tables for layout.

>Resizing your browser window.

I love responsive design for exactly this. I often have small or large browser windows, and being able to choose instead of being constrained by fixed-width sites is great.

Re: Divshot

#64

Post by cyscott »

jakejohnson wrote: post #11
cadab wrote: post #4

Any chance for some invites? I'd love to try.

We'll be reviewing comments here throughout the day and if we can easily find your email you might receive an early invite!

This looks perfect! Can I get an invite? cscott@gmail.com

Re: Divshot

#65

Post by lallouz »

timdorr wrote: post #7

Interesting 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.

Who is the target market for what you are describing though (or for divshot for that matter)? Is it meant to be for slightly less technical people? Is it meant to take over all development/developers in the future?

Being a seasoned developer, front, middle and back end, I find this an interesting product, but something that I would likely never use more than "playing around". I'm not trying to troll here, I'm legitimately curious if anyone else feels this way.

Edit: I did sign up for an invite over a month ago, and I am legit excited to give it a go.

Re: Divshot

#66

Post by mbleigh »

lallouz wrote: post #65
timdorr wrote: post #7

Interesting 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.

Who is the target market for what you are describing though (or for divshot for that matter)? Is it meant to be for slightly less technical people? Is it meant to take over all development/developers in the future? Being a seasoned developer, front, middle and back end, I find this an interesting product, but something that I would likely never use more than "playing around". I'm not trying to troll here, I'm legitim…

We're building Divshot to be a tool that professional developers and designers use every day. I totally understand the "I would never use it for more than playing around" approach, but that's how it starts (see e.g. http://cdixon.org/2010/01/03/the-next-big-thing-will-start-o...). All I can say is give it a chance, watch how it grows, and I think you'll change your mind.

Re: Divshot

#67

Post by SchizoDuckie »

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.

Re: Divshot

#68

Post by superchink »

jakejohnson wrote: post #53
SoftwareMaven wrote: post #44

I'm right at the beginning of designing my templates for a Bootstrap/Django project, so this is a really great time to see this. I'd really like the ability to tweak the designs without needing to edit a text file and reload the browser. Question: do you guys support custom Bootstrap themes? (Oh, and I wouldn't turn down an invite. The email I signed up with is in my profile.)

You're in. Can't wait to hear your feedback and ideas! A: We plan to support custom Bootstrap themes in the near future. Stay tuned!

I'm in a similar boat; never received an invite, but looking forward to trying it out… any chance at getting into the beta? You have my word this will be the last such request.

Re: Divshot

#69

Post by lallouz »

mbleigh wrote: post #66
lallouz wrote: post #65

Earlier quoted context omitted.

Who is the target market for what you are describing though (or for divshot for that matter)? Is it meant to be for slightly less technical people? Is it meant to take over all development/developers in the future? Being a seasoned developer, front, middle and back end, I find this an interesting product, but something that I would likely never use more than "playing around". I'm not trying to troll here, I'm legitim…

We're building Divshot to be a tool that professional developers and designers use every day. I totally understand the "I would never use it for more than playing around" approach, but that's how it starts (see e.g. http://cdixon.org/2010/01/03/the-next-big-thing-will-start-o... ). All I can say is give it a chance, watch how it grows, and I think you'll change your mind.

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.

Re: Divshot

#70

Post by mbleigh »

lallouz wrote: post #69
mbleigh wrote: post #66

Earlier quoted context omitted.

We're building Divshot to be a tool that professional developers and designers use every day. I totally understand the "I would never use it for more than playing around" approach, but that's how it starts (see e.g. http://cdixon.org/2010/01/03/the-next-big-thing-will-start-o... ). All I can say is give it a chance, watch how it grows, and I think you'll change your mind.

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 question.

Post reply on HN