quickly-talk team mailing list archive
-
quickly-talk team
-
Mailing list archive
-
Message #00011
Re: Scope of upgrade command
-
To:
quickly-talk@xxxxxxxxxxxxxxxxxxx
-
From:
Umang Varma <umang.me@xxxxxxxxx>
-
Date:
Wed, 22 Dec 2010 14:02:21 -0600
-
In-reply-to:
<1293045656.17881.22.camel@tambo>
-
User-agent:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
On 12/22/2010 01:20 PM, Michael Terry wrote:
> I had the thought that maybe it would be best if we made our (the
> Quickly project's) intentions and ownership more clear to users (and
> thus to us :)).
>
> For example, what if we had the following layout:
> bin/project_name
> python/...
> python_quickly/...
>
> And the only thing the user was expected to change was code in python/.
> So we'd strip that down as much as possible. All the helper code and
> base classes move to python_quickly. The bin script is also ours, for
> wrapper code.
>
> There would be well-defined entry points into the python module
> (notably, for the main window). But by keeping those to a minimum, we
> could change our code easier.
>
> So a quickly upgrade would just replace the code in bin and
> python_quickly. Tada! The efficacy of this would depend on how well we
> could segregate the two, but it seems worth investigating.
I like this!
Except calling a python module/package "python" doesn't sound very nice
to me. Could we s/python/project_name/ ?
Follow ups
References