[01:11] anyone has those problems? [01:11] http://www.uluga.ubuntuforums.org/showthread.php?t=1137700&page=3 [01:11] im stuck i cant work with my mouse. [01:11] any info? [20:46] didrocks: hey [20:51] rickspencer3: hi ;) [20:52] didrocks: I'm at the airport in Atlanta, working on quickly spec [20:52] i'm wondering if it makes more sense to make the templates easier [20:52] so you would go: [20:52] $quickly new-ubuntu-project coolio [20:53] and then you could go quickly new-window stuff [20:53] thoughts? [20:54] hum, that make sense. So, all templates will work like this? (ubuntu-project -> "quickly new-ubuntu-project name" to create it, foo-project -> "quickly new-project name") [20:55] right [20:55] so to make a new command, create a folder with the command you want, and then put a script in there called run.py, or something [20:55] I'm just wondering how the user can understand that if he wants to take another command from another project, he can do quickly -t ubuntu-project command-name [20:56] well, if we do what I suggest, then any command could work in any project [20:56] so I would rename "new.py" in the ubuntu-project template to "run.py" [20:57] and quickly.py would always look for "run.py" [20:57] (not sure I'm making sense, maybe I should just change the code) [20:57] rickspencer3: I don't really get it actually :) [20:58] (sorry, I'm tired) [20:58] no problem, I understand ^^ [20:58] I was just thinking about implementing a bash completion process [20:58] so to make a new command called foo ... [20:59] this one can do some introspection stuff to look at available commands [20:59] create a directory called foo [20:59] then inside that directory, create a file called run.py [20:59] ok, and so, you remove the template idea [20:59] so then $quckly foo [20:59] that would run run.py in the foo directory [20:59] sort of remove the template idea, more like remove the distinction between commands and templates [21:00] (let me a second, I'm thinking abouy it) [21:00] so like: $quickly ppa could easily be made that way, and new commands for existing templates would be easy to create [21:00] about* [21:01] commands will be longer… Imagine someone wants to add some features to the "quickly release" command: this can't be do in this way… or creating a new folder + command with another name [21:02] hmmm [21:03] The template made some kind of "getting things that works well together" [21:03] hmmm [21:03] not displaying 30 commands, some incompatibles with a project created for another template [21:03] so for quickly release, that runs a script, how would you add that? [21:04] rickspencer3: there is already one kind of release command in the bzr branch [21:04] (your point about project incompatibilities is well taken) [21:04] (not complete at all) [21:04] oh? [21:04] yes, it's just setupping lp crendential and bzr-launchpad binding :) [21:04] so that would be [21:05] $quickly release ubuntu-project? [21:05] no no [21:05] you just cd the project path [21:05] and then "quickly release" [21:05] the release script gets added to the project? [21:05] the call by default is done with the template it was created with [21:05] copied over from the template? [21:06] no, I just copy the template name in a .quickly file [21:06] (in the project directoryà [21:06] so, I can retrieve it afterwards [21:06] retreive* [21:07] if then, someone wants to call the "ubuntu-my-awesome-template" release command, even if this project has been created with quickly new ubuntu-project foo, it can be done by calling: [21:07] quickly -t ubuntu-my-awesome-template release [21:08] so the .quickly file keeps a reference to the project template used, right? [21:08] and so, it will call release.py in template/ubuntu-my-awesome-template/ [21:08] exactly [21:08] hmm [21:08] but we can still call some commands from another templates with the example above [21:09] the bzr integration is sweet, btw [21:09] I think that's what we have to do, at least with the ubuntu-project template [21:09] bzr + lp [21:09] right [21:10] I have to write some errors check, so. Don't play too much with it, atm :) [21:10] ok, this was awesome [21:10] hehe [21:10] well ... let me check it out [21:10] I want to work on the spec for both using it, and adding a template [21:10] it looks like lool got it all set up for debian packaging too! [21:11] it changed a lot over the week :) [21:11] yes, awesome, even if I was planning to do it myself :) [21:11] so, also, to reminds you of the current implementation: [21:11] beuno wants to pimp out the app that is created [21:11] great ;) [21:12] - appart from the new command, the command you call is search first in the template you defined (with -t option) [21:13] I suppose the .quickly file can be used to both scope project related commands, as well as be checked by other commands if they want to change behavior by project template [21:13] - if not, we look at the .quickly file and use the template defined there [21:13] - if the command is not in the template, we try to call a default command in your own bindings/main.py file [21:14] - it also look for hooks, like pre_foo, post_foo [21:14] so, calling "quickly foo" will do: [21:14] pre_foo if present [21:14] foo, found with the previous rules discussed [21:14] and then post_foo, if present [21:14] rickspencer3: and yes, I'm planning adding more stuff to the .quickly file (I already have a list) [21:15] the pre, post idea is good [21:15] I will try to get this documented in the next few days [21:15] so that it is easy to create new templates [21:15] in fact, I want to create: [21:15] $quickly quickly foo [21:15] so you can use quickly to create a quickly template [21:15] :) [21:16] you really want to add entropy to the world ? :) [21:16] heh [21:16] I guess it might be: [21:16] more seriously, that's a great idea, and it can be achieved easily [21:16] (and so, quickly ;)) [21:16] quickly quickly-template, or quickly-command [21:16] I'll dink with it and see [21:16] thanks didrocks! [21:17] you're really welcome :) [21:17] this could be really fun! :) [21:17] I'm sure it will be! [21:17] think to "bzr pull" the trunk regularly! [21:18] it will be difficult for me this week as I will be away from the Internet during the day and james_w is planning to come at home for 3 days, but after that, not problem to push some hard work on it [21:20] rickspencer3: have a good flight and a good rest then ;) [21:24] didrocks: thanks, and I will pull daily :) [21:24] have a good week [21:25] rickspencer3: thanks, you too :) [21:32] rickspencer3: oh, btw, you need ubuntu-dev-tools and bzr to run the release command [21:32] didrocks: thanks for the heads up [21:59] i am so bored [21:59] i am stuck in layover for 5hr :( [21:59] 3 down and 2 to go [22:02] rickspencer3: looks like you have a nice layover as well, heh [22:02] calc: yea [22:03] * calc needs to remember to book his flights really early so he can get better booking next time [22:03] still have an hour before my plane boards :( [22:13] i don't even know when mine boards delta seems to think it should be a secret [22:13] i'm guessing ~ 30-40m before takeoff time [22:20] calc: it's normally 30 mins. before for a domestic flight [22:22] ok [23:02] * calc gets ready to leave, bbl [23:08] calc: have a nice trip :)