4 ms·

Hey James, Sounds like a cool project - excited to see it for sure. The tough part with projects like this is making sure that it's simple but still flexible.

by jenius 14y ago

Hey James, Sounds like a cool project - excited to see it for sure. The tough part with projects like this is making sure that it's simple but still flexible. For example, can you fully customize the rest routes, or are those just generated? If a developer knows enough to work with routing, models, and the back end, why wouldn't they just use rails and activeadmin for the admin panel? If your project is any less simple/flexible than rails, that will be a tough compromise. Either way, this sounds like a pretty sweet project, I'd love to check it out when it's released. What are you thinking about calling it (just so i recognize)?

jameswyse 14y ago
Hey, thanks for replying :) I completely agree with your points. I constantly encounter the same problems when I use other frameworks so I want everything to be fully flexible. At the moment the REST routes are generated for resources and available through the api/resources endpoint. (For example, /api/resources/users/) you can however add whatever other routes you like to /api/ using your own controllers. I'm thinking about adding a simple query language to the REST route syntax to take care of some common requests. That may work something like this: /api/resources/users/$near/lat,lon It's still early stages though so I'll probably go through a lot of ideas before I'm happy with it! It'll be called Nails (or Nails Framework, Nails CMS, whatever sounds closest to the finished idea) - I have the domain nails.io which I'll be using for this project. Cheers!
- jenius 14y ago
  You should check out railwayjs before you get too deep into it - this might do what you were after: http://railwayjs.com/ http://railwayjs.com/
  - jameswyse 14y ago
    Cheers. I've used RailwayJS in the past but I switched to LocomotiveJS[1] which I find much nicer to work with and it's incredibly flexible too. I'm using locomotive in this project on top of express to help with controllers and routing, though I'm thinking about using flatiron[2] which is a pretty solid looking set of modules for routing, middleware, etc. [1] LocomotiveJS: http://locomotivejs.org/ http://locomotivejs.org/ [2] Flatiron: http://flatironjs.org/#data http://flatironjs.org/#data

by jenius 14y ago

jameswyse 14y ago

Hey, thanks for replying :) I completely agree with your points. I constantly encounter the same problems when I use other frameworks so I want everything to be fully flexible. At the moment the REST routes are generated for resources and available through the api/resources endpoint. (For example, /api/resources/users/) you can however add whatever other routes you like to /api/ using your own controllers. I'm thinking about adding a simple query language to the REST route syntax to take care of some common requests. That may work something like this: /api/resources/users/$near/lat,lon It's still early stages though so I'll probably go through a lot of ideas before I'm happy with it! It'll be called Nails (or Nails Framework, Nails CMS, whatever sounds closest to the finished idea) - I have the domain nails.io which I'll be using for this project. Cheers!

jenius 14y ago
You should check out railwayjs before you get too deep into it - this might do what you were after: http://railwayjs.com/ http://railwayjs.com/
- jameswyse 14y ago
  Cheers. I've used RailwayJS in the past but I switched to LocomotiveJS[1] which I find much nicer to work with and it's incredibly flexible too. I'm using locomotive in this project on top of express to help with controllers and routing, though I'm thinking about using flatiron[2] which is a pretty solid looking set of modules for routing, middleware, etc. [1] LocomotiveJS: http://locomotivejs.org/ http://locomotivejs.org/ [2] Flatiron: http://flatironjs.org/#data http://flatironjs.org/#data