Hey, KK. On Apr 11, 2013, at 5:11 PM, kk yap wrote: > I am trying to figure out is POX's betta branch supports any GUI.
None are *supported*. :) The older branch included a GUI based on the one in NOX. With betta, a decision was made to not include any GUI in POX itself, so the old GUI should theoretically be repackaged as a separate project, but it hasn't been. This is probably largely because Kyriakos left us. ;) However, it should also be noted that Kyriakos has a fork which includes an extended version of that GUI. POXDesk was my really quick stab at putting together a basic example/framework for web GUIs, and packaging it as a separate project. It should more or less work in betta. It's not particularly well maintained, but I'm generally happy to try to fix bugs when they're brought to my attention (I'm also open to reasonable feature suggestions and pull requests!). > I tried POXDesk (https://github.com/MurphyMc/poxdesk) but that is > looking for WebServer and MessengerNexus_of_service, both of which I > have failed to locate. Making the component naming of shipped components more obvious / easier to understand is a goal for the carp branch. :) The POXDesk repo actually has a few entries on the wiki which hopefully make this clearer: https://github.com/MurphyMc/poxdesk/wiki/Getting-Started The punchline is probably: ./pox.py samples.pretty_log web messenger messenger.log_service messenger.ajax_transport openflow.of_service poxdesk It might make sense to include a little component in POXDesk (or a secondary launch function, maybe) that fires all of those up itself. :) > I am clearly green with POX here, so some help is appreciated. Hope that helps. -- Murphy
