On Mon, Dec 14, 2009 at 6:19 PM, Arno Rehn wrote:
> Hi,
>
> we already know this problem (KPluginFactoy::create() has it as well) and
> currently only have a workaround, which consists of special-casing the
> affected method. This is obviously not the ideal solution.
>
> So what we really want is
Hi,
we already know this problem (KPluginFactoy::create() has it as well) and
currently only have a workaround, which consists of special-casing the
affected method. This is obviously not the ideal solution.
So what we really want is the following:
For objects that we create ourselves in the bi
On Sat, Dec 12, 2009 at 3:58 PM, Cédric wrote:
>
> Hi richard,
>
> Do you think this is corrected now and if it is in which release will it be
> available ?
No, i'm afraid the code generated by the new smoke bindings generator
is the same as the old one:
void x_12(Smoke::Stack x) {
//
Hi richard,
Do you think this is corrected now and if it is in which release will it be
available ?
Thanks
Cedric
>
>
>
> On Tue, Aug 18, 2009 at 2:59 PM, Richard Dale wrote:
>
>> On Tue, Aug 18, 2009 at 1:45 PM, Cédric wrote:
>> > Thanks Richard,
>> >
>> > That seems to be the problem.
>> > What
On Tue, Aug 18, 2009 at 1:45 PM, Cédric wrote:
> Thanks Richard,
>
> That seems to be the problem.
> What I was telling in my earlier mail is that the javascript binding seems
> to have a similar problem with plasmoid.dataEngine("engine
> name").serviceForSource("source name") and maybe they solved
Thanks Richard,
That seems to be the problem.
What I was telling in my earlier mail is that the javascript binding seems
to have a similar problem with plasmoid.dataEngine("engine
name").serviceForSource("source name") and maybe they solved it by
implementing the service function: plasmoid.service
On Tue, Aug 18, 2009 at 12:45 PM, Richard Dale wrote:
> On Tue, Aug 18, 2009 at 9:24 AM, Cédric wrote:
>> Well,
>>
>> Thanks for your answer Aaron.
>>
>> I think your first suggestion is the write one. I tried to implement this
>> code with the Javascript binding and in the tutorial page
>> (http:/
On Tue, Aug 18, 2009 at 9:24 AM, Cédric wrote:
> Well,
>
> Thanks for your answer Aaron.
>
> I think your first suggestion is the write one. I tried to implement this
> code with the Javascript binding and in the tutorial page
> (http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/Cheat
Well,
Thanks for your answer Aaron.
I think your first suggestion is the write one. I tried to implement this
code with the Javascript binding and in the tutorial page (
http://techbase.kde.org/Development/Tutorials/Plasma/JavaScript/CheatSheet)
they state this :
- DO NOT use plasmoid.dataEng
On Sunday 16 August 2009, Cédric wrote:
> service=dataEngine("tasks").serviceForSource(dataEngine("tasks").sources.fi
>rst)
things i can think of:
* the ruby script engine bindings are not functioning properly
* sources.first is not a valid name of a task (e.g. it's a start up task or
some other
Hello,
I would like to create a ruby plasma applet which will use the tasks data
engine.
I have a problem to call operations on service.
In plasmaengineexplorer i can close a window but i don't manage it in ruby
service=dataEngine("tasks").serviceForSource(dataEngine("tasks").sources.first)
ser
11 matches
Mail list logo
