Skip to main content

UX Pages Project Update

The integration of Dojo into my UX Pages Project has been moving steady along for the pass few months. The current version of Dojo in Domino 8.51 is 1.32 and has certain limitations that hopefully will be eliminated in Domino 8.52 with a version upgrade of Dojo. This has been a huge learning curve for me with many dead ends.

I have added Dojo objects and Dijit form, field, comboBox, check button, radio button, spinner box, filteringSelect, and button widgets into the UX compiler engine. A Dijit widget control can now be represented by a simple UX xml tag. For example, for a simple field,



when compiled will become:



It will automatically add the dojo.require("dijit.form.TextBox") statement into the html and add links to the Dojo, Dijit, and Dojox javascript library.

Domino data is now surfaced as Dojo objects using XML and JSON using Domino agents. Long terms wise, I would like to create a Dojo Domino data store object that can create JSON and XML data stores directly from the Domino views. Can be done but a lower priority since it requires me to go deeper into the architecture of Dojo which I do not have the time.

I am planning to add data grid and more Dijit and DojoX widgets for the next version of the UX Pages Project and clean up the UX compiler code. In addition, I am in the process of separating the database that creates the UX Pages from the database that the web application runs on. Currently, the UX engine is in the same database that the web application runs and that violates my design policy of separating the interface from the data. Also, I am hoping to have the ability to create and select different UX projects and enhance the archiving capability which still has a few bugs.

The knowledge that I have gain helps me in developing XPages applications. Yes, I should be doing all my Domino Web applications using XPages, but where is the fun.
Labels:

Comments

Post a Comment

Popular posts from this blog

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a...
Post a Comment
Read more

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select...
Post a Comment
Read more

The iPhora Journey - Part 3 - Creating an Integrated UI Framework

The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework There are many ways to create the user interface (UI) for a web application. The HTML page could be created on the server and then pushed out. It could be static with the data generated on the page by the server with JavaScript, providing a more dynamic experience, or the server could generate new HTML content to update portions of the web page. XPages or PHP are good examples of this. Another method is to have the web page partially generated by the server and have JavaScript build the rest of the HTML by pulling data from the server via an API. This is the approach used in the Single Page Application (SPA) model. In all cases, it is still dependent on the web server technology being using.  As mentioned previously in this blog, XPages is dependent on complete integration between form and document, whi...
Post a Comment
Read more