What's new? | Help | Directory | Sign in
Google
one-click-installer
Tool and file format to provide one-click installation of third party applications independent of Linux distribution used
  
  
  
  
    
Search
for
Updated Aug 06, 2007 by krzysztof.lichota
Labels: Phase-Implementation
OneClickInstallerTool  
Description of One Click Installer wizard implementation.

Introduction

This page describes most important implementation details of One Click Installer tool.

For changelog, see http://one-click-installer.googlecode.com/svn/trunk/one-click-inst/debian/changelog

For Todo list see Todo.

Details

Implementation language

One Click Installer is written in Python, so it does not require recompilation for each architecture and speeds up development.

Frontend

Application is split strictly into backend and frontend to allow easy porting to various frontends.

Communication between backend and frontend is based on simple commands like "show page with choice, first choice is XX, second YYY, return choice to backend". This should greatly simplify implementing other frontends.

Current implementation provides only one frontend using Qt 3 library.

Backend

Backend is independent from frontend and runs in separate thread, so its execution is sequential.

Currently APT backend is implemented, more backends should be possible to add by abstracting installation backends functionality.

APT backend

Current backend implements managing APT repositories using apt-get, apt-key tools and parsing /etc/apt/sources.list.

Installation is done using apt-get install, but it should be easy to switch it to some method providing more feedback, for example using Synaptic or Adept Batch.

During installation debconf frontend is forced to be Qt to show debconf configuration pages.

Localization

Application interface can be localized using standard Gettext .po files.

See: http://one-click-installer.googlecode.com/svn/trunk/one-click-inst/translations/


Sign in to add a comment