ptero 1.0.2 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 92a24a82b9c9a89a153cdd13a78b8d338a8237a4
-  data.tar.gz: de7cb46577835fec63be3d92570f893a00ea5868
+  metadata.gz: 165c7c7850463518a58561f975ff4c863b628811
+  data.tar.gz: f279bc9d3e83b175e0a375efd23f8d97db7538d0
 SHA512:
-  metadata.gz: e6b5f379a7ab50c0239c7ea8b88b6e50a9101c7c59fff598b31ea585b12b358ab86671e11f5395e34db1f0a43a45b5719538005e269a0e2463977697a707df11
-  data.tar.gz: ae55b4d2f86d5172fb1a89181949910f88b3570a648144fc9156c064448ce9ad906b2042d3763e703b5b436a1a991ae7eb28828c244f20edcab721c3a02e2183
+  metadata.gz: fa735b7f0551635eed1627275afcb2b36b58dffc0236912baa06b257079b24627a1dca74d20cee75df16b24543069395600b6a9b059da3c57e3116907047e952
+  data.tar.gz: f3df3bfd2cb0ef71fb9c9885a00bb8f0580015a03663b1f0a39a1c89642841bfd7b99cf3c8bac371923c44cabe2496dec4b0a6ed114ef38ed0ee5b3a2d712bd2

data/README.md

@@ -6,33 +6,36 @@ Think wearing a giant robot exo-skeleton with lasers and missile launchers while
 
 ### It has the good stuff
 Features include:
-  * RESTful routing
-  * Sensible templates: layouts and views separate
-  * RoR-esque code generation
-  * PHP-ActiveRecord for ORM: No SQL needed!
-  * Installs dependencies quickly and easily with Composer
-  * Built in Ruby: Who doesn't love Ruby?
+ * RESTful routing
+ * Sensible templates: layouts and views separate
+ * RoR-esque code generation
+ * PHP-ActiveRecord for ORM: No SQL needed!
+ * Installs dependencies quickly and easily with Composer
+ * Built in Ruby: Who doesn't love Ruby?
 
 ### It takes care of the bad stuff
 Don't worry about:
-  * annoying PHP syntax errors
-  * copy-pasting or otherwise repeating code
-  * SQL, SQL injection, escaping strings, etc
-  * URLs that look ugly
-  * PHP being stupid in general
+ * annoying PHP syntax errors
+ * copy-pasting or otherwise repeating code
+ * SQL, SQL injection, escaping strings, etc
+ * URLs that look ugly
+ * PHP being stupid in general
 
 ### How do I do it?
 To start using Ptero, make sure your PHP command-line tool is up-to-date, then run the following:
+
 ```bash
 $ gem install ptero
 ```
 
 Now make an application:
+
 ```bash
 $ ptero new Blog
 ```
 
 There! Your web application is seeded and ready. Now you can start generating files.
+
 ```bash
 $ cd Blog
 $ ptero generate page hippo
@@ -45,7 +48,8 @@ Now run an apache server with root directory Blog/www, and navigate to http://lo
 ### Onward!
 Now for the best part. Let's take a look at the generated code.
 
-Here's the default controller, Blog/php/controllers/HippoController.php
+Here's the default controller, Blog/php/controllers/HippoController.php:
+
 ```php
 /*
  *
@@ -99,6 +103,7 @@ Notice that the template has only a few lines of code, and that it extends a lay
 In this way, global layout changes can be made to the global application template, and individual changes made to individual pages. 
 
 For example, let's try doing some arbitrary server-side work and sending it to the client:
+
 ```php
 // HippoController.php
 
@@ -119,6 +124,7 @@ class HippoController extends ApplicationController {
 }
 ```
 the template:
+
 ```twig
 {% extends 'application.html.twig' %}
 
@@ -138,7 +144,8 @@ the template:
 Now our code will print the $sum variable passed to it by the server.
 
 ### Routing
-We already did some routing with the `$ptero route` command, but routes are also stored in a file and editable by hand. Let's open Blog/php/routes.php
+We already did some routing with the `$ptero route` command, but routes are also stored in a file and editable by hand. Let's open Blog/php/routes.php:
+
 ```php
 // Application route maps
 $application->route(array(
@@ -150,16 +157,19 @@ $application->route(array(
 Look! The route we made is there! It maps the string '/hippo' to the controller class Blog\Controllers\HippoController.
 
 You can also print all current routes by running
+
 ```bash
 $ ptero routes
 ```
 
 We can try using RESTful parameters in our application and passing them to controllers. Try this:
+
 ```bash
 $ ptero generate page rhino
 $ ptero route /rhino/:number Rhino
 ```
 Now edit php/controllers/RhinoController.php:
+
 ```php
 namespace Blog\Controllers;
 
@@ -178,6 +188,7 @@ class RhinoController extends ApplicationController {
 }
 ```
 and make the template print our result:
+
 ```twig
 {% block content %}
 	<!-- HTML content code produced by view: rhino -->
@@ -204,6 +215,7 @@ You'll have to bring your own SQL server. Sorry. Try [MAMP](http://www.mamp.info
 Ptero uses PHP-ActiveRecord Databases, which are as easy as pie to use with a few minutes' practice. [Take a look.](http://www.phpactiverecord.org/projects/main/wiki/Quick_Start)
 
 The first step of using Ptero databases is to configure your application. Open config/config.php:
+
 ```php
 <?php
 /*
@@ -236,12 +248,14 @@ return array(
 Change the values 'database-name', 'username', 'password', and 'server' to the configuration of your database so that PHP-ActiveRecord knows where to look.
 
 Now let's generate another page. We'll assume that we have a table called Elephants in our database that has a primary-key int "id", a string "name", and another int "age."
+
 ```bash
 $ ptero generate page elephant
 $ ptero generate model elephant
 $ ptero route /elephants/:number Elephant
 ```
 In php/controllers/ElephantController.php:
+
 ```php
 <?php
 
@@ -279,6 +293,7 @@ class ElephantController extends ApplicationController {
 ?>
 ```
 In views/elephant.twig:
+
 ```twig
 {% extends 'application.html.twig' %}
 
@@ -299,6 +314,7 @@ In views/elephant.twig:
 With this code in place, a request to http://localhost/elephants/n will output the information of elephant with id=n.
 
 In this same way, you can create new Elephants and save them to the database by running something akin to:
+
 ```php
   $dumbo = new \Blog\Models\Elephant();
 	$dumbo->name = 'dumbo';
@@ -315,6 +331,7 @@ This "destroy" command will delete or undo a create operation.
 USE WITH CARE ON UNCOMMITTED CHANGES.
 
 Here are some common inverse commands:
+
 ```bash
 $ ptero new Slideshow               # Create the Slideshow application
 $ cd Slideshow

data/lib/ptero/version.rb

@@ -1,4 +1,4 @@
 module Ptero
   # Do you I need to explain this?
-  VERSION = "1.0.2"
+  VERSION = "1.0.3"
 end

data/ptero.gemspec

@@ -9,7 +9,7 @@ Gem::Specification.new do |spec|
   spec.authors       = ["LuminousRubyist"]
   spec.email         = ["luminousrubyist@zoho.com"]
   spec.summary       = "Command-line interface for Dinosaur projects."
-  spec.description   = "Command-line interface for Dinosaur projects. Use this tool to generate components of Dinosaur applications."
+  spec.description   = "Ruby on Rails-style MVC framework for PHP. Builds fast and clean projects in seconds with pure-PHP controllers, templates, and models. RESTful routes, modular templates, databases without a drop of SQL. You won't be disappointed. Download this gem, then run `$ ptero new <appname>` and be on your merry way."
   spec.homepage      = "http://luminousrubyist.github.io/ptero/"
   spec.license       = "MIT"
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ptero
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
 platform: ruby
 authors:
 - LuminousRubyist
@@ -108,8 +108,10 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 5.4.3
-description: Command-line interface for Dinosaur projects. Use this tool to generate
-  components of Dinosaur applications.
+description: Ruby on Rails-style MVC framework for PHP. Builds fast and clean projects
+  in seconds with pure-PHP controllers, templates, and models. RESTful routes, modular
+  templates, databases without a drop of SQL. You won't be disappointed. Download
+  this gem, then run `$ ptero new <appname>` and be on your merry way.
 email:
 - luminousrubyist@zoho.com
 executables: