Differences between compiling a VC model with Flash or Web Dynpro

Question

Hello forum,
Is there anyone capable of telling me what are the main differences between compiling a Visual Composer model with Flash compiler or Web Dynpro compiler.
I've noticed that some important features aren't available when I use the WD compiler, such as creating a popup directly from the output of a table and I can't install a scroll bar to navigate through the table records (it only allows me to place some navigation buttons in the bottom of the table, and this is not a very user-friendly solution).
If you were me, would you choose the Flash compiler?
By the way, do you know a way to increase the performance of a report created with VC? When I execute the iView on the Netweaver Portal, I see that a iview compiled with Webdynpro consumes less 15MB of memory when running the report than a similar iview compiled with Flash.
Thank you.
Regards,
Ricardo Inácio

Answer 1

I found this old post while searching for something else. The main difference between Flash and Web Dynpro modes is that Flash works and Web Dynpro most emphatically does not. Some of the (many) disadvantages of Web Dynpro mode.
1. It will not let you design your own screens. The designer will let you resize and position your fields thus giving you the illusion of being in control, but at runtime it will resize your fields and position them where it thinks fit.  This greatly increases development time since you can never be sure what any changes you make to your screen will look like until you run it.  
2. You cannot include horizontally and vertically aligned fields in the same form; depending on the option you choose it will align them all vertically or horizontally.  Which means that if you do need eg a horizonal row of pushbuttons at the top of your screen followed by a set of vertical fields, you have to use a separate form for each. 
3. You cannot use the Editing mode = Read-only mode to make all the input fields in a form non-entereable.  You can select it in the designer,but at runtime it doesn't take a blind bit of notice.  The only way to make a field non-enterable is to check the Disabled box which turns it a very pale and almost invisible grey which looks awful.
4. You can't change the font or colour of texts.
5. Lots of the controls are not available eg the clock.
6. You cannot create toolbars on forms, or rather you can but at runtime it just ignores them. 
7. Adding a hyperlink to a pushbutton does not do anything (this is my latest discovery).
All of the above work in Flash mode.  We have to use Web Dynpro because we need the screens to work with screen readers for visually impaired viewers, but anyone who does not have this constraint should avoid using it like the plague.