scispace - formally typeset
Journal ArticleDOI

Automatic generation of mobile widgets

TLDR
The authors' automatic generator of mobile widgets translates the XML‐based documents containing the widgets description based on the Widget Markup Language into functional widgets for various available technologies.
Abstract
Purpose – Mobile widgets represent applications exploiting web technologies and providing specific functionalities in an efficient and user‐friendly way. Owing to the low or medium complexity of the mobile widgets, their development may be simplified and optimized through automatic mechanisms. This paper aims to address this issue.Design/methodology/approach – This paper presents an approach to the automatic generation of widgets, which is based on the separation of concerns between the specification of their structural and functional characteristics, and their appearance. The structural and functional features are expressed at a high abstraction level through the authors' Widget Markup Language, while their appearance through pre‐defined or personalized templates. The authors' automatic generator of mobile widgets translates the XML‐based documents containing the widgets description based on the Widget Markup Language into functional widgets for various available technologies.Findings – The main non‐func...

read more

Citations
More filters
Proceedings ArticleDOI

Evaluation of mobile app paradigms

TL;DR: This paper identified four main mobile application paradigms and evaluated them from the developer, user and service provider viewpoints and selected object recognition app, which is both exciting and challenging to develop.

Developing apps for mobile phones

TL;DR: In this article, the authors contribute to the selection of suitable mobile app paradigms in their development by identifying and describing five mobile paradigmologies namely native apps, platform-based apps, mobile widgets, web apps and HTML mobile apps.
Proceedings Article

Developing apps for mobile phones

TL;DR: In this article, five mobile paradigms namely native apps, platform-based apps, mobile widgets, web apps and HTML mobile apps are identified and described and evaluated from developer viewpoint based on a set of selected criteria.
Proceedings ArticleDOI

Selecting the right mobile app paradigms

TL;DR: This paper identified four main mobile application paradigms and evaluated them from the developer, user and service provider viewpoints and selected object recognition app, which is both exciting and challenging to develop.
Journal ArticleDOI

Automatic Generation of Printed Representations of Ecuadorian Electronic Invoices through XML Data Binding

TL;DR: Improvements are shown not only in the generation time of printed electronic invoices but also in more robust and secure mechanisms for handling electronic vouchers through their representations in XML format.
References
More filters
Book

Design Patterns: Elements of Reusable Object-Oriented Software

TL;DR: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Proceedings ArticleDOI

Rich Internet Applications The Next Stage of Application Development

TL;DR: This paper explores technologies deployed in creating RIA, and considers relative merits and limitations of this new style of application development.
Proceedings ArticleDOI

Write Once, Run Anywhere A Survey of Mobile Runtime Environments

TL;DR: The current state and the future of runtime environments suitable for developing RIAs for mobile clients are surveyed.

Modelling and Generating Ajax Applications: A Model-Driven Approach

TL;DR: A UML scheme for modelling AJAX user interfaces based on the MDA approach is proposed and ANDROMDA is adopted for creating an AJAX cartridge to generate an entire AJAX-based web application with automatic back-end integration.
Journal ArticleDOI

Adapting Content

TL;DR: One major goal of the World Wide Web Consortium (W3C) has been device-independent content or as they say in the Java community, "write once, display everywhere."
Related Papers (5)