panique / mini

Just an extremely simple naked PHP application, useful for small projects and quick prototypes. Some might call it a micro framework :)
1.35k stars 479 forks source link

[potential features] how about a 2.0 version of this, with Twig, PHP-SASS, etc. ? #40

Closed panique closed 10 years ago

panique commented 10 years ago

Hey people, as this barebone got quite good response and obviously is helpful, it might be useful to work on a "more advanced" version in 2014.

Goals: Implement very useful web technologies in a ready-to-go way to encourage people to use them.

UPDATE: This project will get an own repository, like php-mvc-advanced or similar

For example "php-mvc 2" could implement:

1.) SASS/Compass (the improved version of CSS) which compiles SCSS to CSS with PHP (http://leafo.net/scssphp/ does this, installable via Composer).

2.) A view engine, like Twig (installable via Composer).

3.) An ORM library (same here)?

4.) A slim/laravel-like routes.php that basically replaces all controller files

Feel free to add your ideas!

panique commented 10 years ago

5.) a basic ready-to-go implementation of a highly modern JavaScript Framework that might reduce the server-side load massivly: Angular.js or so

panique commented 10 years ago

6.) all configfree (!!) goodies that a modern JS/PHP-application might need, like caching via .htaccess, splitting of application and database (one server for app, one for db)

ljvicente commented 10 years ago

Personally I like the simplicity of the php-mvc. As an idea, adding a basic web security feature like XSS cleaning will be extremely useful.

GrahamCampbell commented 10 years ago

Actually, XXS cleaning can get more than basic. I made a laravel package for it. You can check my security class at https://github.com/GrahamCampbell/Laravel-Security/blob/develop/src/GrahamCampbell/Security/Classes/Security.php. I wouldn't mind this project lifting code out of it.

To be honest the best way of preventing xss is just to escape the user input completely instead of messing with silly regex and creating more complexity.

panique commented 10 years ago

7.) Basic "native" pagination/list/offset example (example.com/product/page/3) 8.) Basic make-my-app-much-faster-stuff like gzip etc., everything that's possible with simple htaccess files 9.) Basic demo of how to integrate something with Composer. It's totally simple, but lot's of people seem to be afraid of Composer.

redstrike commented 10 years ago

2.) A view engine, like Twig (installable via Composer). * MUST HAVE FOR PHP APP 4.) A slim/laravel-like routes.php that basically replaces all controller files

panique commented 10 years ago

for 4.) The router could be PUX (seems to be a very professional one, extremely fast and highly documented, easy to understand): https://github.com/c9s/Pux

panique commented 10 years ago

TWIG is done in https://github.com/panique/php-mvc-advanced

feydk commented 10 years ago

I definitely vote for 7 and 8. Paging is used everywhere and performance is paramount. 6 would be nice to have. I don't care for the rest :)

panique commented 10 years ago

i'll close this issue, as there's a new repo with Twig and SASS support. For talk about further features please open an issue there: https://github.com/panique/php-mvc-advanced