[Kommander-devel] Small improvement ideas for editor

[Eric Laffoon]

On Tuesday 05 September 2006 9:09 am, Michal Rudolf wrote:
> Eric Laffoon,  wtorek, 5 września 2006 10:56:
> >1) Run button on editor toolbar
>
> Ok. On the Todo list. Will do it.
>
> >2) Middle click launches editor for Kommander Text
>
> I will try to do it.
>
> >3) Dialog Initialization and Destroy routines on the menu under "Edit
> >Kommander Text..." (this may be an issue with wizard and MainWindow)
>
> Won't it clutter the popup menu too much? But, maybe, Initialization should
> be default script for a Dialog (that is, it should open when you switch to
> Form1 scripts).

Yes it should be the default as I can't remember ever using regular KT for 
Form1. As for clutter, see below #6.
>
> >4) Listing signals and slots used for widgets on the context menu
>
> Interesting idea. I will think how to do it in the best way.

I'm not sure it's a great idea because perhaps a small dialog that shows 
connections only local to the widget and could launch the main dialog might 
be better. The point is I think we need something local to the widget to show 
what is up. We could do 
Signals in Use -> [list] -> Edit, Delete
Slots in Use -> [list] -> Edit, Delete
>
> >5) Let's formalize the Kommander Snippet format and storage, make a
> > Kommander based management tool and add menu items to the editor
>
> Ok.
>
> >6) move layout functions to a submenu under Layout on the context menu
>
> Which one do you mean?

If you look at the context menu on any widget you have 7 layout functions 
provided. Given the difference between Kommander inserting code and a 
standard C++ dialog designer usage we need those proportionately less often. 
I usually just use the toolbar. Let's put them all under a "Layout" menu and 
thus free up 6 menu slots.
>
> >7) optional flyover thumbnail preview of KT on widgets
>
> I am not sure it will be really helpful. But a list of implemented scripts
> will be.

Actually what would be really nice is an indication say in the toolbar when a 
widget is selected telling you if it is using KT, signals, slots, population 
text, etc... The point is, in order to digest what is in a dialog we have to 
right click, select a dialog and interrogate it. It would be nice to have 
simpler ways to have a thumbnail idea where the code is.

Another idea down the line I have is a panel listing widgets in a tree with 
KT, signals, slots, etc... in tabs on the right. We can use icons with the 
tree to indicate what is in use and you could easily navigate all code 
visually as well as the tactile OO interface we have now.
>
> >8) TextEditor context tool menu on KT editor similar to what is in tool
> > menu so that snippet and custom string dialogs could be built and shared
> > 9) Project menu and very simple project directory functionality with the
> > ability to integrate Kommander based project tools
> >
> >Hopefully these will make as much sense in the morning. ;-)
>
> It looks so to me.
Good, I haven't made a fool of myself typing in my sleep. ;-)
-- 
Eric Laffoon
Project Lead - kdewebdev module