=== nhandler_ is now known as nhandler === Jamie is now known as Guest17177 [06:51] hi im writing some documentation. id like to explain what an upstream is, in a clear manner. could someone please help? [06:59] zubin71: I can't find a nice definition from a quick wiki search. Hunt up jcastro in #ubuntu-community-team : he tends to have good answers to this class of question. [07:00] persia, ok... thankx! :) === tux_race1 is now known as tux_racer [13:21] let's hack [13:21] ? [13:25] black_aprentice: You might be early for a class. You're looking for the opportunistic developer stuff? [13:26] yup, but I already got the new that it starts at 1 pm in my time here [13:29] black_aprentice: You might want to hang out in #ubuntu-app-devel in the meantime. That's the all-day-every-day place for discussions about creating apps. [13:29] persia: already there, but no activity at this time also [13:30] Oh well :( === mohi_away is now known as mohi1 [15:33] was isn nu eigentlich? [16:00] class time? [16:00] time to talk about goocanvas? === 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: Gooey Graphics with GooCanvas - Rick Spencer - Instructor: rickspencer3 || Questions in #ubuntu-classroom-chat [16:00] okay, let us rock [16:01] as usual I have put my class notes on the wiki: [16:01] https://wiki.ubuntu.com/UbuntuOpportunisticDeveloperWeek/GooCanvas [16:01] I'll be using python and pygoocanvas for code samples to talk about goocanvas today [16:01] There is good reference documentaion for goocanvas: [16:01] http://people.gnome.org/~gianmt/pygoocanvas/ [16:01] llive it, learn it, love it ;) [16:01] Unfortunately, it can be a bit tough to find code samples and tutorials [16:01] :( [16:02] so, let's take a look [16:02] So what is a goocanvas? [16:02] A goocanvas is a 2d composing surface [16:02] You can use it to make pretty much any kind of "image" [16:02] It's kind of like an api around a drawing program [16:02] So you can have a ton of fun using a goocanvas, because you are pretty much freed from the constraints of a widget library in creating your UI [16:03] goocanvas is cairo under the covers [16:03] and is designed to easily integrate into your gtk app [16:03] so, before we get into specifics [16:03] questions? [16:03] and note, I will be trying Classbot for the first time, so bear with me for a bit [16:04] no questions? [16:04] eviltwin asked: is goo canvas considered the "approved" replacement to libgnomecanvas? [16:04] I don't know [16:04] I like goocanvas for it's capabilities [16:06] setimike asked: Is goocanvas sort of like glade? [16:06] not at all [16:07] glade is a tool which creates XML files that describe gtk layouts [16:07] goocanvas is a widget which you embed in your program and then use as a drawing surface [16:07] let's take a look [16:07] nadako asked: is it some OO-wrapper for basic cairo drawing things? [16:07] yes [16:07] luismmontielg asked: How do we get pygoocanvas? [16:08] from the repos [16:08] damo12 asked: Can glade add a widget area for pygoocanvas? [16:08] I don't think there is a way to do that [16:08] but I will show you how to add it with code [16:08] So let's add a goocanvas to a pygtk app [16:08] Add it just like a normal pygtk widget [16:09] here's some code [16:09] self.__goo_canvas = goocanvas.Canvas() [16:09] self.__goo_canvas.set_size_request(640, 480) [16:09] self.__goo_canvas.show() [16:09] Be sure to set the size, otherwise it defaults to 1000,1000, it does not default to [16:09] the size alloted to it in your window. [16:09] this is different than normal gtk.Widgets where size is managed for you [16:09] Handle window resizing to resize your goocanvas as well [16:09] For example, if your goocanvas is in a VBox, you can do this: [16:10] rect = self.builder.get_object("vbox2").get_allocation() [16:10] self.__goo_canvas.set_bounds(0,0,rect.width,rect.height) [16:10] store a reference to the root item for your goocanvas, you'll need it later often [16:10] self.__root = self.__goo_canvas.get_root_item() [16:10] The "root" is kinda like the root of an item tree in XML [16:11] so if you do this, you'll have a goocanvas in your app, ready to rock [16:11] questions? [16:11] ok [16:12] let's look at adding things to your goocanvas surface [16:12] I got into goocanvas while working on photobomb [16:12] so I have some code that I can use for examples [16:12] so let's take the example of adding an image to your goocanvas [16:13] assuming you want to modify the image and combine it with other drawing items [16:13] Anything that can be added to a goocanvas is an Item. It get's it's capabilities by inheriting from ItemSimple, and by implementing the Item interface. [16:13] plus each items has some extra capabilities [16:13] so look at the reference for the specific item class, as well as Item and ItemSimple [16:13] Let's add an item to the goocanvas to get a look at how it works in general. [16:14] We'll start by adding an image. [16:14] First, you need to get a gtk.pixbux for your image: [16:14] pb = gtk.gdk.pixbuf_new_from_file(path) [16:14] Then you calculate where you want the image to show on the goocanvas. You'll need a top and a left to place most items on a goo canvas. [16:14] For example, to center the image, I do this: [16:14] cont_left, cont_top, cont_right, cont_bottom = self.__goo_canvas.get_bounds() [16:14] img_w = pb.get_width() [16:14] img_h = pb.get_height() [16:14] img_left = (cont_right - img_w)/2 [16:14] img_top = (cont_bottom - img_h)/2 [16:15] I've calculated the top and left of the item [16:15] now I am ready to create it [16:15] Note that I create the Item, but there is nothing like goocanvas.add(item) [16:15] rather, when you create the item, you set it's parent property. [16:15] it's different than most container relationships, like in PyGtk [16:15] The parent property is the root of the goocanvas [16:15] This is why I remember the root [16:16] because I will be using it whenever I create items for the goocanvas [16:16] finally, here's the code to create the image on teh goocanvas: [16:16] goocanvas.Image(pixbuf=pb,parent=self.__root, x=img_left,y=img_top) [16:16] This basic pattern is how you add all other types of items. [16:16] decide where to put the item, and set it's parent property to the root of the goocanvas. [16:16] To remove the item from the goocanvas, you don't tell the goocanvas to remove it [16:17] rather you tell the item to remove itself [16:17] item.remove() [16:17] questions so far? [16:18] no questions? [16:18] alright then [16:18] let's talk a bit about different types of items that you can add [16:18] In my mind, there are really 3 types of items [16:19] nadako asked: why not standard add/remove functions from parent obj? [16:19] I have no idea [16:19] this is just how the API is [16:19] I presume it's because it is a wrapper around a c-api [16:19] as I was saying, [16:19] In my mind, there are really 3 types of items [16:19] first is normal items that you add to draw the stuff you want [16:20] this includes: [16:20] Ellipse, Image, Path, Polyline, Rect, and Text [16:20] then there are Layout and group items include: [16:20] Group, Grid, and Table [16:20] And then there is also Widget. Widget is pretty cool. [16:20] You can add a gtk widget to your goocanvas, but note that it will live in a world seperate from the goocanvas [16:21] gtk.Widgets won't be rendered if you create images form our goocanvas and such [16:21] However, this is a cool way to add in situ editing to your goocanvas [16:21] We'll just be talking about normal items for the rest of this class though [16:21] I'll take some questions now, if you've got 'em [16:21] fagan asked: What formats does GooCanvas support? (png,jpeg,svg..etc) [16:22] ya know, I never really investigated [16:22] I would presume the first two [16:22] in terms of svg, perhaps that would be supported a bit differently, as many of the items are described with svg language [16:22] or can be [16:23] like an elipse in an svg would be turned into an elipse item [16:23] rather than rendered as an image [16:23] I would be interested to see what different things people try and how it works for them [16:23] tm_lv asked: why goocanvas? [16:23] this is a good question [16:23] I used goocanvas for photobomb because: [16:24] 1. it was an easy API [16:24] 2. it integrate well with pygtk [16:24] 3. it had good reference docs [16:24] 4. it had the functionality to do the things I wanted [16:24] for #4 that was stuff like adding text, paths, etc... [16:24] and also the ability to render off images easily [16:25] nadako asked: is there any ready-to-use things like connector lines that connects two elements and follow their positions [16:25] not that I know of [16:25] nadako asked: also, what about interactivity? drag/drop, mouse clicks, etc [16:25] you handle that manually [16:25] I'll mention mouse handling briefly [16:25] late [16:25] r [16:26] ok, so moving on [16:26] So what are some of the things that you do with an item? [16:26] Well, you compose with it. So you scale it, move it, rotate it, change it's z-order and such [16:26] For a lot of things that you want to do with an item, you use set_property and get_property [16:26] this is the same way of interacting with properties in pygtk, but you do lots more of it in goocanvas [16:27] For example, to set the a might make a Text item like this: [16:27] txt = goocanvas.Text(parent=self.__root,text="some text", x=100, y=100, fill_color=self.__ink_color) [16:27] so here I am adding some text and it will say "some text" [16:27] it will be at x,y 100,100 [16:27] and will use the stored ink color [16:27] then change the text in it like this: [16:27] txt.set_property("text","new text") [16:28] if I want to know what the text is, I can say: [16:28] my_string = txt.get_property("text") [16:28] some capabilities are accessed directly [16:28] such as bounds [16:29] but most are accessed like this [16:29] Let's look at colors for a moment. [16:29] There are generally two color properties to work with, stork-color, and fill-color [16:29] stork-color? [16:29] let's call that stoke-color [16:29] :) [16:29] If you've ever used a tool ink inkscape, this will make sense you to [16:29] for something like a rect, stroke-color is the outline of the rectangle, and fill-color is the inside of the rectangle [16:30] before I discuss a bit more about transforming items ... [16:30] any questions? [16:30] nadako asked: so it's only about drawing things? [16:30] sort of [16:30] I was able to use goocanvas to make a pretty functional editing surface in photobomb [16:31] it included dragging, drawing lines with a pen too, and saving pngs [16:31] but essentially, yes, it's a drawing surface [16:31] tm_lv asked: getters and setters seem to be result of crappy bindings. do you know if there is any work done to make them more pythonic? [16:31] I agree [16:31] but I don't know of any more work to make it more pythonic [16:31] while the API is not perfect, it is functional and robust [16:32] ok [16:32] moving on a bit [16:32] You can move, rotate, resize, and skew items [16:32] The APIs for doing this are intuitive, imho [16:32] To grow something by 10% [16:32] : [16:32] item.scale(1.1,1.1) [16:33] that says make it 1.1 times as tall and wide as it is now [16:33] And to shrink it a bit: [16:33] item.scale(.9,.9) [16:33] Note that the items always consider themeselves to be their original size and orientation, so doing this will cause an item to grow twice: [16:33] item.scale(1.1,1.1) [16:33] item.scale(1.1,1.1) [16:34] Now, when you start rotating and skewing items, some pretty confusing stuff can start happening [16:34] Essentially, an item tracks it's own coordinate system, and doesn't much care about the goocanvas's coordinate system [16:34] So if you rotate an item, for example, the coordinate systems are totally out of whack [16:34] So if you pass the x/ys to an item based on the canvas's coordinate system, it can get waaaay weird [16:34] like if you have a an item rotated 180 degrees [16:35] and you tell it to add 100 to it's x [16:35] it will move left! [16:35] because the items doesn't know or care that it is rotated [16:35] Fortunately, goocanvas has some functions on it that just do these transforms for you [16:35] let's say I catch a mouse click event on an item [16:35] and I want to know where on the item the click happened [16:35] well, the click coordinate are reported in the goocanvas's coordinate system, so I need to do a quick calculation to determine where the click happened on the item: [16:36] e_x, e_y = self.__goo_canvas.convert_to_item_space(self.selected_item,event.x,event.y) [16:36] here self.selected_item is the item who's coordinate system I want to convert to [16:36] so now e_x is x from the item [16:37] 's point of view, not the goocanvas point of view [16:37] phew [16:37] this is weird, but you get used to it [16:37] so, good time for some questions if there are any [16:37] tm_lv asked: can you nest items in goocanvas? [16:37] yes, but I haven't done that [16:38] nadako asked: can you give a link to that photobomb app? [16:38] sure, it's in my junk folder [16:39] https://code.edge.launchpad.net/~rick-rickspencer3/+junk/photobomb [16:39] luismmontielg asked: What could be easier to implement, for a small pygtk app, using pyclutter or pygoocanvas? or whats the difference between those 2 [16:39] clutter is also very cool [16:40] but it's a wrapper around OpenGL [16:40] I suspect that for a small 2d surface, goocanvas will be much better [16:40] however, for rendering animations, clutter will be much better [16:40] you can do drag and drop and such on goocanvas with no problem [16:40] and it has some animation support [16:41] by clutter is all about animations, especially in a cool 3d way [16:41] tm_lv asked: following on the previous one, i'd like to insert a shameless plug - contender #3 the hamster graphics library, sprite-based and python pure: http://wiki.github.com/tbaugis/hamster_experiments/ [16:41] shameless plug accepted ;) [16:41] ok [16:41] moving on [16:41] Just a quick word on paths [16:41] A path is essentially a "squiggle" [16:42] It is defined by a string that gets parsed into x,y coords, and then drawn with a bezier curve formula applied [16:42] let's take a look [16:42] the curve stuff is a bit of math that I don't much understand [16:42] but just to get you started, here is a string that describes a scribble [16:42] line_data = "M 4.0 4.0C4.0 4.0 5.0 4.0 5.0 4.0 5.0 4.0 6.0 4.0 6.0 3.0 10.0 1.0 13.0 2.0 9.0 15.0 6.0 36.0 28.0 11.0 28.0 11.0 29.0 11.0 33.0 12.0 33.0 15.0 32.0 19.0 27.0 51.0 27.0 53.0 27.0 54.0 27.0 54.0 27.0 54.0 36.0 49.0 37.0 49.0" [16:42] it just kind of traces some x/y coords [16:43] then I can make a path out of this: [16:43] path = goocanvas.Path(data=line_data, parent=self.__root, line_width=self.__ink_width, stroke_color=self.__ink_color) [16:43] so this will draw the squiggle in the goocanvas [16:43] Now, a path is also useful because you can use it to clip another object [16:44] like you can draw an arbitrary path around an item and use it kind of like a pair of scissorrs [16:44] You don't use a path object for this, just the string [16:44] item.set_property("clip-path",line_data) [16:44] pretty cool! [16:45] any questions about paths and such? [16:45] ok [16:45] let's go on then [16:45] somebody asked about managing mouse movements and such [16:46] In terms of mousing a goocanvas has the normal gtk mouse tracking capabilities [16:46] to track mouse clicks, for example: [16:46] self.__goo_canvas.connect("button_press_event",self.mouse_down) [16:46] so you can also connect to mousedown, mousemove, mouseup, etc... to handle dragging items around [16:47] self.__motion_handler = self.__goo_canvas.connect("motion_notify_event",self.item_moved) [16:47] self.__mouse_up_handler = self.__goo_canvas.connect("button_release_event",self.drag_stop) [16:47] so that's how I handle dragging items in photobomb [16:47] it's a manual process [16:47] questions? [16:48] ok [16:48] let's go on to the last section [16:48] rendering [16:48] a goocanvas can use cairo surfaces to render off snapshots of itself [16:48] So if I want to make a png, I use an image surface [16:48] x, y, w, h = self.__goo_canvas.get_bounds() [16:48] surface = cairo.ImageSurface(cairo.FORMAT_ARGB32, int(w), int(h)) [16:48] context = cairo.Context(surface) [16:48] context.rectangle(0, 0, 1000, 1000) [16:48] context.set_source_rgb(1, 1, 1) [16:48] context.fill() [16:48] self.__goo_canvas.render(context) [16:48] surface.write_to_png(image_path) [16:48] (I sniped this originally from segphaults grabbersnap code) [16:49] There are other cairo surfaces as well, including a PDF surface [16:49] so you can render to a pdf, for example [16:49] okay, that's the last bit of material I prepared [16:49] any questions about anything? [16:50] quappa1 asked: Can I try photobomb on Karmic? Seems that in your PPA it's only for Lucid. [16:50] I suppose [16:50] I think it should work [16:51] just pull from trunk and give it a try [16:51] ems asked: any chance you could add some goocanvas snippets to acire? [16:51] I suppose [16:51] I don't know when I would get to it [16:51] I would be glad to help someone else who wants to give it a try [16:51] luismmontielg asked: is there any code examples for this? simple working examples? [16:51] not too many [16:52] that's why I wanted to do the class [16:52] photobomb and grabber snap both use it a bit [16:52] so lots of samples there, but no snippets yet that I know of [16:52] fagan asked: will photobomb get into the repo any time soon? :) [16:52] uh [16:52] well [16:52] look at the code and let me know what you think [16:52] there are lots of ideas cram in there, and some pretty bad bugs [16:52] :) [16:53] maybe sometime though [16:53] unless someone wants to take over and finish it off [16:53] no more questions and 7 minutes early! [16:53] you folks were a great class, thanks for coming [16:54] quappa1 asked: photobomb requires something called quickly.prompts. so probably no luck on Karmic? :) [16:54] oh goodness [16:54] yes, that is not in karmic [16:54] but if you are dedicated, you could hack it together [16:54] like pull the quidgets project and stick the code in the photobomb library === mohi_away is now known as mohi1 === 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 || Current Session: Writing a Rhythmbox plug-in - Stuart Langridge - Instructor: aquarius || Questions in #ubuntu-classroom-chat [17:00] Hi, everyone, I'm Stuart Langridge [17:01] Today I'm going to talk about making a Rhythmbox plugin. [17:01] but first I should say: cool talk about goocanvas, rickspencer3 :) [17:01] If you're using Lernid, you'll see slides with code examples. If you don't have Lernid, don't worry; all the code for this plugin is available, and you can look through it to see what I'm talking about, or you can load the slide deck yourself from http://www.kryogenix.org/code/RBMicroBlog [17:01] Specifically, I'm going to talk about making a Python plugin. If you're hoping for in-depth C knowledge, you're talking to the wrong dude. [17:01] Feel free to ask questions in #ubuntu-classroom-chat, and I'll answer them at the end; if someone could collect them, that'd be great. [17:01] or, actually, I'll use ClassBot :) [17:02] What with this being Opportunistic Developer Week and all, I'm aiming for something which scratches a little itch. [17:02] The itch I want to scratch is explained by a tweet I saw from @mandel_macaque, which said [17:02] [SLIDE 2] [17:02] ♥ Space Oddity by David Bowie #lastfm: http://bit.ly/15zv4 [17:02] and I thought: hey, that's quite cool, he's tweeting songs that he's playing that he likes. [17:02] I'd like to do that. But I don't use last.fm, I use Rhythmbox to play my music. [17:02] So why not have a "tweet this song" button, so I can hit it when a song that I like comes along? [17:02] A Rhythmbox Python plugin comes in two parts: an .rb-plugin file, which describes your plugin, and a Python module. [17:03] [SLIDE 3] [17:03] Our first stage, then, is to set up the plugin itself. [17:03] Create the Rhythmbox plugins folder, which you might already have: [17:03] mkdir -p ~/.gnome2/rhythmbox/plugins [17:03] Now, create a folder for our plugin, which we'll call RBMicroBlog [17:03] mkdir -p ~/.gnome2/rhythmbox/plugins/RBMicroBlog [17:04] In there create a __init__.py file: [17:04] touch ~/.gnome2/rhythmbox/plugins/RBMicroBlog/__init__.py [17:04] and an .rb-plugin file: [17:04] gedit ~/.gnome2/rhythmbox/plugins/RBMicroBlog/RBMicroBlog.rb-plugin [17:04] Your rb-plugin file has a specific format: [17:04] [SLIDE 4] === edouard is now known as edouardp [17:04] [RB Plugin] [17:04] Loader=python [17:04] Module=RBMicroBlog [17:04] IAge=1 [17:04] Name=Microblogging [17:04] Description=Microblog what you're listening to [17:04] Authors=Stuart Langridge [17:04] Copyright=Copyright © 2010 Stuart Langridge [17:05] Website=http://www.kryogenix.org/code/rhythmbox-microblog [17:05] The important lines in that are the two that tell Rhythmbox "this is a Python plugin", and "the module name for this plugin is RBMicroBlog". [17:05] [SLIDE 5] [17:06] Python, as you will (hopefully) know, treats a folder called X with an __init__.py file inside as a module named X. [17:06] So, we have our RBMicroBlog folder, with __init__.py inside, which is therefore a Python module [17:06] and also in that folder a .rb-plugin file which says "this plugin is provided by the RBMicroBlog module". [17:06] Right now, then, you have a plugin which doesn't do anything. Which means it has no bugs, true, but isn't that useful. [17:06] On to editing the Python. Opportunistic development is fun! [17:07] Basically, we want our plugin to do this: [17:07] 1. be a plugin that can be enabled and disabled [17:07] 2. put a "tweet this" button on the toolbar, with the Gwibber icon in it, and a tooltip of "microblog this song" [17:07] 3. when the button is pressed, work out which song is currently playing... [17:07] 4. and use the Gwibber API to microblog a message saying "Listening to: One Vision by Queen" [17:07] So, start with the basics. [17:07] [SLIDE 6] [17:08] A Rhythmbox plugin is built as a subclass of rb.Plugin, named the same as the plugin module. [17:08] So, a basic plugin would look like: [17:08] import rb [17:08] class RBMicroBlog(rb.Plugin): [17:08] def activate(self, shell): [17:08] print "Activate!" [17:08] def deactivate(self, shell): [17:08] print "Deactivate!" [17:08] Your plugin's "activate" function is called when the plugin is loaded, so it can do setup, and "deactivate" is called when the plugin is unloaded. [17:08] So, start Rhythmbox -- your plugin hasn't been enabled yet, so in Edit > Plugins, find "Microblogging", and tick it to turn it on. [17:09] [SLIDE 7] [17:09] You might be thinking: where does the output from my print statement go? [17:09] Rhythmbox hides output from plugins unless you want to see it. So, quit Rhythmbox, and restart it as "rhythmbox -D RBMicroBlog" [17:10] Now, when you tick your Microblogging plugin on and off in Edit > Plugins, you should see output in the terminal: [17:10] (15:34:36) [0x8756028] [RBMicroBlog.activate] RBMicroBlog/__init__.py:9: Activate! [17:10] (15:34:38) [0x8756028] [RBMicroBlog.deactivate] RBMicroBlog/__init__.py:13: Deactivate! [17:10] Now, you've got an .rb-plugin file and a Python module, and it's loaded. That's the basics of every Python plugin. The only hard remaining bit is to, y'know, actually write the code that does what you want. [17:11] On, then, to stage 2: put a "tweet this" button on the toolbar. [17:11] This is about adding some UI, and is documented at http://live.gnome.org/RhythmboxPlugins/WritingGuide#Adding_UI [17:11] There are also more examples at http://live.gnome.org/Rhythmbox%20Plugins/Python%20Plugin%20Examples which is a very useful page. [17:12] If you come across more things that you want to do in Rhythmbox, please add them to that page! [17:12] (Also, adding those Rhythmbox plugin "snippets" to the python-snippets project in Launchpad would be pretty cool.) [17:12] Adding UI requires two stages: first, you define where you want to add the UI with some XML [17:12] [SLIDE 8] [17:12] and then you actually hook up a gtk.ActionGroup to the UI, as defined by the XML [17:12] [SLIDE 9] [17:13] To be honest, you can just borrow that bit from another plugin. Understanding gtk.Actions and gtk.ActionGroups is fine for those that want to, but if you just want to add a toolbar button and a menu item, steal the code from somewhere else (like this plugin). [17:13] Now, you'll have a button on the toolbar, and a menu item in the Tools menu. The button has no icon, though. [17:14] A bit more cookbook programming, now: how to load an icon and add it. The icon we want is /usr/share/pixmaps/gwibber.svg [17:14] So, some code to load that icon and make it available for your button [17:14] [SLIDE 10] [17:15] Again, don't worry too much about understanding this: the way Gtk deals with icons is pretty complicated. Borrow it for your own projects. [17:15] Now, you have a button on the toolbar and a menu item, and we've connected them up to call a function self.microblog. [17:15] Stage 3 is to implement that. [17:15] Handler functions, like this one, will be called with two parameters, "event" and "shell". [17:16] We want our microblog plugin to find out what's currently playing. [17:16] There are three ways you might approach the problem of "what do I do to find out what's playing?" [17:17] You could know already (if you're Jonoathan Matthew, the genius Rhythmbox maintainer) [17:17] (er, Jonathan) [17:17] (er, Jonathan) [17:17] You could look it up in the documentation (there isn't all that much; the pages linked above cover some things, but not lots) [17:17] Or you can do what I do, which is poke around in the Python objects. [17:17]