Home Explore Help
Register Sign In
herby
/
mini-mvp
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Browse Source

Remove cruft.

Herby Vojčík 5 years ago
parent
c3e15e25f0
commit
fad70abcf2
3 changed files with 0 additions and 99 deletions
Unified View Show Diff Stats
  1. 0 4
      package.json
  2. 0 38
      parts.html
  3. 0 57
      uninstall.html

+ 0 - 4
package.json
View File 

@@ -31,11 +31,7 @@
 
     "test": "grunt test"
 
     "test": "grunt test"
 
   },
 
   },
 
   "dependencies": {
 
   "dependencies": {
 
-    "@ambers/contrib-jquery": "^0.6.0",
 
-    "@ambers/contrib-web": "^0.8.2",
 
-    "@ambers/domite": "^0.9.0",
 
     "@ambers/lang": ">=0.25.0",
 
     "@ambers/lang": ">=0.25.0",
 
-    "@ambers/silk": "^0.6.0",
 
     "es6-promise": "^4.2.6"
 
     "es6-promise": "^4.2.6"
 
   },
 
   },
 
   "devDependencies": {
 
   "devDependencies": {

+ 0 - 38
parts.html
View File 

@@ -1,38 +0,0 @@
 
-<!DOCTYPE html>
 
-<html>
 
-
 
-  <head>
 
-    <title>Amber Mini MVP</title>
 
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 
-    <meta name="author" content="Herby Vojčík" />
 
-  </head>
 
-
 
-  <body>
 
-  <p>The sample app contains a few additional parts beyond Amber itself:</p>
 
-  <ul style="width: 40ex">
 
-      <li>The common infrastructure: testing.js, devel.js, *.json,
 
-          .gitignore, big part of Gruntfile.js,
 
-          <code>devDependencies</code> in package.json
 
-      </li>
 
-      <li>Common code (MiniMVP-Tests package).</li>
 
-      <li>These introductory files: parts.html and uninstall.html</li>
 
-      <li>Polyfilling: some dependencies in package.json
 
-          and their use in Gruntfile.js and index.html.
 
-      </li>
 
-      <li>The webapp-specific code (MiniMVP package).</li>
 
-      <li>The webapp-specific dependencies in package.json
 
-          (modules silk, domite, contrib-web and contrib-jquery).
 
-      </li>
 
-      <li>The webapp entry point index.html.</li>
 
-      <li>The webapp-specific infrastructure: deploy.js
 
-          and parts of Gruntfile.js that use webapp-specific pieces.
 
-      </li>
 
-      <li>The lambda-specific code (MiniMVP-Backend package).</li>
 
-      <li>The lambda handler file lambda/index.js.</li>
 
-      <li>The lambda-specific infrastructure: lambda.js
 
-          and parts of Gruntfile.js that use lambda-specific pieces.
 
-      </li>
 
-  </ul>
 
-  </body>
 
-
 
-</html>

+ 0 - 57
uninstall.html
View File 

@@ -1,57 +0,0 @@
 
-<!DOCTYPE html>
 
-<html>
 
-
 
-  <head>
 
-    <title>Amber Mini MVP</title>
 
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 
-    <meta name="author" content="Herby Vojčík" />
 
-  </head>
 
-
 
-  <body>
 
-  <p>Once you start developing your own app / lib / backend, you should
 
-      remove all unnecessary parts left from the sample app.</p>
 
-  <ul style="width: 40ex">
 
-      <li>You can choose to polyfill less or not at all in Gruntfile.js / index.html,
 
-          as a consequence polyfilling dependencies can be uninstalled.
 
-      </li>
 
-      <li>In case you don't need webapp part at all, you can remove
 
-          deploy.js (and its appearance in testing.js), MiniMVP package,
 
-          webapp-specific dependencies in package.json
 
-          (modules silk, domite, contrib-web and contrib-jquery),
 
-          remove "start the app" call in index.html
 
-          and remove webapp-specific parts in Gruntfile.js.
 
-      </li>
 
-      <li>You should keep index.html (you need it to develop),
 
-          but in cleaned form (see below).</li>
 
-      <li>In index.html <code>&lt;body&gt;</code> tag,
 
-          everything should be removed, except
 
-          the <code>&lt;script&gt;</code> tag
 
-          that initializes Amber and starts your app;
 
-          then you can add elements specific to your own webapp
 
-          to the page (or leave it bare if case in previous item happened).</li>
 
-      <li>In case you will develop the webapp part,
 
-          you will probably only use one set of libraries presented
 
-          (there are more options so you can see and choose).
 
-          So either you keep silk which depends on domite,
 
-          or you keep contrib-web which depends on contrib-jquery.
 
-          Your Gruntfile.js may contain references
 
-          to these modules in <code>libraries</code>
 
-          field(s). Fix those fields to not contain removed libraries.</li>
 
-      <li>In case you are developing an Amber library (eg. not the app),
 
-          you'll probably end up not needing any of the aformentioned libraries
 
-          (depends on how UI-heavy your library are),
 
-          and you likely can remove the intro MiniMVP class
 
-          and the "start the app" call in index.html.
 
-      </li>
 
-      <li>In case you don't need the lambda / backend part at all,
 
-          you can remove lambda.js (and its appearance in testing.js),
 
-          MiniMVP-Backend package, lambda directory
 
-          and remove lambda-specific parts of Gruntfile.js.
 
-      </li>
 
-      <li>These introductory files: parts.html and uninstall.html can be deleted.</li>
 
-  </ul>
 
-  <p>As the last step, make sure the dependency tree is in a correct state
 
-      by recreating it: run <code>npm run reset</code> from your CLI.</p>
 
-  </body>
 
-
 
-</html>