Ulp! Code! ;)
/branches/work/~fmontesi/
I made a first version of the script library for making adaptors.
YahooSearch.ol is an implemented custom adaptor that does the following:
- takes an init parameter at starting;
- composes request data and calls the yahoo web search service converting this
On Tuesday 25 November 2008 00:55:23 Aaron J. Seigo wrote:
> On Monday 24 November 2008, Fabrizio Montesi wrote:
> > On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote:
> > > On Monday 24 November 2008, Fabrizio Montesi wrote:
> > > > We would need to support the loading of Jolie scripts anyw
On Monday 24 November 2008, Fabrizio Montesi wrote:
> On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote:
> > On Monday 24 November 2008, Fabrizio Montesi wrote:
> > > We would need to support the loading of Jolie scripts anyway (for more
> > > complex cases or coding distributed behaviour as
On Monday 24 November 2008 20:24:59 Aaron J. Seigo wrote:
> On Monday 24 November 2008, Fabrizio Montesi wrote:
> > We would need to support the loading of Jolie scripts anyway (for more
> > complex cases or coding distributed behaviour as backend to a plasmoid),
> > so while this option (the XML o
On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> use case: widget wants to publish it's own service onto the network
>
> * it takes a Plasma::Service and, again with a one liner and no jargon it
> pushes the service by a name passed in; this would get automatically set up
> using SODEP
On Monday 24 November 2008, Fabrizio Montesi wrote:
> We would need to support the loading of Jolie scripts anyway (for more
> complex cases or coding distributed behaviour as backend to a plasmoid), so
> while this option (the XML one) could be nice I'm wondering if we would end
> up with too many
On Monday 24 November 2008 18:10:06 Aaron J. Seigo wrote:
> On Sunday 23 November 2008, Fabrizio Montesi wrote:
> > On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> > > something else i just remembered:
> > >
> > > we're going to want to think about the full round trip "experience":
>
On Sunday 23 November 2008, Fabrizio Montesi wrote:
> On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> > something else i just remembered:
> >
> > we're going to want to think about the full round trip "experience":
> >
> > use case: widget wants to use a web service
> >
> > * it says
On Saturday 22 November 2008 02:49:57 Aaron J. Seigo wrote:
> something else i just remembered:
>
> we're going to want to think about the full round trip "experience":
>
> use case: widget wants to use a web service
>
> * it says "give me this web service" -> that should be a one liner with no
> j
On Saturday 22 November 2008 02:39:34 Aaron J. Seigo wrote:
> On Thursday 20 November 2008, Fabrizio Montesi wrote:
> > ---
> > --- Service Exposure
> > ---
> > Example of service exposure:
> > Plasma::Service *s = ...; //Some plasma service obtained in some way.
> > Plasma::ServicePublishingJob *j
something else i just remembered:
we're going to want to think about the full round trip "experience":
use case: widget wants to use a web service
* it says "give me this web service" -> that should be a one liner with no
jargon in it, just the URL of the service and return a Plasma::Service re
On Thursday 20 November 2008, Fabrizio Montesi wrote:
> ---
> --- Service Exposure
> ---
> Example of service exposure:
> Plasma::Service *s = ...; //Some plasma service obtained in some way.
> Plasma::ServicePublishingJob *j = s->publish();
>
> Here Plasma::Service::publish() is a wrapper for:
>
Hi everyone,
this is a recap mail about the current status of the integration of JOLIE and
Plasma, so that everyone can jump in and to make discussing it easier.
As you can see in SVN, the JOLIE integration layer didn't make it for KDE 4.2.
That's to avoid cluttering with Plasma's API when the p
13 matches
Mail list logo
