From my previous blog post for my 0.1 release...
Stated 0.2 expectations:
- Submit a bug report for NetworkManager about the automatic web authentication
- Start hacking the NM code to allow signals to be sent to the extension for various events
- Get the extension to be more like an event listener for the signals being sent
Hopefuls/What I was thinking would be good:
- Double-check that my memory management is proper
- Make the dbusClient constructor accept arguments for DBus interface and object paths, to make it better for others to use
- Along with the above, change extension settings for the XPCOM side to let it be compiled without the name "nmautologin" alowing for the components to be used without the other half
- get the XPCOM to work on all systems (that part of the article simply has "TODO" there)
Modified and met expectations:
- Sent an email to the mailing list for NetworkManager about the automatic web authentication
- Got the extension to run in the background listening for the signals being sent
- Changed extension settings for the XPCOM side to let it be compiled with the name "dbusclient" allowing for the components to be used without the primary extension (could be used by others purely for DBus)
What I hope to have done by submission time:
- Double-check that my memory management is proper
- Make the dbusClient constructor accept arguments for DBus interface and object paths, to make it better for others to use
What I will NOT be doing, for either 0.2, 0.3, or later:
- Start hacking the NM code to allow signals to be sent to the extension for various events
- Consensus is to have daemon running listening to NM and passing on to Firefox
- Firefox extension would need to be able to connect to the DBus System Bus (where NM talks) which is tightly held down, rather than the Session Bus I'm using now
- get the XPCOM to work on all systems (that part of the article simply has "TODO" there)
- With a third program compiled anyways, this makes more sense being compiled specific to the architecture
