News for hackers. Stuff that matters.

GiovanniFrigo

Been using your tool almost since day one. It's lightweight and simple enough to provide me with exactly the metrics I need. Keep up the good job!
Re:Attacking the Washington, D.C. Internet Voting System [pdf] on Wednesday November 23, 2016 @03:06AM (#13020977)
This attack is really accurate and well-crafted.. and scary at the same time. Unfortunately, seems like we are not ready for Internet Voting Systems yet!
Re:Show HN: A fork of sudo with Touch ID support on Monday October 31, 2016 @04:10AM (#12834943)
I love this. Should buy a new MacBook just to be able to use this :D
Re:Intel acquires Itseez, company behind OpenCV on Wednesday June 01, 2016 @04:21AM (#11812845)
What a misleading, click-baiting title..
Re:How to build a Telegram BOT to suggest you pizza on Tuesday March 22, 2016 @12:39PM (#11337775)
/me likes pizza, /me likes bot
Re:Show HN: A React.js yearly calendar component on Wednesday November 18, 2015 @04:06AM (#10586718)
Thanks for the suggestion! will surely look into making it more accessible!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @03:44PM (#10577016)
check out http://react-components.com, they have a nice collection there!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @02:36PM (#10576589)
No market research here, TBH! It is a component extracted from a project we did with our agency Belka, but we'd love if people start using it in other projects!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @02:34PM (#10576569)
Great! thanks for the explanation and the docs!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @12:51PM (#10575831)
Great! yeah that was definitely something I wanted to add, here in Italy we usually use Monday as week start.

Feel free to submit a pull request then! I just kindly ask you if you could use airbnb's Javascript and React style guides, that is a pretty good standard IMHO https://github.com/airbnb/javascript/tree/master/react

Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @12:23PM (#10575672)
That reduced the click delay from approx 90ms to 67ms, that's a pretty solid -25% there! Thanks for the suggestion, @jkkramer!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @12:02PM (#10575533)
Thanks! Useful links, I didn't know anything about this. Will surely start using the `NODE_ENV=production` environment variable from now on!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @11:28AM (#10575308)
Also, you can get way more competent answers on reddit (/r/reactjs) or on stackoverflow :)
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @11:25AM (#10575294)
I suggest you to read this (http://stackoverflow.com/a/31638988/2304450) very good stack overflow answer, you'll find some interesting introduction to inline styles if that's what you were looking for.

A different approach could be to pass a `classScope` string props down to the components, and each component then applies it to the classes it uses (Example: return (<div className={this.props.classScope + "inner-div"}></div>); ). This way we could achieve better css selector scoping, at a cost of a slightly more verbose code when using a component.

Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:53AM (#10575073)
Yeah, we are belka.us and we are not ashamed of doing self-promotion here.

I don't see what's wrong here: every company in the IT world releases open source components: Django, Bootstrap, Foundation and React itself are open source projects backed by companies. But there's also smaller things being released every day, and each of them contributes to the great world of open source.

We use open source, we give back to the open source community. We are giving away our time for free releasing a component, I don't see anything bad adding a small link to our website.

Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:43AM (#10575023)
You definitely won't use this for date selection, but we found it useful to layout the whole year and to review it at a glance.

Thanks for your kind words anyway! :)

Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:40AM (#10575005)
Will surely do, thanks! Also, how did you test the onClick delay? by spamming timestamps in the code? :D
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:39AM (#10575000)
Yeah, that's a component, no more, no less.

I just wanted to share this, I think some people disagree with you if I am in homepage right now

Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:15AM (#10574855)
Please do! Also if you have any feature request use github's issues to let me know!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @10:14AM (#10574844)
Any idea on how one could optimize the rendering function to reduce this lag (which BTW I can barely see on my 2015 MBP)?
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @09:44AM (#10574665)
Cool! If you find any bug or have any feature request please open an issue on github!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @09:44AM (#10574662)
Yeah that's another interesting use case! Maybe I'll add the "select period" feature, thanks for the idea!
Re:Show HN: A React.js yearly calendar component on Monday November 16, 2015 @09:37AM (#10574631)
It's definitely not common, but sometimes it's useful to have the whole year under your eyes.

Basically we needed it for a project where we had to display how an year was subdivided into 4 different periods. Here we also highlighted the working, festive and prefestive days.

I think it turned out to be an interesting layout, you can see it here: http://postimg.org/image/4yqaywm2r/.

Errata corrige: 84 MB. 120 was the debug build!
I won't call 120 MB (total weight of our app, including assets) an impressive amount of space. Also consider it's something people will use for work purposes, an unique configuration tool instead of having 3 or 4 small tools to configure each single meter type.
I get your point here, but since the bundled Chromium version is compiled by ourselves we do not rely on an external toolset, allowing us to support just one version at a time. If you're intrested, we use Sparkle (http://sparkle-project.org/) to deliver remote software updates.