I am going to develop website by using Yii framework. I will use netbeans to do it (and if it will be possible) with build-in Yii plugin. And here is my dilemma:
Should I use newest 2.0 version, which is demo version since yet, or use version 1.1.14, which is suported by my netbeans plugin. On official site of Yii I found quite good documentation for 2.0 version. Could you help me with some advices? Will be 1.1.14 version still suported be Yii community, could I use it without lot of painful searching for documentation or it would be better to stick with newest version?
Directly from their website: "Yii 2.0 is not ready for production use yet. It is currently under heavy development and we may introduce significant changes without prior notices. You may consider using Yii 2.0 if you just start to learn Yii or you do not have a tight project schedule."
They clearly are not encouraging using it in production in any way.
2.0 version is bet yet... because of this I suggest you to use 1.14 stable version ... in real project always better to use stable versions
there is available
Yii 1.1.15 is released (security fix) as well
The answer really depends on what the purpose of your Yii app is.
Are you building a quick demo? A throw away app? A 5 page app with no long-term maintainability needs? Go with Yii 1.1.15, it's very well documented and you will be able to work in a hurry.
Are you building a project with a minimum 3-5 year life? A web app that will see significant investment over the years? A web app that will have multiple developers involved in it? Go with Yii 2.0.
I've built large web apps with Yii 1.1.x and it works nicely. But for any significant new project, Yii 2.0 is a better fit. PHP as a language has progressed significantly since Yii 1.1 was designed and it shows.
In addition, development on Yii 1.1 is slowing down (the core team is more focused on Yii 2.0). I've for bug reports and pull requests for Yii 1.1 that have been outstanding for months. Not a slam on the core team (Yii 2.0 is where the future is), but Yii 1.1 is quickly going into maintenance mode.
Related
As a developer I have to make a upfront commitment for 5 years support for a new Laravel project.
My question is - whether I should use Laravel's Long Term Support (LTS) version only?
What could be the potential pitfalls with regards to the support commitment if I use the latest Laravel 5.3 instead of the LTS version?
Any information regarding points to be considered like pros/cons with regards to the support commitment for 5 years when using the latest Laravel version versus using LTS version would help me make a correct decision.
To keep your application framework-agnostic, or to make it easier to swap out or not depend on the framework, the approach which worked the best for me was to isolate my business logic in separate libraries.
I handle those libraries using GITLab server, and I expose them to my composer via satis.
If you use Laravel's routing to map request to a controller, then you can use your library inside that controller and perform the rest of the work.
Constructing your app this way lets you:
isolate business logic
rely on framework to provide correct input since you can use middleware to filter out requests that don't fit.
have it easier when it comes to swapping the framework out
you're using composer, which lets you easily manage library and framework version(s)
This way, you can upgrade your app bit by bit as time goes by, you don't have to rely on having only one framework version forever, without being able to use newer releases.
Good luck with your project!
RedBean has in its API's an Rest Server till version 3.5
http://redbeanphp.com/manual3_0/rest_server
I was wondering where to find RedBean_Plugin_BeanCanResty for RedBean 4? Since it isn't listed in the API any more. Is it still available? or is it deprecated?
It's been removed, but is still available as a plugin according to their changelog:
Why are the BeanCan Servers gone?
They blurred the distinction between plugin and core. Also, the RedBeanPHP Adaptive branch is going more in the direction of a framework which is a better place for BeanCan as well. RedBeanPHP 4 returns to the core of the library: on-the-fly ORM. Another reason is that it turns out it is pretty much impossible to prescribe the interface of a JSON or REST API.
This functionality is still available as a plugin
I was wondering if any one had any kind of success integrating a Zend Framework 2.0 beta in a Zend Framework 1.11 project.
I am currently building a project using ZF 1.11. I don't want to use ZF 2.0 yet since they say on the developpers blog that backward compatibility isn't guaranteed. The project developpement will span over a few months and I don't want to fix a lot of stuff when I update to the newest release (which will resolve bugs and vulnerabilities).
Is there a quick tutorial, or did anybody include a Zend Framework 2.0 module (using PHP namespaces) in a "vintage" Zend Framework release using includes?
An alternative possibility, if what you want is to introduce Dependency Injection in your ZF 1.11 project, is to use the Symfony DI component. I worked fine for me.
There are some web resources about the details, most notably this one: http://losohome.wordpress.com/2010/01/22/integrating-symfony-dependency-injection-service-container-with-zend-framework/
Hope that helps,
My advice at this stage is to develop your project with ZF 1.11. 2 will not be backwards compatible with ZF ZF 1.11, but there is talk of some tools / tutorials that will help to update, but I am very skeptical about it!
I want to start developing in an MVC framework, specifically CakePHP.
I see they have released 2.0.0-RC2 and was wondering if it is a waste of time to start an app in 1.3 when 2.0 is right around the corner. Should I start learning and developing in 2.0-RC2 rather as I'm guessing most of what I will learn in 1.3 now might become redundant soon?
Thank you.
I would advise against starting on a Release Candidate when you are new to the platform or programming pattern - mostly because you won't know the difference between broken/missing functionality and your lack of knowledge.
Start with the stable build, then move to the new hotness once it has an official release.
For now, you can start learning CakePHP 1.3. There is official documentation from where you can start and also you have a lot of examples on internet. When CakePHP 2.0 come stable you will be ready to work with it.
Well .. first of all , i would recommend against use of php frameworks before you have learned enough to understand how they work.
But especially large distance should be kept from Cake and other Ruby on Rails clones in PHP. They all are filled with bad practices, and it is not MVC pattern which they are implementing.
I would start with CakePHP 2.0.0-RC2 as CakePHP 2.0 is the future of CakePHP. CakePHP 1.3.x is outdated in my opinion as it is still PHP4-based...
For documentation, see the cookbook for CakePHP 2.0: http://book.cakephp.org/2.0/en/ . And if there are questions, ask in the IRC channel, or post in the Google group (or here), and/or read the source code.
I am currently developing a system on a server running PHP version 5.1.6 thus I am forced to use Symfony 1.1 in the current environment.
I am planning to migrate the application from 1.1 to 1.2 in the somewhat near future and I was wondering if anyone has any experience with this?
I have attempted to migrate a system from 1.0 to 1.1 and that was a major pain in the rear.
How has it been for anyone out there migrating from Symfony 1.1 to 1.2?
My 2 cents is that it all depends on how many forms you have in your application, that was by far the most painful part. Symfony 1.2 has an entirely new form system.
you can always do compac10 = true or whatever ...to make your old code compatible,..
Symfony 1.2 does have many new useful widgets,..and propel 1.3 is a significant improvement, fixed some bugs that I was actually running into.
It should be fairly easy if you didn't use custom SQL queries with Propel (i.e. manual hydratation) as Propel 1.3 switches to PDO.
I migrated an 1.1 app to 1.2 and I had nothing to do except running the automatic upgrade script.
For me, migration to 1.2 was fairly painless. The upgrade script should do all hard work.
The biggest problem will be migrating to propel 1.3 if you have used 1.2 ( default with symfony 1.0.x and 1.1.x). If you were using propel 1.3 before ( with sfPropelPlugin) or Doctrine there shouldn't be any problems.
Another one will be porting admin generated modules to new admin generator, but in 1.2 the oldones still work for now.
Those listed above are the biggest changes in 1.2.
And I love 1.2 for it has lots of new cool stuff ( REST routing, new admin generator, some minor fixes etc.)