code-organization

What is the best way to organize code that belongs to the same project in a Python development environment? What are the do and donts of Python project organization? Do you separate each class in a file? Project A Classes "subsystem1" class1 class2 subsystem1Module "subsystem2" "utils" "etc" Tests Whatever etc? Any suggestions? Oh, and please describe what are the (possible) problems of each type of organization. What are considered best practices for organizing Python code? Some suggestions are at http://jcalderone.livejournal.com/39794.html and http://infinitemonkeycorps.net/docs/pph/ There

The famous Best Practice Recommendations for Angular App Structure blog post outlines the new recommended angularjs project structure which is now component-oriented, not functionally-oriented, or as named in the initial github issue - "Organized by Feature". The blogpost suggests that each file inside each module should start with the module name, e.g.: userlogin/ userlogin.js userlogin.css userlogin.html userlogin-directive.js userlogin-directive_test.js userlogin-service.js userlogin-service_test.js The question is: what is the point, pros and cons of repeating the module name inside each

I'm using GIT to manage a Content Management System (CMS) project. The CMS can have multiple plugin (module). So basically, I want to have 3 types of repositories: The core CMS development ( every new project is a checkout of that last stable & unconfigured version ) 1 repository per module/plugin. ( every new project will checkout the last stable version of the module they want to implement ) 1 repository per project ( each client will be a repository that represent the personalization from the core CMS and the modules ) For the type 1 & 2, I guess it's simple basic repository. But when it

Let's say I have a namespace like that: var myNamespace = { foo: function() { }, bar: function() { } }; What is the best way to split this code into files defining foo and bar separately? I'm not worried about loading time - I'll concatenate it back into one file before deployment. At the start of each file: if(myNameSpace === undefined) { var myNameSpace = {}; } File 1: myNamespace.foo = function()... File 2: myNamespace.bar = function()... // File1: // top level namespace here: var myNamespace = myNamespace || {}; // File2: myNamespace.foo = function() { // some code here... } coderPatros In

How do you decide between writing a function inside a module or as a static member of some type? For example, in the source code of F#, there are lots of types that are defined along with a equally named module, as follows: type MyType = // ... [<CompilationRepresentation(CompilationRepresentationFlags.ModuleSuffix)>] module MyType = // ... Why don't you simply define the operations as static members of type MyType? Here are some notes about the technical distinctions. Modules can be 'open'ed (unless they have RequireQualifiedAccessAttribute). That is, if you put functions ( F and G ) in a

JAVA - NETBEANS This is an IDE question I am always working with collapsed methods, because I want to be able to see my methods all together. This is a little time consuming because I have to use the mouse to scroll up to the declaration of the method and click on the - (minus) icon. And then respectively go to the method I want to work on and click on the + (plus) icon. Is there a way through a keyboard shortcut to do the collapse (and respectively the expand)? Peter Tillemans I copied a piece from http://wiki.netbeans.org/KeymapProfileFor60 . The first option is for Win/Lin and the second

Just to keep things interesting and close my final open question, the solution that implements the below functionality in a nicely organized manner with a decent architecture gets a good bounty. The full code is on jsfiddle, and feel free to ask any questions :) How do you usually organize complex web applications that are extremely rich on the client side. I have created a contrived example to indicate the kind of mess it's easy to get into if things are not managed well for big apps. Feel free to modify/extend this example as you wish - http://jsfiddle.net/NHyLC/1/ The example basically