• Tony Morris (unregistered) in reply to scheky
    scheky:

    Mike R:
    ..snipped random attempts at flaming

    Hell, JAVA was never supposed to actually be portable.  That's somehting marketing made up and the team had to make good on.



    Java (not JAVA*) was indeed intended to be portable from its first inception. You might be referring to Oak, its predecessor.

    * http://qa.jtiger.org/GetQAndA.action?qids=73&showAnswers=true

    Tony Morris
  • anonymous coward (unregistered) in reply to Gene Wirchenko
    Gene Wirchenko:
    John Smallberries:

    Please correct me if I'm wrong. Is everything "global" in FoxPro?


    No, and it has been like that since it was first released.  Later versions have even more non-globals.

    Sincerely,

    Gene Wirchenko



    Woohoo! a foxpro defender.  Just to be sure no one misunderstands, foxpro has public and private variables.

    Public variables work just like everyone thinks they should.  Private variables, well, try this program:

    a=1
    =func1()         && call func1

    function func1(x)
        private a      && declare a as private
        a = 3            && set a=3
        =func2()      && call func2
        ?a                  && print a.  (nice syntax, by the way)

    function func2(x)
        a=5               && set a=5

    This code prints 5.  Well, WTF does it mean that a is private in func1?  What it actually means it that the a=3 in func1 does not affect a's value in any scope that calls func1.  Declaring it private in func1 does absolutely nothing to protect it inside func1.

    Because of this, a foxpro project that I have seen has EVERY "local" variable prefixed with a two letter abbreviation and underscore.  (Apparently two letter abbreviations are guaranteed unique.)

    Visual foxpro actually added (gasp) a LOCAL keyword that declares local variables, but if you try to pass a local by reference in a function call, it won't work.  Hope you don't happen to try to call a swap function on local variables.
  • (cs) in reply to Adam Courtney
    Anonymous:

    Actually it's Fox Pro,  and the quilty party was long gone before I got here.

    Ya know, it's not very manly to admit to liking quilting bees.
  • AmmoQ Hater (unregistered) in reply to dubwai
    dubwai:

    Anonymous:
    AmmoQ - with all of the defense of these WTFs the past couple of days, I beginning to think you authored quite a few yourself.

    No really, why are defending such code.  If what you speculate is true, then this code, and code like it, should never see the light of day.

    I'm confident that AmmoQ is a very competent developer.  Perhaps he's playing devil's advocate.  I think his point here is that sometimes, you're given a WTF, and no time to fix it so you just pile it on.  I know I have done this.  Sometimes it's the most reasonable approach.



    Really? I don't care for his volumes and volumes of posts and the fact that he often states and then restates incredibly obvious conclusions. I get the feeling a lot of his posts only exist for the sake of posting.

    Of course this WTF could have come into being because of a larger WTF that was in place first. It could also be that the WTF came into being all on its own and there was no need for using this scheme at all. Both of these possibilities seem readily apparent. Neither can be ruled out and, more importantly perhaps, these possibilities don't change the fact that the approach used is completely idiotic.
  • John (unregistered) in reply to brazzy

    "Because it proactively integrates our synergy paradigm to strategically leverage solutions for an increased productivity potential!"

    [coworker with a 'corporate bingo' sheet] BINGO!

  • (cs) in reply to ammoQ
    ammoQ:
    Doesn't/Didnt't FoxPro work on the same files like DBase, Clipper? I didn't mean to say they cannot be queried by SQL, but unlike "pure" SQL databases, the position within a file may be meaningfull in a Dbase file. For example, you can say "go to the 51st record and delete it". Of course not something you should build relations on, but sufficient for a database tool to identify exactly one row without actually knowing (or even having) a primary key. (comparable to the rowid in Oracle's database)

    An SQL database is a database composed entirely of a string of SQL insert statements. Somehow I'm pretty sure that isn't what you meant. Each db maker has their own goofy file formats, though they're mostly all based on pointers to rows with pointers to variable-length column data - in the case of flatfiles, simply kludged into translating SQL into repeated table-scans and row-fetches.
  • (cs) in reply to Thuktun
    Thuktun:
    DLLs are specific to Microsoft Windows and OS/2, AFAIK.  I'm sure Mike R knows what he's talking about, and your response seems petulant and pointless.

    Ever heard of a .so?

    Thuktun:
    Many programs written in VB either had to ship the runtimes with their installer (which made it a HUGE download in the days before widespread broadband) or insist the user download it separately.  VC++ runtimes weren't as onerous, as they were somewhat modularized and quite a bit smaller than their VB counterparts.

    Yeah, right. Most new C++ programs either have to distribute msvcp71 & msvcr71 (almost as large as msvbvm60) or risk non-stop emails, forum posts, etc over and over. Not to mention any data access components or other dependancies built into the latest windows version but not prior ones. Same for any previous versions, if all OSes had to be supported.

    And what the hell, Mike, vb runtime 6 is not larger than 5 floppies, it's 1.35M and fits just fine on one 3 1/2". vbrun300 was barely larger than a 5 1/4" floppy at 390K. All you convinced me is how bad you flunked arithmetic.
  • (cs) in reply to dubwai
    dubwai:

    I swear some people are writing code on acid.  I'd love to be there when someone wants to change the color scheme.

    [manager] We've been asked to update the color scheme to fit the corporae standard.  I've got the intern on it.

    [developer] Wait, the logic depends on the RGB values of the components.

    [manager] What?  Why?!

    Now here's the game, kind of like madlibs:  What's the developers response?  I'd get it going but I can't even think of a reason.  I need to eat.



    [developer] Well, when you and I think of color, we consider it as a continuous spectrum, but in reality, light can only exist at several pre-set frequencies, or quanta, which, incidently, I would like to propose as the name of our current under-development architecture.

    [manager] Quanta. I like it. Go on, Overmann.

    [developer/Overmann] As I was saying, if a given atom with correctly positioned valence electrons is struck by a photon in a given quanta, it can be elevated, or "excited," into a higher energy level, but only one of a certain few set energy levels. Thus every atom is effectively a finite state machine, manipulable by photons. Incidently, when the electron returns to its native orbital, it emits a photon of similar charicteristic to the one that first struck it, which could then theoretically go on to excite an electron in another atom. By the way, how's Orbital for the new command shell?

    [manager] Not damn bad. You were saying?

    [Overmann] Right, given this knowledge, a single atom could, if stimulated propperly, be used in a sort of binary-analogical "chemical reaction", in a manner similar to a transistor. This sort of electro-optic circuitry could be infinitely smaller than modern silicon chips, and as I mentioned, the key to managing data int he circuit would be color manipulation.

    [manager] That's brilliant! Who came up with this.

    [Overmann] Well, Einstein came up with the quantum theory stuff, and the rest I thought up while licking peyote off my secretary's abdomen.

    [manager] Get out of my office.


    Don't let this happen to you. Tell your local university to stop requiring basic chemistry for computer science majors.
  • Z (unregistered) in reply to bit
    Anonymous:
    John Smallberries:
    Anonymous:

    John Smallberries:
    Anonymous:
    I get it - the WTF is that the colors don't match.  And that everything is primary colors, which would make your eyes hurt after a while...

    --Daniel T

    Green is a primary color?

    (sorry, sometimes I can't help being an asshole...)

    Well, it is in the RGB color system...


    Indeed. That still doesn't make G a primary color.
    Yes, it does. It's a primary color in the RGB system, because in that system, every other color is composed from these three. That's precisely the definition of a "primary color".


    Yes, that is the definition of a primary color (reasonably well explained at http://en.wikipedia.org/wiki/Primary_colors for example). However, Danile T talked about the kinds of colors that would make your eyes hurt. Presumably, three colors all stimulating one of the cones maximally each would be kind of annoying to a human. These colors are, IIRC, yellow-green, green and violet, where green happens to be the only color corresponding to a basis in the RGB-system.

    For a very good discussion about the misnomer "primary color", see http://handprint.com/HP/WCL/color6.html.
  • (cs)

    I suppose that the program specification read something like: "If you press the red button..."

  • (cs) in reply to md2perpe

    Wow. Cool WTF. Tightly Separated, indeed.

    As for those slamming foxbase/foxpro/dbase/clipper, It's actually pretty damn good for what it was intended for. Okay, the language itself has a couple of oddities, but that's no biggie, after all, as a programmer you're supposed to be able to adapt to shit like that.

    Personally, I'd have no qualms at all recommending Foxpro over VB/Access. In all honesty I'd prefer Ruby/Postgres, but foxpro does have everything in a very neat package...

    Simon

  • (cs) in reply to tufty
    CornedBee:

    The psychological model is most closely represented by the HSV model. H for Hue is the angle in a colur wheel. S for Saturation is how, well, saturated the colour appears. Lack of S means grey. V for Value is the brightness, ranging from black to white. (Depending on the exact model.)


    That's the HSL model you're describing.

    In HSV (used by Photoshop) the V or B slider ranges from black to a "full value". This full value is anything between white and the fully saturated colour. In HSV, going from full red (F00) to white (FFF) constitutes a drop in saturation from 100% to 0%.

    In HSL, however, the gradient between a Full Value and White is mere  an increase in L (Lightness).

    Adobe software in general use HSV.
    Paint Shop Pro uses HSL.
    The Windows colour picker uses HSL.
    Bryce gives you the choice, but inadvertantly switched the HSV/HSL labels.

    HSL has a small defect in that the saturation ramp isn't linear but curved in favour of saturated values.

    HSL has the advantage that you can easily determine if an RGB coordinate is 100% saturaded: if one or more of the RGB values is 255 or 0, S is 100%.

    HSV has a limitation in that high-saturation, light colours are hard to obtain if you only have sliders, and don't have a SV-square like in Photoshop.

    It's a fallacy to give ranges from 0-255 to each of the HS[V|L] channels. For example, at 100% saturation and 24-bit colour, there are 1500+ hues and 512 lightness levels.

    At 0% saturation there is 1 hue and 255 lightness levels.

    It's pointless to argue which one is more 'correct', so I'm not getting into it. You can barely even explain the concepts of sautration and brightness to a non-graphic person, so it's all exteremely subjective and there are no rules. It suffices to understand the differences in distribution of colours within the colour space, so as to more accurately get the colour you want.

    I write colour stuff on a programming forum.
    Go me.
  • (cs)

    OK, that is just loonacy!!!

    I'm currently working on a large app and we have decided to opt ofr the MVC model and I can tell you that if any of my code monkeys started using the colours on the front end to determine what logic to do on the back I'd kick their asses off the project faster than you can can say "red means new user, right?"

    People like this should be removed from the programming gene pool!

  • (cs) in reply to scheky
    scheky:

    First, any modern operating system (don't use DOS...if you really want to say DOS was a good OS, you are in serious need of therapy) REQUIRES AT LEAST 4-5 Meg of supporting files.  Java (which you agree is piggish) requires 20ish.  You CAN get away with crt.dll (only 186k) on Windows, but you will also be using several other OS dll files to make up for it.  This is assuming you aren't using MFC.dll.


    Never said DOS was a good OS, I simply mentioned that a COM file can get by without any dependencies (except the hardware its on) whatsoever, in this case DOS is just simply a loader, and does not provide any services.


    Now, you can argue that MFC is evil..I won't fight it, but if you are using C++ and NOT using it, good luck making any kind of time to market.  If Time to market is not a concern to you, well, you don't really have an opinion that matters.  Time to market is pretty much ALL that anyone who signs our checks really gives a damn about.  If they stop signing, you will likely end up as a fry cook with those amazing social skills of yours.

    Most of what I do today is MFC, but I'm well aware that this requires MFC's libraries to be in place, but you can statically link MFC and the CRT to the executable, its size is negligable, because everything the exe didn't use is usually discarded by the linker.


    Once again, I say...EVERY MODERN PROGRAMMING LANGUAGE HAS A RUNTIME.  VB wasn't the first, and I agree at the time it was a good bit, but it really didn't wear that albatross solo for long (ok, actually Visual C was the first, but MS included the runtime with the OS, a promise they made to VB programmers that they never made good on, much like adding .NET runtimes to the OS).

    Never said programming languages didn't have runtimes, I just stated that I believed VB's runtime was excessive, is all.


    The P-Code advantage was NOT portability.  Hell, JAVA was never supposed to actually be portable.  That's somehting marketing made up and the team had to make good on.  P-Code existed to take little harddrive space.  P-Code was a concept developed by ex-mainframe folks who thought every tiny bit of storage needed to be hoarded.  It was a natural extension of dll files.  Add a runtime (which is actually nothing more than a group of dll files) and your exe's are much smaller than an app that doesn't require it.  That 5 meg runtime along with 6 applications takes up less space than 6 apps written in C that are 2 megs each.  This was a time when harddrives were still sub-gig and businesses took storage space as a serious issue.  Technology broke us out of this sink, but for the time, it WAS actually a good solution.  For a GUI application, P-Code could wait just as fast as anything else for a user to click a button.  Did you know Excel was once written in P-Code?  It existed as P-Code (with a runtime bootstrapper) long before VB4 (VB3 was purely interpreted).

    Yes-- But, used properly, DLLs are much better. I'm not complaining about VB3 or 4, but rather 5 and 6 where the runtime did take up 5MB (which had the option to compile to native code). For anything but a simple GUI data entry app, p-code was miserably slow.


    Now, that stated, I hate VB as a language.  I never liked it.  It WAS however, the solution to what most businesses needed.  It IS the reason so many of us actually have jobs currently.  It MADE the IT department in most corporations.  Like it or not, it opened the door for corporate acceptance of desktop applications.  C++ would have failed miserably and Delphi (the only RAD competition and actually a superior product) had Borland to mismanage and screw it up.  VB is a horrible mess as a language, but it filled a void that our industry needed.

    Totally agreed. VB was full of limitations, as well. It was difficult (but not impossible, if you knew what you were
    doing) to do simple things other applications did without effort.


    Learn to research, then form an opinion.  Otherwise, your opinion means nothing.  Hell, if you are going to hate something, hate it for valid reasons (like the almost but not quite OO abortion that VB was).   It was a programming language.  It was a successful programming language (as in, projects that were coded in it are still in use in a widespread manner).  It was responsible for a lot of our peers to make a paycheck every month.  How people can hate an abstract like a programming language with such furor is simply beyond me.  It's not a fucking religion.  Bad code was and is written in every language.

    Who's flaming, now? Or rather who started this in the first place.


    That said, I'm 39.  I wish I was still a kid. 



    Well, you only have 10 years on me. Which isn't much by my standards.
  • (cs) in reply to sadmac
    sadmac:

    [Overmann] Right, given this knowledge, a single atom could, if stimulated propperly, be used in a sort of binary-analogical "chemical reaction", in a manner similar to a transistor. This sort of electro-optic circuitry could be infinitely smaller than modern silicon chips, and as I mentioned, the key to managing data int he circuit would be color manipulation.



    You had me going (/sarcasm) until that part.  Anyone who knows Quantum mechanics knows that this circuit is not infinitely smaller than a transister.  Several orders of magnitude yes, but that is about all.

    Looks like programers need to take more physics.
  • fatgeekuk (unregistered)

    I am ashamed to say that although I did not write this, I have used something similar.

    In VB attached to an Excel worksheet, the form open routine quieried info related to what fields where mandatory, setting the background of these specific fields to yello, all the others to white.

     

    On the forms "OK" btn, I checked each field that had a yello background for a value.

    This was within the single form. not very MVC, but it saved having the business logic used to decide mandatoriness in two places.

    I sit here ashamed.

     

  • Just another WTF (unregistered) in reply to hank miller

    hank miller:
    sadmac:

    [Overmann] Right, given this knowledge, a single atom could, if stimulated propperly, be used in a sort of binary-analogical "chemical reaction", in a manner similar to a transistor. This sort of electro-optic circuitry could be infinitely smaller than modern silicon chips, and as I mentioned, the key to managing data int he circuit would be color manipulation.



    You had me going (/sarcasm) until that part.  Anyone who knows Quantum mechanics knows that this circuit is not infinitely smaller than a transister.  Several orders of magnitude yes, but that is about all.

    Looks like programers need to take more physics.

    And less Peyote

  • (cs) in reply to Mung Kee
    Mung Kee:
    John Smallberries:
    <font size="1">
    Alex Papadimoulis:
    </font>

    
    MsgBox "There was an error creating the client. " & _
    "Please ensure all required fields were entered."
    <font size="1">

    Yeah, don't validate the input or anything...wait for it fail, then change the control color.</font>


    Meanwhile, the labels on the client are changing to every color in the RGB scale so the user is wondering WTF is going on.  I hope they have a color legend.


    That is soooo funny. This is probably what their app looks like: http://www.chowchows.com/information.html. lol. (I'm sorry if this is your website...)
  • (cs) in reply to Dustin
    Dustin:
    Mung Kee:
    John Smallberries:
    <font size="1">
    Alex Papadimoulis:
    </font>

    
    MsgBox "There was an error creating the client. " & _
    "Please ensure all required fields were entered."
    <font size="1">

    Yeah, don't validate the input or anything...wait for it fail, then change the control color.</font>


    Meanwhile, the labels on the client are changing to every color in the RGB scale so the user is wondering WTF is going on.  I hope they have a color legend.


    That is soooo funny. This is probably what their app looks like: http://www.chowchows.com/information.html. lol. (I'm sorry if this is your website...)


    Goog god man!  I was one blink tag away from convulsing on the floor.
  • foo (unregistered)

    This isn't confined to the world of the programmer, sadly. A project I was recently working on had two conflicting formal requirements signed off by the customer:

    • if a certain GUI component is coloured grey, it can't be selected with the mouse.
    • said components must be the same colour as the colour of the object they represent - which was an object in an external system with an arbitrary colour scheme.

    The obvious result being, supposedly selectable items were no longer selectable whenever their colour happened to be grey...
  • (cs) in reply to El Duderino
    El Duderino:
    dubwai:

    I swear some people are writing code on acid.  I'd love to be there when someone wants to change the color scheme.

    [manager] We've been asked to update the color scheme to fit the corporae standard.  I've got the intern on it.

    [developer] Wait, the logic depends on the RGB values of the components.

    [manager] What?  Why?!

    Now here's the game, kind of like madlibs:  What's the developers response?  I'd get it going but I can't even think of a reason.  I need to eat.

    [developer]  Because that's what marketing put in the requirements!
    or
    [Paula]  I'm Brillant!



    Seriously, I'm a genius

  • (cs) in reply to tufty
    tufty:
    Wow. Cool WTF. Tightly Separated, indeed. As for those slamming foxbase/foxpro/dbase/clipper, It's actually pretty damn good for what it was intended for. Okay, the language itself has a couple of oddities, but that's no biggie, after all, as a programmer you're supposed to be able to adapt to shit like that. Personally, I'd have no qualms at all recommending Foxpro over VB/Access. In all honesty I'd prefer Ruby/Postgres, but foxpro does have everything in a very neat package... Simon


    To amplify, give the name of ONE language that does not have oddities.  (Oddities that you are used to are still oddities.)

    Sincerely,

    Gene Wirchenko

  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:
    tufty:
    Wow. Cool WTF. Tightly Separated, indeed. As for those slamming foxbase/foxpro/dbase/clipper, It's actually pretty damn good for what it was intended for. Okay, the language itself has a couple of oddities, but that's no biggie, after all, as a programmer you're supposed to be able to adapt to shit like that. Personally, I'd have no qualms at all recommending Foxpro over VB/Access. In all honesty I'd prefer Ruby/Postgres, but foxpro does have everything in a very neat package... Simon


    To amplify, give the name of ONE language that does not have oddities.  (Oddities that you are used to are still oddities.)

    Sincerely,

    Gene Wirchenko



    From the odd come oddities.  After all, we ARE engineers.  Let's make a distinction between oddities and WTFs though.  The former, or course, does not denote the latter.
  • (cs) in reply to anonymous coward

    One of the problems with xBASE is that most people have very outdated information.  Many programs have considerable feature change over the years, but somehow, this is not considered when an xBASE language is discussed.

    Anonymous:
    Woohoo! a foxpro defender.  Just to be sure no one misunderstands, foxpro has public and private variables.

    Public variables work just like everyone thinks they should.  Private variables, well, try this program:

    a=1
    =func1()         && call func1

    function func1(x)
        private a      && declare a as private
        a = 3            && set a=3
        =func2()      && call func2
        ?a                  && print a.  (nice syntax, by the way)

    function func2(x)
        a=5               && set a=5

    This code prints 5.  Well, WTF does it mean that a is private in func1?  What it actually means it that the a=3 in func1 does not affect a's value in any scope that calls func1.  Declaring it private in func1 does absolutely nothing to protect it inside func1.


    Why would it?  I do not find this behaviour surprising at all.  This behaviour is true in other languages, PL/I for one.  What is surprising is that private is not a declaration of a variable, only that any prior declaration should be ignored in the scope of the private.

    Private variables are from dBASE III Plus.  VFP has kept a lot of compatability.  Private variables do not get much use these days.  My app has them only at the outer level, where they serve as globals (except that they would not be globals if my app was called from within another VFP program).

    Because of this, a foxpro project that I have seen has EVERY "local" variable prefixed with a two letter abbreviation and underscore.  (Apparently two letter abbreviations are guaranteed unique.)


    Nah, it is just Hungarian Pollution^WNotation.

    Visual foxpro actually added (gasp) a LOCAL keyword that declares local variables, but if you try to pass a local by reference in a function call, it won't work.  Hope you don't happen to try to call a swap function on local variables.


    The default parameter passing type for functions is call-by-value.  Prefixing the actual parameter with an at-sign will make it a call-by-reference parameter, and the swap works just fine.  I just checked under VFP 6 SP 5 (Build 8961).  The scope of the actual parameter is irrelevant.

    Sincerely,

    Gene Wirchenko

  • (cs) in reply to sadmac

    awewsome! how true :P

  • (cs) in reply to dubwai
    dubwai:

    I swear some people are writing code on acid.  I'd love to be there when someone wants to change the color scheme.

    [manager] We've been asked to update the color scheme to fit the corporae standard.  I've got the intern on it.

    [developer] Wait, the logic depends on the RGB values of the components.

    [manager] What?  Why?!

    Now here's the game, kind of like madlibs:  What's the developers response?  I'd get it going but I can't even think of a reason.  I need to eat.

    Well, by the time they get around to changing it, the original programmer will be gone and nobody will be sure exactly how the logic works. So someone will go in and change the color, and wonder why the app stops functioning properly. Especially since the case of 'invalid color' doesn't seem to be handled at all.

    *chuckle*

  • (cs) in reply to Gene Wirchenko
    Gene Wirchenko:
    To amplify, give the name of ONE language that does not have oddities.  (Oddities that you are used to are still oddities.)

    I can't come up with one. That was kind of the point. Foxpro was being moaned about for its handling of non-globals, which is "odd" in respect to other languages. Odd it may be, but it is most certainly consistent (not an accusation one could level at VB), and does the job it's supposed to. I like it.

    Simon

  • Arachnid (unregistered) in reply to sadmac
    sadmac:

    [developer] Well, when you and I think of color, we consider it as a continuous spectrum, but in reality, light can only exist at several pre-set frequencies, or quanta, which, incidently, I would like to propose as the name of our current under-development architecture.

    [manager] Quanta. I like it. Go on, Overmann.

    [developer/Overmann] As I was saying, if a given atom with correctly positioned valence electrons is struck by a photon in a given quanta, it can be elevated, or "excited," into a higher energy level, but only one of a certain few set energy levels. Thus every atom is effectively a finite state machine, manipulable by photons. Incidently, when the electron returns to its native orbital, it emits a photon of similar charicteristic to the one that first struck it, which could then theoretically go on to excite an electron in another atom. By the way, how's Orbital for the new command shell?

    [manager] Not damn bad. You were saying?

    [Overmann] Right, given this knowledge, a single atom could, if stimulated propperly, be used in a sort of binary-analogical "chemical reaction", in a manner similar to a transistor. This sort of electro-optic circuitry could be infinitely smaller than modern silicon chips, and as I mentioned, the key to managing data int he circuit would be color manipulation.

    [manager] That's brilliant! Who came up with this.

    [Overmann] Well, Einstein came up with the quantum theory stuff, and the rest I thought up while licking peyote off my secretary's abdomen.

    [manager] Get out of my office.


    Don't let this happen to you. Tell your local university to stop requiring basic chemistry for computer science majors.


    Oh come on, that's ridiculous. A programmer with a secretary?
  • (cs) in reply to John Smallberries

    Sure it does...
    At least, green is an additive primary colour.

    Check it out

         -dave-

  • Inopia^Aardbei (unregistered)

    Huh, that's nothing. I used to do some programming for a guy that had written his own CMS in visual basic as an IIS plugin. He had some code that would parse an anchor tag, that had special case code for the anchor tag being upper case () and lower case code (). I believe the code for each case was completely different as well. When I asked him if I should fix it, he literally said "no, I don't know wich site will stop working if you touch that".

  • (cs) in reply to Mung Kee

    Other than the colors, the tiling-from-hell background image, the trippy horizontal lines and the music, I see nothing wrong with it. 888,888 visitors agree with me. Background music encourages efficient (i.e. quick) visits to an internet site.

  • (cs) in reply to Just another WTF

    so, what happens when the manager says "I don't want the app to change its color, it's ugly".

    Then, a smart designer will make all the colors the same color.

    Then, the function is always successful! Will the designer get a raise?

  • (cs) in reply to ReligousFlameWarrior

    I would love to see something like this done in Javascript only to see everything fall apart as soon as someone uploads the new CSS file.

  • Elektron (unregistered)

    I think I use this in one of my apps, actually...

    shame

  • anon (unregistered)

    The REAL wtf is that the author is using pure-red, pure-green and pure-blue colors. Those look ugly..

  • HTMLOCDER.exe (unregistered)

    I've seen some of this code, written in Javascript. It was a language test. You did the input into text fields, which were originally white, but changed to green in case of a correct answer (everything hooked on the onBlur event) and, obviously, red in case of an incorrect one. The fun part was that if you answered incorrectly, you couldn't make another try on that textfield. It displayed an error box, saying something like, "No cheating!". This messagebox was thrown when you tried to type in a red-coloured text field... ---SNIP--- if(this.backgroundColor=="red") { this.blur; alert("No cheating!"); } ---SNIP---

Leave a comment on “Colored Logic”

Log In or post as a guest

Replying to comment #:

« Return to Article