Hello! Recently I read an article on Meteor's package based architecture. http://experimentsinmeteor.com/package-based-architecture/
I am really impressed by this approach. Few advantages of adapting to this approach are: * `meteor update` command can handle app updates * Each independent feature becomes a package. Removing a certain package will just remove a particular functionality but the application will still work. * OGV API: OGV packages will serve as an API for other Meteor applications. Thus getting a wide range of developers interested in OGV I tried dividing OGV's functionality into packages and came up with following: * OGV:Converter Converts a .g file to .obj file * OGV:Uploader Uploads file to OGV server * OGV: Viewer Enables the app to view the uploaded model * OGV: Search Enables to search for models or users * OGV: Accounts Adds permission and roles to users * OGV: Notifications Beautiful notifications for each update in OGV Above is a rough list I could figure out myself. May require some discussion for finalizing the OGV package list. Hoping to get the best out of it. -- Fear is wisdom in the face of danger. It’s nothing to be ashamed of Gauravjeet Singh http://github.com/gauravjeetsingh ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
