Forms are the foundation of interactive web and what we call Web 2.0. In this article I will walk through the possible problems web developers encounter when creating web forms and solutions to those problems.
This article will be useful to people who are starting web development or who are experienced at it.
This article refers to Form implementation in Agile Toolkit. For documentation and demonstrations of forms in Agile Toolkit see http://agiletoolkit.org/doc/form
, file upload
It’s been 4 years since I showed up for M50 Enterprise Program (Government program helping start-ups in Ireland) dressed in jeans and t-shirt. I had an idea for on-line project and I wanted to pursue my goal. My belief was that if I write a great software and make it look good, people would certainly start using it. Sometimes it turns out to be like that, but it rather an exception that a rule.
Back then my idea failed, however I have learned two important things about software development:
- Research is very important. Talk with potential clients of what they want before putting your effort into making it.
- Find a shortest path to your goal. Make things work first, then make them work good.
By sticking to those two rules you can avoid spending time on something unnecessary, failing a project or even go bankrupt. Let’s see in more details how to achieve those goals in practice with help of Agile Toolkit.
I came over this old question on StackOverflow: “Which PHP Framework will get me to a usable UI the fastest?” I couldn’t help but wonder, why people are not aware of all those other PHP UI frameworks? There are few, right? If you google for “php ui” you can find them. Those are more generally referred to as UI toolkits. But why those toolkits are not known in the mainstream?
Why there is a gap between UI toolkits and mainstream frameworks? If UI is Yin and backend is Yang – why can’t they co-exist?
Here is what I think..