=== Zami_ is now known as Zami [10:05] how can i look at past irc classroom logs? [10:06] http://irclogs.ubuntu.com/ [10:06] thanks === tux_race1 is now known as tux_racer === yofel_ is now known as yofel === screen-x is now known as hds === hds is now known as screen-x === ghost is now known as Guest97661 [16:08] s [16:18] jono: did you receive my slides? (and for generating the translation string, just quickly package or quickly share/release) [16:20] didrocks, yep, they are in there :) [16:20] didrocks, isnt there an argument to pass setup.py if I remember right? [16:20] I remember dpm did something [16:21] not sure if it's related at all with what you are talking about, but there is: python setup.py build_i18n [16:22] RainCT, thats it! [16:22] woo! [16:22] jono: if you want to do that outside of quickly yes (but the previous command calls that). It's ./setup.py --build-i18n [16:22] let me check for the syntax exactly :) [16:22] one sec [16:22] thats cool for updating the translations template without packaging [16:22] thanks RainCT, didrocks! === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - http://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Event: Ubuntu Opportunistic Developer Week - Current Session: Creating stunning interfaces with Cairo - Laszlo Pandy - Instructor: laszlok || Questions in #ubuntu-classroom-chat [17:01] Hello everyone, i'm gonna be talking about using cairo with python today [17:02] I haven't prepared any slides, but I'll be using some links [17:02] and it will be less structured than usual, so feel free to shout out or ask questions at any time in #ubuntu-classroom-chat [17:03] I won't mind taking a large detour, we'll probably have plenty of time for it [17:03] So cairo is a drawing API [17:04] if you know about SVG graphics, it does the same sort of thing [17:04] it has strokes, fills, gradients, etc [17:04] Its also a very modern drawing api [17:04] the library was written quite recently [17:05] I mean modern in that it has good alpha support, and really good antialiasing [17:05] so when you draw graphics they scale well and look very clean [17:06] unlike previous generation APIs like Java graphics (don't get me started) [17:07] Cairo integrates really well with GTK, in fact most widgets in GTK are now drawn using cairo [17:07] I will show you how to use it with GTK and also how to use some other cairo backends like svg, pdf, and png [17:08] In terms of creating stunning interfaces, it can be done with cairo. If you create a stunning GTK app then you are doing it with cairo anyway ;) [17:08] however cairo is low level [17:09] if you are using cairo directly you are drawing all the lines and calculating all the geometry yourself [17:10] There was a talk yesterday about goocanvas, which uses cairo and gives a much higher level view. You can deal with objects instead of geometry calculations. [17:10] But if anyone has questions about that, please ask [17:10] http://www.cairographics.org/samples/ [17:11] here is a page on the cairo website with some sample code and how it will look [17:11] the code is in C, but it is quite similar to python as you will see [17:12] QUESTION: Can we build all the application interface using Cairo (except for the Window container)? [17:14] yes you can, but it will involve a lot of trickiness if you want to detect mouse clicks on many different objects [17:14] it will work fine for a simple drawing, but once you start using lots of objects you might find the geometry to figure out which one is clicked it too much [17:14] this is why things like goocanvas were invented; to automate those things [17:15] QUESTION: can we use cairo to create the interface separate from the logic that runs the program? [17:15] yes, in the same way that you would have a GTK interface separate from the program logic [17:16] QUESTION: maybe for later, is there a preferred way of doing animations in cairo? [17:16] cairo does not provide support for animations, so it has to be done essentially the same as animations in other drawing apis [17:17] that means having a timer to redraw the screen and have code to redraw the whole screen (or just the parts that change) [17:18] so as you can see in the samples, cairo has primitives for arcs, lines, etc. [17:18] Thinking about an interface in these primitives is a bit low level, but it gives you the great flexibility [17:19] QUESTION: Does the animation redraw method you just described use a lot of cpu power? [17:19] if your drawing is complex, it probably will [17:19] but cairo is quite efficient, and allows you flexibility for caching drawings [17:20] for example if you have a background which requires a long time to draw, you can draw it to an ImageSurface in memory instead [17:20] and then it is one operation to draw it on screen [17:21] QUESTION: would like to add to performance that strokes are the ones that are expensive. [17:21] that's not a question ;) [17:22] http://www.cairographics.org/documentation/pycairo/reference/index.html [17:22] here is the python documentation for cairo [17:22] that is good reference when looking at the next link [17:23] http://laszlopandy.com/files/drawing_interface.html [17:23] here is some poorly commented python code I prepared [17:23] QUESTION: waht are all the required components to start working on cairo+python? [17:23] only cairo, python and pycairo [17:24] if you want to render directly on screen (as opposed to png or svg) you should have pygtk installed as well [17:24] for example, in the code i prepared I am importing both gtk and cairo [17:25] copy and paste this code into your editor [17:25] if you run it with no arguments you will get a gtk window [17:25] if you give it 'png', 'svg' or 'pdf' as an argument, it will generate that kind of file [17:25] so lets take a look at the GTK code, in the DrawingInterface class [17:26] it creates a window, and adds a gtk.DrawingArea [17:27] the DrawingArea is a widget which is like a blank canvas we can draw to [17:28] then we set the size of the window, and show it [17:28] not much to see there [17:28] the expose event is the event when the X server tells the window to redraw itself [17:28] so this is what we are using to trigger our drawing code [17:29] also notice that in the GTK code the cairo context is created directy from the widget. GTK is integrated with cairo and makes it easy [17:29] the context is what holds all the information about your drawing as you add lines and shapes [17:30] the draw_rounded_rentangle() method is converted from the C example on http://www.cairographics.org/samples/ [17:30] if you compare them you can see it is mostly identical code [17:31] QUESTION: please explain the underlying functiosn used in on_expose [17:31] http://laszlopandy.com/files/drawing_interface.html [17:31] in on_expose we create the cairo context associated with the widget [17:32] so when we draw using that context, it will draw on the widget [17:32] widget.get_allocation() returns a renctangle with the width and height of the window, so we know how much space we have to draw [17:32] and self.drawing.draw() calls the method on the drawing class three lines below that [17:33] QUESTION: will the get_allocation be called only after drawing.draw is called? [17:33] this is equivalent to: [17:33] rectangle = widget.get_allocation() [17:33] self.drawing.draw(ctx, rectangle) [17:34] so the draw() method can know the size of the widget [17:34] by default, the DrawingArea widget is the default gtk colour [17:35] so in the draw() method I create a rectangle the size of the widget and fill it with white [17:35] the context remembers things like rectangles i have created, and also what colour i set it [17:36] after I call fill() the rectangle is removed from the context and put on the screen, but the colour is still set [17:36] so remember to change your colour or it will be whatever you set it previously [17:36] QUESTION: Is it possible to do some basic 3d transformation? (Like perspective on GIMP) [17:36] cairo is a 2d canvas, but you can do transformation [17:36] to fake a perspective [17:37] take a look at http://www.cairographics.org/documentation/pycairo/reference/matrix.html#class-matrix [17:38] In get_gradient() http://laszlopandy.com/files/drawing_interface.html [17:38] you can see cairo makes gradients really simple [17:38] you create a gradient with a start and end point to define how long the colour change will be and in what direction [17:39] and then you set stops on the gradient, just like you would do on inkscape or other graphics programs [17:39] the first argument to add_color_stop_rgb is the offset between 0 and 1 [17:39] so i set two colour stops. One at the beginning and one at the end [17:40] you can easily add a third one in set it to offset 0.5 and your gradient will blend three colours [17:41] now look at the bottom part of the code where it says if arg == 'pdf': [17:41] i mentioned earlier about using image surfaces to store your drawing in memory [17:41] surfaces also allow you do store in files [17:42] QUESTION: can you set the gradient to go through the hues in the opposite direction? [17:42] yes [17:42] either reverse the offsets [17:42] (set the first one to offset 1, and second to offset 0) [17:43] or reverse the pairs of (x,y) parameters to the LinearGradient constructor [17:44] QUESTION: does the context variable acts as a placeholder or as a memory buffer? [17:44] it is the same as the drawing context created from the GTK widget except it writes to a file [17:45] so it will store your drawing in memory and write it to the file when you complete a fill() or stroke() [17:45] QUESTION: How to make it write to a jpg file? [17:46] JPG file compression is meant for pictures where there are not perfectly smooth lines [17:46] PNG compression works much better for drawings, things with smooth and sharp borders [17:46] so cairo does not support JPG directly, i would write to svg or png and use imagemagick to convert it [17:48] so as you can see, cairo surfaces make it really easy to export to other formats [17:49] and if you were writing on windows or mac, you would use a surface specifically for the platform and the rest of the api would be the same [17:50] any questions? [17:50] QUESTION: does cairo do that "redraw only changed parts" automagically, or do we manually tell what changed ? [17:50] you could have to do that manually [17:51] in this case i redraw the white rectangle each time, therefore blanking the entire screen [17:51] this is something that goocanvas would also automate for you [17:52] QUESTION: How difficult is it to use cairo in combination with pygoocanvas? (For example, if I wanted to draw/animate something like a progress indicator on top of my goocanvas while waiting for goocanvas to update during a slow operation.) [17:52] that seems like a strange use case, but it should work [17:52] theoretically you can use cairo to draw on top of any GTK widget [17:53] as long as the proper flags are set [17:55] QUESTION: What are the advantages of using cairo directly instead of through goocanvas? [17:55] goocanvas is much higher level [17:55] and cairo is very lightweight [17:56] if you are doing something simple and want the flexibility, or don't mind doing the drawing manually then cairo is the way to go [17:56] its really easy to get started with, and can work with GTK mouse clicks, etc well for simpler things [17:57] if you know you have a bunch of objects you want to drag around on the screen, goocanvas will probably make your life much easier [17:57] QUESTION: the png format uses the format_argb32 constant. the manual shows 3 more. can u tell the formats they specify? [17:58] referring to http://www.cairographics.org/documentation/pycairo/reference/constants.html#constants-format [17:58] FORMAT_ARGB32 is colour surface with alpha support [17:59] FORMAT_RGB24 is the same without alpha support so you will not be able to do transparency [17:59] the others are for alpha only masks and do not store colour values [18:00] these formats are for image surfaces. You may need to specify alpha only if you want to make a transparency mask === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - http://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Event: Ubu ntu Opportunistic Developer Week - Current Session: What's new in Quickly 0.4 - Didier Roche - Instructor: didrocks || Questions in #ubuntu-classroom-chat [18:01] awesome laszlok, thanks for your session :) Just a question, when will you do a Quickly template for a cairo project? :p (kidding) [18:01] so, welcome everyone on the session about Quickly 0.4 [18:02] [SLIDE 1] [18:02] who is interested on what we backed for Quickly 0.4? hands up in -chat! [18:03] nice [18:03] so, I'm Didier Roche, one of the Quickly developer and also desktop team member [18:04] (and fresh ubuntu core dev :)) [18:04] for people not seeing the slide, you can get them at http://people.canonical.com/~didrocks/Quickly-0.4.pdf [18:04] it should be on the Session tab in lernid [18:05] so, first, what this session is *not* about [18:05] this session isn't a presentation of Quickly. This has already been done later this week by Rick Spencer. logs availabled at https://wiki.ubuntu.com/MeetingLogs/OpWeek1003/Quickly [18:06] [SLIDE 2] [18:06] (at least, it works me in lernid :p) [18:06] (and that's not Quickly's fault ;)) [18:06] so, 0.4 is unfortunately still in development === yofel_ is now known as yofel [18:07] it still needs some stuff to be added in launchpad to make things easier [18:07] and I prefer to do that the right way than a quickly screenscrapping [18:07] so, warning, it's unstable, the current version is 0.3.5 [18:07] I hope to release the stable version before lucid beta 1 [18:08] in any case, Quickly 0.4 will be in lucid :) [18:08] so, a little about stats [18:08] last version which is 0.2.6 has been release approximately 6 months before [18:08] and a lot happens in 6 months :) [18:09] you can see some stats for the addicts: 250 commits and 12930 changed lines [18:09] to be honest, some file had been moved, so if we want to be fair, I would say 4000 code of code have been really impacted [18:09] it's a lot, and I'll show you now what are in those lines :) [18:10] [SLIDE 3] [18:10] souces: how to be informed of what's new? [18:10] well, this session is dedicated to that, so that's a good first step :) [18:10] (I'll probably blog on planet ubuntu too when Quickly 0.4 will be out) [18:11] a more detailed sources the NEWS file in trunk [18:11] I try to keep it pretty complete [18:11] and of course, if you want full details, you have to read the 250 commits :) [18:13] let's first see what's the most noticeable changes [18:13] the first thing is that the ubuntu-project template (the only one which existed in 0.2.x) is no more… [18:13] don't be panic, it has just been renamed ubuntu-application [18:13] of course, existing project will be transitionned appropriately so that you don't have to change anything for existing Quickly users [18:13] Quickly 0.4 will welcome at least one new template, and even maybe a third one in trunk :) [18:14] ubuntu-cli template is to create a command line soft with all the ubuntu-application intgration [18:14] (a lot of people asked for a cli template :)) [18:14] ubuntu-game (or pygame, or whatever) will be detailed later in this week by Rick, you should be already aware of that if you read planet ubuntu [18:15] also, artfwo (thanks to the template inheritance I'll described later) is beginning to implement a gedit-plugin template [18:15] so, a lot of goodness to come in a very short time :) [18:15] [SLIDE 4] [18:16] as there is no question, let's dive a little bit more on what's interest most of you: ubuntu-project… hum… ubuntu-application new capability ;) [18:17] first thing (and I'll come back later on that) you have to understand is that your existing app will be converted for 0.4 [18:17] it will be the first time you run a quickly command on it [18:17] (also if you proceed some tab completion) [18:17] that's needed and it's a new Quickly core capability [18:18] that implies that projects which will be converted to Quickly 0.4 won't work anymore with a previous version of Quickly [18:18] (it's still possible to convert back by hand, but complicated) [18:19] as I wrote, ubuntu-application in 0.4 has a new versionning scheme [18:19] that means that project will follow by default ubuntu way of versionning thing [18:19] for instance, if I run "quickly release" just now, my release will be 10.03 [18:19] if I run quickly release again, it will be 10.03.1 [18:19] and so on :) [18:20] you are still able to provide your release version yourself [18:20] the second point is the most tricky one but the one on the top priority list [18:20] did you have some troubles setting up your gpg and ssh key on LP to make your first quickly share/quickly release? [18:21] that will be (we hope) part of the past in 0.4! [18:22] this is what I'm currently working and that needs a lot of work on launchpad side… and I'm not a LP hacker [18:22] so, normally, if you don't have one, Quickly will do everything for your [18:22] you* [18:23] also, selecting the right email adress through some algorithms :) [18:23] moving on… [18:23] quickly license has been totally reshaped [18:23] no more Copyright file which populate an AUTHOR file, you will only have to edit the AUTHOR one [18:23] (this confused some people before) [18:24] the next one is more interesting [18:24] when you quickly release, your changelog will automatically be collected with all the messages you provided in "quickly save " from the last release [18:24] it will create a release and milestone on launchpad [18:24] upload your tarball too to be available on the first page [18:25] and create an annoucement with your changelog [18:25] of course, as a good upstream, it signs the tarball file too (as it's recommended as a best practice) [18:26] you can see what it gives on my test project: https://edge.launchpad.net/fooby [18:26] next point is ppa [18:27] when Quickly 0.2 was released, launchpad only enabled you to have one ppa [18:27] which was called… "ppa" [18:27] things have changed now and you can have multiple ppa [18:27] also, some people would like to upload the package to a team ppa [18:27] and to be honest, that makes sense :) [18:27] so, now, you can upload to any ppa you want [18:28] either by providing --ppa [18:28] to quickly share and release [18:28] or to put it as a default with quickly configure ppa [18:28] of course, shell completion still works there and give you the list of all ppa you have access [18:29] (/!\ it's slow on LP side, can take more than 10s) [18:29] ppa_name can be: "myppa" or "team/ppaname" [18:29] and shell completion works for everycase :) [18:30] on another aspect, as I wrote some commands have been rename to be more consistent [18:30] quickly dialog is now quickly add dialog [18:30] (that will avoid in the futur to have 50 commands in a template) [18:30] quickly lp-project is quickly configure lp-project [18:30] and quickly glade is now quickly design [18:31] of course, as always, statement completion is here to help you to find commands name and arguments to the commands :) [18:31] for instance quickly configure [tab][tab] will show you all available options like ppa, lp-project, bzr [18:32] [SLIDE 5] [18:32] ah, I like very much next option :) [18:32] when you "quickly release", now, you will have the about dialog automatically refreshed [18:33] that means, your logo, but also the new version number appears, the Copyright holder, the homepage, the Credit (authors) button and license one [18:33] so, no need to before or to think about them, Quickly is handling that for you :) [18:34] that avoid to make a .1 release with "I forgot to…" [18:34] next item (no, not the blank one) had been asked also by a lot of persons [18:34] being able to add manual dependencies [18:35] "why care, quickly already grab all the depends for us?" you will tell me… [18:35] that's both true and false to be honest :) [18:35] for instance, if you launch a command yourself as a subprocess pythondistutils-extra won't find it and you will have a missing dependency [18:36] so now, for that, you can just fire away $ quickly configure dependencies [18:36] as "dependencies" is typo-prone, think about using shell completion for that too :) [18:37] next thing is bzr branch, as for ppa, you can tell where you can push and pull your code if you are interested in :) [18:37] quickly configure bzr of course :) [18:38] maybe the tutorial which (I'm afraid) is still not internationalized will be thanks to fagan. But nothing sure yet, still ongoing work :) [18:39] of course, this was only the most important things I can list for that session for ubuntu-application template, but there are a lot of various fixes, new licenses available, packagin tweak, internationalized application, and so on :) [18:39] [SLIDE 6] [18:39] oh btw, I forgot about the apport hook! [18:40] all project will come (but you can still disabling that if you don't want) an apport hook by default [18:40] and the menu will have the launchpad addition for translation and help in the help menu [18:40] ok, so, now, really slide 6 :) [18:41] this is for prospective template developers and people interested in making a GUI for Quickly [18:41] first thing is importing commands between templates is available [18:41] QUESTION: does having an apport hook mean that if the program crashes and stuff you can send a detailed report to the launchpad project? [18:41] dbell: exactly :) [18:42] and you get that for free :) [18:42] so, back on importing commands [18:42] if one day you want to look at the ubuntu-cli template [18:42] you will see that there is 0 line of code [18:42] yes, no typo, I said 0! [18:43] it's just a new boiler plate, and I import all commands from ubuntu-application [18:43] so, basically, there is a commandsconfig with: [18:43] [ubuntu-application] [18:43] IMPORT=configure;create;edit;license;package;release;run;save;shar [18:44] (for obvious reason for a cli template, I don't import design and add dialog :)) [18:44] and then, I can create a ubuntu-cli application, edit, licence, package… [18:44] and get statement completion for all of those using the new boiler plate code :) [18:45] so, creating a template from an existing one is really really easy [18:45] QUESTION: Will apps still work if python-launchpad-integration isn't installed (eg. on other distros) [18:45] RainCT: we try to include that as a patch, so that pristine tarball doesn't have that code and so other distros aren't impacted [18:45] (it's basically a try: pass) [18:46] well, other functions (quickly ;)) [18:46] you can now pass option to template [18:46] we have apport integration [18:46] so ubuntu-bug quickly is your friend :) [18:47] as I told you, you can now quickly configure [tab][tab] --ppa [tab][tab] [18:47] that means that the core has now option completion for you [18:47] we handle template upgrade [18:47] (even if you launch a command from one template into another project) [18:47] like quickly --template my-awesome-template foocommand [18:48] we have also now an API [18:48] so, if you want to build a GUI or integrate it into an IDE, that's the way to go :) [18:48] of course, in addition to thing, many fixes and refactoring [18:48] [SLIDE 7] [18:49] I've already talked about the ubuntu-cli template [18:49] the most important thing is that it's a new boiler plate for no code for the commands :) [18:49] if you want to implement your own template with import of ubuntu-application command, that's where to look for examples [18:50] QUESTION: Any examples on the API? [18:50] osteenbergen47: basically, you just have to "from quickly import api" and then, look at the api file [18:50] if you are interested in that, join #quickly and I can help you :) [18:50] QUESTION: is there a tutorial on how to do own/custom templates ? [18:51] oskude: I've written one for Quickly 0.2, let me find the link [18:51] http://blog.didrocks.fr/index.php/post/Build-your-application-quickly-with-Quickly%3A-Inside-Quickly-part-6 [18:52] (and now, I kill my Internet connexion as I host myself my server ;)) [18:52] this is quite outdated [18:52] I will refresh that once 0.4 out [18:52] [SLIDE 8] [18:52] so, you want to try Quickly 0.4? (well, 0.3.5) [18:53] as I mentionned before, we warned, you can't convert back your project to the previous format [18:53] and I don't have the time to ensure that everycommand works at each commit, but I try to fix the issue within the day [18:53] so, jump into #quickly, so that you can yell at me that it's broken :) [18:54] and if you want to test, branch the trunk [18:54] bzr branch lp:quickly [18:54] export PATH=/bin:$PATH [18:54] (note the /bin :)) [18:54] quickly --version should normally answer you about the current version [18:54] [SLIDE 9] [18:55] of course special thanks to Rick to have the idea of this project [18:55] and he will do the two next session, stay around :) [18:55] also some contributors are really awesome and help pushing the project further :) [18:55] [SLIDE 10] [18:55] so, taking questions now in the 5 remaining minutes [18:56] QUESTION: Is there an easy way to try fresh quickly on Karmic? The straightforward setup.py build/install way results in a lot of errors. [18:56] right, there is a bug logged about that [18:56] I don't see anything preventing for backporting to karmic [18:56] BUT [18:56] you need last distutils-extra version [18:57] (else you can't add depends, nor you have the automated changelog goodness) [18:57] and I probably have to fix setup.py [18:57] I think I'll try to provide a package in the quickly ppa for karmic [18:57] QUESTION: Is there a ppa-daily of Quickly for auto installing the last one? [18:58] there is a daily ppa, jcastro was the owner IIRC, I don't know the current state to be honest [18:58] I think export PATH is more convenient :) [18:58] and that's what I do everyday :) [18:59] well, of course the day we can do "quickly release lucid", I think Quickly will take some thousands lines of code :) [18:59] The dailies work, if they don't work for you just poke me. [18:59] but as I still like my job, it won't happen :) [18:59] I guess it's time :) [18:59] and thanks jcastro [19:00] thanks all for your attention [19:00] now, stage is to you rickspencer3 [19:00] and thanks for having launched Quickly once more :) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - http://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Event: Ubuntu Opportunistic Developer Week - Current Session: Create games with PyGame - Rick Spencer - Instructor: rickspencer3 || Questions in #ubuntu-classroom-chat [19:01] hi all [19:01] ready for some pygame stuff? [19:02] great [19:02] as usual, I got my notes ready before hand and stuck them on the wiki: [19:02] https://wiki.ubuntu.com/UbuntuOpportunisticDeveloperWeek/PyGameClassNotes [19:03] so I'll go through each section and take questions [19:03] Pygame is a library for making arcade style sprite games [19:03] It features very easy blitting and colision detection [19:03] I have some sample code to help with understanding pygame here: [19:03] https://code.edge.launchpad.net/~rick-rickspencer3/pygame-template/trunk [19:03] I think you can go: [19:04] bzr branch lp:pygame-template too [19:05] note that some of this code is a bit old, and I need to reformat it and such [19:05] but it [19:05] s failry readable [19:05] however, it will eventually be a quickly template, hopefully in time for lucid [19:05] if you want to grab that it might help you follow the class a bit, but it is not required [19:05] it comes with some basic game play that you can study and modify [19:05] essentially, it is kind of like asteroids [19:05] you control the black triangle in the middle, and there are two enemies [19:05] Of course you will want some docs [19:05] Pygame has good docs here: [19:05] http://www.pygame.org/docs/ [19:06] before we discuss how to set up a game [19:06] any questions? [19:06] ok, then let us rock [19:06] so, you're going to set up a game [19:06] first thing you need to do is set up a game surface [19:07] and do other initalizations [19:07] so .. [19:07] initialize pygame libraries [19:07] pygame.font.init() [19:07] pygame.mixer.init() [19:07] (assuming you are using fonts and sound of course) [19:07] then create a screen [19:07] the screen will be the surface on which your sprites will be drawn, essentially where your game will occur [19:07] screen = pygame.display.set_mode((800, 480)) [19:08] that's for an 800 x 400 pixel game [19:08] also, create a couple of variable you will need later [19:08] like a background image [19:08] background = pygame.image.load(path_to_background) [19:08] notice the image is a PyGame image [19:08] and a clock [19:08] clock = pygame.time.Clock() [19:08] you'll see why we need the clock next [19:09] pygame games use a good old fashioned input loop [19:09] don't know if you all ever programmed with an event loop [19:09] but it was very common for writing GUI apps back around when dinosaurs used computers [19:09] essentially, you tell your app to keep looping [19:09] and whenever it goes through the loop do a few things [19:10] 1. respond to user input [19:10] 2.update data for any sprites on the screen [19:10] this includes seeing if any sprites have collided [19:10]