While JPolite V1 is an initial attempt to ease portal development, V2 goes even further into code structure improvement for better development support. But the question has been haunting me for some time, that what about V3, even more developer oriented enhancement? Or something else?
Checking through designers’ portfolios, I came across this Nike Bauer site design, sorta old news but still inspiring to me.
And then this conceptual video about a collaborative research project initiated by Bonnier R&D on future magazine reading experiences.
Now that my mind is made up that JPolite V3 will focus on user experience innovation, to mimic or incorporate above conceptual ideas and more, with just HTML, CSS & JavaScript.
Also struck me is an old saying “… the future is already here. It’s just not very evenly distributed” by William Gibson from 1999
I deem myself mostly a developer and hardly a designer, but I find myself constantly getting hints and inspirations from design communities which more or less influenced my technical design and implementation. And I believe most of Dieter’s principles can be applied to software domains without problem.
There’ve been lots debates around “less is more”, or “more is more”. My take is that, take such ideas seriously, not literally. Just like what Einstein said, “Everything should be made as simple as possible, but NOT SIMPLER”.
Complete rewritten of code structure, a smaller core with a strong customization system
Ongoing:
XDO – A restful resource presentation layer with message processing and event handling, powered by Chain.js
Layout Persistence - sample code will be provided on how to save and retrieve module layout data
Theme Support – two sample themes are given, “Grayscale” and “Classical” which can be switched from Firefox View menu
Module Types – various types of modules can be included and applied on different modules easily
Comprehensive Customization samples
Documentation …
Notable feature: when you first open the page, you will be prompted to pick a navigation tab style, Kwicks, LavaLamp or “Traditional”. That is, you can pick your favorite look and feel for the main navigation tabs. Which also means you can easily include jQuery UI plugins and customize JPolite2 without touching the core!
The content of the modules are now just for testing purpose, please note not to be misled
After some investigation and tryout, I’ve decided to include cool iQuery plugins like Gritter, jqModal as well as Chain into JPolite 2, and some initial integration work have gone smoothly. And these libraries are actually jQuery plugins, that I think it good to build a mechanism for smooth integration of various plugins in a manageable manner.
BlueTrip CSS framework has been chosen as the foundation of CSS where I’ll leave the original framework code untouched and provide only JPolite native customizations. Although JPolite was originally designed without a grid system in mind, I’ll try to align with the grid system to provide better control over the layout.