Home

Download

Higthligths

Firsteps

Tutorial

Advocacy

Specs&soluces

Docs

Faq

About AskApy

Contact

Admin

Advocacy



For the most part of his life a system administrator has to deal with a great amount of machines and heterogenuous distributated softwares.

An administrator is not a core developper who spends is life playing with third levels langages.
An administrator deals with scripts, softwares and os commands.

Sometimes for a well defined operation an administrator needs to automate a procedure.
It is at this moment, for a short time of his life, that he becomes a task developper.

This is the reason why writing code for this purpose must be simple, effective, and evolutive.

  • simple
    the langage must be easy to learn and easy to write.
    So this langage must be a script langage.
  • effective
    the langage must be both portable enought to work over heterogenuous Operating Systems.
    the langage must be specific enought to cover the specifics APIs present on a particular system.
  • evolutive
    The langage must be clear and maintainable.
    Often the administator writes the code for himself, first to make his life easier.
    But once the code is available and efficient, demands come from third party users who want to take advandage of this simplicity.
    This is why the code must be re-readable, evolutive and support heavy coding.
    So this langage must also deeply be an object langage.

Often it happens in three steps.

  • Fist step
    The administrator writes the code for himself.
    The code is a simple command with a row trivial parameter.
  • Second step
    The administrator want to provides the code to his closest specialist mates :
    The code is a adapted to provide well defined and checked parameters.
  • Thirds step
    Incomming third party users demands force the administrator to provide a Graphical User Interface to non specialist users.

AskApy help you to realise these steps.

  • Fist step
    You write your task code in an Apb module (in yourmodule.py), with no specifics parameters, but a trivial one.
    You add this Apb in the yourcube.xml descriptor file.
    Your Apb is then available booting to any server of the architecture :
    As a command (using the ask.py command) with an unique trivial parmeter.
    As a graphical user interface (using the AskApy graphical client interface view.py or a browser).
    It represents a form, with a component for this unique trivial parmeter.

  • Second step
    You describes your specfics parameters in yourmodule-desc/parameter.py.
    Your Apb is then available booting to any server of the architecture :
    As a command (using the ask.py command), with a list of your specific parameters.
    As a graphical user interface (using view.py or a browser).
    It represents a form, with a list of component with the specifics characteristics of your parameters.

  • Third step
    You want to enhance your GUI.
    You use the AskApy graphical framework to write your specific yourmodule-desc/view/call.py (and perhaps yourmodule-desc/view/retrn.py).
    Your Apb is then available booting to any server of the architecture :
    As a command (using the ask.py command), with a list of your specific parameters.
    As a graphical user interface (using ApbViewer or a browser).
    It represents a form with your GUI specific layouts.