Support for the Ribbon framework [feature-requests:#57] would be nice, but it is a large framework and fully encapsulating it would be a substantial undertaking.
When [will OWLNext have] a Ribbon toolbar?
It is currently not on any plans (see our roadmap). Version 6.40 is planned to be released as soon as we have fairly solid 64-bit support (compatible message dispatch, etc.), so I doubt Ribbon support will make it in that version. Version 7 is in early planning, so there is more opportunity to get it into that version.
In any case, it depends on someone stepping up to the plate to do the actual work. You are welcome to contribute if you want to make it happen.
Personally, I don't need Ribbon support in my applications, and I have too much else on my list.
I'm also on the same thinking; I've stopped using MS-Word when they switched to Ribbon toolbar (I'm using now Libre Office), it requested relearn the interface just to do the very same thing.
If yoy want to modernize the look and feel of your application here are my suggestions:
Deprecate BWCC and switch to OWLNext Glyphbuttons.
Add a theme for your application (there is an example in the OWLNext website)
I've stopped using MS-Word when they switched to Ribbon toolbar
This is a point worth emphasising. The radical difference in UI that the Ribbon framework presents, makes its use risky in legacy applications. In my view, it should therefore only be used for new applications. Since OWLNext is a poor choice for new applications, it is perhaps not worth the investment of time and effort. We have a lot of items on the to-do list for OWLNext that is much more important for the maintenance of legacy applications, which is the primary purpose of OWLNext, after all.
Another issue worth noting is that the Ribbon framework is based on COM. So if it was to be supported in OWLNext, its implementation could probably benefit from the use of OCFNext, which would mean that it cannot go into the core library, but instead should probably go into the extension library OWLExt, or alternatively, go into a new stand-alone extension library.
Last edit: Vidar Hasfjord 2013-02-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, note that, since the Ribbon framework has so many dependencies, it can add significant start-up time to the application. This may be unacceptable for tools that need to be opened and closed frequently. E.g. see
Hi,
When OWLNext will has a Ribbon toolbar?
VCL has ribbon toolbar.
In order to make application looks modern, adding a ribbon toolbar is a good choice.
Thanks
Last edit: Vidar Hasfjord 2013-02-23
Hi James,
Support for the Ribbon framework [feature-requests:#57] would be nice, but it is a large framework and fully encapsulating it would be a substantial undertaking.
It is currently not on any plans (see our roadmap). Version 6.40 is planned to be released as soon as we have fairly solid 64-bit support (compatible message dispatch, etc.), so I doubt Ribbon support will make it in that version. Version 7 is in early planning, so there is more opportunity to get it into that version.
In any case, it depends on someone stepping up to the plate to do the actual work. You are welcome to contribute if you want to make it happen.
Personally, I don't need Ribbon support in my applications, and I have too much else on my list.
Related
Feature Requests: #57
Hi James:
I'm also on the same thinking; I've stopped using MS-Word when they switched to Ribbon toolbar (I'm using now Libre Office), it requested relearn the interface just to do the very same thing.
If yoy want to modernize the look and feel of your application here are my suggestions:
Sebas
This is a point worth emphasising. The radical difference in UI that the Ribbon framework presents, makes its use risky in legacy applications. In my view, it should therefore only be used for new applications. Since OWLNext is a poor choice for new applications, it is perhaps not worth the investment of time and effort. We have a lot of items on the to-do list for OWLNext that is much more important for the maintenance of legacy applications, which is the primary purpose of OWLNext, after all.
Another issue worth noting is that the Ribbon framework is based on COM. So if it was to be supported in OWLNext, its implementation could probably benefit from the use of OCFNext, which would mean that it cannot go into the core library, but instead should probably go into the extension library OWLExt, or alternatively, go into a new stand-alone extension library.
Last edit: Vidar Hasfjord 2013-02-23
Also, note that, since the Ribbon framework has so many dependencies, it can add significant start-up time to the application. This may be unacceptable for tools that need to be opened and closed frequently. E.g. see
http://code.google.com/p/tortoisegit/issues/detail?id=1616
I am thinking that VCL Ribbon can be a choice.