[Kommander-devel] Connecting Kommander with Kross

[Eric Laffoon]

On Thursday 19 October 2006 2:05 pm, Michal Rudolf wrote:
> Eric Laffoon,  czwartek, 19 października 2006 23:00:
> >It also offers less than
> > relevent options for bool. It seems we could simply convert this to
> > true/false.
>
> execute(bool) is missing. I wasn't sure how to implement it, as all params
> are internally strings (they are handled by DCOP, not by internal parser).
> Perhaps 1/0 is better than true/false.

That's fine. 
>
> >Anyway this looks more complete than you indicated and it brings a lot of
> >potential to using these widgets. There is one thing that might make
> > sense. To minimize scripts we could use logic to manage behavior if we
> > knew what signal and possibly what object called.
>
> My idea was to use item(0) as caller name. Then, item(1) will be the first
> parameter. My question is: is it simple enough? And what should I return
> for 4 parameters (item(1)...item(4))? 4 or 5?

First off see the attached table demo. I was initially confused as to what the 
signal was for changed data and then I thought there might be a reason to 
want to read a cell when entering and exiting. In any event the point is that 
if you know the calling object and you want to manifest different behavior 
you will need two scripts because you won't know the signal. Maybe this won't 
be an issue, but a better question is if we can anticipate future needs. As 
far as your idea I think we can say first that we are most likely to be 
limited to 3 or at most 4 parameters we can address with strings. It would be 
wonderful if we had some slick way to serialize and unserialize other data 
types as strings... I think the problem with your idea is that people expect 
zero based indexes. I think a better idea is new specials...
Self.calledBy or Self.CallingWidget
Self.callingSignal
or
Self.callData(0) = widget
Self.callData(1) = signal
Something along this line allows us to extend the available info.

So the interface for automatic connection of signals and slots with automatic 
scripts for actions is next on the table?
-- 
Eric Laffoon
Project Lead - kdewebdev module
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tabledemo3.kmdr
Type: application/x-kommander
Size: 5851 bytes
Desc: not available
Url : http://mail01.fortunecookiestudios.com/pipermail/kommander-devel/attachments/20061019/20c5e6b5/tabledemo3-0001.bin