[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Status of KoMacro ?
From:       Thomas Zander <zander () kde ! org>
Date:       2007-05-20 10:16:09
Message-ID: 200705201216.09312.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 20 May 2007 11:58:52 Cyrille Berger wrote:
> I don't understand where pytho^D ruby (for me :) ) and kross fit in all
> of this.

Did you read this thread?
http://lists.kde.org/?t=116255327100001&r=1&w=2

Ok, from the top.
User does something and a command gets created for your recording.
Whenever that 'command' gets added to the list of commands there is a 
choice;
we either save that as a C++ object (which might be serialized later) or 
we store it as a python command on a script.

Re-running the list of commands then simply becomes running a script 
instead of your custom commands.

This makes it unneeded to serialize the C++ to XML and more importantly, 
it makes it unneeded to read that XML later to recreate those C++ objects 
that can be run again.  Since in my idea you simply run the script 
through kross. No need to create those command objects again.

We might want to add comments in the script so a GUI can read it and show 
nice objects for people that don't want to know there is a script at all.
But I discussed details like that in the above linked thread ;)

The biggest advantage I see is that a user can record some work and then 
tweak the recorded macro either through a GUI or simply as a script. His 
choice.
Which is an immensely powerful learning tool as most people are better at 
altering an existing script than creating a new one. And recording then 
(additionally) just became a tool to start writing your own scripts.

Hope that makes it clear! :)
-- 
Thomas Zander

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic