I've worked on a port of Congruity to the new libconcord API, including an update to the Python bindings. Patches are attached to the bug report below.
An overall summary of the congruity changes: -The configuration file parsing had to be moved to the connectivity check page as the parsing function now assumes init_concord() has been called. -The status widgets for connectivity checks, configuration updates, and firmware updates are now dynamically generated based on the callbacks. -Other misc API updates. -This patch for congruity assumes the new API (ie, I did not attempt to retain backwards compatibility with the old API) I have tested this with a 688 (I had to simulate the firmware updates as they do not work on 688 currently) and all seems to work fine. Additional testing and feedback is appreciated! Scott https://sourceforge.net/tracker/?func=detail&aid=3536485&group_id=201579&atid=978130 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
