Hi! On Feb 2, 2008 4:38 PM, Paul Filimon <[EMAIL PROTECTED]> wrote:
> Hello, > > I made a screen cast [1] for Apache/Wicket at GHOP. > > Please check it and send me your opinion. Probably I will have no time > to receive your opinions and to improve it in time for GHOP, but if > you have some time please share your thoughts. > > Since I am also a student participating in GHOP, I don't think my comments have too much weight, but hopefully you will consider them nonetheless. Are you on the list? (I'm not sure, so I've CCed you, but if you are, please let me know that I don't have to.) > [1] http://paul.balaur.com/tmp/ghop_0001.wmv > > I think, overall, it's okay, especially considering how difficult screencasts tend to be. Here are a few thoughts... - I didn't know you could click on the little icons to fix errors! That's more of a "learning how to use eclipse" type thing, but it's still very informative. That said, it's sometimes faster to use the automatic completion (hit Ctrl-Space), so it might be useful to do that for later parts of the video. (Explaining how to use auto-completion would be useful to new eclipse users, though, so I guess it's a question of whether we are targeting users who are experienced with eclipse and new to wicket, or new to both eclipse and wicket.) - I noticed a few pauses where you weren't talking/explaining, and where you weren't doing things... is that to let the user catch up and follow along, or...? I was told that it's a good idea if you are talking with the video. - - There's a point at about 8:15 or so where you're adding the TextArea to CommentForm... it appears to take fifteen-odd seconds for you to figure out (after much clicking and attempting to be discreet at looking at what Eclipse is telling you) that you need to add a semicolon to the end of the line. This looks a bit odd. It is usually a good idea (if you have time) to go through the actions a few times before recording the screencast. If you go through it nearly flawlessly, you look more professional. (If you don't have time to rerecord, you could have imported the video into some sort of video editor and snipped this part out.) - It's hard to tell, but did you follow the example online[1]? I see parts of it there, but it doesn't look like an exact match... - Since you were using Windows, have you considered using Windows Media Encoder 9[2] to record your desktop? If you use the "Windows Media Video 9 Screen" codec you might have a much smaller file size. (I'm not 100% sure, though, because I didn't use Windows to create my screencast.) - Just so you know, Java automatically calls .toString() on most things when you run them through print, so you don't have to. - It would be nice if you mentioned the wicket website at the end of the screencast. Even if they don't make it into a submission in time for the GHOP deadline, I hope you will take these thoughts into account. [1] http://wicket.apache.org/exampleguestbook.html [2] http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx -- Michael Chang Please note that not all formatting may be preserved in Office/Word/Powerpoint documents sent to me. Please use OpenDocument (not Open XML), HTML, and RTF where possible. See http://www.gnu.org/philosophy/no-word-attachments.html Thank you.
