Events editor

[BogDan Vatra]

2008/11/11, Andreas Pakulat <apaku at gmx.de>:
> On 11.11.08 13:29:59, BogDan Vatra wrote:
>> 2008/11/11, Andreas Pakulat <apaku at gmx.de>:
>> > On 11.11.08 11:13:39, BogDan Vatra wrote:
>> >> 2008/11/10, Andreas Pakulat <apaku at gmx.de>:
>> >> > On 10.11.08 19:51:09, BogDan Vatra wrote:
>> >> >> Hi,
>> >> >>
>> >> >
> >
>> > Except that it only works for "builtin" signals/slots, which is not
>> > acceptable in the long-run for KDevelop's Designer integration. Besides,
>> > the designer integration specifically allows and encourages to provide a
>> > custom signal/slot editor.
>>
>> Please give me something to read .
>
> Ok, this one I don't understand :)

:) I need some docs to see how to create a custom signal/slot editor
for designer.

>>
>> Ok. But I cant promise you this will be ready for 4.0. I don't want to
>> think how hard is to rewrite the signal/slot editor.
>
> I don't expect any of this to be done for 4.0 actually. I'm also not saying
> you need to start on this right now. I was just trying to explain what the
> ultimate goal is for the signal/slot editor in KDevelops designer
> integration. Its totally fine if you start with adding a new editor that
> allows to create auto-connect slots.
>
> I still am not sure I want to ship the designer integration with 4.0,
> because its still "half-baked" and needs quite a bit of work.
>

What a pity, I use the designer integration from kdevelop every day ;((

>
> Maybe, you could try to find the .ui file in the project tree, get its
> parent which should be a ProjectTargetItem and let the projectbuilder build
> the target item. This would automatically re-generate them, which might
> work for now. See the ProjectItem classes, the IProject class,
> IBuildSystemManager and IProjectbuilder for information on this. Oh and
> probably also IProjectController. api.kde.org is your friend, look into the
> interfaces and project libraries.
>
Thanks for the tips, I'll take a look.

>> > A fully working signal/slot editor is just a first step :) an
>> > important one though.
>>
>> Please give me some docs.
>
> Docs for what? You mean what a fully integrated designer might allow? Well
> for one, it'll provide the language information for the .ui files, i.e. a
> declaration for each widget, with declarations for all the subwidgets.
> (similar to what the C++ support knows after seeing the ui_xxx.h file).
> Then there is custom widgets which we want to support, i.e. write a class
> inside KDevelop and kdevelop will show it inside the designer - on-the-fly.
>
> I think we currently don't have any real docs of these ideas, there might
> be some available in our wiki in the KDevelop4 section though.
>

If we have to rewrite the signal/slot editor we need to know how to
read all connections from ui file, and how to write this connections
back to ui file.

BogDan,