Definitely, here is my todo: -finalize any sort of design tweaks to get the pattern matching upto par with previous clients. -add more methods for loading DDR data. Currently we load from filesystem (OpenDDR style), would like to: -load from user defined files -load from user included jar -load from default URL and user defined URL -clean up/polish code, use a standard logger, finalize API, etc
So yes, I think most of this should be ready soon, as in days/week. Radu had mentioned he would like to contribute, so that will be helpful. Eberhard has already ported the client to .NET. Some of my longer term goals: -The DDR data, need to get it updated regularly. Also would like to start cleaning it up and enhancing it. Updates need to happen regularly first... -Supporting a new langauge? PHP? Python? Ruby? If the language supports Lists, Maps, string manipulation, and has decent performance it should be very straight forward. ________________________________ From: Bertrand Delacretaz <[email protected]> To: [email protected] Sent: Wednesday, June 26, 2013 10:15 AM Subject: Re: device map java client On Wed, Jun 26, 2013 at 4:04 PM, Reza <[email protected]> wrote: > ...I think everything left is fine tuning now.... Very cool - I would suggest making a release of that module as soon as you feel it's ready (in the "release early, release often" sense) - that might help get feedback. -Bertrand
