programming, part I
Lecture 1 (important)
• About the course
• About examination
• Start groups
• Access to code (CVS)
Lecture 2 (if you like)
• How to use CVS
• How to use Cygwin to compile
• Eclipse as IDE
• Java questions?
• Assignment 1
• Erik Borälv, room 1157
• News, changes, assignments
• Progress, assignment feedback as PDF,
Course evaluation 2008
• Overall opinion about the course? (3.88)
• The course framing (the way the course was planned and executed (3.54)
• The course examination (4.06)
• Want more lectures
• Hard (or uneven) work
• No experience in group meetings, seminars
Open door policy
Try to make assignments even in work load
Clearer structure for group meetings
Diary, for individual effort
The course is about implementation and construction – not graphical design!
• The focus is on learning how to implement graphical user interfaces the ”right way”.
• Problem-based learning
• The course is 100% practically oriented; scientific theories provide the base, but we’ll learn it
through practical experience.
Goal of the course
After completing this course you will…
• Be able to implement a graphical user interface
• Understand how GUI:s updates automagically if correctly implemented
• Know how to connect logic with presentation
• Be able to make your own graphical components, if it should be necessary
• Tools for group-based code development
• Similar to industry style of work
• New assignments handed out every second week
• Assignments turned in every second week
• Bruce Eckel: Thinking in Java (online)
• The net
Practical experience (Learning by doing)
No written exam. Grade based on:
• The group’s overall result
• Individual diary
• Individual activity and shown understanding during group sessions
• Presentation/documentation of solutions
Use existing components from an interface library to build an interactive user interface
Be able to produce an interface that has support for several languages, by separating linguistic contents from program code
Separate an interface's behavior from its appearance
Produce responsive interface
Structure program code in a way so that the different parts of the code are independent of one another
To plan and create solutions where the visual presentation are independent of the underlying data structure
Present individual and group results in discussions and seminars
On the basis of a plan be able to implement an interactive interface
Grades: 3, 4, or 5; or ECTS (A-F) grades
Weekly group sessions
45 min; probably 3 groups per meeting
Mandatory: if you are prevented from
attending, report this to Erik before to the meeting
• You will get an extra assignment if not attending (to write a short paper about a specific topic)
• Prepare any questions you might have
• Bring code, screenshots
You can start the group assembly directly after this lecture.
• Slot 1 (usually 13-14) : A+B+C
• Slot 2 (usually 14-15) : D+E+F
• Slot 3 (usually 15-16) : G+H+I+J
• Slot 4 (usually 16-17) : K+L+M+N
Change time with someone if your group has difficulties a certain time.
All programming will be performed in Java 6, with an editor and a compiler
The user interface library - Java Swing
To get experienced in Java, it’s important with individual studies and hands-on practice
If you are less experienced in Java, an initial effort will make everything a lot easier later on
Overall project goal: a MP3-player
• Refined during the 4 assignments
Deadline for assignment 1 is 29 January.
• Basic. Should not be too difficult.
• Focus is on getting started with your team members and Java+CVS+Ant+diary
• Check the course homepage for instructions
Concurrent Versions System
Handles different versions of your files and
makes sure that everything is available at one place.
All of your code and other resources such as icons must be checked into the group’s CVS.
To get CVS access, fill out and turn in the CVS paper form.
Build-tool. Works like make – only better.
Used to compile code.
De-facto standard when developing in Java.
You don’t need to know everything but should be able to understand ’build.xml’, what it
does, and how.
<!-- Starts the player. -->
<target name="run" depends="build">
<java taskname="Player1" classname="player.ui.Player1"
<!-- Starts the diary client -->
<java taskname="DiaryClient" classname="kaa.diary.DiaryClient"
• 4 persons/group
• Don’t forget to turn in a CVS-form
Start to work early.
I’ll try to get the CVS:s to up and running as soon as possible.
Want more lectures? Ask!
Don’t hesiste to ask for help with compilation errors etc.
• Bring code: on paper, in laptop, in CVS
1. Select a group, fill out a form
2. Fill out a CVS form, one per person 3. Make sure your tools are working
4. Start working on assignment 1