[Kommander-devel] Connecting Kommander with Kross

[Eric Laffoon]

On Thursday 19 October 2006 12:44 pm, Michal Rudolf wrote:
> Eric Laffoon,  czwartek, 19 października 2006 21:33:
> >Does this mean it will be done on a case by case basis per widget? I ask
> >because the rich text and table widgets would benefit greatly from this
> > and also would have more work involved. It would be nice to spread this
> > power without making yourself crazy.
>
> What do you mean by 'case by case basis per widget'? Obviously, not all
> signals can be used (mostly those with pointers are unusable for us), but
> other should work.
> Can you give some examples what would you like to do?

Yeah, make me stop and think when I'm busy. ;-) Okay, it's better than you 
said. I see that I can use execute(int,int) with tables even where signals 
look like (int,int,int,QPointer) because it just uses what it can. Very cool. 
This eliminates the need for long loops to recalc everything and means you 
can simply replace array elements. Looking at the text editor I see it 
handles the integers but misses a QString. It also offers less than relevent 
options for bool. It seems we could simply convert this to true/false.

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.

-- 
Eric Laffoon
Project Lead - kdewebdev module