Question: how can we launch etoys from the browser when someone clicks on a URL? Marco notes that a hook can readily be added to do the launching, but how will etoy parse the input URI?
SJ
On Tue, 2007-03-20 at 15:33 -0400, Samuel Klein wrote:
Question: how can we launch etoys from the browser when someone clicks on a URL? Marco notes that a hook can readily be added to do the launching, but how will etoy parse the input URI?
You can get the URI from the handle which is passed to Activity constructor (handle.uri). But then I don't know if/how it can be passed to etoys...
Marco
On Mar 20, 2007, at 22:32 , Marco Pesenti Gritti wrote:
On Tue, 2007-03-20 at 15:33 -0400, Samuel Klein wrote:
Question: how can we launch etoys from the browser when someone clicks on a URL? Marco notes that a hook can readily be added to do the launching, but how will etoy parse the input URI?
Why would we need to "parse the input URI"? And what *is* an "input" URI?
We could of course download the project from the URI, but why should we do that again when the browser already did it?
You can get the URI from the handle which is passed to Activity constructor (handle.uri). But then I don't know if/how it can be passed to etoys...
I somehow missed part of this conversation. What happens if in the browser an etoys project file is downloaded?
I'd suppose that based on the mime-type there is a registry for d-bus services to handle the downloaded file. Then a d-bus request is made which launches the activity. Somehow the location of the downloaded file, as well as the URI should be passed via d-bus to the activity. Is that basically correct?
Anyway, once the etoys activity is launched, we would simply load that project file and then invoke the project.
- Bert -
On Tue, 2007-03-20 at 22:50 +0100, Bert Freudenberg wrote:
On Mar 20, 2007, at 22:32 , Marco Pesenti Gritti wrote:
On Tue, 2007-03-20 at 15:33 -0400, Samuel Klein wrote:
Question: how can we launch etoys from the browser when someone clicks on a URL? Marco notes that a hook can readily be added to do the launching, but how will etoy parse the input URI?
Why would we need to "parse the input URI"? And what *is* an "input" URI?
We could of course download the project from the URI, but why should we do that again when the browser already did it?
You can get the URI from the handle which is passed to Activity constructor (handle.uri). But then I don't know if/how it can be passed to etoys...
I somehow missed part of this conversation. What happens if in the browser an etoys project file is downloaded?
I'd suppose that based on the mime-type there is a registry for d-bus services to handle the downloaded file. Then a d-bus request is made which launches the activity. Somehow the location of the downloaded file, as well as the URI should be passed via d-bus to the activity. Is that basically correct?
Correct, except we only pass the location of the downloaded file as an URI (file://).
In the python Activity object it's handle.uri.
In the dbus service it's:
@dbus.service.method("com.redhat.Sugar.ActivityFactory", in_signature="a{ss}") def create(self, handle):
where handle is a dictionary.
Marco
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Marco Pesenti Gritti -
Samuel Klein