Difference between revisions of "GCube Web Site and Distribution Site"
Luca.frosini (Talk | contribs) |
Luca.frosini (Talk | contribs) |
||
| Line 4: | Line 4: | ||
<del> | <del> | ||
Clicking on the first, would move the user to the gCube Software Artefact distribution page while clicking on the later would move her to the gHN Distribution page. The gCube Software Artefact distribution page should be a dynamically generated, backed by a Joomla! component, page that should gather information generated by the ETICS Build Reports tool and present it to whoever interested, in a user-friendly fashion. By default, this page would present the current Stable release, though previous Stable releases as well as the current Integration and Development ones, will also be made available from the same page through an on-screen menu. | Clicking on the first, would move the user to the gCube Software Artefact distribution page while clicking on the later would move her to the gHN Distribution page. The gCube Software Artefact distribution page should be a dynamically generated, backed by a Joomla! component, page that should gather information generated by the ETICS Build Reports tool and present it to whoever interested, in a user-friendly fashion. By default, this page would present the current Stable release, though previous Stable releases as well as the current Integration and Development ones, will also be made available from the same page through an on-screen menu. | ||
| + | </del> | ||
[[File:Distr.jpeg|center|frame]] | [[File:Distr.jpeg|center|frame]] | ||
| + | <del> | ||
On the other hand, clicking on the gHN Distribution anchor should link to a page with a descriptive article and a pointer to the latest gHN available for download. | On the other hand, clicking on the gHN Distribution anchor should link to a page with a descriptive article and a pointer to the latest gHN available for download. | ||
| + | </del> | ||
[[File:Distr1.jpeg|center|frame]] | [[File:Distr1.jpeg|center|frame]] | ||
| + | <del> | ||
The information presented in the gCube Software Artefact distribution page is retrieved automatically from distribution.xml and certification.xml files generated by ETICS Build Reports. This way, changes within a Release Cycle are automatically reflected the page without any additional effort. On the other hand, in order to add a new Release for download from the gCube Website, the site administrator has to update the releases that point to each version (e.g. stable or integration). A version that stops to be considered as either integration or stable is tagged as a previous. An important point, are the links to the documentation wiki pages. These cannot be retrieved automatically and so they are constructed using a service name to corresponding Wiki link, mapping database table. This table is part of the gCube Software Artefact distribution Joomla! component and is maintained by the site administrator. Thus, with the introduction of a new component the developer should also provide the corresponding documentation Wiki page and contact the site administrator in order, for the later, to update the mapping file with the map for the new component. | The information presented in the gCube Software Artefact distribution page is retrieved automatically from distribution.xml and certification.xml files generated by ETICS Build Reports. This way, changes within a Release Cycle are automatically reflected the page without any additional effort. On the other hand, in order to add a new Release for download from the gCube Website, the site administrator has to update the releases that point to each version (e.g. stable or integration). A version that stops to be considered as either integration or stable is tagged as a previous. An important point, are the links to the documentation wiki pages. These cannot be retrieved automatically and so they are constructed using a service name to corresponding Wiki link, mapping database table. This table is part of the gCube Software Artefact distribution Joomla! component and is maintained by the site administrator. Thus, with the introduction of a new component the developer should also provide the corresponding documentation Wiki page and contact the site administrator in order, for the later, to update the mapping file with the map for the new component. | ||
</del> | </del> | ||
Revision as of 17:26, 7 September 2015
The gCube Website, found at [1] is a portal, based on Liferay, for distributing all information related to the gCube technology. Among others, the gCube website offers the tools for the distribution of software produced by the Project. Thus, a dedicated section, named "Downloads" (under Developer section ) is available from the Website's menu bar. The page contains basic information about the software that is distributed through the site.
Clicking on the first, would move the user to the gCube Software Artefact distribution page while clicking on the later would move her to the gHN Distribution page. The gCube Software Artefact distribution page should be a dynamically generated, backed by a Joomla! component, page that should gather information generated by the ETICS Build Reports tool and present it to whoever interested, in a user-friendly fashion. By default, this page would present the current Stable release, though previous Stable releases as well as the current Integration and Development ones, will also be made available from the same page through an on-screen menu.
On the other hand, clicking on the gHN Distribution anchor should link to a page with a descriptive article and a pointer to the latest gHN available for download.
The information presented in the gCube Software Artefact distribution page is retrieved automatically from distribution.xml and certification.xml files generated by ETICS Build Reports. This way, changes within a Release Cycle are automatically reflected the page without any additional effort. On the other hand, in order to add a new Release for download from the gCube Website, the site administrator has to update the releases that point to each version (e.g. stable or integration). A version that stops to be considered as either integration or stable is tagged as a previous. An important point, are the links to the documentation wiki pages. These cannot be retrieved automatically and so they are constructed using a service name to corresponding Wiki link, mapping database table. This table is part of the gCube Software Artefact distribution Joomla! component and is maintained by the site administrator. Thus, with the introduction of a new component the developer should also provide the corresponding documentation Wiki page and contact the site administrator in order, for the later, to update the mapping file with the map for the new component.
