Skip to content

Home

Jump to bottom
bumbu edited this page Feb 8, 2013 · 22 revisions

Windows Programming Laboratories Repository

Windows Programming Laboratories Repository

Prerequisites

  • C++ average to strong background
  • Spoken and Written English

Purpose of the Course

  • Event-driven programming (message-oriented)
  • API
  • Windows applications development

Additional Purposes

  • Version Control Systems (git)
  • Code style
  • Debugging
  • Virtual machine
  • 3-tier architecture
  • Testing

Rules About Rules

Laboratory work follow rules that where public when submission was done. If you'll do a submission after rules change, your submission will be processed using new rules.

Red pill and Blue pill

Both paths have different laboratory works and some differences in:

  • grading policy
  • submission process

Red Pill

You’ll follow New curriculum. Laboratory works are more complex, covers all the material from Old curriculum (Blue pill) and try to cover new nowadays technologies. There are much more points, so even if you think that you are middle-skilled developer, you anyway can have highest mark.

You'll have to work using GIT. If you’ll submit your work before deadline, I’ll count it as presence at laboratory hours.

List of available laboratory works and their details are on Red Pill page.

Blue Pill

You’ll follow Old curriculum. Laboratory works are easier, but have less points.

List of available laboratory works and their details are on Blue Pill page.

Grading Policy

You can foresee your marks by following Grading Policy rules.

Submission Process

In order to pass this course you have to submit all you laboratory works. For details view Submission Process page.

Having questions?

First check issues page and closed issues page. Then check facebook page.

If your question is still unanswered then:

  • if your question is about schedule, classroom, some events, some deadlines or anything else that is specific for your group, ask it on facebook page
  • otherwise ask questions about laboratory works by opening new issues

Stay updated

In order to recieve changes on repository or on its wiki, there is a watching button on top of repository page. Also you can keep an eye (email feeds, sms notifications ...) on facebook group page.

Want to contribute?

Contribute to laboratory works descriptions or samples

To edit laboratory works descriptions or samples do a pull request to WP repository with your proposals/changes/typo fixes.

Contribute to wiki

To edit/create a wiki page do:

  • Manually create a fork of the WP wiki on your GitHub account:
    • Create a new repository on your GitHub account. Let's call it "WP-Wiki"
    • Clone the WP wiki repo to your local machine somewhere: git clone [email protected]:TUM-FAF/WP.wiki.git
    • Remove the original "origin" remote and add your github repo as new "origin" git remote rm origin and git remote add origin git://github.com/<YOUR_USERNAME>/WP.wiki.git
  • Make your proposed changes locally, then push them to your github account:
    • git push -u origin master ('-u origin master' only required the first time; afterwards just do git push)
  • Submit a ticket to the WP issue tracker requesting me to review your changes and merge them in. Please be sure to include a link to your repo and describe what you've changed.

Clone this wiki locally