1 / 16

Condor user interfaces for mobile terminals

Condor user interfaces for mobile terminals. Javier Vales Alonso (jvales@delta.ait.uvigo.es) Javier González Castaño (javier@ait.uvigo.es) Universidad de Vigo (Spain). Outline. Goals Mobile internet & wireless technologies Portable devices and their hierarchy Web system architecture

annice
Download Presentation

Condor user interfaces for mobile terminals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Condor user interfaces for mobile terminals Javier Vales Alonso (jvales@delta.ait.uvigo.es) Javier González Castaño (javier@ait.uvigo.es) Universidad de Vigo (Spain)

  2. Outline • Goals • Mobile internet & wireless technologies • Portable devices and their hierarchy • Web system architecture • WAP system architecture • Examples • Conclusions & future work

  3. Goals • Integrate Condor in the mobile internet world. • Allow different levels of user accessibility. Or: ¿what is missing in Condor to face the mobile Internet?

  4. Mobile Internet • Internet technologies and services for mobile devices. • Mobile-Internet is driven by the convergence of: • Wireless technologies • Portable devices

  5. Wireless technologies • They will enable easy interconnection of a wide range of portable computing devices. • Present: 2G systems (GSM, IS-95). • Incoming: Wireless LAN (IEEE 802.11), Bluetooth, HomeRF, LMDS, 3G systems (UMTS).

  6. Mobile devices • (Wireless) laptops (first mobile solution) • PDAs (Palm pilot, pocketPC,...): user interface with limited capabilities. Handwriting recognition. • WAP-enabled mobile phones: user interface even more limited. • Next: Wearable computers (less comfortable, need goggles). Speech recognition.

  7. Condor Condor • Program tuning: • Final-stage programming utility • Small modifications in source code • Program generation • Check queue status • Remove, hold & release jobs • Submit new jobs • Alarm on job finish Usability • Check queue status • Remove, hold & release jobs • Submit new jobs • Program tuning +

  8. Layer implementation • PDA layer is implemented as a web service. This has many advantages: • Familiar interface. • WAP system implementation is a subset of PDA system implementation (compatibility & reutilization) • Almost all PDAs have web browsers (platform independence) • WAP layer uses WML browsers.

  9. Web system architecture HTTP Server 1. Operation request 3. Non-Condor command mapping 2. Condor command mapping CGI CGI HTML HTML Condor-enabled system Non-Condor commands Condor commands

  10. WAP system architecture HTTP Server WAP G A T E W A Y 1. Operation request 3. Non-Condor command mapping 2. Condor command mapping CGI CGI WML WML Condor-enabled system Non-Condor commands Condor commands A L A R M

  11. WAP system overview

  12. WAP system example - Job submission

  13. Web system overview

  14. Web system overview

  15. Web system overviewProgram tuning

  16. Conclusions & future work • Definition of usability-hierarchy for mobile internet devices • Assumption: Cell phone/PDA units everywhere • Remote execution of most functions • Other paradigms: Interface servers (X-Windows, Citrix)?

More Related