Question about OLD vs. NEW parsing syntax

[Barry Treahy <treahy@mmaz.com>]

As a new MV user, I have what I guess is more of a style question than
anything regarding the MV syntax changes moving from OLD to NEW and, perhaps
because I am new, I find this conflicting or perhaps I need a better understanding
of MV.

I understand that the new format appears like (a snippet from ord/basket):

    <FORM ACTION="[process-target secure=1]" METHOD="POST">
      <INPUT TYPE="hidden" NAME="mv_session_id" VALUE="[data session id]">
      <INPUT TYPE="hidden" NAME="mv_doit" VALUE="refresh">
      <INPUT TYPE="hidden" NAME="mv_orderpage" VALUE="ord/basket">
      <INPUT TYPE="hidden" NAME="mv_checkout" VALUE="ord/checkout">
      <INPUT TYPE="hidden" NAME="mv_nextpage" VALUE="ord/basket">
 
      <BR>
      <TABLE BORDER="0">
        <TR><INPUT TYPE="submit"
         
          NAME="mv_click" VALUE="Add this Item">
        </TR>
      </TABLE>

yet I personally find this easier on my eyes and have numerous instances where I can only do what I want using the old style of MV tags:

[set Add this Item]
  mv_session_id=[data session id]
  mv_doit=refresh
  mv_todo=refresh
  mv_orderpage=ord/basket
  mv_checkout=ord/checkout
  mv_nextpage=ord/basket
[/set]

    <FORM ACTION="[process-target secure=1]" METHOD="POST">
      <TABLE BORDER="0">
        <TR><INPUT TYPE="submit"
         
          NAME="mv_click" VALUE="Add this Item">
        </TR>
      </TABLE>

I mentioned that there seems to be things I cannot do with the new format and what I'm specifically referring to, is having numerous buttons in the same form, each with a different MV functions.  If this can be done with the new format, how would one go about doing that?

TIA 

Barry