Eben,
For on thing, Etoys refers to things as projects, which already sound like
self contained bundles of sorts, much like a
sessions in their own right. Combining several projects in one session
just complicates matters, when each can
clearly be stored as its own entry within the
Bert,
First, my apologies about the epic proportions of this email. In it, I
attempt to explain both my working perspective on the usages of the
terms 'activity', 'Activity', and 'Activity instance' and the
implications of our recent security work on the pratical meaning of
these terms.
If the
We (the security minions) had been working under the assumption that
etoys would be operating in single-instance mode because of memory issues.
--Noah
Bert Freudenberg wrote:
Well, we can create several projects and switch between them, like
for making a presentation. Until now this has been
Well, we (the etoys minions) try to accommodate whatever the platform
requires.
Our original thinking was to have just one Etoys process that serves
multiple instances. There were issues on the Sugar side, like that
Sugar insists on having a separate X window for each activity instance.
So
Hi Erik,
I suggest that if the datastore API is not enough for your needs, open a
ticket in trac requesting for multiple file by entry support to be added
to the DS API.
By now, remember you can just put a set of photographs inside a tar file
and send that to the DS.
Regards,
Tomeu
On Thu,
The idea is to have the notion of container entries that can contain
other journal entries.
This does get tricky fast. I think we'll need to discuss it briefly at our
design charrette on Tuesday. There are certainly many cases where we could
use it, but I think a flat system where each
Seriously folks, this is not just a request for an API extension.
This is *begging* for the non-trivial aspects of the Sugar
environment to be fleshed out, at least in writing, if not in code.
We're hopping from trial to trial with patchy interim solutions. And
this how many months before
Bert Freudenberg wrote:
Seriously folks, this is not just a request for an API extension.
This is *begging* for the non-trivial aspects of the Sugar
environment to be fleshed out, at least in writing, if not in code.
We're hopping from trial to trial with patchy interim solutions. And
Bert,
I was replying to Erik's request and that is a totally different one
from yours, in my opinion.
From what I understand, you are asking about how to handle different
instances of the same activity and what relationship exists with their
journal entries. Eben answer did not clarified your
On Fri, 2007-07-27 at 12:37 +0200, Michael Rueger wrote:
On Jul 27, 2007, at 9:15 , Tomeu Vizoso wrote:
By now, remember you can just put a set of photographs inside a tar
file
and send that to the DS.
By now? So, By when is it going to change? And how?
Assuming these photographs
On Jul 27, 2007, at 12:43 , Tomeu Vizoso wrote:
Bert,
I was replying to Erik's request and that is a totally different one
from yours, in my opinion.
From what I understand, you are asking about how to handle different
instances of the same activity and what relationship exists with their
On Sat, Jul 28, 2007 at 02:00:46AM +0200, Bert Freudenberg wrote:
Thank you Michael, this at least makes the security side more clear
to me.
Then it served its purpose. :)
So if an activity would like to handle multiple instances in one
container or even one process, that would be fine.
Was my question so easy that it didn't need a response? :-)
Seriously... how should activities save/serialize multiple files for
correct indexing/viewing in the Journal? We need an answer yesterday.
On 7/25/07, Erik Blankinship [EMAIL PROTECTED] wrote:
I am wondering if there is an answer
I am wondering if there is an answer yet to this question from about a month
ago?
On 7/12/07, Bert Freudenberg [EMAIL PROTECTED] wrote:
If I understand the Sugar philosophy correctly, we won't have
multiple documents per activity. If we want to have multiple
documents opened at the same time,
Well, for the most part the single-document-per-activity-instance is the
model. There are of course some exceptions to this rule. For instance, in
a given web browsing session most people will visit a number of different
websites; As such, the session is treated as the object within the
15 matches
Mail list logo
