John L. Clark wrote: > I am exploring the possibility of adding a new part to the XXE interface > using the GUI customization instructions. This part maintains state, so > it seems like it should be a hidden, "behind the scenes" part when not > being used, but the user will also want to interact with it at times. > Will this require multiple parts, some of which are actions that will > need to ask the App for a reference to the hidden part and then query > that part for information, or is there a way to make a single part > satisfy a set of action requests (like setting it up as an > ActionListener for a set of menu actions)?
The only benefit of splitting an AppPart into a ``hidden'' part and a GUI part is to allow to compose full blown user interfaces as well as alternate, simplified, user interfaces. In the latter case, only the ``hidden'' part is used. Therefore I would recommend creating a single AppPart which has a GUI (even if it is not often used), which maintains its own internal state and which does most of its job behind the scene.
