quickly-talk team mailing list archive

[tony byrne <tony.badwolf@xxxxxxxxx>]

Can you please shed some light on it? :)
I found it in an old email.

"(I'm still pondering if we shouldn't put as well the custom templates
here: like
~/.config/quickly/templates/ubuntu-application/foo-template
but I'm unsure about the discoverability TBH)"
Didier Roche <didrocks@xxxxxxxxxx> 10 August 2012 07:04

Imagine several students on terminals in a multi-user environment.
Lecturer says "Now class - run your tests"
On my machine I see /tmp/test-project and /tmp/quickly-templates are
created during the tests so the users cannot test simultaneously. It
came to mind when I considered the  quickly team member who needs to
test the non quickly team member mock objects. He might open 2 logins
and test simultaneously as well.

On 13/08/2012, Didier Roche <didrocks@xxxxxxxxxx> wrote:
> Le 10/08/2012 22:25, tony byrne a écrit :
>> How about
>> ~/.config/quickly/templates/ubuntu-application/hooks/post_create.py
>> ~/.config/quickly/templates/ubuntu-application/foo-template
>
> Hey,
>
> I don't really understand this schema, you basically have:
>
> ~/.config/quickly/templates/<first_template_name>/<custom_template_name> ?
>
> Can you please shed some light on it? :)
>
>>    Another consideration as part of the conquer the world project (bug
>> #1 ?) would be quickly being used in school setting, e.g. programming
>> 101. Separate temp folders per student would be essential.
>>
>> Imagine several students on terminals in a multi-user environment.
>> Currently tests run in /tmp/ better would be ~/.cache/quickly/ so they
>> cannot overwrite each other. Also true for a quickly team member who
>> logs in as mere_mortal, who may trip up over old temp files with
>> team_member's permission.
>
> Tests should run using mkstemp if it's not the case already (so no
> overwrite, they are supposed to be unique est that we clean them after
> the tests). If not, we should fix that in the reboot. :)
>
> Cheers,
> Didier
>