JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net

The open source
grid computing

 Home   About   Features   Download   Documentation   On Github   Forums 
July 12, 2020, 04:17:45 AM *
Please login or register.

Login with username, password and session length
Advanced search  
News: New users, please read this message. Thank you!
  Home Help Search Login Register  
Pages: [1]   Go Down

Author Topic: page_location for UILauncher?  (Read 3535 times)


  • Guest
page_location for UILauncher?
« on: April 08, 2008, 08:16:32 PM »

UILauncher.main() requires the URL of a 'page_location'.  Does anyone know what this URL is (or if it's documented anywhere). Presumably the url contains the host name or ip address of the system where the jppf server is running but it's not obvious to me what the protocol and port are.



  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2262
    • JPPF Web site
page_location for UILauncher?
« Reply #1 on: April 08, 2008, 09:15:47 PM »

Hello bd,

This feature is really not documented, it's something we need to work on.
Basically, the URL parameter is the location of an XML document from which the entire GUI is generated.
We have implemented a framework that enables the dynamic generation of UI components such as text entry fields, check-boxes, lists, containers, etc...It also allows the setting of the components layout.
The interactions between components are defined through a script directly in the XML document. The script can be any script language that provides interactions witrh Java. We currently use Javascript (Rhino library), but it could as well be Groovy or something else.
You can take a look at the XML for the Admin console in the admin/src/resources/org/jppf/ui/options/xml folder.
This framework provides us with a number of benefits:
  • The GUIs are easier to and faster to build
  • Some automated features such as the persistence of field values through the Java preferences framework. Maybe you noticed that when you enter a value, it will be restored the next time you start the Admin console?
  • Easy localization/internationalization of the UI
  • A lot less trouble with the graphic layout
  • This framework directly generates the UI components (as opposed to generating source code, works only with Swing for now), so theoretically it is possible to add/remove components at runtime, even though we don't use that functionality yet.
  • After a bit of refactoring of the API, it should be relatively painless to use the same XML descriptors for multiple widget toolkits (Swing, SWT, HTML pages or others)
Currently we do not have any plan to make this an actual library in the short term, as we are solely focusing on JPPF features, but we are definitely keeping our attention on it.

I hope this helps,
Pages: [1]   Go Up
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at Fast, secure and Free Open Source software downloads