Expanse DSL Rule of Flourida

[咖啡屋的鼠标]

Hi everyone,
   The components in Flex is too many. Shall we expanse our rule of DSL like follow:
   Now,if I want to select a Tab of Tabbar. I may wite the script like this:
===
|click|css=Tabbar[id="xxx"] > Tab [label="yy"]|
===
  
  It looks very strange. Maybe it can be like this:
===
|select|css=Tabbar[id="xxx"]|label|yy|
===

  But in this way the calss of the action "select" will be bigger and bigger. We need another key word.So,it will be like this:
===
|select_tabbar|css=Tabbar[id="xxx"]|label|yy|
===
 
  Now we will create a new Action Class. It's a bad way.Last weekend, I discuss this question with gigix. Now I think shall we support function definition rule like this:
===
|def|function|select_tabbar|$selector|$propName|$propValue|
|click|$selector > Tab [$propName=$propValue]|
|end|

|select_tabbar|css=Tabbar[id="xxx"]|label|yy|
===

  And we can support user import head file like this:
===
|import|zzz.flh|

|select_tabbar|css=Tabbar[id="xxx"]|label|yy|
===
  What's your opinion?