1) Chat - approved, should be implemented
2) 60 troop - Ariel prefers 120, to match his previous studies. need to find a solution, maybe gradual appearing.
3) Delayed game: Should be implemented
4) Score - give some boolean value for victore/lose
5) Tournaments - make the player sign in every level, and right now manually set the rate.
More open issues:
2) tournaments - when?
2) 60 troops on board
3) delayed game when no players are there
site updated according to the discussion with Ariel at 2/1/09
improved design (updated sketch on the site)
changed into ice habitat
created a unit division screen
Created a Pinguin external class
added cool music and music controls
game pinguin sketch was added.
site was updated with the new workshop
We're honored to have a guest talk by Ohad Ben-Cohen who will speak about a joint work with Avishai Wool.
Their work was presented at the Black Hat conference last year.
And now for something completely different —
Please send me what is your preferred project, with whom would you like to work, any existing expertise/knowledge, etc. (even if you're not yet officially registered).
The Netflix Prize: Quest for $1,000,000
Sunday, 9/11, 11:15, Schreiber 309
Speaker: Yehuda Koren, Yahoo! Research
Abstract: The collaborative filtering approach to recommender systems predicts user preferences for products or services by learning past user-item relationships. Their significant economic implications made collaborative filtering techniques play an important role at known e-tailers such as Amazon and Netflix. This field enjoyed a surge of interest since October 2006, when the Netflix Prize competition was commenced. Netflix released a dataset containing 100 million anonymous movie ratings and challenged the research community to develop algorithms that could beat the accuracy of its recommendation system, Cinematch. In this talk I will survey the competition together with some of the principles and algorithms, which have led us to winning the Progress Prizes in the competition.
Grades were submitted today, so you should all see them tomorrow or so.
We'd like to thank you for all the hard work and the genuine enthusiasm.
It's been a pleasure for me1 to see each project growing from an initial idea to a mature, stand-alone gadget/application/thingamabob.
Good luck to you in your other exams, and see you in the Google office meeting (still not sure when).
No hard copy is necessary; all submission is in web format on the wiki.
Your pages should resemble a typical small open-source software homepage.
The effort required is the same as in writing that long word document that no one will ever read.
Please refrain, however, from making your page look like the very same word document.
Examples for pages (non-mandatory)
- Non-technical main page, with a screenshot and introductory text
- Download/more screenshots/gadget demonstration page
- User documentation and FAQ page
- Development info page, with full source code, known bugs, etc.
- Todo / wishlist page
Some visual style tips:
- Keep pages short; don't make the reader scroll more than 1-2 pages. Use wiki features (e.g., tabs) or create additional pages.
- Use wiki features appropriately: headings, tables, lists. It's a really simple syntax.
- Write in English for our international readers.
- Avoid screenshots of large amounts of text to enable search engine index your page.
Some examples for small-software websites (not all of these are web-related, but you get the idea).
Remember the milk ToDo application w/gadget
Sacred Destinations gadget
Congratulations! the semester has just started and you're almost done with the workshop.
We hold one last class meeting on Jan 31 (instead of Jan 24) where you'll present the penultimate version of your projects.
Fortunately, now Oded can officially examine and criticize praise your hard work.
Also joining us for the showdown are our Googlers; Prepare your bug reports questions!
Note that we traded our usual room for the prestigious Schreiber 309 seminar room.
I remind you again to prepare your project to submission (including web documentation) as the class will be shortly followed by individual grading meetings.
Tomorrow we won't meet, as the Course Schedule says.
But that does not exempt you from creating your project page!
The very least I expect is filling the Abstract and Group members sections.
I created a template for you to use when creating the project page.
Just enter the project name in the box on the sidebar and it will create for you the page project:name-of-your-project with the template.
Don't forget to press preview to see the template in action!
We meet again this Thursday.
Groups which have decided on their project briefly tell about it to other groups (no need to have a presentation).
Workplan is still not needed, but get it ready for next week or so.
Also, see the Google Gadgets Talk presentation on the Course Schedule page.
As said in class last week, next week (1/11/07) we'll have a presentation of iGoogle gadgets by Googlers.
Almost all individual projects now have some descriptive text. In tomorrow's class I will explain a bit more about each of these.
Don't forget that you can always come with your idea!