Could you share how do you combine the hourly cost with wattage readings?

kwh x $

Price is generally a dollar figure for 1000W per hour.

Thanks! Unfortunately all my data readings are in kW. I've been trying to figure out how to get hourly roll-up working and then multiply each hourly reading by price in Prometheus.

The goal of the DEA is not to reduce crime or address drug usage. The prime objective is to generate profit via asset forfeiture and cash seizures. The doctors and pharmaceuticals can sue back, and nobody wants that.

> I wouldn't do it by standing at a whiteboard racking my brain for the details, and I certainly wouldn't set a one-hour timer.

That...

That's where peer-review comes in. Hopefully you aren't committing to master all by yourself these kind of changes.

I'm not clear if your question is why do people write or why do people use static site generators?

the question was "why do people write static site generators" (see the linked tweet) - sorry for not making it clear enough

It's not StrongLoop marketing. I wrote the article and also haven't heard about your modules. I try to stay up to date with NPM (running http://npmawesome.com/) and unfortunately completely missed your work :(

I agree that libraries should not be handling errors in any unusual way, or better yet just re/throw them and let consumer take care of that. That's where the promises/zones might be useful.

Right. I don't mind if people want to use promises in their own code as long as they don't force their use on library users.

have you tried Co (https://github.com/visionmedia/co) and if so what's your experience?

Looks very solid, please mention somewhere that it's jquery based, i have to check the source to figure that part out

What do you guys think? Yay, nay?

After rolling my own solution for tokenized autocomplete a few times, I love the idea. I found a few nits, though.

1. I assumed that autocomplete would catch the word "autocomplete" after I deleted the token. It took me a while to find a word that was in the autocomplete collection. Might be a good idea to choose default tokens that are in the demo collection.

2. I found the dropdown triangle to the right confusing. What is it supposed to do?

3. Arrow keys don't work properly on text before it is committed to a token. The insertion point keeps getting bumped to the end of the word. Likewise for clicking in the middle of a word before it is tokenized.

4. Finally, I think as many people expect the tab key to tokenize the current word as those who expect the enter/return key to do that. Having the tab key jump focus out of the input is probably desirable in some use cases, but not as a default.

I think it's a great idea! I'd love to use it! Some ideas:

- Clicking on a selection didn't make it look like a tag (blue box) - Once you have more than 4 blue tags in the field, additional ones don't get added or aren't visible. It's probably best to add another line of height to see them all. Or to avoid the problem entirely, take the resolved 'tags' out of the input box and put them below. Perhaps by accepting a jQuery selector for where they should be dropped? - It would be nice if the 'prompt' option also read from the html5 placeholder attribute - tag items that are set should probably be settable via the option value not the display text, or maybe both? - An option to remove the blue arrow: if you have thousands of items in the list you don't want to display them all.

Thanks for feedback

> Clicking on a selection didn't make it look like a tag (blue box)

This will be fixed in the next patch release

> Once you have more than 4 blue tags in the field, additional ones don't get added or aren't visible.

I'm able to ad any number of tags and the input expands vertically to accomodate. What browser/os are you on?

> It would be nice if the 'prompt' option also read from the html5 placeholder attribute

Good idea, will add it to the queue!

> tag items that are set should probably be settable via the option value not the display text, or maybe both?

Not sure what you mean.

> An option to remove the blue arrow

Blue arrow comes from the Array plugin, omitting which will result in the missing arrow.

I see the input expand vertically now, cool! Looks like duplicates are allowed, which probably shouldn't.

On the tag items I meant that in your demo code you have: tagsItems : [ 'jquery', 'plugin', 'tags', 'autocomplete' ],

Which is a listing of the items to include by their visible text. My suggestion is to use an ID instead (if they're objects). I ran $('input#textarea').val() on your demo and didn't get any value, how do you get the value out of the input box?