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