Action script 5 learning content manager
5692
$$
- Posted:
- Proposals: 0
- Remote
- #6963
- Archived
Description
Experience Level: Intermediate
Learning tool written in action script 5.
In order to permit maximum re-use of content, the tool separates the content, the layout of the
elements and the design of the training modules.
In the tool, the content is stored independent of the positioning of the elements (template) and of
the graphics presentation (style).
A screen is defined by
- The elements that compose it (text, media, buttons)
- The display surface for the elements (one may want to reserve parts of the screen for
navigation buttons, designs or logos)
- The layout of the elements as a function of the display surface available
- The style of the text fields and the graphic identity used for the screen and the different
elements.
These elements are stored in different files and assembled at the moment of display. So it is easy
to modify one part without changing the rest.
To display a screen, the template needs 4 files :
- data.xml: here are the data. Each screen has its own data file data.xml. The name of this
file is the ID of the screen (defined in structure.xml, see next chapter) concatenated with
_data.xml .
- ui.xml: these are the display and style parameters. Each screen also has its own xml file.
The name of this file is the ID of the screen (defined in structure.xml, see next chapter)
concatenated with _ui.xml.
- asset.swf: here are all the graphic elements needed for the display (bullets, backgrounds,
icons, etc...). This file is common to the whole module.
- style.css: these are the styles for each text component. This file is common to the whole
module.
In order to permit maximum re-use of content, the tool separates the content, the layout of the
elements and the design of the training modules.
In the tool, the content is stored independent of the positioning of the elements (template) and of
the graphics presentation (style).
A screen is defined by
- The elements that compose it (text, media, buttons)
- The display surface for the elements (one may want to reserve parts of the screen for
navigation buttons, designs or logos)
- The layout of the elements as a function of the display surface available
- The style of the text fields and the graphic identity used for the screen and the different
elements.
These elements are stored in different files and assembled at the moment of display. So it is easy
to modify one part without changing the rest.
To display a screen, the template needs 4 files :
- data.xml: here are the data. Each screen has its own data file data.xml. The name of this
file is the ID of the screen (defined in structure.xml, see next chapter) concatenated with
_data.xml .
- ui.xml: these are the display and style parameters. Each screen also has its own xml file.
The name of this file is the ID of the screen (defined in structure.xml, see next chapter)
concatenated with _ui.xml.
- asset.swf: here are all the graphic elements needed for the display (bullets, backgrounds,
icons, etc...). This file is common to the whole module.
- style.css: these are the styles for each text component. This file is common to the whole
module.
Edward C.
100% (2)Projects Completed
3
Freelancers worked with
3
Projects awarded
20%
Last project
10 Apr 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies