I tried to see information for Ontario, Canada, but it keeps loading and never shows the results. Is it a problem, or Ontario was not included in the code?

In any case, great idea and initiative!

We can probably safely localStorage the search results for queries for anywhere between an hour and a day, and it would drastically improve the responsiveness of the application and cut down on network traffic. Consider the case of when the user deletes a particular tag, which triggers a search which they obviously just did earlier but re-requests all the data.

If, after a successful search, you refine the tags/cities you're searching for down to a group that has no results, the "matching startups also tagged with..." list continues to show outdated results. Not sure if this is by design, but it seems flawed to me.

http://cl.ly/1w343T0j0u0v34473y12

When running...

sudo node dev

from the command line, after entering a password, a blank line is printed. There should be a message printed that indicates a successfully running server

Paste this code into the bottom of the page before the closing tag:

Currently, it is easy to miss the loading gif.

We blow up on 0.9: https://github.com/boazsender/StartupDataTrends/tree/0.9

It's great to be able to get valuations by vertical and geographic market but it would be very useful if you could also slice by time period so you could be sure data was accurate for the most recent period (e.g. six months)

So that I can sort the list by screenshot availability

...it should duplicate the search boxes on the left. Looks like it also kills some events too.

Bug!

This is meant more as a discussion for now, but I'm of the mind that global DOM queries are completely out of place when you're writing "modular" client side apps like this. Doing $(".queries .like .this") lets views (or really, an arbitrary code anywhere) completely dig into the guts of other views and spreads state all around modules. I ran into this type of problem when working on #18, when $(".about .loading") was being slid down in the search module, but slid up (and down sometimes too) in the base module.

This type of cross-module messaging is much better addressed using pub/sub (mixing Backbone.Events into modules).

I'm just wondering why there are two search inputs instead of just one "omnibox" (for lack of a better term)

The measure of the intro text should be narrower, and maybe the header/footer/search box could be tightened up a bit.

If you do a search, and then immediately click on a startup, and then click on screenshots, they are not there, which is fine, but then if you click on another startup before it is done loading, you get the wrong detail pain (far right pain) for the startup you are looking at.

When there are enough search results to reach the bottom of the page, the final result renders partially beneath the footer:

Taken in Chromium 18 in Linux.

This also occurs to a lesser extent in Opera 11 in Windows 7. This does not appear to be an issue in the following browsers (on Windows):

• Chrome 16
• Firefox 5
• Safari 5.1

...although it's still a bit close:

Taken in Chrome 16 in Windows 7.

I was unable to verify in IE8 or Firefox 3 since the design doesn't seem to support those browsers for other reasons.

Can you view it on an individual level or just in aggregate? Sorry if this isn't the right forum to do this, but it seemed to be from the website.

You are invited to RSVP for the AngelList User Group in San Francisco on Tuesday March 12th 2013 at 5:30PM. In addition to the User Group benefits, you will have the advantage to discuss StartupDataTrends and get feedback. RSVP here…

http://www.meetup.com/AngelList-User-Group/events/99113522/

Please let me know if you can make it so we can put you on the agenda.

You are welcome and encouraged to share this invitation.

Cordially,

John
https://angel.co/jheuristic

see app/modules/base.js

stats is currently unable to install without a --force option applied to NPM. I'd propose figuring out the sanest versions for all the modules and then committing the node_modules folder directly into the repository ala:

http://eng.yammer.com/blog/2012/1/4/managing-nodejs-dependencies-and-deployments-at-yammer.html

I'm somewhat tied up with Kibits, so for now the best I can do is a dump from JSHint...

$ jshint base.js 
base.js: line 62, col 34, Missing semicolon.

1 error

$ jshint example.js 

$ jshint search.js 
search.js: line 3, col 29, Expected an assignment or function call and instead saw an expression.
search.js: line 4, col 39, Expected an assignment or function call and instead saw an expression.
search.js: line 55, col 10, Missing semicolon.
search.js: line 74, col 8, Missing semicolon.

4 errors

$ jshint startup.js 
startup.js: line 3, col 31, Expected an assignment or function call and instead saw an expression.
startup.js: line 4, col 41, Expected an assignment or function call and instead saw an expression.
startup.js: line 31, col 22, Missing semicolon.
startup.js: line 61, col 49, Expected an assignment or function call and instead saw an expression.
startup.js: line 76, col 36, Expected an assignment or function call and instead saw an expression.
startup.js: line 81, col 18, 'i' is already defined.
startup.js: line 165, col 34, Missing semicolon.
startup.js: line 167, col 11, Don't make functions within a loop.
startup.js: line 166, col 12, Missing semicolon.
startup.js: line 169, col 8, Missing semicolon.
startup.js: line 382, col 31, Missing semicolon.

11 errors

$ jshint utils.js 
utils.js: line 8, col 13, 'val' is already defined.
utils.js: line 12, col 21, Missing radix parameter.
utils.js: line 47, col 41, Expected an assignment or function call and instead saw an expression.

3 errors

I started to address this with #18, but there are still quirks that could be worked out. The "About" screen has too much padding at the top, because the div.inner is still occupying space even when it's empty. This, coupled with the "↓ Start your search by searching for a location, a specific market, or both!" text, means that every "fresh' search leads to both columns jumping up vertically, and then the columns jumping back down when there are no active tags being searched.

The top of the contents of the left and right container should align at the top, always, and the indicative help text should probably be hidden with visibility:hidden; or a similar technique that means the space doesn't go away when the text does.

need to minify js and tie to deployment.

We have a build process for that, and it makes it difficult to debug potential issues inside of libraries like Backbone or jQuery.

On a less-tall viewport, with a lot of "matching startups also tagged with" in the list, the list overlaps the footer instead of being hidden by it.

http://gyazo.com/aed034b6bae5652ffd9792e21e461739

The StartupData Trends tool is awesome! I was trying out some of my own jsonp calls and they are working fine, but I don't see how you got the dollar amounts raised. Maybe it's a question for Angellist, but which json call did you use to get dollars? Thanks in advance!

As per the readme.

$ node dev

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: listen EACCES
    at errnoException (net.js:614:11)
    at Array.0 (net.js:689:28)
    at EventEmitter._tickCallback (node.js:192:40)

http://josscrowcroft.github.com/accounting.js/

For search: Give the user more options up front. What about a list of buttons that lets the user quickly drill down by location, industry, stage, or seeking?

For results: Show more data divided up into divs so you don't have to click a million times to compare stats across startups?

Incidentally, I am working on this, and am considering forking StartupDataTrends with an integrated version of it. Let me know what you think.

http://dev.startupgrid.net