What we need for etoys is a way to explicitly save a project, and
then be able to resume from that point any number of times without
fearing of it to be overwritten automatically.
Any idea how to do that within the journal philosophy?
- Bert -
On Sep 19, 2007, at 19:59 , Eben Eliason wrote:
Well, as I mentioned, you can do so for now by creating a new clean
copy each time you want to modify it. If you're talking about example
or template files, then I would recommend keeping a clean copy within
the bundle so that you can create a new clean journal entry from that
at will.
Once
Hello,
I branched sugar for trial-3. Please push changes on the branch only
if you have got Jim approval to get them into the images.
If you need to make changes to other modules make sure to branch them
and to inform the mailing list about it.
Tips about how to branch and how to work on a
On 7/28/07, Tomeu Vizoso [EMAIL PROTECTED] wrote:
On Sat, 2007-07-28 at 11:53 +0200, Marco Pesenti Gritti wrote:
* The shell service needs to be in a separate process/thread than the
UI one, to avoid performance issues and dead locks. Tomeu is already
working on it, I want to get it in as
On Sat, 2007-07-28 at 11:53 +0200, Marco Pesenti Gritti wrote:
* The shell service needs to be in a separate process/thread than the
UI one, to avoid performance issues and dead locks. Tomeu is already
working on it, I want to get it in as soon as possible.
Looks like dbus-python doesn't
5 matches
Mail list logo
