What are you working on? November 2011 Edition

[Gook Nukem]

[QUOTE=i300;33392433]Whats with the dumbs? I think that's pretty neat.[/QUOTE]
I think it's pretty cool to be honest, you should add video so you can tear your favorite film in real time :v:

[icantread49]

[QUOTE=Quark:;33392606]I think it's pretty cool to be honest, you should add video so you can tear your favorite film in real time :v:[/QUOTE]

cool idea but probably won't happen due to insane memory constraints.

in fact, the only reason i made this "real-time camera" feature is because using iOS's built-in camera-capture feature takes way too much memory and forces my app to close too often

[Z_guy]

[QUOTE=birkett;33392139]Doom3 / idTech4 source code was just released. GPLv3, going to take a look at it tonight.[/QUOTE]

I just downloaded a tarball and, holy shit, it builds without any dependency hell!

[NovembrDobby]

[QUOTE=i300;33392433]Whats with the dumbs? I think that's pretty neat.[/QUOTE]

Might be because he spread out the 'same' content over 3 posts (the info about the live image thing, a gif of it, then the same gif with the similar text).

But I wasn't part of the dumbing crew so I wouldn't know

[Anonim]

I just lost all respect for id software.

They didn't convert their tabs to spaces in Doom3. Fuck 'em all to hell!

[Neo Kabuto]

[QUOTE=Anonim;33393114]I just lost all respect for id software.

They didn't convert their tabs to spaces in Doom3. Fuck 'em.[/QUOTE]

Is that really that horrible?

[icantread49]

[QUOTE=Anonim;33393114]They didn't convert their tabs to spaces in Doom3. Fuck 'em all to hell![/QUOTE]

why the fuck would you convert tabs to spaces ???

[Anonim]

[QUOTE=Neo Kabuto;33393119]Is that really that horrible?[/QUOTE]

It should be a crime against humanity.

[Z_guy]

[QUOTE=Anonim;33393139]It should be a crime against humanity.[/QUOTE]

Wait, are you serious?

[BlkDucky]

I never got the whole "spaces are better than tabs" thing.

[Staneh]

I actually prefer tabs over spaces.

[Jack Trades]

Why would spaces be better than tabs?

[Neo Kabuto]

[QUOTE=Staneh;33393221]I actually prefer tabs over spaces.[/QUOTE]

I just prefer that they're all the same in the codebase. My OCD brain hates having to work with some code someone else made that uses some different indent amount. At least tabs are always going to look the same on one computer.

[Jack Trades]

Speaking of OCD habits, I can't stand using someones code that looks like this:

function Foo()
{
foo.bar = 0;
}

It supposed to look like this:

function Foo() {
    foo.bar = 0;
}

[Nigey Nige]

everyone shut the fuck up
[img]http://i.imgur.com/5PSZe.png[/img]
i've had a breakthrough

it's the inside of an arcade cabinet

[Neo Kabuto]

[QUOTE=Jack Trades;33393286]Speaking of OCD habits, I can't stand using someones code that looks like this:

function Foo()
{
foo.bar = 0;
}

It supposed to look like this:

function Foo() {
    foo.bar = 0;
}

[/QUOTE]

And then there's the people who break up any string that's more than a few characters into multiple lines of code.

[Jookia]

[QUOTE=amcfaggot;33391240]

-- Copyright 2011 Andrew McWatters. All rights reserved.
--
-- Redistribution and use in source and binary forms, with or without modification, are
-- permitted provided that the following conditions are met:
--
--    1. Redistributions of source code must retain the above copyright notice, this list of
--       conditions and the following disclaimer.
--
--    2. Redistributions in binary form must reproduce the above copyright notice, this list
--       of conditions and the following disclaimer in the documentation and/or other materials
--       provided with the distribution.
--
-- THIS SOFTWARE IS PROVIDED BY ANDREW MCWATTERS ``AS IS'' AND ANY EXPRESS OR IMPLIED
-- WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
-- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ANDREW MCWATTERS OR
-- CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-- CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-- SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-- ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-- NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
-- ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
--
-- The views and conclusions contained in the software and documentation are those of the
-- authors and should not be interpreted as representing official policies, either expressed
-- or implied, of Andrew McWatters.

-- Begin implementation of "Very Yes" as inspired by Strong Bad Email #118 via:
-- http://www.homestarrunner.com/sbemail118.html
-- Andrew; Check to see if computer over, first.
if not COMPUTER_OVER then very_yes=true end
-- End implementation

[/QUOTE]

[url=https://bbs.archlinux.org/viewtopic.php?pid=511373#p511373]Nothing beats this gem.[/url]

[icantread49]

[QUOTE=BlkDucky;33393199]I never got the whole "spaces are better than tabs" thing.[/QUOTE]

probably because spaces [i]aren't[/i] better than tabs

[Staneh]

[QUOTE=Jack Trades;33393286]Speaking of OCD habits, I can't stand using someones code that looks like this:

function Foo()
{
foo.bar = 0;
}

It supposed to look like this:

function Foo() {
    foo.bar = 0;
}

[/QUOTE]

I still really prefer the first way, though I tab one time, like this:

        function Foo()
        {
            foo.bar = 0;
        }

[Octave]

I use the first one. :smith:

[Jack Trades]

[QUOTE=Neo Kabuto;33393303]And then there's the people who break up any string that's more than a few characters into multiple lines of code.[/QUOTE]
You mean like doing

switch (foo) {
    case x:
        bar = 0;
        break;
    case y:
        bar = 1;
        break;
}

Instead of

switch (foo) {
    case x: bar = 0; break;
    case y: bar = 1; break;
}

?

[editline]23rd November 2011[/editline]

[QUOTE=Staneh;33393342]I still really prefer the first way, though I tab one time, like this:

        function Foo()
        {
            foo.bar = 0;
        }

[/QUOTE]
I understand [I]why[/I] people do it, it's because they want to see where the function end and starts easily, but Notepad++ (hail Notepad++) already shows that to me without me having to waste an extra line of code for that :colbert:

[Yogurt]

Working on water physics in MD. It's incredibly complex. I don't even know where to begin.

Each water block has a metadata value from 0-100. That's its height. So a block can be partially filled with water.

I just can't think of a way to do it. For instance, if I have a single block in a one-block high pool, how do I make the water all "level out?"

[Neo Kabuto]

[QUOTE=Jack Trades;33393366]You mean like doing

switch (foo) {
    case x:
        bar = 0;
        break;
    case y:
        bar = 1;
        break;
}

Instead of

switch (foo) {
    case x: bar = 0; break;
    case y: bar = 1; break;
}

?[/QUOTE]
No, that's (the first one is) how I prefer my code.

I was thinking more like:

String genericstring = "This is a really "+
"really, really, really, really, really, "+
"really, really, really, really, really, "+
"long string, as an example of "+
"really long strings";

vs

String genericstring = "This is a really really, really, really, really, really, really, really, really, really, really, long string, as an example of really long strings";

It just messes with my reading too much to be worth not having to scroll for long strings, and it makes no sense with word wrap, like even this forum has.

[Jack Trades]

[QUOTE=Neo Kabuto;33393392]I was thinking more like:

String genericstring = "This is a really "+
"really, really, really, really, really, "+
"really, really, really, really, really, "+
"long string, as an example of "+
"really long strings";

[/QUOTE]
I never seen anyone do that but...[B]WHY[/B]?!

[Lexic]

I prefer spaces personally, because some things expand tabs to 8 characters long, when it is a universal law THAT THEY SHOULD ONLY BE FOUR. [IMG]http://i.imgur.com/2hMBT.gif[/IMG]
Anyway, look, content!
[IMG]http://i.imgur.com/sQVtX.jpg[/IMG]
Why yes, it does look rather like the last bit of content I posted, but that was running from this rather large (mostly) C function.
[IMG]http://i.imgur.com/9Vm36.png[/IMG]
Now, it's running on (nearly) all my own code in C++, and more importantly, [b]I know what every part of it is actually doing[/b].
[IMG]http://i.imgur.com/vsXmR.png[/IMG]
Woo learning.

[acpm]

It's really fucking dumb to convert tabs to spaces because tabs and spaces are two entirely different characters. But that's not where the problem lies. The problem lies in that tabs are ambiguous separations of space, with no solid single convention. You have tab to 4 spaces and tab to 8 spaces, as major conventions, then slightly stranger 2 space equivalents and etc.

These conventions are present due to different editors aligning monospace fonts for readability purposes, and aligning "partial tabs" to half-convention specifications. Today's modern tab conventions stem from extremely horrid decisions in literal space management in documents, as tabs moved from the technical tab stop mechanic generally representing a fixed typewriter margin space, to a transliteration of indentation in word processing. 4 and 8 spaces are thought to represent dominate margin indentations for fonts at 12 pt or 1 em to equate 0.5 an inch or 1 inch specifically.

In my opinion, tabs today should represent a static amount of monospaced blank characters or a fixed scalable size in other typographic counterpart definitions.

[Jack Trades]

I personally don't even have Line Wrap turned on in my IDE because I find it incredibly annoying.

[zenby]

[QUOTE=Z_guy;33392865]I just downloaded a tarball and, holy shit, it builds without any dependency hell![/QUOTE]

Where from?

[acpm]

4 spaces represent

[Octave]

[QUOTE=Jack Trades;33393420]I never seen anyone do that but...[B]WHY[/B]?![/QUOTE]

I believe the historical reason was to fit it on narrow terminal screens, that were mostly around ~80 characters in width