=== MickE is now known as Guest71373 [03:35] hmm [03:45] hi [03:45] hi [03:46] hi [03:46] hi [03:46] hi [03:50] There is no class now. [03:50] !classroom [03:50] The Ubuntu Classroom is a project which aims to tutor users about Ubuntu, Kubuntu and Xubuntu through biweekly sessions in #ubuntu-classroom - For more information visit https://wiki.ubuntu.com/Classroom [11:17] Ciao [11:42] hello [12:12] when does the class start? [13:18] hii === zyga is now known as zyga-food [13:22] hello === zyga-food is now known as zyga [14:47] WHOIS raju1 === raju1 is now known as genupulas === vito_ is now known as Guest7278 === dpm is now known as dpm_ [15:57] is everyone ready for another day of cool app developer sessions? [15:57] day 2 of ubuntu app developer week is about to start! [15:58] yeeeeeaaahh [15:58] :) [15:59] There's a change in schedule. Today's first talk will be by dpm :) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: App Developer Week - Current Session: Making Your App Speak Languages with Launchpad Translations - Instructors: dpm [16:00] ok, let's wait for Classbot to kick off and then get started [16:00] oh, there it is... :) [16:01] Logs for this session will be available at http://irclogs.ubuntu.com/2011/09/06/%23ubuntu-classroom.html following the conclusion of the session. [16:01] allright, let's roll [16:01] Welcome to this session on setting up your project for translations in Launchpad [16:02] My name is David Planella I work as the Ubuntu Translations Coordinator in the Community team at Canonical, [16:02] where I work with our translations community to bring you a localized Operating System. [16:03] I also tend to help with any topics related to translations and Launchpad, and that's what we're going to talk about today :) [16:03] That's a really exciting topic to me, as Launchpad makes it really easy to make your applications translatable and available to everyone in almost any language, and I hope you enjoy it as much as I do. [16:03] Translators are really awesome people! [16:04] I'll leave some time for questions at the end, but feel free to ask them throughout the session [16:05] Anyway, let's get started, shall we? [16:05] Assumptions [16:05] ----------- [16:05] [16:05] I will start with an application ready set up for translations, so I'm not going to go into much detail there. [16:06] (I'll take questions, though, if there are any) [16:06] My intention is to focus in getting you started with exposing your project's translations to everyone for translation. [16:06] We're going to be using these tools: [16:07] bzr [16:07] quickly [16:07] python-distutils-extra [16:07] In particular quickly, which we'll use to start with a nearly ready-made project with translations set up [16:08] (You can install it by running the 'sudo apt-get install quickly' command or you can get it from the Ubuntu Software Centre) [16:08] [16:08] Creating the project and setting it up for translations [16:08] ------------------------------------------------------- [16:08] [16:08] We'll use quickly to create a project called 'fooby', and then we'll set up the last touches needed to configure translations. [16:09] As I said, we won't go into the detail of setting up the application for translation, as quickly will do the heavy lifting for you, === paglia_s is now known as paglia_ss [16:09] but here's a high level overview of what needs to be done to add internationalization support to an app, in case you need to do it outside of quickly: === paglia_ss is now known as paglia [16:10] Generic Steps to Internationalize an Application [16:10] ================================================ [16:10] [16:11] * Integrate gettext (http://www.gnu.org/s/gettext/) into the application. Initialize gettext in your main function [16:11] * Integrate gettext into the build system. There are generally gettext rules in the most common build systems. Use them. [16:12] * Mark translatable messages. Use the _() gettext call to mark all translatable messages in your application [16:12] * Care for your translation community. Not necessarily a step related to adding i18n support, but you'll want an active and healthy translation community around your project. Keep the templates with translatable messages up to date. Announce these updates and give translators time to do their work before a release. Be responsive to feedback. [16:12] anyway, going back to the subject [16:13] So if you've got all those tools installed, you can simply fire up a terminal window (Ctrl + Alt + T) and run the following command: [16:13] quickly create ubuntu-application fooby [16:13] This will create an application named 'fooby' [16:13] and give you some information about it on the first run [16:14] then change to the fooby folder: [16:14] cd fooby [16:14] And finally run: [16:14] python setup.py build_i18n [16:15] That should have finished the last bits to set up translations, so that you can already link up your application with Launchpad Translations [16:16] in particular, what that last command did was to created the po folder in your project, to contain what it's called the translations template and the translations files themselves [16:16] you can see the template there by running: [16:16] ls po [16:16] have a look at it: [16:16] gedit po/fooby.pot [16:17] It's important to get a bit familiar with it, but you don't have to remember the whole format [16:17] you should simply know what it is for now :) [16:17] and that Launchpad needs it to be in your project [16:18] A few bits and pieces on translation templates: [16:18] * Gettext: They follow the gettext format: http://is.gd/fC8p6 [16:19] * Name: They are generally named after your project, with a .pot extension. E.g. fooby.pot [16:19] * One template per app: Generally applications need only one template [16:19] * Layout: They generally live in the po/ folder, along with the translations [16:19] * Content: They are text files which contain: [16:19] * A header with metadata [16:20] * A set of message pairs: msgid are the original strings extracted from the code and exposed to translators, and msgstr are the placeholders for the translations, which are always empty in the templates. [16:20] * Launchpad import: They are imported into Launchpad and exposed for translations for all languages in https://translations.launchpad.net/$YOUR_PROJECT [16:20] * Updates: You update the template whenever you have new strings in your app and you think they are stable for translation (generally shortly before release) [16:21] * Tools: you update templates with gettext based tools: [16:21] * generally intltool -> 'cd po && intltool-update -p' [16:21] * or increasingly python-distutils-extra for python projects -> 'python setup.py build_i18n -p' [16:22] You don't have to remember all of this [16:22] But hopefully these points will give you some insight on translation templates [16:22] At least you should know how that you must update the template from time to time [16:23] and the command to do it [16:23] Repeat it with me - "I _will_ update the translation from time to time, at least once before a release" [16:23] :-) [16:24] You'll see that your project still does not contain any translations, but again, let me give you a quick overview on translations, so you know what we're talking about: [16:24] So here we go, a few words on translations: [16:26] * Template-based: They are created from the template and share the same gettext format [16:26] * Name: They are named after the $CODE.po scheme, where $CODE is an ISO 639-2 code. E.g. ca.po for Catalan, de.po for German. Some have an optional country specifier. E.g. pt_BR.po (Portuguese from Brazil) [16:27] * Layout: they are all in the same directory as the POT template. So: [16:27] * po/fooby.pot [16:27] * po/ca.po [16:27] * po/pt_BR.po [16:27] * ... [16:27] * Creation: Launchpad creates them for you the minute someone translates the first message online [16:27] * Code integration: you can let Launchpad commit them to a branch of your choice or you can export a tarball containing them all (more on that later) [16:28] Anyway, let's continue. Now that you've added the template to your code, you can commit it by running the following commands: [16:28] bzr add po [16:28] bzr commit -m 'Created my first ever awesome .pot template. Go translators, go!' [16:29] And let's publish it in Launchpad (note that you'll have to change the Launchpad URL to your user name instead of 'dpm'): [16:29] bzr push lp:~dpm/fooby/translations [16:29] Nothing particularly hard to understand on the naming scheme above: dpm is my user name, fooby is the project and translations is the bzr branch name in Launchpad [16:29] Ok, so that completed the first step! [16:29] Next: [16:30] ah, forgot to ask, any questions so far? [16:30] Andy80 asked: what about Qt application? They don't use gettext. They have their own method to be translatable (basically it's just a matter of tr("This is a message") ) and I noticed that in Unity-2D we're using a sort of macro. Why don't we improve the launchpad integration even for Qt applications? [16:30] good question [16:31] as Unity 2D is an Ubuntu project, it has to integrate well with Launchpad and the way Ubuntu translators translate, which is again Launchpad Translations [16:32] in short, in the Unity 2D project there is some code that intercepts the Qt tr() calls and converts them to gettext() calls [16:33] so effectively Unity 2D, despite being a Qt project, uses gettext for translations [16:33] I agree that it'd be nice for Launchpad to support the Qt format [16:33] but as you see, you can easily use gettext from Qt-based apps too [16:34] Ok, let's continue [16:34] Setting up code hosting [16:34] ----------------------- [16:34] [16:34] We want our project to be available to everyone to translate, so we'll need to publish it in Launchpad first. [16:34] That's beyond the scope of this session, so we'll continue from the already registered fooby project in Launchpad: [16:34] https://code.launchpad.net/fooby [16:35] In case you are interested, though, registering a new project in Launchpad is as easy as going to https://launchpad.net/projects/+new [16:35] Some of the URLs I'll post to set up your project will not allow you to open some of the pages due to permissions, so if you have your own project in Launchpad, just substitute the 'fooby' part in the URL with your project's Launchpad id [16:36] The first thing we'll have to do in our project is registering a bzr branch, [16:36] so we'll simply go to the Code tab in Launchpad, choose the "Configure code hosting" link [16:36] and then on the "Link to a Bazaar branch already on Launchpad" you can enter the branch we published earlier on (~dpm/fooby/translations) [16:36] A shortcut is to simply go to: [16:36] https://code.launchpad.net/fooby/trunk/+setbranch [16:36] to do this [16:37] So now we have all we need to start setting up translations. [16:37] You see that all components in Launchpad are integrated, so you set up a branch to be linked to translations [16:37] Just as a recap, you can see and explore the resulting code from here: [16:37] https://code.launchpad.net/fooby [16:37] Feel free to browse it (http://bazaar.launchpad.net/~dpm/fooby/translations/files) [16:37] or download it (bzr branch lp:fooby) and play with it [16:38] Ok, so code hosting setup: (./) Finished! [16:38] [16:38] Setting up translations in Launchpad [16:38] ------------------------------------ [16:38] [16:38] Now we come to the most interesting part [16:38] Let's divide this in 4 steps [16:38] 1. Telling Launchpad where translations are hosted [16:38] The first step it to tell Launchpad that we want to host translations there. [16:39] On your Launchpad's project, just click on the Translations tab, or go to this URL: [16:39] (remember to change 'fooby' to your project's name!) [16:39] https://translations.launchpad.net/fooby/+configure-translations [16:39] Then choose the "Launchpad" option to tell Launchpad translations will be done there, and click on "Change" [16:39] That was an easy one, wasn't it? [16:39] 2. Configuring permissions [16:39] Now we are going to tell Launchpad how we want our translations permissions to be (i.e. who and how can translate it), [16:40] and which branch translators should focus on. [16:40] Simply go to the Translations tab again and click on the "Change permissions link" [16:40] Or here's the direct link: https://translations.launchpad.net/fooby/+settings :) [16:40] I recommend the following setup: [16:40] Translations group: Launchpad Translators [16:40] Translations permissions policy: Structured [16:40] Translation focus: trunk (or choose your branch here) [16:40] Assigning the translations to a translation group will make sure a team for each language will review translations before they are submitted, ensuring the quality of translations [16:41] A translations group is simply a set of teams, one per language, that takes care of translations in that language [16:41] They can be specific to a project or generic. [16:41] I recommend the Launchpad Translators group because it contains a set of already established and experienced teams: [16:41] https://translations.launchpad.net/+groups/launchpad-translators [16:41] as per the Structured policy [16:42] it gives you a good balance between openness and quality control: [16:42] only the team members of an established team will be able to translate your project [16:42] And for languages without a team it will allow everyone to translate, facilitating the barrier of entry to translators at the expense of QA [16:42] The other ends of the permissions spectrum are Open or Restricted [16:42] You can learn more about these here: [16:42] https://help.launchpad.net/Translations/YourProject/PermissionPolicies [16:43] It's the project maintainer's call, but I personally discourage them to use Open [16:43] Ok, we're nearly there, next step: [16:43] 3. Setting up what needs to be translated [16:43] You need to also tell Launchpad what needs to be translated. That's again quite easy. On the Translations tab again, choose the trunk series and specify your branch there [16:43] Direct link: https://launchpad.net/fooby/trunk/+linkbranch [16:43] Another easy one done :) [16:44] 4. Configuring imports and exports [16:44] That's for me the most interesting bit [16:44] The settings on this section basically enable Launchpad to do the work of managing translations for you [16:44] You can tell Launchpad to import your translation templates automatically whenever you do a commit in your branch [16:44] So you don't have to upload them manually [16:44] If you are migrating a project with existing translations, you can tell it to import them too [16:44] And finally, you can let Launchpad commit translations automatically to a branch of your choice [16:45] I find that just awesome [16:45] So for the imports, on the Launchpad page, on the "Import translations from branch" section: [16:45] I recommend choosing "Import template files" and then "Save settings" [16:45] For exports: look at the "Export translations to branch" section and then click on the "Choose exports branch" link [16:45] So that was it! [16:46] 4 easy steps that should not take you more than a few minutes to set up, and your app is ready for the world to translate! [16:46] Just a few final words: [16:46] Play with translations [16:46] ---------------------- [16:46] As a developer, it might be interesting to see how translators do their work. [16:46] Exceptionally for this project (remember how I advised not to use Open permissions, tough :) I've set the translations permissions on the fooby project to Open [16:47] So you can submit translations online [16:47] and get a feel for the work that translators do [16:47] As a developer, it will give you an understanding on how they work. It is always interesting to get to know other workflows [16:47] and it's always good to have an insight on all areas of contribution related to your project [16:47] You can start translating fooby here: [16:47] https://translations.launchpad.net/fooby [16:48] So that was it really, it wasn't that hard, was it? [16:48] Let me give you a quick summary of what we've talked about and then take questions [16:48] Summary [16:48] ------- [16:49] Most of the steps described here today you'll only need to do once, unless you need to change the settings. They were: [16:49] 1. Setting up code hosting (in case you hadn't already) [16:49] 2. Setting up translations in Launchpad [16:49] 2.1. Telling Launchpad that it's hosting your translations (https://translations.launchpad.net/fooby/+configure-translations) [16:49] 2.2. Configuring permissions: recommended -> Structured, Launchpad Translators (https://translations.launchpad.net/fooby/+settings) [16:49] 2.3. Setting up the translations branch (https://launchpad.net/fooby/trunk/+linkbranch) [16:49] 2.4. Configuring imports and exports (https://translations.launchpad.net/fooby/trunk/+translations-settings) [16:49] So really, once your project is set up for translation, the only things you'll have to remember are: [16:49] to update the template before a release, [16:50] announce to translators that they can start their work, [16:50] and merge the translations to your main branch. [16:50] If you are using the same branch for translation imports and exports, you won't even have to do that! [16:50] There are 10 minutes remaining in the current session. [16:50] ok, so we've got 10 minutes left - if you've got any questions, bring them on! :) [16:50] jsjgruber_natty_ asked: How can an application bring up a translation for a particular local "on-demand"? Now get the spanish version, now french version? [16:51] I'm guessing you're asking this for test purposes [16:52] in normal usage, the application will automatically load the translation for the right locale defined in the system [16:52] so if my desktop's language is set to Catalan, the app, assuming gettext has been correctly initialised in the code, will automatically load the Catalan translation [16:53] but if you want an app to load another language, you can call the app on the command line specifying the language code, e.g. [16:53] $ LANGUAGE=de myapp [16:54] Running that command would load the German translation of myapp ('de' is the ISO code for German) [16:54] other questions? [16:55] matteonardi asked: how does translations get into users machines? Is there 1 (and only 1) package for each language? What if my application comes from a ppa? [16:55] There are 5 minutes remaining in the current session. [16:56] translations get distributed and installed along with the application. On the technical level, translations are .mo files, one for each available translation in your app [16:56] It does not matter if your application comes from a PPA [16:57] the PPA will contain all the necessary .mo files, which means the translations will be installed on the system of everyone who installs the PPA [16:57] ok, 3 minutes left, I can probably take another one if there is any [16:58] ok, if there aren't any, the only thing remaining is to thank everyone for listening in and asking interesting questions, and I'll see you next time! [17:00] Next up is Kaleo, the man behind Unity 2D, who'll tell you all about how this awesome piece of software was put together [17:00] Kaleo, as soon as the Classbot kicks in with the intro, the floor is yours! === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: App Developer Week - Current Session: The Making of Unity 2D - Instructors: Kaleo [17:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/09/06/%23ubuntu-classroom.html following the conclusion of the session. [17:00] dpm: thank you David [17:01] dpm: thank you everyone for joining this session [17:01] dpm: My name is Florian Boucault [17:01] dpm: and I am one of the software developers behind Unity 2D [17:02] dpm: I would like that session to be as interactive as you guys would like [17:02] dpm: so don't hesistate to ask any question at any time [17:02] (and I'll drop the dpm :)) [17:02] Unity 2D is essentially an implementation of the Unity user interface using Qt and QML [17:03] it reuses the same backend technologies used in Unity 3D [17:03] and intends to provide a UI that matches Unity 3D [17:03] the main goal of Unity 2D is to run on platforms that do not provide accelerated OpenGL [17:04] it also simplifies the development of the shell UI quite a bit === raju1 is now known as genupulas [17:04] it is made up of 4 UI components [17:04] 3 of which you can see on the following diagram: [17:04] http://people.canonical.com/~kaleo/classroom/unity_2d_wireframe.png [17:05] - the app launcher on the left [17:05] - the top panel with the application menu and the indicators [17:05] - the dash that is a UI to essentially search for content [17:05] - and the one not in the diagram, the workspace switcher [17:06] the workspace switcher allows user to switch between workspace, applications and windows [17:06] right now these 4 components are separate programs that are displayed on top of every other windows [17:07] they are written with QML [17:07] and use APIs defined in C++/QObjects in a common library called libunity-2d-private [17:08] a lot of these APIs just wrap other libraries, such as wnck, bamf, dee, etc. [17:08] and made these functionalities easily accessible to QML uis [17:08] I can go into the details of what each library provides us with [17:09] if anybody has questions about that [17:09] these 4 components are fairly window manager agnostic [17:09] today Unity 2D ships with Metacity [17:09] but it should work equally well with others: compiz, kwin, xfwm.. [17:11] historically Unity 2D's development started last year towards the end of the summer [17:11] and grew into being the default interface for ARM based Ubuntu isos [17:11] development happens on Launchpad [17:12] getting started for developers is straightforward [17:12] and documented https://wiki.ubuntu.com/Unity2D [17:12] at* [17:12] each component (dash, launcher, etc.) has a separate directory in the source tree [17:13] and can be hacked on independently [17:13] the policy for trunk is that it has to be releasable at any point; === sergio91pt_ is now known as sergio91pt [17:13] that means, no regression when introducing no features and only landing features that are ready [17:14] automated builds are produced every day [17:14] and released into a PPA: https://launchpad.net/~unity-2d-team/+archive/unity-2d-daily [17:16] (connection issues here) [17:17] for developers who want to play around with it (or fix bugs) [17:17] the required knowledge to get on the project is: [17:17] - QML and Javascript for the UI pieces [17:18] - C++ if you want to add features that require new data that our backend does not provide [17:18] one thing to remember is that we try to keep the list of features between Unity 2D and 3D to be synchronised [17:19] so if you have an idea about the UI, don't forget that it needs to be done in both [17:20] I think that's enough for the general presentation. [17:20] Do you guys have any specific question? [17:20] let me take Andy80's :) [17:21] Andy80: we have a wrapper for indicators as well [17:21] Andy80: it's a C++/Qt API that calls the API of the unity-panel-service [17:21] Andy80: and essentially gives us a list of indicators to render [17:22] Andy80 asked: do we have a wrapper for indicators too or are we just calling the original methods? [17:22] (thanks ClassBot) [17:24] anybody else? :) [17:24] dpm asked: which libraries should an app developer wanting to interface his/her app with Unity 2D should know about? [17:25] so, dpm, the integration into Unity 2D is the same as the integration into Unity 3D [17:25] once you have done it for one you have done it for both [17:25] the libraries concretely are libunity [17:26] you can integrate with the launcher with that [17:26] you can also create a lens to add content to the dash (for example the Gwibber lens) [17:26] finally you can also integrate with the top panel's indicators [17:26] the way Banshee is integrated for example [17:27] in the sound menu [17:27] does that answer the question? [17:28] mohammedalieng asked: are there any plans to provide desktop gadgets, specially it is the default interface for ARM devices ? [17:28] mohammedalieng: there are no concrete plans so far for desktop gadgets [17:29] mohammedalieng: right now if one needs them I would personally recommend to use KDE's "gadgets" [17:29] that is the Plasma ones [17:30] it fits well technology wise with Unity 2D as it uses QML as well [17:30] Andy80 asked: if I correctly understand, Unity-2D must have the same features of Unity but without the 3D effects that would not be possible on PC without a 3D graphic card. But we know that QML is used even on hardware with 3D acceleration to have very nice effects too (look for example Harmattan running on Nokia N9). Would not be better to develop just Unity-2D + Unity-effects insted of duplicating the work having to develo [17:31] Andy80: I essentially agree with that [17:31] to add on that on a technical level [17:31] the visual possibilities of QML today are pretty advanced [17:31] especially on the effects side [17:31] the only limitation today is on the 3D side of things [17:32] only rudimentary 3D is available [17:32] which is a gap that can be closed with Qt Quick 3D [17:32] I have experiments of integrating 3D objects and scenes into the launcher and the dash [17:32] it works fairly well [17:33] on the performance side, we are already pretty good with the rendering engine we enforce the use of, raster [17:33] Unity 2D also works with the OpenGL2 engine [17:33] and we are quite looking forward to migrating to QML2 [17:33] that will provide very nice performance improvements [17:34] by adding a better rendering model when it comes to OpenGL and modern GPUs [17:35] the important thing to remember here is that: [17:35] 1) we are not limited by QML UI-wise (we can use Qt Quick 3D or even write our own OpenGL based QML ui elements) [17:36] 2) the QML code we write today for QML1 will work in the future without changes with QML2 and QML3D [17:36] Andy80: does that answer the question? [17:37] Andy80 asks: "what are we waiting for?" [17:37] we are waiting for you :) [17:38] there is quite a lot of invisible work happening in Unity 2D [17:38] that takes quite a bit of our attention [17:38] (we are just 3 developers today) [17:38] for example, supporting multi monitor properly [17:38] right-to-left languages [17:39] languages that need special input methods [17:39] fixing important bugs :) [17:40] so, developers are of course always available [17:40] on freenode #ayatana [17:40] and for those lucky ones going to UDS [17:40] they will be happy to spend time with those interested [17:41] we will have a session as well planning for Ubuntu P [17:41] dpm asked: what are the issues with right-to-left languages? Is it a matter of QML not supporting them well? [17:41] dpm: the issue was indeed that QML was not supporting them well [17:41] dpm: so, we had a first shot at it working around that limitation [17:42] but now Qt 4.7.4 is out with Qt Quick 1.1 that supports natively RTL languages [17:42] so we are mostly in the clear now [17:42] in Oneiric we will support them decently [17:42] another example of invisible work is accessibility support [17:43] critical for us as Unity 2D is becoming the default desktop on Ubuntu Oneiric where Unity 3D cannot run [17:43] I like to see Unity 2D as the universal version: [17:43] - works everywhere [17:44] - works for everybody [17:44] (all machines, all cultures, all needs) [17:44] that's being a bit idealistic of course :) === yofel_ is now known as yofel [17:44] thanks for the question dpm === bulldog98_ is now known as bulldog98 [17:47] rsajdok asked: Is there the list of new feature which will be added to Unity-2d in future? [17:48] rsajdok: so, the first set of features we want to add are the ones that are in Unity 3D but not in 2D yet because we have not had time to do them [17:48] rsajdok: https://bugs.launchpad.net/unity-2d/+bugs?field.tag=delta-with-3d [17:49] rsajdok: and of course the wish list items https://bugs.launchpad.net/unity-2d/+bugs?search=Search&field.importance=Wishlist&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed [17:49] for those who want to start easy to learn how it works inside and implement something not too difficult [17:49] we use the bitesize tag [17:50] https://bugs.launchpad.net/unity-2d/+bugs?field.tag=bitesize [17:50] There are 10 minutes remaining in the current session. [17:51] thanks ClassBot [17:53] alright folks, just a few minutes for more questions [17:54] Andy80 asked: are you aware if any other distro is interested in Unity/Unity-2d? This could bring more contributions to the project [17:55] Andy80: I know somebody contacted us to package it up in OpenSuse [17:55] but that's the extent of my knowledge [17:55] rsajdok asked: Are there bugs in pure javascript? [17:55] There are 5 minutes remaining in the current session. [17:56] rsajdok: yes, it happens often that the issues can be fixed with a bit of QML + javascript [17:58] rsajdok asked: How find these bugs? [17:58] rsajdok: unfortunately we don't have such a list readily available [17:59] rsajdok: you will have to try I am afraid [17:59] I think it's time for me to leave the stage to Curtis Hovey [18:00] Thanks a lot for a great session Kaleo! [18:00] :) [18:00] thanks dpm, thanks for the questions everybody === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: App Developer Week - Current Session: Making App Development Easy: Gedit Developer Plugins - Instructors: sinzui [18:00] Next up Launchpad legend Curtis Hovey will talk about his developer plugins for Gedit [18:00] Logs for this session will be available at http://irclogs.ubuntu.com/2011/09/06/%23ubuntu-classroom.html following the conclusion of the session. [18:06] What is gedit? [18:06] gedit is a simple text editor [18:06] with support for syntax highlighting [18:06] that can be extended for new uses [18:07] See https://live.gnome.org/Gedit to see a full list of features [18:07] gedit ships with plugins to help power-users [18:07] The gedit-plugins package for provides tools to help developers [18:07] Many developers provide extra plugins for specific development [18:08] See http://live.gnome.org/Gedit/Plugins for a list of plugins supported by gedit 3.x [18:09] Developers will want to install a few packages from Ubuntu universe to get the set of plugins that I recommend and use. [18:09] Using Software Center [18:10]