re-structurize demos #51
Conversation
A proposal for a demos structure. * demo files are moved to the demo directory * js files moved to the demo/js directory * localization files moved to the demo/l10n directory * fixed Grunt.js and .gitignore according to the new structure A list of demos is not complete. There are some new demos and some rewritten old demos.
|
? |
|
I don't know is it necessary to show in demos how to use a loader with a url parameter. Let it lie down here. Maybe, it will be useful someday. Maybe, not ) |
|
@DWand If you have another demo which isn't covered yet, feel free to add it :) |
|
@PascalPrecht here it is #54. |
|
We have already a server for such purpose. If you start In case you really need to use NodeJS, we can apply an additional server.js right into this. |
|
@knalli, it's not necessary a NodeJS. It might be anything, which can handle a GET request and send back a correct response. I know, that there is server provided by grunt (or something like this), but I don't know how to use it )) I usually work with PHP on the server side. It would be great (or, at least, interesting), if you can show how to handle this situation. |
|
If you only need static files served by a server (i.e. for XHRs), just place the files in the corresponding demo folder. You can fetch them with For routing, you can base your stuff on my #55. |
|
Static files are working pretty good even without server :)) But in 9 example we use a registerLoader with URL. And a module requests for translations like: [given_url]?lang=[langCode]. So, that page (which is requested) would to understand this GET parameter and handle it. |
|
The routes (you have already made them) are stored in |
|
#54 is updated |
A proposal for a demos structure.
A list of demos is not complete. There are some new demos and
some rewritten old demos.