Difference between revisions of "User talk:Skotty"

From Robowiki
Jump to navigation Jump to search
m (Some thoughts on packaging source files)
Line 3: Line 3:
  
 
I'd also like to point out that not packaging your source doesn't necessarily keep people from checking out your code.  Class files can be decompiled.  Just a thought...
 
I'd also like to point out that not packaging your source doesn't necessarily keep people from checking out your code.  Class files can be decompiled.  Just a thought...
 +
 +
I too use Eclipse for development, and have never had trouble with packaging the source code.  I have ''options -> preferences : development options'' set to my ''...\workspace\robots\'' directory which contains my ''...\src\'' and ''...\bin\'' directories, then I can package my robots in ''robot -> package robot for upload''; this dialogue contains an "include source" check box (enabled by default).  --[[User:AW|AW]] 23:21, 27 May 2011 (UTC)
  
 
== Rant on Lost Form Submissions ==
 
== Rant on Lost Form Submissions ==

Revision as of 01:21, 28 May 2011

Packaging Source Files

At the moment, my robot XanderCat is not packaged with source. This is fine, since the Xander framework is not entirely complete yet. Though when I am ready to package with source, I'm not sure how I will do it. I use Eclipse for development. I can add the bin directory under the developer options to run my robot while it is under development. But when I go to package it in Robocode, I'm not sure there is any way to tell it where the src folder is. I could also just check to see what all Robocode is putting into the jar files, and write my own Ant built script. Or I might just provide the source as a seperate download from the wiki page. Thoughts?

I'd also like to point out that not packaging your source doesn't necessarily keep people from checking out your code. Class files can be decompiled. Just a thought...

I too use Eclipse for development, and have never had trouble with packaging the source code. I have options -> preferences : development options set to my ...\workspace\robots\ directory which contains my ...\src\ and ...\bin\ directories, then I can package my robots in robot -> package robot for upload; this dialogue contains an "include source" check box (enabled by default). --AW 23:21, 27 May 2011 (UTC)

Rant on Lost Form Submissions

Bitten by poor web application design again. After having to pause one of my edits to take care of another matter, I returned a bit later, finished my edit, and submitted it. However, my session had timed out. Much to my surprise, MediaWiki did not preserve my edit. I thought MediaWiki was classier than that.

It is a newbie web developer mistake to have a web application lose someones edit due to a session timeout. The proper action is to save the edited data, give the user a chance to log back in, and then apply the edit or return them to the edit page without losing the edit. I'm often surprised at how many web applications exhibit this glaring flaw...so many, that I almost consider it my own mistake for not copying the text to notepad before submitting. But it is not my own mistake. It's the web application's mistake. A mistake that I am really growing tired of seeing again and again and again...


Eh? I have never had session timeout with MediaWiki. Are you sure it is really session timeout? I know for the fact that MediaWiki use token cookie for authentication. BTW, I know Chrome preserve form data on 'Back' button. I don't know about other browsers, but I think they do too.

On completely unrelated note, I found that FanFiction.net authentication system more frustrating: if I checked "Remember me for one day", it remember exactly one day i.e. if I start edit on 23.58 and finish on 24.01 hours after my login, my edit will be gone :( --Nat Pavasant 12:51, 27 May 2011 (UTC)