We want to find our service quick !  So many services now, who has time to scroll ?
Now in the SwingGui - Search !  (honestly should have done this years ago ;)

Servo Joystick & Arduino seem to work over a remote connection now (mostly) - BoardInfo & DeviceSummary were not serializable (fixed)

There are still a few issues regarding displaying of ports and some other thing - most can be fixed by using asynchronous messaging in the SwingGuis.  If you use the Service directly (except in onState) it will probably cause problems ...

Oh .. and don't create a service when they are connected - interesting endlless service tabs are created 

Original Joystick was worky - but only for specific models of joystick which had hardcoded component names.  Then Joystick Gui was borked . Now ! Joystick Gui is dynamically built based on what it finds in the components - it can inspect and attempt to interface with anything jinput can find.

There are lots of updates to the SwingGui although some of them are not evidently noticible.  On is that messaging in the SwingGui is closer now in design to the routing of messages and callbacks in the WebGui

On advantage of this is the ability now to create "Widgets".  Swing Widgets are simple objects which allow you to "view" some aspect of a service through the tab UI of another service.  Take Serial for example.  "Everything" needs the serial service, so its nice to be able to "view" the controls of connect/disconnect, port selection, and refreshing ports through the Service your using (e.g. like Arduino)

This 'sort-of' worked before, but it was a mess, each service copy/pasted parts of the SerialGui into there own.  Some worked .. some did not.  But Now !!  There's just a single PortGui !!!

And it always behaves the same, and it works !  And its as simple as this:

portGui = new PortGui(serial.getName(), myService, tabs);
addTop(3, portGui.getDisplay());

That's it .. 2 lines - make it & display it...  it takes care of everything else ...

GUIService is now Swing ! - with no more freezing !

Good News .. All compilation errors are fixed, I've gone through "some" Swing user interfaces and fixed them up (using the new ServiceGui helper methods .. e.g. addLine etc.)
OH .. AND I FIXED THE YEAR OLD BUG OF THE GUI FREEZING ON STARTUP !!! - also lots and lots of clean up.

Bad News ... GUIService is NO LONGER GUIService .. Service names should be implementation specific.  hence for this day forward GUIService will now be "Swing" .. I've fixed and synced everything I could on "develop" branch - including all scripts in Pyrobotlab (develop branch) ..   This is also in preperation for JavaFX as it is the next "Swing" for native windows Java UIs.

Please let me know if you run into any problems - thanks ..

MQTT Gui .. 
Now it worky  !  There was much refactoring and a bit of learning Mqtt ...  

Its fun to send messages to a Mqtt broker .. but its funner to connect MRL instances through it  !
(That will be step 2) :)

Categories are Worky ! (again)

I've been having fun refactoring the Swing GUIService.  I've learned a considerable amount about user interfaces, Swing, MVC and a bit about JavaFX since I started the GUIService a gazillion years ago.  In the process of cleaning up all the sins I committed in the past (ie spaghetti code) I've been re-writing service guis and testing them.  

When I started updating KeyboardGui I cam across Mat's added gem.  He Borg'd in jnativehook project - which puts a global hook into keyboard & mouse.  I moved it from the KeyboardGui into the service.  It publishes keyboard and mouse events if MRL loses focus, or even if there is no gui at all !  Thanks Mats !

I've made ui helper methods in the ServiceGui (parent class to all Swing service panels) - and it can produce the keyboard ui with only 4 lines of code.  Adding more stuff is as simple as adding more panels or lines of variables or labels.   

public KeyboardGui(final String boundServiceName, final GUIService myService, final JTabbedPane tabs) {
    super(boundServiceName, myService, tabs);
    addPanel("keyboard");
    addLine("key", lastKey, "code", lastKeyCode);
    addPanel("mouse");
    addLine(mouseX, ",", mouseY);
  }

There is no longer any init() .. all gui construction is done in the service gui's constructor.  The init() was residual from Applet programming.

getState(Service service)  has been changed to onState(Service service) 

public void onState(Keyboard keyboard) {
    SwingUtilities.invokeLater(new Runnable() {
      @Override
      public void run() {
      }
    });
  }

This goes with the rule where :

         publish{Method}  ---will call --> on{Method}  or
         get{Method}  ---will call --> on{Method}

@Override
  public void subscribeGui() {
    subscribe("publishKey");
    subscribe("publishKeyCode");
    subscribe("publishMouseMoved");
  }

  @Override
  public void unsubscribeGui() {
    unsubscribe("publishKey");
    unsubscribe("publishKeyCode");
    unsubscribe("publishMouseMoved");
  }

Not sure how long it will take me .. but with the new structure and helper methods - the code is substantially smaller and cleaner...

Still have more work before I check in ...  back to the polishing !