Comments

• 

  about 7 years ago by mvancura | Reply

  There is an Example you may test. In the HTML page directory you can see there is just the page itself, the input YAML file and two JavaScript libraries. No database is needed, the one input file is enough. This file is in the text format readable and writable by both humans and machines, may be placed into a git repository for version control.

  All frontends can use this same data file for different purposes at the same time - it can be read as a configuration file of PTFUtils, for example, and at the same time different HTML pages showing different parts of data in different forms may be set - with no extra service needed, no PHP at webserver, no need to convert the data to different formats at server side at all. Everything is done automatically in the client's browser. The example HTML page shows this: there are three different views defined, you can select it by clicking on top buttons, even more times...

  Of course, another topic is how to maintain the data file. To allow a cooperation of both SW and people. You can see some keys there are expected to be handled by SW (from Clarity etc.) and some of them are definitely manually set (personal notes).

×
Edit Comment 3054
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
There is an [Example](https://w3.suse.de/~mvancura/L3_list/test.html) you may test. In the [HTML page directory](https://w3.suse.de/~mvancura/L3_list/) you can see there is just the page itself, the input YAML file and two JavaScript libraries. No database is needed, the one input file is enough. This file is in the text format readable and writable by both humans and machines, may be placed into a git repository for version control. All frontends can use this same data file for different purposes at the same time - it can be read as a configuration file of PTFUtils, for example, and at the same time different HTML pages showing different parts of data in different forms may be set - with no extra service needed, no PHP at webserver, no need to convert the data to different formats at server side at all. Everything is done automatically in the client's browser. The example HTML page shows this: there are three different views defined, you can select it by clicking on top buttons, even more times... Of course, another topic is how to maintain the data file. To allow a cooperation of both SW and people. You can see some keys there are expected to be handled by SW (from Clarity etc.) and some of them are definitely manually set (personal notes).
 
×
Reply to mvancura
There is an Example you may test. In the HTML page directory you can see there is just the page itself, the input YAML file and two JavaScript libraries. No database is needed, the one input file is enough. This file is in the text format readable and writable by both humans and machines, may be placed into a git repository for version control.
All frontends can use this same data file for different purposes at the same time - it can be read as a configuration file of PTFUtils, for example, and at the same time different HTML pages showing different parts of data in different forms may be set - with no extra service needed, no PHP at webserver, no need to convert the data to different formats at server side at all. Everything is done automatically in the client's browser. The example HTML page shows this: there are three different views defined, you can select it by clicking on top buttons, even more times...
Of course, another topic is how to maintain the data file. To allow a cooperation of both SW and people. You can see some keys there are expected to be handled by SW (from Clarity etc.) and some of them are definitely manually set (personal notes).
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview