ExternalScript plugin ready to be merged (and some Quanta news)

Niko Sams niko.sams at gmail.com
Sun Jun 20 09:20:34 UTC 2010


On Sat, Jun 19, 2010 at 15:58, Milian Wolff <mail at milianw.de> wrote:
> On Saturday 19 June 2010 08:31:36 Niko Sams wrote:
>> On Tue, Jun 15, 2010 at 22:58, Milian Wolff <mail at milianw.de> wrote:
>> > Heyho :)
>> >
>> > I just more or less finished the ExternalScript plugin. What is it? Well,
>> > it's a quick'n'easy plugin ~(1000loc) to execute arbitrary external
>> > scripts or
>>
>> > commands. Example:
>> Works great, I'll try to use my old Quanta3 scripts with that (have to
>> update Kde first at work)
>>
>> Some issues:
>> - add placeholders that make it possible for the script to communicate
>> with kdevelop using
>>   dbus (PID would be enough i think)
>>   example usecase: open a document in kdevelop
>> - add placeholders for current project path / all project paths
>> - show the placeholders somewhere
>> - make output view optional (when executing a script that generates
>> code the opening
>>   output view is just a waste of space)
>> - show the toolview by default (?)
>
> All done now,
great!

> except for the "all project paths" - do you really need that?
No, this was just an idea. I don't have an use case for that.
If needed the projects should be better queried using dbus. (if that
is possible)

Niko




More information about the KDevelop-devel mailing list