A couple of weeks ago I started messing with Titanium Appcelerator. Coming from Domino Designer and Eclipse the IDE will look very familiar. It's eclipse and it's based off of Aptana Studio. I guess the biggest issue to being productive is the learning curve for the API. But honestly when is that not the case? So starting to delve into this, Titanium apps are purely client side javascript based. You write the CSJS that builds the UI, Business Logic, Layout, everything. While this may seem daunting at first it actually makes pretty good sense I think. If like me you don't like large javascript files it forces you to think in a

close

A couple of weeks ago I started messing with Titanium Appcelerator. Coming from Domino Designer and Eclipse the IDE will look very familiar. It's eclipse and it's based off of Aptana Studio. I guess the biggest issue to being productive is the learning curve for the API. But honestly when is that not the case? So starting to delve into this, Titanium apps are purely client side javascript based. You write the CSJS that builds the UI, Business Logic, Layout, everything. While this may seem daunting at first it actually makes pretty good sense I think. If like me you don't like large javascript files it forces you to think in a

Read more

OK, so today is the 2nd day I've spent with the Mobile controls from Domino 9.0.1. I must say the lack of a 9.0.1 Beta is quite obvious. So some of the "improvements" IBM made to the mobile controls are the addition of onBeforeTransitionIn/Out onAfterTransitionIn/Out. While these events are sorely needed, the implementation IBM chose to use doesn't work is kind-of odd. So, a brief rundown of the transition events pre 9.0.1. I posted a while back about how to implement these methods in your mobile application. Short version is do a dojo.connect to attach to the needed transition event of an appPage. Then in that function make an RPC call

close

OK, so today is the 2nd day I've spent with the Mobile controls from Domino 9.0.1. I must say the lack of a 9.0.1 Beta is quite obvious. So some of the "improvements" IBM made to the mobile controls are the addition of onBeforeTransitionIn/Out onAfterTransitionIn/Out. While these events are sorely needed, the implementation IBM chose to use doesn't work is kind-of odd. So, a brief rundown of the transition events pre 9.0.1. I posted a while back about how to implement these methods in your mobile application. Short version is do a dojo.connect to attach to the needed transition event of an appPage. Then in that function make an RPC call

Read more

Posted in IBM, Mobile, XPages

Check out my first NotesIn9 video about adding a Dojo Scrollable Pane in order to get a fixed bottom tab bar with the Extension Library Mobile Controls. A big thanks to David Leedy for publishing my video. Hope you enjoy the video. Share This:

close

Check out my first NotesIn9 video about adding a Dojo Scrollable Pane in order to get a fixed bottom tab bar with the Extension Library Mobile Controls. A big thanks to David Leedy for publishing my video. Hope you enjoy the video. Share This:

Read more

Posted in Dojo, Mobile, XPages

At Red Pill Development, Peter Presnell has encouraged our development efforts to use a "Mobile First" approach. The process is that you design your mobile interface first, get everything working properly and then move on from there to Tablet and then Web Browser interfaces re-using as much as possible from the previously working mobile implementation. This approach has several advantages: It forces you to research, gather requirements and only display and write code for the things you actually NEED The flow of the application will be defined by the mobile interface It shapes the direction of the entire project It forces you into thinking differently Makes the next interface implementations easier

close

At Red Pill Development, Peter Presnell has encouraged our development efforts to use a "Mobile First" approach. The process is that you design your mobile interface first, get everything working properly and then move on from there to Tablet and then Web Browser interfaces re-using as much as possible from the previously working mobile implementation. This approach has several advantages: It forces you to research, gather requirements and only display and write code for the things you actually NEED The flow of the application will be defined by the mobile interface It shapes the direction of the entire project It forces you into thinking differently Makes the next interface implementations easier

Read more

Have you ever had a dream that you were so sure was real? Well today is the first step in realizing that dream. A few months ago I made a post about being one of the co-founders for a new company called Red Pill Development. This company was founded on the controversial belief that modernizing Notes applications one at a time by reproducing all of the existing functionality is a loosing strategy.  In order to turn a profit modernizing applications, you have to do so en-masse and only include the features that are needed and being used. We came about this epiphany from attempting to reproduce Notes applications in their entirety

close

Have you ever had a dream that you were so sure was real? Well today is the first step in realizing that dream. A few months ago I made a post about being one of the co-founders for a new company called Red Pill Development. This company was founded on the controversial belief that modernizing Notes applications one at a time by reproducing all of the existing functionality is a loosing strategy.  In order to turn a profit modernizing applications, you have to do so en-masse and only include the features that are needed and being used. We came about this epiphany from attempting to reproduce Notes applications in their entirety

Read more

Posted in Mobile, Red Pill, redpill, XPages

At Red Pill Development we're pushing the envelope a bit on XPages Mobile, we're certainly pushing the mobile controls to their limits. Because of this sometimes we need to take matters into our own hands and override the XPages Mobile controls and kind-of take over how they operate or create our own. One of the things you're going to encounter when you delve into XPages Mobile development is trying to put a Tab Bar at the bottom of the screen that actually stays at the bottom of the screen. We were able to incorporate this by implementing the Dojo ScrollablePane as a custom dijit. We needed to pursue this route as

close

At Red Pill Development we're pushing the envelope a bit on XPages Mobile, we're certainly pushing the mobile controls to their limits. Because of this sometimes we need to take matters into our own hands and override the XPages Mobile controls and kind-of take over how they operate or create our own. One of the things you're going to encounter when you delve into XPages Mobile development is trying to put a Tab Bar at the bottom of the screen that actually stays at the bottom of the screen. We were able to incorporate this by implementing the Dojo ScrollablePane as a custom dijit. We needed to pursue this route as

Read more

Posted in Dojo, Mobile, XPages

Here lately, I've been working on getting events to fire within a mobile application in XPages. For example when a page first loads (i.e. is navigated to but not "transitioned" to) or when a transition/navigation to another page within the single page application. No events are published or made available via the domino designer IDE but we still need to be able to do something when a navigation/transition event happens. So, how do we do this and what are the event names? Well the dojo event names are: onStartView – Only works with Domino 9 or Dojo 1.8 onBeforeTransitionIn onAfterTransitionIn onBeforeTransitionOut onAfterTransitionOut These events should provide you a means to run

close

Here lately, I've been working on getting events to fire within a mobile application in XPages. For example when a page first loads (i.e. is navigated to but not "transitioned" to) or when a transition/navigation to another page within the single page application. No events are published or made available via the domino designer IDE but we still need to be able to do something when a navigation/transition event happens. So, how do we do this and what are the event names? Well the dojo event names are: onStartView – Only works with Domino 9 or Dojo 1.8 onBeforeTransitionIn onAfterTransitionIn onBeforeTransitionOut onAfterTransitionOut These events should provide you a means to run

Read more

Posted in Dojo, Mobile, XPages