Skip to main content

MWLUG XPages Design Competition Winner Is

Thank you everyone for participating in the MWLUG 2011 XPages Design Competition. We were hoping to have more entries, but we know it takes a lot of effort for submitters to create an entire application for a competition. We received a total of two entries.

The winner of the MWLUG 2011 XPages Design Competition is Ferry Kranenburg who happens to also be a winner for the OpenNTF Custom Control competition. In addition to the Galaxy Tab 10.1 tablet, Ferry will receive from Teamstudio, one development license and 10 user license of their Unplugged solution. In addition, Teamstudio will help convert Ferry's app if possible to a mobile app using their tools. Baiju Thomas will receive a Amazon $100 gift card as runner up.

Special thanks to all our judges and Mike McGarel for running this competition.
Labels:

Comments

Niklas Heidloff said…
Congratulations Ferry.

Richard, will the applications be made available somewhere (hopefully OpenNTF)?
August 31, 2011 at 11:38 PM
Domino Interface said…
Niklas,

Ferry has already made it available on OpenNTF.org. Hopefully the other contestant, Baiju Thomas, will do the same. Both of them will also be made available on our web site to download maybe next week.

Hopefully we can do this next year and give contestants more notice. It would be nice to have all the nifty fifties converted over to XPages.
September 1, 2011 at 7:49 AM
Philippe Riand said…
Congrats Ferry!

Beyond having the application on openNTF, it would be great to have a running version somewhere where we can browse the recipes :-)
September 8, 2011 at 6:55 AM
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, which e
Post a Comment
Read more