Skip to main content

I have been Flexed, a New Adventure in UI Design

Over the past couple of months I have been optimizing our IBF 3.0 technology to develop applications. One of the goals of the project is to develop Notes applications with an interface design that is effective for users, especially small business users. The design team and myself have gone through a number of different designs understanding the limitations of the Lotus Notes Basic client. I thought about designing just for the Lotus Notes standard client, but I do not like it because it is big, slow, and the UI is buggy. As many who know me, I would have preferred that IBM revamped the Basic client rather than go with the an Eclipse framework. I understand why IBM went with the Eclipse framework, my I still do not like it. I am a proponent of small and lite clients. The Lotus Notes Basic client is much leaner and faster, but the UI and controlling it even with all the tricks that I and others like Chris Blatnick and Nathan Freeman has come up with is still lacking. This is especially important since we are developing commercial products that are marketed to small businesses. Each time we ran into design issues that stopped us because of known bugs or design deficities that has never been fixed some of which have been there since Notes 5 and 6. I remember asking IBM at the Ask the Developer session at Lotusphere when the CSS problems would be fixed and the response was in the next version (Notes 7). Well if is still there even in Notes 8!

With XPages as the new buzz word, we thought about developing our applications as a pure Web solution. However, the response is not there and we still wanted the ability to have offline capability and start off it as an application like we have in the Notes client.

Therefore, after researching different RIAs we have decided to try creating an Domino RIA application using Adobe Flex. The combination of Flex and AIR hoping will give us what we have been looking for. It might be a dead end, but from all the research that I have done it may provide 90 to 95% of what we need.

Would this replace the Lotus Notes client, I seriously doubt it. After this exercise, we might be back to the Notes client again. Programming and experimentation many times results in dead ends.

If you are interested in Flex with Domino there are some good blogs on this subject. So far I have found these blogs on Flex and Domino very helpful. If there are others, let me know.

Angel Figueroa and Mark Ambler
http://flexingdomino.blogspot.com/

Jake Howlett
http://www.codestore.net/store.nsf/blog/

There is also a list of videos on Flex from Adobe. I would like to thank Mark Myers for the link.
http://sessions.adobe.com/FlexInAWeek/feed.xml

Comments

Anonymous said…
I totally agree with you on the Client, and i have been though this as well and keep coming back to redesigning mode ,Flex is give me another option that is not only a complete off-line / on-line solution but it will give us ( the designer) the option that we have not be able to deliver to our users and that is very pro look and Feel - I hope that IBM and Adobe will bring us a API that we can bring this technology closer together - Pálmi

Popular posts from this blog

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

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

The iPhora Journey - Part 4 - JSON is King - The How

  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 The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document.  However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo