|
4 | 4 |
|
5 | 5 | [For the newbies there is a set of videos that nicely explain nim, jester (and moustachu) and got me up and running..click to view](https://www.youtube.com/watch?v=zSXbifhuZSo&t=600s)
|
6 | 6 |
|
7 |
| -[Wiki - but read below info first](https://github.com/some-avail/json2web/wiki) |
| 7 | +[Wiki - click to go there; but read below info first](https://github.com/some-avail/json2web/wiki) |
8 | 8 |
|
9 | 9 |
|
10 | 10 | ### Introduction
|
11 |
| -Firstly, Json2web is meant for Nim-programmers, not for end-users. It can be seen as a sample-application or small framework, that a programmer can use as a base to create an end-user-app. Therefore (besides code) no executable releases are delivered, which the program is supposed to compile him-/herself. |
12 |
| -Json2web started originally as a set of nim-modules plus their implementation to make it easy to create web-controls, like checkboxes. Based on the principle of separation of concerns, the idea was to create a separate gui-definition in json, from which the gui is generated by specialized procedures. But actually only the complicated elements are generated, the simple ones can be put in project_inner.html. Before Json2web, in Readibl I used nim-constructs for the definition, but that was cumbersome. The project has turned into some subprojects of increasing complexity to showcase those posibilities. The latest subproject is Datajson, which is a generalized database-form (based on Sqlite). The project exposes different options to do things that may or may not be usefull in different situations and could be usefull for learning-purposes. |
| 11 | +Firstly, Json2web is meant for Nim-programmers, not for end-users. It can be seen as a sample-application or small framework, that a programmer can use as a base to create an end-user-app. Therefore (besides code) no executable releases are delivered, which the programmer is supposed to compile him-/herself. |
| 12 | + |
| 13 | +Json2web started originally as a set of nim-modules plus their implementation to make it easy to create web-controls, like checkboxes. Based on the principle of separation of concerns, the idea was to create a separate gui-definition in json, from which the gui is generated by specialized procedures. But actually only the complicated elements are generated, the simple ones can be put in project_inner.html. Before Json2web, in Readibl I used nim-constructs for the definition, but that was cumbersome. |
| 14 | + |
| 15 | +The project has turned into some subprojects of increasing complexity to showcase those posibilities. The latest subproject is Datajson, which is a generalized database-form (based on Sqlite). The project exposes different options to do things that may or may not be usefull in different situations and could be usefull for learning-purposes. |
13 | 16 |
|
14 | 17 | ### Json as gui-definition
|
15 | 18 | The method to do this is that you start with a json-file in which you create the definition of the needed controls or web-elements, based on a template-json-file. In this template-definition all the possible controls are written, which you can alter or copy to accomodate you gui.
|
@@ -65,8 +68,8 @@ The technique to run specific code is based on a textarea-element "curaction" in
|
65 | 68 | - project_inner.html
|
66 | 69 | - project_outer.html
|
67 | 70 | - project_gui.json
|
68 |
| - - /public/css-sheet |
69 |
| - - /public/javascriptfile |
| 71 | + - /public/project_sheet.css |
| 72 | + - /public/project_script.js |
70 | 73 | - /stored_gui_nodes/ use dir only when persistOnDisk is chosen
|
71 | 74 | - try to compile and run the code. When you decide you want to build something based on the code do the following:
|
72 | 75 | - substitute your own projectname for the project (currently datajson) both in the filenames and for constants and variables in the modules themselves.
|
|
0 commit comments