Microsoft has released RTW version of Microsoft Ribbon for WPF
-
I downloaded the Sample app along with the source code. It's great that most of the issues we face in WPF Ribbon has been address like Shortcuts, Navigation keys, etc. You know what, they have fixed the bug when we maximize the RibbonWindow and the RibbonWindow for XP is better now. Click here[^] to get the version.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
Think of me as a customer. I won't spend my money on any application or upgrade that has a ribbon.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Think of me as a customer. I won't spend my money on any application or upgrade that has a ribbon.
I wanna be a eunuchs developer! Pass me a bread knife!
The application where I use this Ribbon is 11 years old product and we showcased them (clients) with the Ribbon, they love it. One of the reason might be they are now very familiar with Office 2007/2010.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
-
I downloaded the Sample app along with the source code. It's great that most of the issues we face in WPF Ribbon has been address like Shortcuts, Navigation keys, etc. You know what, they have fixed the bug when we maximize the RibbonWindow and the RibbonWindow for XP is better now. Click here[^] to get the version.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
I wouldn't bother look at Fluent On CodePlex utterly bliss.
-
I wouldn't bother look at Fluent On CodePlex utterly bliss.
Norm .net wrote:
Fluent On CodePlex utterly bliss.
Yes it is. But there are some licensing or internal problems in using Open Sources in our product. They would rather force the developer to develop a new instead of using Open sources. :^)
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
-
I downloaded the Sample app along with the source code. It's great that most of the issues we face in WPF Ribbon has been address like Shortcuts, Navigation keys, etc. You know what, they have fixed the bug when we maximize the RibbonWindow and the RibbonWindow for XP is better now. Click here[^] to get the version.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
The post you link to, is 2 1/2 month old.
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
The post you link to, is 2 1/2 month old.
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth EditionThe post link might be old, but it is new in Lounge. ;P
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
-
The application where I use this Ribbon is 11 years old product and we showcased them (clients) with the Ribbon, they love it. One of the reason might be they are now very familiar with Office 2007/2010.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
Well, if they enjoy having to traverse the screen several times to click huge objects just to get to a command that would normally be on a visible toolbar or in an easy-to-remember menu location, then more power to them. It's a lot less power to their productivity, but you can't win 'em all, I suppose. Just make sure that there are key combinations for every (as in *EVERY*!) command, and that the list of key combinations is easily accessible (i.e. can remain on screen, out of the way) so that power users don't have to waste their time switching ribbon elements back and forth. In fact, make the list of key commands clickable, so that we don't have to actually enter the command on the keyboard, and, to keep it as unobtrusive as possible, use icons to represent the key combinations, that only show the key combinations on hover. And make sure that the ribbon can be completely hidden (even the tabs), to maximise the available workspace. Those would be great enhancements to the ribbon concept.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Well, if they enjoy having to traverse the screen several times to click huge objects just to get to a command that would normally be on a visible toolbar or in an easy-to-remember menu location, then more power to them. It's a lot less power to their productivity, but you can't win 'em all, I suppose. Just make sure that there are key combinations for every (as in *EVERY*!) command, and that the list of key combinations is easily accessible (i.e. can remain on screen, out of the way) so that power users don't have to waste their time switching ribbon elements back and forth. In fact, make the list of key commands clickable, so that we don't have to actually enter the command on the keyboard, and, to keep it as unobtrusive as possible, use icons to represent the key combinations, that only show the key combinations on hover. And make sure that the ribbon can be completely hidden (even the tabs), to maximise the available workspace. Those would be great enhancements to the ribbon concept.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
Just make sure that there are key combinations for every (as in *EVERY*!) command, and that the list of key combinations is easily accessible (i.e. can remain on screen, out of the way) so that power users don't have to waste their time switching ribbon elements back and forth. In fact, make the list of key commands clickable, so that we don't have to actually enter the command on the keyboard, and, to keep it as unobtrusive as possible, use icons to represent the key combinations, that only show the key combinations on hover. And make sure that the ribbon can be completely hidden (even the tabs), to maximise the available workspace. Those would be great enhancements to the ribbon concept.
Agreed.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
-
Mark Wallace wrote:
Just make sure that there are key combinations for every (as in *EVERY*!) command, and that the list of key combinations is easily accessible (i.e. can remain on screen, out of the way) so that power users don't have to waste their time switching ribbon elements back and forth. In fact, make the list of key commands clickable, so that we don't have to actually enter the command on the keyboard, and, to keep it as unobtrusive as possible, use icons to represent the key combinations, that only show the key combinations on hover. And make sure that the ribbon can be completely hidden (even the tabs), to maximise the available workspace. Those would be great enhancements to the ribbon concept.
Agreed.
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)
*sigh* I described a toolbar.
I wanna be a eunuchs developer! Pass me a bread knife!
-
*sigh* I described a toolbar.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
I described a toolbar.
Sure you did. You can collapse a Ribbon like a menu/tool bar by double clicking the tab header. I would use that open when a power user needs it. Moreover we are providing plenty of shortcut keys (will be documented).
Venkatesh Mookkan (My: Website | Yahoo Group | Blog Spot | Follow me @ Twitter)