Eventually I reincarnated my personal site using alpha version of Sapid CMF 2. I’m still in progress refining the CMS release, but actually the only what I brought from old version is its name. So, what is going to be?
About 10 years ago web-projects were mostly static and development process pretty simple. Now difference between web-applications and desktop applications disappears, functional complexity of web-projects grows up. It demands to new requirements. That’s usual now – the project is long-term , many of experts take part (non-experts as well). Everybody brings to the project backlog new ideas and goals, before the development stage as well as after. You see, goals and stories mutate and so the tasks. Preliminary estimation by time loses its reasonability. Obviously, it’s needed especial development methodology. Among so popular nowadays Agile methods there are exactly what we need – Feature Driven Development (FDD).
Has it ever occurred to you to fancy about all Facebook applications are simple and similar per se? All of these virtual hugs, gifts, greeting cards, wishes, likenesses, poke, smiles, karma-exchange and other psychological “stroking” differ only with the form, in which user get their portion of attention. Thus this niche is always open for persons interested to test their own ideas. Facebook applications enroll the audience in the way viral marketing works. Users invite their friends to use the application, those friends invite new user the same way. You see, if you have a worth idea, theoretically you can obtain the audience which works out at 20 millions of Facebook users. So there is nothing surprising in that some amateur Facebook applications are sold for tens of thousand dollars.
It is common to encounter success stories that begin with the words: “I’ve have been lucky in my life. I’ve made good friends and met like-minded people who have helped me from the beginning.
Opinions on the future of Web 2.0 differ, and sometimes a lot, but no one would argue that this concept in many ways shaped the present-day Internet. That is why we, developers, should follow new tendencies and trends on the market. Web 2.0 brings with it new requirements.
Today theres no lack of reports on successful Web 2.0 community projects. This is by no means surprising as the latest community projects provide advanced interactive experience for the audience while attracting impressive investments. This results in rapid growth within the market segment and businessmen rush in to get their share of the deal. The market now offers a huge number of solutions, and some of them seem to be of quite agreeable quality. Yet very few eventually amount to a success. Why is that?
What do we know about e-business? Can we consider a corporate site a form e-business? And what about an internet-store? Try a search by any of the popular engines and you will learn a lot about e-business centers but much less about e-business as such. Most web-developers still fail to offer anything beyond the very conventional solutions: official web-site, catalogue, online store, etc. But is that really enough to develop effective e-business solutions?
Today everyone talks about Web 2.0. But while the idea of a collective intelligence, implied here by the terms inventor Tim OReily remains an object of trivial speculations, it is obvious that the World Wide Web is changing. Web applications are increasingly approaching the level of functionality, which is usually found only in desktop applications. And as this trend is gaining momentum, we can already witness the dawn of a new era brought about by a novel kind of web applications - Rich Internet Applications (RIA)
Aspect Oriented Software Development (AOSD) is a methodology meant to implement new aspects in software component using external components, but without altering the code that implements the core functionality.
The AOSD concept was applied originally by Java developers. They developed a compiler that implements the AOP (Aspect-Oriented Programming, an implementation of AOSD) white box approach, i.e. the compiler the merges the code that implements the software components core functionality with the necessary code alterations to implement the new aspects where necessary.
This paper provides an introduction into the paradigm of aspect-oriented software development (AOSD). It includes a multitude of practical examples, provided with a view to objectify such abstract approach as AOSD, as well as to help the reader easily grasp its essence and advantages. The paper is primarily intended for programmers working with PHP. Its aim is to demonstrate a way of applying AOSD in PHP-based projects already today.
Your site may contain a wealth of technical terms. The user while viewing it may have to wonder about their meaning. What can be done to provide site visitors with instant answers to the questions they have?
I am sure being accustomed to desktop applications GUI, users find interfaces of web-applications as extremely uncomfortable. Their notes, probably unexpressed, are timely within AJAX Age. Besides, it is not so difficult to make web-applications more user-friendly.
They allow to structure information within sites, separate it from design. The XSLT standard exists for quite a long time. XSLT is a perfect solution in conception, but practically too laborious. This causes developers to find new solutions, that include features of the open standards and are easy to use. One of those solutions is XML Sapiens markup language.