Live data from Hacker News

Ink – Interface Kit

ink.sapo.pt

51–60 of 73 posts

Re: Ink – Interface Kit

#51
post #9

It feels to close to Bootstrap without bringing enough new stuff to the table to be worth it. It's nice to see people making alternatives, but it needs to be a lot more developed.

Well, like I said above, it addresses some internal issues my colleagues had. It also tries to make a lot of things simpler for web designers (especially regarding the grid system) without tying you down too much.

Re: Ink – Interface Kit

#52
post #23
post #18

Earlier quoted context omitted.

Forms is a nice addition over Bootstrap for me.

Bootstrap has always had forms.

We have always been at war with Eurasia :)

Seriously now, yes, Bootstrap has always had forms. But as a developer who merely dabbles in design, I personally prefer Ink's markup because it's responsive off the bat (at least compared to BS 2.0, haven't tried 3.0).

Re: Ink – Interface Kit

#53

Can we please come up with a better markup for form element grouping than "div.control-group"? Specifically, HTML has always allowed nesting an inside - and that's more than enough to create either a horizontal or stacked layout. No s needed. And no "for" attribute needed with an unnecessary input ID.

To my knowledge this is incorrect. Assistive technologies don't recognize input names when nested inside of label elements, and as a result is frowned upon by the W3C. Unless you meant something else by, "...HTML has always allowed nesting an inside ..."

Source: http://www.w3.org/TR/WCAG20-TECHS/F68.html

Re: Ink – Interface Kit

#54

Earlier quoted context omitted.

They support IE7, which I believe Bootstrap 3 has dropped. If you don't do the comparison yourself, you're at risk of losing out.

I'm at risk of losing out if I have to go through 20 pages of documentation and compare line-for-line against Bootstrap rather than the creator going "we decided not to just re-skin Bootstrap primarily for reasons A, B, and C".

I'm going to reveal a big secret. I actually managed to find out the tidbit about IE 7 without reading it line by line.

Their primary job is not marketing. Their primary job is to build the framework.

Why do you think things like Y Combinator exists? They do some work others aren't willing to and others lose out because of it.

It's to the developer's benefit to tell you why his product is good, but it's not their duty. These guys worked on and released a free product for you. You can choose to use it if you want but they don't owe you anything or an explanation of why it's better than Bootstrap.

Re: Ink – Interface Kit

#55
post #48
post #14

I think this is cool, so I say good job on that front. But I kind of feel like you're trying to introduce yet another low end sedan. There's already hundreds, and I've already purchased one. It's gonna take at least a few more years for me to be ready to shop for a new one.

Well, we're not actually selling, but rather giving it away :) Seriously now, it's been in internal use for a good while because it solved problems that Bootstrap didn't address (like the particular grid flavour and some corner cases in responsive layouts), and the best way gather feedback and improve it is, of course, making it public.

It's a technical debt metaphor. Myself and the company I work for have all learned the caveats of bootstrap and how to hack through them. Now it's happily sitting in most, if not all, of our projects. It just doesn't make sense for us to change at this point.

Re: Ink – Interface Kit

#56

Earlier quoted context omitted.

I'm at risk of losing out if I have to go through 20 pages of documentation and compare line-for-line against Bootstrap rather than the creator going "we decided not to just re-skin Bootstrap primarily for reasons A, B, and C".

I'm going to reveal a big secret. I actually managed to find out the tidbit about IE 7 without reading it line by line. Their primary job is not marketing. Their primary job is to build the framework. Why do you think things like Y Combinator exists? They do some work others aren't willing to and others lose out because of it. It's to the developer's benefit to tell you why his product is good, but it's not their dut…

Nowhere did I imply they had a duty to do so - just that it'd be to their benefit, because the people considering such a framework have dozens to choose from that all look alike. They presumably put it out there because they'd like people to use it.

Re: Ink – Interface Kit

#58
At first I thought the filepicker.io folks, who recently rebranded as Ink, had released a UI kit.

Of course they don't own those 3 letters which have a wide array of meaning, similar to words like "bootstrap", "ember", "buffer", or "backbone". I'd be hesitant to use those words in a product, open source or otherwise, however.

Re: Ink – Interface Kit

#60
I may give this a shot. The way they manage columns without needing to specify the number of columns in a div seems nice.

For instance, if I want a two column layout, I put two divs inside the '.column-group' container. Now (theoretically) if I were to dynamically add a third column, it seems that Ink would automatically adjust the other two columns to fit.

With bootstrap, I would need to change the '.spanx' of each div within the '.row'

Post reply on HN