madlib-settings
v0.1.7
Published
Centralised settings for other madlib modules
Downloads
9
Readme
madlib-settings
Used to turn output from madlib-xml-objectifier into an XML string
acknowledgments
The Marviq Application Development library (aka madlib) was developed by me when I was working at Marviq. They were cool enough to let me publish it using my personal github account instead of the company account. We decided to open source it for our mutual benefit and to ensure future updates should I decide to leave the company.
philosophy
JavaScript is the language of the web. Wouldn't it be nice if we could stop having to rewrite (most) of our code for all those web connected platforms running on JavaScript? That is what madLib hopes to achieve. The focus of madLib is to have the same old boring stuff ready made for multiple platforms. Write your core application logic once using modules and never worry about the basics stuff again. Basics including XHR, XML, JSON, host mappings, settings, storage, etcetera. The idea is to use the tried and proven frameworks where available and use madlib based modules as the missing link.
Currently madLib is focused on supporting the following platforms:
- Web browsers (IE6+, Chrome, Firefox, Opera)
- Appcelerator/Titanium
- PhoneGap
- NodeJS
installation
$ npm install madlib-settings --save
usage
var settings = require( "madlib-settings" );
// Use init for default settings that wont be set if a value already exists
//
settings.init( "timeout", 30000 );
// The 2nd parameter to get is the value that will be returned if no setting exists yet
//
currentTimeout = settings.get( "timeout", 15000 );
// You can remove a single setting or purge all settings (!!) if you are so inclined
//
settings.unset( "timeout" );
settings.pruge()