Live data from Hacker News

Tomorrow Theme

github.com

101–110 of 139 posts

Re: Tomorrow Theme

#101
post #62

If HN believes creative thinking is a waste of time I’ll get downvoted for this but I fancy just letting my imagination go wild so here goes... Video gamers can supposedly differentiate between tones more similar to one another than non-gamers. Perhaps, if you made a theme of very similar colors, you could achieve the same benefit from programming. Although I suspect it might not work because the difference in the co…

I tried explaining a similar concept to a designer recently - When I use Sublime Text 2 I use the minimap to visually identify sections of code based on their rough shape, and get to learn bits of code or sections of a file purely on its indentation / minimap pattern.

Thats exactly what I do with sublime as well, except i do it for log files. similar exceptions/errors in log files tends to have similar shapes thoughout, and you can scan a log file to find probable problems due to the patterns of errors without having to read each individually

Re: Tomorrow Theme

#102
post #71

Earlier quoted context omitted.

You might find graphical programming languages like LabVIEW interesting; here's a little tutorial that shows what LabVIEW programs look like: http://www.ee.buffalo.edu/faculty/paololiu/edtech/roaldi/tut... "Wires" that carry values are color-coded according to their contents (integers are blue, floating point values are orange, booleans are green, etc.). Loops like FOR and WHILE are actual "loops" that encircle the r…

LabView IS fun, I've written a couple of drivers and a (physical device) testing GUI with it. As I've been thinking about it more I see two hurdles to overcome with LabView though: - Layout: Spaghetti code becomes a very tangible issue if you don't follow guides on routing religiously. Intro courses only touch on this and LabView code in the wild are rarely clean. These visual routing guides are ORTHOGONAL to good co…

I like your assessment of LabVIEW. I find that if your code is turning to spaghetti, you're not using enough sub-VIs. Try to find blocks of code that accomplish one thing and put that code in its own VI. As a bonus you get to design a little icon for your new sub-VI. :)

Your "rabbit hole" analogy is spot-on and I'm not sure how NI can address some of those problems. Some things like Ctags that are so valuable in text-based languages just seem to have no obvious analogy in a graphical programming language... it's fun to imagine though.

(Caveat, chemist talking about programming)

Re: Tomorrow Theme

#103
I really wanted to like this, but I think that colors preferences are both subjective and born of habit/experience which leads to wiring our brains to expect certain colors for certain things, because I don't like pastels, and I don't like red as a non-alert color.

It's a good idea, with a lot of thought put into it. The author should keep trying. Maybe there is more than one right option.

Personally, I think the best way to do this is by a "hot or not" site for fonts and colors. Have a page for each language with "hot or not" of random fonts and color combinations until the stats show which combinations certain groups like. Tie in other surveys as well and give away gift certificates to Amazon each month as a prize for over 100 votes that aren't outliers.

Re: Tomorrow Theme

#104
post #70

Earlier quoted context omitted.

It's free, for one thing. IntelliJ is still for-pay if you want Java EE features, and while few of my projects are Java EE all of them use some EE features (JSF, especially). I tried IntelliJ community edition and was not very impressed. The time/cost of switching is pretty high. I'm not sure what the value is I'd be getting for that effort--better completion? More graphical ways of doing things? If I had $200 to blo…

The full version has a 30 day trial. I used to use Eclipse/Netbeans. I hate java and intelliJ actually makes it bearable.

I don't know about you, but "try this software you don't need so that if you like it you can pay me $200 you don't have" isn't a compelling pitch. NetBeans works fine. Blacklisting HN would do twenty times more for my productivity than a better IDE.

Re: Tomorrow Theme

#106

Earlier quoted context omitted.

LabView IS fun, I've written a couple of drivers and a (physical device) testing GUI with it. As I've been thinking about it more I see two hurdles to overcome with LabView though: - Layout: Spaghetti code becomes a very tangible issue if you don't follow guides on routing religiously. Intro courses only touch on this and LabView code in the wild are rarely clean. These visual routing guides are ORTHOGONAL to good co…

I like your assessment of LabVIEW. I find that if your code is turning to spaghetti, you're not using enough sub-VIs. Try to find blocks of code that accomplish one thing and put that code in its own VI. As a bonus you get to design a little icon for your new sub-VI. :) Your "rabbit hole" analogy is spot-on and I'm not sure how NI can address some of those problems. Some things like Ctags that are so valuable in text…

If you right click a VI in a LabVIEW project you can "Find Callers" and "Find SubVIs"

I'm using LV 2009, I'm not sure what version this was added.

Re: Tomorrow Theme

#107

Vim users should go here: http://vimcolorschemetest.googlecode.com if they haven't before, that's where I found darkburn, a darker variant of zenburn that I've been happy with for a couple years.

[deleted]

Re: Tomorrow Theme

#108

Vim users should go here: http://vimcolorschemetest.googlecode.com if they haven't before, that's where I found darkburn, a darker variant of zenburn that I've been happy with for a couple years.

I use vividchalk, which I was happy to see there on the list. It's amazing how many variations on color schemes there are.

Re: Tomorrow Theme

#109

Earlier quoted context omitted.

I'm not a LabView fan for various reasons, but something neat they've added as of V8.0 (I think) is an auto-format tool which will take a mess of wires and organize it. Vastly improves readability, and works really well.

Hmm, we were still running 6.1 in 2008 which probably explains a lot. (No upgrade path allowed at that time)

Wow 6.1 is ancient... :-) LabVIEW 8.6 is a huge leap forward in usability, stability, and performance. If you can upgrade to 2011 that's even better.

-National Instruments employee

Post reply on HN