Aid the user in creating Navigation Models, such as the one in Fig. 8 of the FrameWeb 2020 paper.
Creating View and Controller packages should already be working, see Section 3.1, Fig. 13 of Igor's work.
Navigation Models should follow the more recent proposal of Pedro's work. Tables 3 and 4 in that paper indicate the stereotypes and associations to support.
Here is a list of features to include to add support to Navigation Models, feel freel to break this issue in smaller ones if you think it's appropriate:
Similar to Fig. 15 of Igor's work, add context menus to add stereotypes to classes in View packages only: <<page>>, <<partial>>, <<form>> or <<binary>>;
Similar to Fig. 18 of Igor's work, add FrameWeb constraints method = <value>, result = <value>, ajax, redirect.
Aid the user in creating Navigation Models, such as the one in Fig. 8 of the FrameWeb 2020 paper.
Creating View and Controller packages should already be working, see Section 3.1, Fig. 13 of Igor's work.
Navigation Models should follow the more recent proposal of Pedro's work. Tables 3 and 4 in that paper indicate the stereotypes and associations to support.
Here is a list of features to include to add support to Navigation Models, feel freel to break this issue in smaller ones if you think it's appropriate:
<<page>>,<<partial>>,<<form>>or<<binary>>;method = <value>,result = <value>,ajax,redirect.