gina 0.1.1-alpha.106 → 0.1.1-alpha.109

package/README.md

@@ -44,13 +44,17 @@ sudo chown -R $USER $(npm config get prefix)/lib/node_modules
 ```
 
 
-> __NB. :__ If you choose to use `sudo npm install -g gina`, you have to make sure that everytime you need to use the gina CLI, or if you use a specific command like `npm link gina`, you will have to do it with `sudo`.
+> __NB. :__ If you choose to use `sudo npm install -g gina`, you will also o use the `sudo` for specific commands like `npm link gina`.
+> Again, the use of `sudo` is discouraged.
 
-Then
+
+
+You can now check if Gina is properly installed.
 
 ```  tty
-npm install -g gina@latest
+gina version
 ```
+__NB.:__ This is a shortcut for `gina framework:version`
 
 
 #### 2nd method - Custom PREFIX
@@ -62,6 +66,12 @@ By adding at the end the `--reset` argument, you will ensure a factory reset for
 npm install -g gina@latest --prefix=~/.npm-global
 ```
 
+You can now check if Gina is properly installed.
+
+```  tty
+gina version
+```
+__NB.:__ This is a shortcut for `gina framework:version`
 
 
 #### 3rd method - local to your project
@@ -74,10 +84,10 @@ npm instal gina@latest
 
 __Attention:__  to use gina CLI, you will need to run it from your project location since the CLI was not installed with the global argument `-g`.
 
-#### You can now check if Gina is properly installed
+You can now check if Gina is properly installed.
 
 ```  tty
-gina version
+./gina version
 ```
 __NB.:__ This is a shortcut for `gina framework:version`
 
@@ -175,7 +185,8 @@ Then restart your bundle
 gina bundle:restart frontend @myproject
 ```
 
-Now edit the `home` control in `src/frontend/controllers/controller.js` so that you can have `self.render(...)` instead of `self.renderJSON(...)`
+Now edit the `home` control in `src/frontend/controllers/controller.content.js` so that you can have `self.render(...)` instead of `self.renderJSON(...)`
+
 
 Once it's done, you just need to refresh your browser.
 
@@ -225,6 +236,7 @@ gina env:use prod @myproject
 __NB.:__ If you need to change it for a particular bundle, you still can do it at runtime using `--env=<your env>` to override the default settings. This will not set `<your env>`as the default environment for the whole project.
 
 
+
 #### Other operations you can apply to your environment:
 __Adding a new environment for your project__
 ```tty
@@ -240,6 +252,12 @@ __Defining an existing environment as `development` (you can only have one like
 gina env:link-dev <your new dev env>
 ```
 
+__Benefits from using a `development` environment__
+You will not have to restart your bundle anytime you modify files inside directories like :
+- /controllers
+- /piblic
+- /templates
+
 ### Logs
 
 #### Getting the logs

package/framework/v0.1.1-alpha.109/VERSION

@@ -0,0 +1 @@
+0.1.1-alpha.109

package/framework/{v0.1.1-alpha.106 → v0.1.1-alpha.109}/core/template/boilerplate/bundle/config/templates.json

@@ -3,7 +3,7 @@
     // common definitions : will apply for all templates
     "_common": {
         // by default, or it will load `layout.html` if exists or `nolayout.html`(from the framework assets)
-        "layout": "{templatesPath}/html/layout/main.html",
+        "layout": "{templatesPath}/html/layouts/main.html",
         // means that the file name of the template is the same as the route name
         // You can override it through the routing.json
         "routeNameAsFilenameEnabled": true,
@@ -26,16 +26,16 @@
 
     "home": {
         // If you want to exclude all global css
-        //"stylesheetsExcluded": "*",        
+        //"stylesheetsExcluded": "*",
         // If you also want to get rid of `gina` definitions, use "**" while excluding
-        
+
         // local css - Will fetch from {bundle}/public
         "stylesheets": [
             {
                 "url": "/css/home.css"
             }
         ]
-        
+
         // If you want to exclude all global js
         //"javascriptsExcluded": "*"
     }

package/framework/v0.1.1-alpha.109/core/template/boilerplate/bundle_templates/html/content/homepage.html

@@ -0,0 +1,8 @@
+{% extends 'html/layouts/main.html' %}
+
+{% set data = page.data %}
+{% block content %}
+    <div class="content">
+        <h1>{{ data.msg }}</h1>
+    </div>
+{% endblock %}

package/framework/v0.1.1-alpha.109/core/template/boilerplate/bundle_templates/html/includes/error-msg-noscript.html

@@ -0,0 +1,11 @@
+<noscript>
+  <div class="wrap error-msg">
+    <a href="http://www.enable-javascript.com/fr/">
+      <p>Pour fonctionner correctement, ce site nécessite que JavaScript soit activé.</p>
+      <p>Tous les navigateurs récents supportent le Javascript, vous n’avez probablement besoin de changer qu’un réglage pour l’activer.</p>
+      <h2>
+        Comment activer Javascript dans votre navigateur&nbsp;?
+      </h2>
+    </a>
+  </div>
+</noscript>

package/framework/v0.1.1-alpha.109/core/template/boilerplate/bundle_templates/html/includes/error-msg-outdated-browser.html

@@ -0,0 +1,8 @@
+<!--[if lt IE 8]>
+  <div class="wrap error-msg">
+    <div>
+      <h2>Vous utilisez un navigateur <strong>non supporté</strong>.</h2>
+      <p>Pour pouvoir utiliser ce site <a href="http://browsehappy.com/">mettez votre navigateur à jour</a> ou <a href="http://www.google.com/chromeframe/?redirect=true">activez Google Chrome Frame</a>.</p>
+    </div>
+  </div>
+<![endif]-->

package/framework/{v0.1.1-alpha.106/core/template/boilerplate/bundle_templates/html/layout → v0.1.1-alpha.109/core/template/boilerplate/bundle_templates/html/layouts}/main.html

@@ -9,10 +9,17 @@
         <meta name="robots" content="index, follow, noarchive">
         <meta name="distribution" content="global">
         <meta name="viewport" content="width=device-width, initial-scale=1.0">
-        {{ page.view.stylesheets }}
-        {{ page.view.scripts }}
     </head>
     <body>
-        {{ page.content }}
+        <div class="outer-wrap">
+            <div class="content wrap">
+                {% include "./html/includes/error-msg-outdated-browser.html" %}
+                {% include "./html/includes/error-msg-noscript.html" %}
+
+                {% block content %}
+                    <p>If you view this message you didn’t define a <strong>content</strong> block in your template.</p>
+                {% endblock %}
+            </div>
+        </div>
     </body>
 </html>