关于NX二次开发，经典界面到RIbbon界面转换的菜单开发技巧

admin

关于NX二次开发，经典界面到RIbbon界面转换的菜单开发技巧
0 w) A# U  X1 j7 ]

经典界面到RIbbon界面转换

在经典界面下，需要的文件
. ]7 `6 }- @1 m& T+ G

• customer_men.men
• customer_toolbar.tbr
  7 Y+ {& }. _) o  T- N: M

在ribbon界面下你可能需要的文件
6 e! @4 q/ u: s2 j, ~# z" c. S% S# g

• customer_men.men
• customer_tab.rtb
• customer_toolbar.tbr
• customer_toolbar_alternate.tbr
• customer_group.grb
  
  - C7 s- o. @7 a4 t1 ^

举例如下：
+ Y- Y: I2 D' S  Z

, J: i1 F  k1 b8 g% `customer_men.men
!
5 r% Y& _3 ?3 Y- U# E!  Customer menu file
!
!  Contains button definitions to be used in
!  toolbars and Ribbon files
1 }! ?5 e% l$ K5 H- S+ m!
% R- c8 z+ R0 p0 x
VERSION 120

: E: }+ p0 F# y. L, YEDIT UG_GATEWAY_MAIN_MENUBAR

TOP_MENU
5 v7 K. I) \3 r8 C; y- }    CASCADE_BUTTON CUSTOMER_MENU
% X" u( A0 h% I3 G! h" c' _    LABEL Customer Menu

END_OF_TOP_MENU
+ l) w+ U& n9 S! H2 W9 ?- y
MENU CUSTOMER_MENU
; z) \/ K* X( ]/ D
    BUTTON CUSTOMER_BUTTON_1
0 V( g# K( j  S* q: _* s    LABEL Menu Button1
        RIBBON_LABEL Ribbon Button1
, e. U7 f- u9 U8 m1 I9 {# m- R        TOOLBAR_LABEL Toolbar Button1
( F* {+ i7 |+ M4 M5 F  o    BITMAP fileopen

, }; p6 L/ s3 c; z: @6 E- G    BUTTON CUSTOMER_BUTTON_2
    LABEL Menu Button2
* d$ H& r( p4 b% d9 S& `$ p        RIBBON_LABEL Ribbon Button2
1 X) P: S! N4 b- @, \! Q4 S; V! m        TOOLBAR_LABEL Toolbar Button2
8 m- L4 a" M4 `  |' l    BITMAP filesave

# w. h" c) N$ p/ v$ ]4 x0 i. `3 R    BUTTON CUSTOMER_BUTTON_3
    LABEL Menu Button3
        RIBBON_LABEL Ribbon Button3
        TOOLBAR_LABEL Toolbar Button3
8 Y- E& o5 }+ ~/ n# H    BITMAP current_feature

    BUTTON CUSTOMER_BUTTON_4
    LABEL Menu Button4
        RIBBON_LABEL Ribbon Button4
        TOOLBAR_LABEL Toolbar Button4
. `) L) f1 [9 r8 @  k    BITMAP block
7 q6 {8 k% [# n3 @- R7 f  R
" i5 u4 d+ u/ b) e* w3 S, T1 f    BUTTON CUSTOMER_BUTTON_5
3 v1 S/ y, [3 h3 y. V    LABEL Menu Button5
/ p; i. S# R5 B: X        RIBBON_LABEL Ribbon Button5
! p/ X! Q- V. Z: ]        TOOLBAR_LABEL Toolbar Button5
. Y- b3 V, m( a3 I3 L: D    BITMAP checkgreen

9 g2 X* p3 s/ ^8 G9 u; sEND_OF_MENU

: @) a- d7 f" L. O, J

% U, U* C: N- r( ]& Icustomer_ribbon_tab.rtb
!
!  Customer Ribbon Tab
' M5 W% m3 e3 \+ ~, n3 H!
& e( S$ {9 Z1 F! t9 _# Q!  This file will create a new customer tab containing three groups and
9 X& u+ @+ n8 n: ^( K6 o' ~!  one top level button.
!

TITLE  Customer Tab
VERSION 170
7 K) ?5 m3 E7 t* ]" R% A; g
: r' K5 |% T1 Q4 T. r) H!  The first group represents a Ribbon group that references an existing
!  toolbar with no Ribbon style changes.  
!
* M( }/ W* k+ X- {!  This is the quickest way to add existing toolbar content into Ribbon mode.
!
GROUP  customer_toolbar.tbr
* c' w" U5 N8 _. d
! r0 v4 ?/ j" c" Z!  The second group represents a Ribbon group that references an existing
; t+ r& _5 [( k$ n. l: a# T!  toolbar with Ribbon specific style changes added to it.  There is no difference
!  in how this toolbar is referenced in the .rtb file compared to the first
5 A9 l0 a, {  f& C, F!  toolbar as a group.  The only differences from the first group exist within
8 n) j4 x8 u$ R  B7 }!  the .tbr file itself.
!
!  This approach has advantages for customers that will deploy both Ribbon and
- D" l' f; e0 V$ @!  Classic Mode customizations since all the content is defined in the .tbr
!  file and it will stay synchronized in both modes.  Only one set of customizations
: C' w0 ], e2 a* g. S! j8 d$ x!  will need to be maintained while still making use of RIBBON_STYLE to
!  control the presentation of the buttons on the Ribbon.
!
GROUP  customer_toolbar_alternate.tbr
7 Q+ e+ E) y6 ]# X
!  The third group represents a Ribbon group that has been created explicitly
6 {) [: h# @3 F; R- u0 E. D!  as a Ribbon group and will not exist in Classic Toolbar mode.  This is the
7 m' l2 ]$ F2 U7 o7 `+ G!  preferred option since the user will be able to take advantage of all the
!  layout styles and containers offered by the Ribbon.  
!
!  For customers that will deploy both Ribbon and Classic Mode customizations,
" R! T- @2 E; @0 N( s9 H!  this approach will result in no synchronization and two sets of customizations
! W, Y0 v: Z) R- g8 R4 M  a3 q( m!  will need to be maintained.
!
* g( O& n- b- r( E) j" F6 F7 ^!  A group can alternatively be defined directly inside the .rtb file by using the
!  keywords BEGIN_GROUP and END_GROUP.  
!
GROUP  customer_group.grb
! q( D6 e* V- H1 h
2 _, b) N( r7 @$ {5 Y+ _!  Example of a button that is placed directly on the Ribbon without being
1 A+ U7 r" f1 P! }+ l* i  K!  contained in a group.  This is a simple way to add a button to a tab
" H- @6 `6 ?7 Q9 _!  but is not recommended for many buttons since groups have advantages.
!  
# [( a0 n; a2 `; V6 U!  A few advantages of groups:
!     1. Easier to move many buttons around together in quick customization.  
; ~. e0 O6 C# W  Q+ P" c8 S0 Q!        For example, MB3 on a group and choose "Add to Left Border Bar".  
!        This will move the whole group to a new location.  If buttons are
!        not in a group, they need to be moved one at a time.
!
6 B3 X. q  |. s0 ]! q!     2. Provide a label to describe its contents.
3 @1 B. ^- x% ]" l' B4 K6 Q4 F) s!
BUTTON CUSTOMER_BUTTON_1
LABEL Button1 Directly on Tab
, n, h) u, T2 Q9 Z: k" K
7 q& H2 g% d4 B* l' ^% ?' {
( o) R  X7 a1 L5 g$ r' Z
customer_toolbar.tbr
: l! g* e4 h: ^% |3 d2 B" Z!
/ n4 H, N+ K0 \, m!  Customer Toolbar File
!
1 Z/ V9 k( |: Q5 v& ~) N7 `# H9 o!  This is similar to an existing toolbar file containing
% \& \+ v3 }$ T!  no Ribbon changes.
/ y; R! o, a, q4 E  M  w!
7 a# V, n) \' o2 V5 Y' @2 f& h!  In Classic Toolbars mode - This toolbar will still show up in the
!     toolbars list.
!
+ U! }6 ~, P1 W6 F4 P8 Y!  In Ribbon mode - This toolbar will be automatically converted to a
4 M- s7 f" b( u  i/ b  n!     Ribbon group and will appear in the "Classic Toolbars as Groups"
!     section in the Customize dialog.
% C, Y5 M2 |  s% y5 Z; A0 e4 {!  

TITLE Toolbar
VERSION 170

+ U& a) B# E& V; D$ b0 Y! sBUTTON CUSTOMER_BUTTON_1

BUTTON CUSTOMER_BUTTON_2
+ S8 C" o; K: f4 n
7 t# l- p5 f# l  f7 s) s* VBUTTON CUSTOMER_BUTTON_3
" u/ K8 s5 Y. X& }0 m3 Z
# V9 l7 o- C# o6 Q* K% e4 u0 {BUTTON CUSTOMER_BUTTON_4
1 v5 m" `' {( f& K' A6 j, y# L
BUTTON CUSTOMER_BUTTON_5



customer_toolbar_alternate.tbr
!
1 z# a2 ]. q5 m7 H6 \5 b1 U1 O!  Customer Toolbar File (Alternate)
( Q& D, _. c6 `! k: b( F' S  u9 M!
!  This is similar to an existing toolbar file with new
, j/ W" u- C, x  d' G5 F!  Ribbon styles added.
!  
2 M( s2 ^7 f# S% j8 R1 j!  The RIBBON_STYLE will be honored when the toolbar is loaded
  K2 |# d, V- E+ l!  in Ribbon mode as a group but will be ignored when the toolbar
% N# E( n. i0 B# b7 ]# S* u!  is displayed in Classic Toolbars mode.
!
!  In Classic Toolbars mode - This toolbar will still show up in the
!     toolbars list.
!
0 J" r8 i; j+ d9 \6 a! A- @2 Y!  In Ribbon mode - This toolbar will be automatically converted to a
!     Ribbon group and will appear in the "Classic Toolbars as Groups"
2 p" g! y  w2 {4 u!     section in the Customize dialog.
!

TITLE Toolbar (Alternate)
VERSION 170
( h: f+ |6 }( ]: Q1 y+ A, i+ f3 T
BUTTON CUSTOMER_BUTTON_1
LABEL Toolbar(Alt) Button1
RIBBON_STYLE LARGE_IMAGE
1 S& Y& Q" v1 @8 K
8 |- q- b# Y# _; v% B& L5 iBUTTON CUSTOMER_BUTTON_2
9 o( n  h  g4 R7 |% p. t$ KLABEL Toolbar(Alt) Button2
RIBBON_STYLE LARGE_IMAGE

% X# \$ i7 A4 |BUTTON CUSTOMER_BUTTON_3
0 Y1 z! d* f0 v/ v7 ALABEL Toolbar(Alt) Button3
1 L. W2 D/ z$ H3 C* ARIBBON_STYLE SMALL_IMAGE_AND_TEXT
; |2 x/ F; A2 o& L" V4 U
* {( F' {7 U% O. eBUTTON CUSTOMER_BUTTON_4
  T$ K8 f# D; a* R9 X6 s' Y2 \LABEL Toolbar(Alt) Button4
4 Y) {- `6 m$ ^) u. ~: c4 CRIBBON_STYLE SMALL_IMAGE_AND_TEXT
5 S9 i; |  d# F% k3 u$ b
BUTTON CUSTOMER_BUTTON_5
( B/ \- z( ?( D/ n6 wLABEL Toolbar(Alt) Button5
RIBBON_STYLE SMALL_IMAGE_AND_TEXT
: ^6 U5 J+ A! L) m
3 ^9 w3 v( T6 s9 C+ U

6 p9 X4 t2 h/ P+ @customer_group.grb
!
!  Customer Ribbon Group File
!
!  In Classic Toolbars mode - This group will be unavailable
- l/ I: Z; D& h6 G!
!  In Ribbon mode - This group will show up in the "All Groups" list
% s  z( V% e9 f" H!     in the Customize dialog.
; f8 {7 I  t8 P; [+ z: ~!
! m6 ^3 ^$ i& L$ v4 b' z0 y4 n!  The labels of the buttons are defined using the RIBBON_LABEL token in the MEN files
- Y- [: K$ n$ y8 D$ s!
; r# q- a. {+ G
TITLE Group
( j8 M$ c; s0 U( c" N* \5 ]VERSION 170

  c! N" `0 z' Q7 e!  No LABEL defined, using RIBBON_LABEL defined in customer_men.men
BUTTON CUSTOMER_BUTTON_1
RIBBON_STYLE LARGE_IMAGE

!  Example of a gallery defined in a GRB file.
8 l6 V) ]- E3 o$ S  A!
" N  N/ R8 ]# u% K( w) U$ r!  If this gallery is to be used in other places, then it could be
!  defined in its own gallery (GLY) file and referenced here
, X+ I8 x* _8 ~1 h* v) t!  Example:
!    GALLERY customer_gallery.gly
!
: [( A6 X. m/ m0 T$ U) eBEGIN_GALLERY  CUSTOMER_GALLERY
0 ?. _2 `6 A6 w+ \2 k9 XCOLUMN_IN_RIBBON 2
. C$ z: B, ]8 gCOLUMN_IN_POPUP 2
9 @0 s( N# Q( g7 q4 H, T, u+ J, WLABEL Gallery
4 d/ a$ [8 ~& u4 V0 P' Z; p, cGALLERY_STYLE MEDIUM_IMAGE_AND_TEXT
3 J) n9 {0 O6 e2 A
    BUTTON CUSTOMER_BUTTON_2
- D8 M3 g  V- j1 c0 X
    BUTTON CUSTOMER_BUTTON_3

6 f# W9 }" I) L: z" @7 N    BUTTON CUSTOMER_BUTTON_4

/ g8 h0 `. q/ K2 U: }    BUTTON CUSTOMER_BUTTON_5
  ]$ m5 w0 O* `. T0 t) b8 f
END_GALLERY
& A% d) z) |8 s+ `/ L
$ o8 q7 t; n$ Q$ E; P
: O/ a" n+ D- q! r' B( f