Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have used codeigniter for few of my projects in my portfolio and currently seeking a job opportunities. However, I heard yii is a very nice and high demanded php framework in the market now. Is that true? Should I turn my attention to yii or keep building more codeigniter projects in my portfolio for my first web developer job? Thanks for the help.
Well this does not fit here but what i have learned that since 4-5 months industry here have started working on Yii. I have been working on Yii since 4 months it is easy and supports Rapid Application Development.
Moreover performance may be key factor but to me its time to development that this framework allows you. I have worked on CI but Yii is far more ahead of that. provides you nice JQuery implemenation does Ajax validations for you and much more.
I recommend it 100%.
If you see what is in market you may not be able to learn whole things and some how things keep changing once COBOL was famous but now........... so basically on everything I guess factor overrides is Ease and Rapid Application Developement these are provided by Yii
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I'll try to be as brief as possible;
My page load time increased 40% and I don't know why, in the atttached image you have the before and after loading times, plus the waterfall view for both the first and the repeated view.
The setup: LNMP VPS, opcache, memcache, joomla with T3 framework template, using joomla file caching
I did the following changes (unfortunately I didn't think about testing after each individual change):
-upgraded to the latest joomla, template, and template engine
-compressed images
-upgraded to PHP 7 (from 5.6)
-everything else is the same, including using the same server for testing and having the same server load
The only explanation I can come up with is that the provider is overloading their servers, making my VPS slower.
Please feel free to write any insight/ideas you have.
Thanks!
Screenshots from webpagetest.org
After extensive testing on various other platforms, using the same setup (I even copy-pasted the config files for php, php-fpm, mysql, etc) I found out that the issue was the hosting company which seems to be overselling.
Using different but identically specced hosting the page now has a first view load time of ~0,9s.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
When migrating Oracle Forms and Reports, there are several options for that :
ADF
APEX
Yor suggestion ...
Which one do you think is the best in terms of business continuity and also ease of technological transition? Do you have experience in such migrations?
At the end, I would like to know if it would be necessary to migrate or just keep "Oracle Forms/Reports"
Regardless of what tool vendors might say, this is going to be an exercise in rewriting your application.
So the real questions is, why do you want to do this? Oracle are continuing to support Forms for some time yet. There are plenty of things we can do to modernize our Forms applications whilst retaining our investment in the existing software. I urge you to look at Mia Urman's presentation Give Your Forms a Facelift: Tips and Tricks for Forms UI Modernization which she gave at a UKOUG event I helped organise a couple of years ago.
If your mind is absolutely set on a re-write you'll find APEX is the easiest path for developers with a Forms/ PL/SQL background.
Update for 2018:
Oracle have been getting back behind Forms. The 12c release had over 100 new features. Okay, some are quite minor but it's a clear statement of intent. Find out more.
It's a big "it depends". ADF is a comparable alternative, while APEX is easier to learn and find resources to build.
The developer tools statement of direction is a great place to start and a while ago I provided my own commentary (http://www.grassroots-oracle.com/2012/03/on-oracles-statement-of-direction-for.html)
i think you should also check oracle JHeadStart , as mentioned in the documentation :
JHeadstart Forms2ADF Generator; creates ADF Business Components and a
JHeadstart Application Definition file based on Oracle Forms files
Hope that Helps .
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
A client has an old version of Magento (1.2.0.3). Can I upgrade directly to (1.6.1.0) or do I have to go through a progressive series of upgrades to make it work.
Generally I think it's better to do progressive updates. It's also better to keep up with new versions and don't let clients fall behind too much. Consider offering them a maintenance contract for a monthly fee or a fee per upgrade.
The biggest changes are between version 1.3 and 1.4 where the Magento team has done a fairly large overhaul of all templates by optimizing the HTML and renaming CSS class names. So it will also depends on how much customization has been done to the site's theme. I've just completed a 1.3.x upgrade to 1.4.2 which took be about 100 hours. This is long for such an upgrade but I've also done a lot of clean up work as the 1.3.x version was not very well built (by another web agency).
The website is now much more upgrade proof and upgrading to 1.5.x and 1.6.x is now a fairly straight forward job taking probably just a couple of days.
Go for progressive and turn off any modifications
and use default template. backup each upgrade step
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
i am new to the web and i understand that MVC is very important to web development. I'd like to do a project that could help me understand the MVC.
Plus, I also can't clearly understand what it is actually. i mean i can't find any good lesson or article that describes to the n00b. so if you guys could help me in that matter too that would be most appreciated.
Thanks in advance.
Start with CodeIgniter. It is a great MVC framework written in PHP. While you build a site in it, you can look at the code and learn how it works.
But remember, as with each design pattern, using it should not be a goal per se. Using a design pattern can help you find and build good generic solutions, but you shouldn't feel too bad if it doesn't work out exactly as you'd like. You'll learn and do better (or differently) next time and you're always free to skip or alter the pattern. It's just a tool.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I want build an application by using the framework.
the application contains two parts: the Back-End and the Front-End.
Everybody who have experiences can suggest me which ways should I do?:
Develop the Front-End first Or Develop the Back-End first
Or give more tips on the start up project?
thanks
I usually start with the backend to get the major functionality implemented, but even so, it's pretty much inevitable that the frontend and backend will have to be developed at the same time at some point in the project.
People can say what they want about separating presentation and functionality, and that's a good principle, but the reality is that the presentation influences the functionality and vice versa.
You might get the backend mostly written, and then you make the frontend, but you will probably decide to change some things and end up working on both together.