Author Archives: Lee

[Comment] Re: Helium Doping

i sucked a big balloon nd now iono wat happened 2 mah throat. it is so freakin messed up now!!!!!! its like all shiny nd transparent. nd excusè moi but im not a druggy. i do not appreciate those ppl that assume that dumb nd stupid r da same thing. u can b book smart nd do very stupid things. trust me…i wood noe.

[Comment] Re: Kudos to the person who solves this problem

Dude, I totally agree with you. Case in point, Yahoo Email! If you type in a bunch of text in the email, come back a little later and somehow you are signed out (any number of ways for this to happen), trying to submit takes you to the login, but once logged in you can't go back.

I think it's BOTH sides that should take this on. First of all, ALL server side apps that have sign-ons of some sort and require input should, across requests, save your input as if you were signed in, allow you to sign in, then take you to the next step. Period. It is horrible usability when this is not the case and I often dont revisit. I also will often write the support people and let them know I am an enterprise engineer and whoever is doing thier site has their head up their arse becasue of this situation and to give me a call, I can fix it.

The other end is the browser. Sometimes I can't understand why I hit the BACK button which supposedly fetches a cached page BUT in FireFox at least, all my input is gone. GONE!! I don't remember this being a problem in IE, but I haven't used IE for a couple years now. I really do think that if a browser can cache pages, it should cache all the input values as well.

[Comment] Re: Locating log4j.properties within Eclipse

When I add LOG4J_PROPS, the error message about no appenders goes away, but there is an unwelcome side effect.
<pre>
Prior to the change, Run… [Test] displays
(*) Run a single test
Project foo
Test class: com.foo.test.Test
Test method:testBar

</pre>
After adding LOG4J_PROPS, the test method goes away. It's not a writeable text-entry field, so I cannot retype the desired method. This causes all tests in the class to run, not just the desired method. Ideas?
<p>
Also, is there a way to have one LOG4J_PROPS apply as a default to all tests?