On Fri, 5 Jul 2013, Phil Dibowitz wrote: >> Since you're back...so, for supporting the Harmony Link, we're going to >> need to make an addition to the API to support setting it up. For >> configuring it, we have to set Wifi parameters, set a room name, set email >> address, etc. Because the of the way these things are setup using the >> "MH" protocol - you basically read/write to different "files" on the >> device, I was thinking about maybe just adding a couple of generic calls >> and handling the details of the different files at a higher level. As in >> something like: >> >> mh_read_file(filename, buffer) >> mh_write_file(filename, buffer) >> >> rather than adding calls for the specific things: >> >> mh_configure_wifi(ssid, key) >> mh_scan_wifi(buffer) >> mh_configure_room(room) >> mh_configure_email(email) > > That leaves a whole lot of very special knowledge up to the caller > (concordance, or some other client app). > > I think typically in the Remote classes we've provided things like read_file() > and write_file() then in libconcord we provide things like mh_configure_wifi() > - and that seems like a good trend to continue.
Ugh, OK. I was looking forward to offloading some of the heavier parsing work to Python rather than doing it in C. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel