The Making of Nexus
|
Welcome to "the making of" the Nexus project. My name is Joe Hacobian, and I'm going to show you why this project is so exciting. Before I get into the technical details however, here is some background on the name chosen for this project.<<-Show->> nexus |ˈneksəs| noun ( pl. same or -uses ) a connection or series of connections linking two or more things : the nexus between industry and political power. • a connected group or series : a nexus of ideas. • the central and most important point or place : the nexus of all this activity was the disco. ORIGIN mid 17th cent.: from Latin, ‘a binding together,’ from nex- ‘bound,’ from the verb nectere. If you examine how the Nexus component and it's supporting architecture behaves and what it sets out to accomplish, I think you'll agree that the name is appropriate. Nexus is where all the disparate Joomla "puzzle pieces" come together to form an integrated whole which is very efficient to grasp and work with. It is where all things meet. Here you will find stories about Myself, Steve and Yuriy's battles with and victories over the "old way" of doing things in Joomla. There were countless nights of insomnia-driven researching, through the API wilderness whilst thinking to ourselves "Why doesn't someone DOCUMENT this stuff?!?" in that sad and confused state of mind that you might experience if you drive through a 50 mile stretch of highway in the american southwest where there is no development, not even gas stations as far as the eye can see for a solid hour of freeway driving. It's a place where nature has not been kind. A place where it just looks desolate and you'd hate to be stranded there. Yeah that's what it's like to have a bright idea in Joomla-land today, you smile at the thought, only to gaze out the window at the brutal desolation whirling by on the other side of a transparent sheet of glass. You realize that were you to try to implement such an idea the shear heat of the knowledge-desert would dehydrate you of life energy within a couple of hours of google searching. That's the kind of weariness we faced when attempting to realize the dream of a drag and drop CMS with automated site-management-assistance subsystems. I'm still somewhat dumbfounded to find myself still here in 2011, still running an intrepid hosting company with happy customers and I sometimes tell Steve "It's like I'v woken up from a development nightmare to discover that I'm still alive, and am bringing an awesome tool to the market." He just shrugs and says "What's next on the list?" I wonder if Linux does that to people… After you learn to survive and thrive in Linux, nothing can scare you... Then I come to my senses and remember how frightening hardware design and assembly language can be ^_^. In case you were wondering, yes I like to dabble in all kinds of design, not the least of which are mechanical, electronic, or software. Embedded systems are my current darling... All those sensors!!! As Steve sometimes puts it I'm kindof a mad-scientist... I hope these posts and stories are as fun for you to read as they were for us to write. |
The Nexus Block DiagramNo late night, development and bloging session would be
complete with out a nice serving of block diagrams.
Here I show you the Nexus block diagram which is a characterization of how the behaviour of the various layers (Nexus UI, Nexus Abstraction, Joomla Component level, and finally Joomla API) has been designed. Note: There is technically no difference between the Joomla Component level and the Joomla API level. I make this distinction due to the clear operational difference. Please forgive the redactions, I can't unveil the details of the strategy "all at once just yet" but I do want to give you a taste... Last Updated (Friday, 22 July 2011 13:14) |
||
|




