You can get immediate help in NOLOH's IRC channel
at #noloh on irc.freenode.net. A member of the NOLOH team will be able to help you with your program or answer any questions you might have. You can also send us an e-mail at email@example.com
NOLOH stands for "Not One Line of HTML®." What this means is that there will be no markup that dictates what your program does. However, you can of course still use markup/HTML to display static content. You can even interact with NOLOH using your markup in unprecedented ways, while still retaining complete control in your code. See MarkupRegion and RichMarkupRegion for more information.
We have tried various accessibility software (and emulators) on NOLOH applications with
good results. However, because of the diversity of these programs and the
complexity of the problem of making rich applications accessible, we feel
we cannot really tout accessibility as a fully complete feature of NOLOH
quite yet. But there are two exciting things on the horizon of this
developer challenge! As you may already know, the W3C has a subsection
called the Web Accessibility Initiative (WAI), and they have this to say:
1) "People with disabilities (using desktop or laptop computers) and
people without disabilities who are using mobile devices have similar
interaction limitations and they experience similar barriers when
interacting with Web sites." (http://www.w3.org/WAI/mobile/experiences) At
this very moment, we are developing into the kernel a way to render NOLOH
transparent to the developer, of course) to provide them with a nice,
degraded experience. This feature is on the version 1.7 roadmap and will
be complete soon. Consequently, according to the WAI article, this system
would be of much help to people with disabilities.
2) The WAI has been drafting a set of guidelines and standards for Rich
Internet Applications called the WAI-ARIA. This research is aimed at
tackling the problem of making common web widgets (the example they like
to use is TreeList, which is a built-in NOLOH Control) interact well with
accessibility software. We have been following these developments closely.
As soon as they make their work in progress official, you can bet that we
will begin implementing their suggestions into the NOLOH kernel
transparently to the developer. The result of this effort should be an
unprecedented feature-rich experience for people with disabilities.
One of NOLOH's core tenets is that applications should be available to as
many clients as possible, no matter what browser they use, whether they're
on their cellphone, etc... In the case of each type of client, we make the
application as feature-rich as possible. To broaden this user base in any
way, in this case to include clients with accessibility needs, is always a
very exciting possibility. Another of NOLOH's tenets is that the kernel
should completely handle all these tasks transparently to the developer,
so that code you write in NOLOH now will likely not have to be changed at
all when we incorporate the various ARIA guidelines.
So to answer your question shortly: Right now, NOLOH applications interact
fairly well with accessibility software. In the future, after the
completion of the mobile system described in (1), and the release of ARIA
standards described in (2), the level of interaction and feature-rich
experience for people with disabilities will be totally unprecedented.
Thank You for your inquiry,
NOLOH automatically manages all aspects of user view state. Application developers can choose to store/restore view state to make it persistent across sessions.
PHP is the fourth most popular programming language and the most popular language for developing web applications. According to Netcraft PHP is installed at over 1.2 million IP addresses hosting over 20 million web sites. There's also a very large and active community of PHP developers.
No. PHP is an interpreted language so development cycles tend to be faster than with compiled languages like Java. It's nice to be able to make a change to the code, save the change, and then just click the refresh button on the browser to see the effect of the change.
On the server side, all that is required is an HTTP server that can be configured for PHP with PHP 5.1 or greater installed. That's it.
NOLOH may sound too good to be true but as you can see, it's not vaporware. NOLOH came about simply by looking at the way rich Internet application development is currently being done and asking if there was a better way to do it. Rather than accepting the status quo and kludging together existing tools and protocols, the developers of NOLOH consciously chose to set out on an entirely different path.
Not really. It's a lot like overnight success that's been 20 years in the making. If it were that simple nobody would have found the need to develop MVC frameworks or use Ajax which, in our opinion, are overly complicated.
No. You can use any and all of the tools you are currently using to develop applications in PHP. While NOLOH was built using object-oriented principles and object-oriented approaches are encouraged, NOLOH neither requires the use of any particular development tool nor enforces any particular development approach, methodology, or design pattern. You could, if you wanted, develop an MVC framework using NOLOH if you wanted to implement that design pattern.