Good approaches for packaging PHP web applications for Debian
Many PHP web applications follow this model for installation and upgrade:
How to modularize and package a client-side Javascript library today?
I’ve been catching up with the modern client-side JS ecosystem and reading up on CommonJS and AMD (incl. associated tools – browserify, requirejs, onejs, jam, dozens of others). If I’m writing a Javascript library, how do I modularize/package it such that it can be most broadly accessible (ideally by users who swear by CommonJS, AMD, and especially neither)?
What are the benefits of having a remote database for your command line utility
I’m current working on a command line app that will grab resources online for you when you’re setting up a new project locally. Right now all the urls for the resources I need are hardcoded into the application and adding new targets require updating the software.
How do I know when should I package my classes in Ruby?
In Ruby, I’m creating a small game development framework. Just some personal project – a very small group of friends helping.
How do I know when should I package my classes in Ruby?
In Ruby, I’m creating a small game development framework. Just some personal project – a very small group of friends helping.
How do I know when should I package my classes in Ruby?
In Ruby, I’m creating a small game development framework. Just some personal project – a very small group of friends helping.
How do I know when should I package my classes in Ruby?
In Ruby, I’m creating a small game development framework. Just some personal project – a very small group of friends helping.
Component design: getting cohesion right
I currently have a set of components named DataValues, ValueParsers, ValueFormatters and ValueValidators. The first one defines an abstract base class DataValue and contains a whole load of implementations. The 3 other components each define in interface similar to their name (minus the “s”), and also contain a bunch of implementations of those. These 3 depend on DataValues. There are no further dependencies.
Component design: getting cohesion right
I currently have a set of components named DataValues, ValueParsers, ValueFormatters and ValueValidators. The first one defines an abstract base class DataValue and contains a whole load of implementations. The 3 other components each define in interface similar to their name (minus the “s”), and also contain a bunch of implementations of those. These 3 depend on DataValues. There are no further dependencies.
Component design: getting cohesion right
I currently have a set of components named DataValues, ValueParsers, ValueFormatters and ValueValidators. The first one defines an abstract base class DataValue and contains a whole load of implementations. The 3 other components each define in interface similar to their name (minus the “s”), and also contain a bunch of implementations of those. These 3 depend on DataValues. There are no further dependencies.