[00:04] <mhall119> aquarius: pong
[00:06] <aquarius> mhall119: heya. I know I've asked this before, but I'm not sure of the current state of play: can I make a quickly QML + PySide app?
[00:44] <mhall119> aquarius: maybe with https://launchpad.net/quickly-community-templates installed
[00:44] <mhall119> I'm not sure what language/qtlib they use though
[00:46] <mhall119> ah, looks like ubuntu-application-qt uses PySide
[00:47] <mhall119> and ubuntu-application-qtquick does it with QML
[00:47] <aquarius> as does qtquick-application, which is what I want
[00:47] <mhall119> aquarius: I don't know what the status of those templates is though
[00:47] <mhall119> could be kind of rough
[00:47] <aquarius> except... it hasn't been edited since June
[00:47] <aquarius> and I know you guys are busy changing stuff :)
[00:47] <mhall119> aquarius: stable quickly hasn't changed much since June
[00:47] <mhall119> lp:quickly/reboot is where all the action is
[00:48] <mhall119> in fact, it's what I was working on when you pinged me
[00:48] <aquarius> yeah, that's what I'm worried about. I don't really want rough...I want to make an app, not hack on quickly this evening ;)
[00:48] <aquarius> I shall give it a try, and thanks!
[00:49] <mhall119> best of luck
[00:49]  * aquarius installs qtquick template :)
[00:53] <aquarius> mhall119: one other thing... can I stop quickly making my project a bzr repo?
[00:54] <aquarius> it's already in a bzr repo
[00:57] <aquarius> mhall119: unping. I'll just do a separate thing :)
[01:01] <mhall119> aquarius: not easily, no
[01:02] <mhall119> if you're in a directory that you ran "bzr init-repo" on, then it should re-use that repo, and just create a new branch
[01:05] <aquarius> mhall119: cool, thanks
[01:05] <mhall119> man, I've written so much Quickly code, and I've still only recreated 20% of the existing functionality
[01:31] <aquarius> mhall119: hrm, quicly license blows up because it can't find an xml thing. Is this likely to be a problem with the qtquick template, or a general quickly problem??
[01:45] <mhall119> aquarius: probably the qtquick one
[01:47] <aquarius> mhall119: traceback is at http://paste.ubuntu.com/1393380/ if that means anythig to you
[04:55] <HERPDERPingt0n> hello?
[09:33] <aquarius> dpm, ping
[10:14] <dpm> aquarius, pong
[10:15] <aquarius> dpm, am I correct to think that you wrote the quickly qtquick template?
[10:17] <dpm> aquarius, I didn't write it, I just set up the project in Launchpad for all community templates and was involved in helping angeloc (the author) to get it packaged and in some discussions about how to handle translations -> http://bazaar.launchpad.net/~quickly-templates-hackers/quickly-community-templates/trunk/revision/10
[10:17] <aquarius> dpm, oh. :)
[10:17] <aquarius> dpm, so, I need to talk to angeloc, then
[10:18] <aquarius> or possibly someone who's quickly-knowledgeable, because "quickly license" doesn't work in that template. I *think* it's because the license stuff assumes that the UI files it's editing are glade files, which they aren't in a QML template :)
[10:18] <dpm> yeah, he hasn't been around much lately, but IIRC, he sent an e-mail a while ago on the quickly list, saying he wanted to continue with the development
[10:19] <dpm> afaik, not all commands work on the template yet, but can't tell off the top of my head which ones do work
[10:20] <aquarius> dpm, the problem is that a bunch of stuff depends on quickly license working, I think... and I don't know how to fix that, because it's calling functions in the base ubuntu-application template, so I don't think I can override them
[10:20] <dpm> aquarius, here's Angelo's last update. You might want to reply to the list, perhaps it will resurrect the thread: https://lists.launchpad.net/quickly-talk/msg00170.html
[10:20] <aquarius> dpm, aha, cool
[10:21] <aquarius> if this ends up in a future where I become maintainer of the qml template, dpm, I am going to blame you
[10:21] <dpm> aquarius, oh, so you already figured out my master plan? :P
[10:21] <aquarius> and then I'm going to put special effort into making you pay. :)
[10:22] <aquarius> I shall reply to the message ;-)
[10:22] <dpm> :)
[10:23] <aquarius> meanwhile, who knows enough about quickly to help me override stuff? I suppose that's mterry or didrocks or mhall119?
[10:24] <dpm> yeah, I think so. didrocks probably the best one at this time of the day, he should be on #quickly or the usual #ubuntu developer channels
[10:25] <dpm> aquarius, and something more: mhall119 is working (on a best-effort basis) on the Quickly Reboot project to make it easy to integrate Quickly into developer tools, which will change how templates are written - http://mhall119.com/2012/11/quickly-rebooted/
[10:25] <dpm> ccccccbfuiihrevtlurjeengdutihcidvhkrtnllljlh
[10:25] <aquarius> dpm, yeah. I am pretending that the reboot doesn't exist.
[10:25] <aquarius> since otherwise I can't do anything at all until it's done
[10:26] <dpm> yeah, sounds like a good approach if you just want to fix the template so that it works for now
[10:32] <aquarius> dpm, yeah. I don't think the problem is actually in the qml template, though... but I don't know enough about quickly to properly decide. Have mailed the list, anyway
[10:33] <dpm> cool
[10:38] <dpm> aquarius, now that I've got you here, a totally unrelated question: do you happen to know how the u1 music app for Android displays the cover art for songs/albums? I've got images for most of my albums in their folders, but sometimes they don't seem to get picked up, so perhaps it just reads the images embedded in the songs? I'm not expecting you to know each and every detail, so I'm asking you in case you know off the top of your head, or if you ca
[10:38] <dpm> n point me to the next best person to ask
[10:38] <aquarius> dpm, it reads images embedded in the songs. It does not pick up cover images in the same folder as the songs
[10:39] <dpm> aquarius, ah, thanks, then that'll be some work for me to do during the weekend ;)
[10:39] <aquarius> :)
[10:40] <aquarius> once you've written a shell script which bakes cover.jpg into every mp3 in that folder, be sre and release it ;)
[10:40] <dpm> :)
[12:02] <dpm> aquarius,
 hey didrocks, quick question on quicky regarding aquarius question on https://lists.launchpad.net/quickly-talk/msg00171.html - would an override (e.g. creating an empty 'license' command on the qtquick template) fix Stuart's upgrade problem?
 dpm: a workaround is to create an empty license command yeah, but a better fix is to have the license command fixed in the ubuntu-application template :)
[12:02] <dpm> let me reply on the mailing list, though
[12:06] <aquarius> dpm, ooh! you are a helpful person, yes you are :)
[12:34] <dpm> glad if it helps you :) I've now replied on the list with more details
[14:14] <mhall119> aquarius: I believe you're right, the license command is expecting glade files, which probably means the qtquick template didn't override/replace that with something custom
[14:19] <aquarius> mhall119, right. I don't really understand how quickly fits together in order to try and fix it...
[14:59] <dpm> aquarius, my reply on the mailing list should give you some guidance on how to fix it. The quickest thing might be to remove 'license' from the commandsconfig file and drop an empty license.py file on the root of the qtconfig template folder
[15:00] <aquarius> dpm, you are giving me too much credit for intelligence. How do I override a command with my own? I assume you're not suggesting that I manually edit the stuff in /usr/share/quickly/templates ?
[15:02] <dpm> aquarius, yeah, sorry, I should have been more detailed. For a quick test, I think you can:
[15:03] <dpm> 1. Remove 'license' from the /usr/share/quickly/templates/ubuntu-application-qtquick/commandsconfig, under the [ubuntu-application] section
[15:04] <dpm> 2. Drop an empty 'license.py' file under /usr/share/quickly/templates/ubuntu-application-qtquick
[15:05] <dpm> If that does not work, you might have to do these same two steps under /usr/share/quickly/templates/ubuntu-application-qt (as the qtquick template inherits commands from the qt template)
[15:06] <dpm> aquarius, and if that still does not work, then we'll probably need didrocks to lend a hand
[15:06] <aquarius> dpm, cool, I'll give that a try. (I'm a bit sad that I have to edit the system-level files, though. I hate doing that. / belongs to apt, not me. /home/aquarius belongs to me. :))
[15:08] <dpm> yeah, but the nice thing is that if that proves to work, then we'll commit a fix in the quickly-community-templates, it will get automatically packaged in the daily PPA, you'll be able to install it, and all /home will belong back to aquarius ;)
[15:09]  * aquarius laughs
[15:09] <dpm> aquarius, actually, I think you can install templates under any location, so you can copy them to your /home folder for the purposes of testing. Let me see if I can find out how to do that
[16:13] <aquarius> dpm, that sounds like a useful thing if it's possible...
[16:53] <Odd-rationale> Hello! I have a packaging question. In a bzr builddeb recipe, can I specify a local branch?
[17:06] <commandoline> Odd-rationale: local as in on your computer? Then the answer is no, launchpad is a web service.
[17:07] <Odd-rationale> commandoline: OK. Thanks.
[17:10] <Odd-rationale> OK. So I have a separate debian packaging branch. Is there a way to specify a different debian directory using debuild?
[17:11] <commandoline> sorry, I don't know. You can always try to just replace the directory in there?
[17:13] <Odd-rationale> Well the source branch does not have a debian/ directory. It is in a separate branch. Also, I don't think bzr supports nested branches.
[17:37] <commandoline> Odd-rationale: well, with the lp recipes, you can include a directory from another branch. On the local file system, you can just copy the debian dir into the target branch before building I'd say?
[17:39] <Odd-rationale> commandoline: Thought about that. Was hoping that there might be a more elegant solution. But thanks!
[17:46] <commandoline> well, there might well be, but I don't know it ;)
[17:46] <mspencer> Is this a good place to ask a question about how to set up a Quickly project?
[17:49] <commandoline> mspencer: It is, although there's #quickly too if nobody knows an answer here.
[17:50] <mspencer> How can I create a Quickly project named 'contributor-console' but have the source directory be 'contributorconsole', not 'contributor_console'?
[18:01] <Odd-rationale> Is it considered best practices to put the debian directory in a separate branch or as part of the source package?
[18:04] <JanC> Odd-rationale: a separate branch makes it possible to have different packaging per OS release
[18:55] <aquarius> mspencer, I don't think quickly knows the name of the folder it's in? So... you could just quickly create ubuntu-application contributor_console and then rename the folder?
[18:56] <mspencer> aquarius: Would the name of the project be used anywhere else?
[18:56] <aquarius> mspencer, good question, and I'm not sure. dpm, mhall119, ^^
[18:58] <mhall119> aquarius: mspencer: I don't belive that quickly cares what it's own folder is called
[18:58] <mhall119> bzr might though, I'm not sure
[18:58] <mspencer> Would it be possible to do 'quickly create contributor-console' and then run sed on all the files to replace contributor_console with contributorconsole?
[18:59] <mhall119> mspencer: that will probably break things unexpected ways
[18:59] <aquarius> mspencer, it might, but I suspect you'd screw up paths in that case... I assume quickly will create a contributor_console_lib folder and so on. I wouldn't fiddle with that too much if I were you,
[19:00] <mspencer> I didn't think it was a good idea anyway.
[19:01] <mspencer> mhall119: Even if it didn't, wouldn't the project name be used in other files, such as the executable?
[19:01] <mspencer> mhall119: I'm refering to the project name, not running sed.
[19:02] <mhall119> mspencer: a bunch of files refer to others by their filename or python module name
[19:03] <mspencer> So is it possible to tell quickly not to put a '_' in the source folder name when I create the project?
[19:05] <mspencer> This isn't a big deal, I just wanted the directory structure to match that of software-center, etc. where the project is called software-center but the source folder is called softwarecenter.
[19:08] <mspencer> I've also got several questions related to using a Launchpad project, is this a good place to ask?
[19:24] <aquarius> mhall119, if I've got a quickly template with a bug in it, what's the best way of fixing that bug and testing? Can I put a local copy of the template somewhere and have that override the one in /usr/share/quickly/templates?
[20:13] <mhall119> aquarius: quickly has a pretty thorough test suite, if it's one of the built-in templates
[20:14] <mhall119> aquarius: I don't remember if you can run a template outside of /usr/share/quickly.
[20:17] <mhall119> aquarius: ah ha!  It will search through an env variable called QUICKLY_TEMPLATES, containing colon-separated paths
[20:17] <mhall119> it will also check in ~/quickly-templates
[20:50] <aquarius> mhall119, superb!
[20:50] <aquarius> mhall119, thank you. I shall give that a try
[20:50] <aquarius> mhall119, it's one of the community templates, which are clearly not as well tested...
[20:51] <aquarius> although it would be nice if "quickly license" in the base template printed a warning if it couldn't find the author in the .ui files rather than exploded. :)
[20:54] <mhall119> aquarius: ubuntu-application really wasn't a suitable base template for qtquick
[20:55] <mhall119> in fact, none of them were really structured in a way that made them usable for derivative templates
[20:55] <mhall119> that's part of what I'm working on fixing in the reboot
[20:56] <aquarius> mhall119, so qtquick should have been a completely independent template?
[20:56] <aquarius> it seems to work OK so far, apart from the license thing, although I've only tried "quickly package"
[20:57] <mhall119> aquarius: ideally yeah, since so much of ubuntu-application assumes Python+Gtk
[20:58] <mhall119> I'm going to try and make some generic base templates that are re-usable for the reboot
[21:01] <aquarius> mhall119, yeah. I was hoping to make an app now, which is why I'm using the community template...