2008/10/3 D. Michael McIntyre <[EMAIL PROTECTED]>:
> Emanuel proposes:
>> slot-name: slot_filter_selection
>> action-name: filter_selection
>> icon-name: filter_selection
>
> No. We're definitely not going to have slots with names like this, so the
> only way to make any change would be to change the other strings to use
> lowerCamelCase notation as well, like filterSelection and so on.
>
My main-point was unification here, so editing would be simplified
(e.g. with copy and paste.)
>
> I think it would probably be best just to leave well enough alone though.
>
ok
>
> If we use external files, we'll use XML. We use XML everywhere. The guitar
> chord dictionary, the instrument parameter presets, our own native .rg
> and .rgd files. Adding some new format is nonsense. No.
>
I would prefere if you did not call my suggestions nonsense, since
they have pros and cons as everything else.
The rest of your arguments is convincing though, so let's
stick to and use xml.
> * Some users like to rearrange their menus and toolbars by hacking their .rc
> files. If we continue to use something like this, they can continue to do
> that.
>
good point.
> * We should consider users who like to rearrange their toolbars through the
> GUI, doing their own action mappings.
>
I'm not sure, how this would be best realized with qt4 either.
My assumtion:
We have to use QSettings, for storing the "geometry" of QWidgets.
We could additionally store the docking area currently used by the toolbars.
The actions appearing on the toolbar would be configured in the xml.
Regarding the file structure:
this is a part of a current rc xml file:
<MenuBar>
<Menu name="file">
<Menu name="import" append="new_merge"><text>&Import</text>
<Action name="file_import_project" />
<Separator/>
<Action name="file_import_midi" />
<Action name="file_import_rg21" />
<Action name="file_import_hydrogen" />
</Menu>
looks like we can keep it as it is.
I also found this:
<State name="have_project_packager">
<enable>
<Action name="file_import_project"/>
<Action name="file_export_project"/>
</enable>
</State>
We could additionally add a file listing the actions with more
detailed properties:
<actions>
<action name="import_midi_file">
<label lang="en">Import a midi file</label>
<label lang="de">Importiere eine Midi Datei.</label>
<shortcut>Qt::CTRL + Qt::Key_M</shortcut>
<iconName>import_midi</iconName>
<isToggle>false</isToggle>
<checked></checked>
<actionGroupId></actionGroupId>
<enabledConditions></enabledConditions>
<parentWidgetId></parentWidgetId>
<slotTargetWidgetId></slotTargetWidgetId>
</action>
<action name="import_hydrogen_file">
<label lang="en">Import a hydro file</label>
<label lang="de">Importiere eine Hydro Datei.</label>
<shortcut>Qt::CTRL + Qt::Key_M</shortcut>
<iconName>import_midi</iconName>
<isToggle>false</isToggle>
<checked></checked>
<actionGroupId></actionGroupId>
<enabledConditions></enabledConditions>
<parentWidgetId></parentWidgetId>
<slotTargetWidgetId></slotTargetWidgetId>
</action>
</actions>
It would be very good, if the written code would
work in a way, that the QActions already defined would not
necessarily require a modification (or a move to the xml file).
Best Regards
Emanuel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
