modularity

问题 I've a relatively large graph with Vertices: 524 Edges: 1125, of real world transactions. The edges are directed and have a weight (inclusion is optional). I'm trying investigate the various communities within the graph and essentially need a method which: -Calculates all possible communities -Calculates the optimum number of communities -Returns the members/# of members of each (optimum) community So far I've managed to pull together the following code which plots a color coded graph

问题 I want to pass a provider right to a component. @NgModule({ declarations:[ SomeComponent.withProviders([provider1,provider2]), AnotherComponent.withProviders([provider1,provider2]) ] }) export class NestedModule{} My question: Can I configure my components while defining them in the module like above? More information: The reason do I need such a thing: I need to define a value provider at module level. The component looks at it's parent component to find say provider1 if it doesn't have one.

问题 The Java tutorials that I read, like to use nested classes to demonstrate a concept, a feature or use. This led me to initially implement a sample project I created just like that: Lots of nested classes in the main activity class. It works, but now I got a monstrous monolithic .java file. I find it somewhat inconvenient and I now intend to break to multiple .java files/classes. It occurred to me, however, that sometimes there may be reasons not to take classes out of their enclosing class.

问题 I have an Activity A hosting two main Fragment F1 and F2 . Both F1 and F2 have nested Fragment , each with its own Listener interface for exchanging data. From what I understood from the answer to this question, the activity A : needs to know every single interface declared by the fragments hosted by F1 and F2 needs to route the events generated by the fragments in F1 and F2 to the correct main fragment, F1 or F2 . If I understood correctly, there is no modularity in this approach: the

问题 I'm studying about detection communities in networks. I'm use igraph and Python For the optimal number of communities in terms of the modularity measure: from igraph import * karate = Nexus.get("karate") cl = karate.community_fastgreedy() cl.as_clustering().membership For supply the desired number of communities: from igraph import * karate = Nexus.get("karate") cl = karate.community_fastgreedy() k=2 cl.as_clustering(k).membership However, I like to do this using networkx. I know get optimal

问题 I am working on a product suite which has 4 products. Right now, all of the configuration data is either in the XML or properties files.This approach is not maintainable as we have to manage different configuration file for different environment(for e.g. Production, Development etc). So, what is the best way to handle configuration data? Also, can we modularize this into a separate module? So that all products can use this module. We don't want to use the property files. I am looking for a

问题 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

问题 I'm creating a node.js project following the class constructor pattern: function my_class(x,y){ this.x = x; this.y = y; } The starting point of the project is the main.js file. Any class of the project must be able to access global objects (such as "world" and "socket") which are defined on main.js . I found 4 options: I define my classes inside main.js . They'll have access to main.js 's globals for being on it's closure, but main.js will become bloated. I move the class to another file such

问题 I'm currently working on my first larger node.js application which should work as modular as possible using plugin-like dependencies. Because I'm in the early stages of development and am also quite new to node, this involves a lot of trial and error hence I need to restart the application a lot. Therefor the start time should be as short as possible. In my case I'm having a file structure like this /lib - core functionality /plugins - local modules, will be moved to external packages later

问题 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