modularity

Starting from those three declarations : type SharedMsg = SharedAction type Page1Msg = Page1Action type Page2Msg = Page2Action I there a way to obtain an equivalent of the following one? Like a way to "merge" union types ? type Msg = SharedAction | Page1Action | Page2Action ============================= Context : I am splitting an Elm application into one module per page with their own folders. Some actions will be shared, and some actions will be page-specific. If I was to use the Html.map method, I feel that I would have to re-write every shared action that a page uses in its own PageMsg

From MSDN : It is likely that most of the views in your modules will not have to be displayed directly, but only after some action by the user. Depending on the style of application, you may want to use menus, toolbars, or other navigation strategies for your users to access views. In the initialization method of the module, you can also register with the application's navigation structure. In the event handlers of your navigation structure (that is, when a user clicks on a menu item), you might use View Injection techniques to add views to the appropriate regions. I've a similar scenario, I'm

I am currently porting a framework for building applications on J2ME to Android. This framework consists of several projects that compile to libraries (jars). Each individual JAR can contain graphical data (resources, J4ME screens, etc.). Every project generally has a well defined entry point (module). When someone wants to build an application using the framework he must only create a Midlet project and add library dependencies and use the imported classes. We have been using the same approach to develop the Android framework. In this case we have only used normal Java Projects inside Eclipse

I've started toying with JavaFX 2 and I really like the ease with which one can create a UI with FXML. However, once you get past the basic examples and you need a UI with many windows, it seems illogical to have the definition for the whole application's UI in a single FXML file. Is it possible to write separate components in separate FXML files and then include them as needed? Say for example that I wanted a window to popup when the user clicks on an item from the main menu; could I write the definition for that window in a separate FXML file, load it at runtime and add it to the node tree?

My Android main application will consist in a main program, with a few pre-installed modules. Then I want to offer different modules later, best would be as separate files. Modules like: location, weather, agenda. How would you accomplish this? I want to keep in the database the modules that are installed/present. So I must put sometimes the modules into database, maybe by detecting if there are present at launch time. The main app will work based on these modules. How can I build these modules as separate files? They won't be an entry point in my application. So they must not be an

I try to build a modular application using AngularJS. My first idea is to group each module by functionnality with this kind of folder structure : /core controllers.js directives.js app.js /modules /users controllers.js directives.js /invoices controllers.js directives.js /messages controllers.js directives.js ... Notice that the "core" folder contains basics features that will always be in the app. Others modules can be add or remove independently. As my application will be large, I also want to use lazy loading. I implemented this solution : http://ify.io/lazy-loading-in-angularjs/ which