These are thoughts about transitions between plug-in views. Especially after I had a chat with Kaleo, yesterday, I would like to post my thoughts about this.
h1. Transitions h2. Introduction Some plug-ins need different views for themselves. For example a player plug-in could have a view with a list of files and a view to play a file (or the list). In one view the list is in foreground and the player in the back and in the other view it is vice versa. As for now the Elisa-Project holds only experimental support in thezerofive branch to handle the transition and programming of these views. These are only in Draft state and far from final, furthermore it seems the structure is not fully implemented, yet. We will create a Plug-in with multiple views to demonstrate the way these transitions could work. h2. Idea The Idea behind our plug-in is to get closer to the model-controller-view pattern and be flexible in the design of each view. Furthermore impressive transitions will be made possible. Our plug-ins will have a modell for calculations and data-access to external libraries/sources. Also it will include (atleast) one view. In each view states of PGM-Drawables will be saved. The controller finally decides which view to choose for example by user input. h2. Example have a look at the attachment, please. File-Structur could be: elisa/plugins/myplayer/setup.py elisa/plugins/myplayer/plugin.conf elisa/plugins/myplayer/model elisa/plugins/myplayer/model/player.py elisa/plugins/myplayer/model/filelist.py elisa/plugins/myplayer/main_controller.py elisa/plugins/myplayer/views/ elisa/plugins/myplayer/views/main.py elisa/plugins/myplayer/views/player.py elisa/plugins/myplayer/views/filelist.py
<<attachment: Transition-FileList.png>>
