In this show Jesse Gallagher returns to give us an introduction to this amazing Framework he’s created to try and improve the XPages coding experience.
I can’t say that I totally “get it” yet BUT it looks VERY interesting. I have so far taken the “controller” piece from the framework and I’m successfully using that in my applications and I’ll be featuring that on NotesIn9 very soon. It’s really improved how I create my applications.
In this show Dan Friedrich, a brand new contributor joins the Hackathon! He’s a customer (like me!) that’s been doing a lot with XPages. He’s going to talk about using Bootstrap and Font Awesome in your XPages applications.
Before the demo I take a little time to update the status of the XPages Mobile Controls and iOS8 issues as well as some overall personal opinions on the Mobile Controls themselves.
The demo starts around the 10:00 if you want to skip over my opinion stuff.
Dan’s site is: https://xpagesandme.wordpress.com/
In this show, Jesse Gallagher officially starts the NotesIn9 Hackathon with a great introduction on “custom renderers” in XPages. While this seems to be a really scary topic, Jesse explains it in a way that even I can grasp it.
Just to quickly recap the 3 problems that I know about.
1. Uploading photos to a web app doesn’t work.
2. XPages Mobile Controls don’t work
3. An Edit box with Typehead / drop down selection doesn’t work.
Problem 1 is clearly in Apple’s court. Hopefully that will get fixed in 8.0.1
Problem 2 is being investigated by IBM as we speak. That’s all I know about that. I have heard from others that Mobile controls will KINDA work if when tapping you hold your finger down for at least 10 seconds or so. I’ve seen this work but not constantly for me.
Now the big one. Issue 3. We use typeahead a LOT so this is a big one for us as well. It appears to me that 9.0.1 FixPack 2 completely fixes this!!! Woo Hoo!!
So if that affects you, or you have other dojo related issues with iOS8 you might want to test FixPack 2 to see if that helps. Just note that in addition to a more recent version of Dojo it also includes a new CKEditor which has caused some people problems I believe.
Good Luck
1.) JT reports that it might be working somewhat – BUT you need to “hold your tap” for 10-ish seconds. http://www.bleedyellow.com/blogs/NotesShop/entry/io8_xpages_mobile_controls_update?lang=en_us
This was confirmed by others. Personally I could NOT get this to work even once on my iOS8 iPad 3 but did see it work once on my iPhone 5s. I would not consider this a workaround.
If anyone cares to try I set up a test page here: http://watchtower.notesin9.com/mobileTest.nsf/m_home.xsp
2.) At the day job we created an PMR with IBM labeling this a critical problem. Since that’s specific to us I can’t share that number but would encourage others to submit this problem report as well. If you do submit this as a problem IBM might ask for code so they can reproduce it. I’ve include the XSP code from my test page at the end of this post.
3.) Via a comment on one of my recent blog posts The XPages team is investigating this issue.
<?xml version=“1.0” encoding=“UTF-8”?>
<xp:view xmlns:xp=“http://www.ibm.com/xsp/core” xmlns:xe=“http://www.ibm.com/xsp/coreex”>
<xe:singlePageAppselectedPageName=“Home” id=“singlePageApp1”>
<xe:appPagepageName=“Home” resetContent=“true” id=“appPage1”>
<xp:panel>
<xe:djxmHeadinglabel=“Home” id=“djxmHeading1”>
<xp:this.facets>
<xp:panelxp:key=“actionFacet”></xp:panel>
</xp:this.facets>
</xe:djxmHeading>
<xe:outlineid=“outline1”>
<xe:this.treeNodes>
<xe:basicLeafNodelabel=“Page 1” href=“#Page1”></xe:basicLeafNode>
<xe:basicLeafNodelabel=“Page 2” href=“#Page2”></xe:basicLeafNode>
</xe:this.treeNodes></xe:outline>
</xp:panel>
</xe:appPage>
<xe:appPagepageName=“Page1” resetContent=“true” id=“appPage2”>
<xp:panel>
<xe:djxmHeadinglabel=“Page1” back=“Back” moveTo=“Home” id=“djxmHeading2”>
<xp:this.facets>
<xp:panelxp:key=“actionFacet”></xp:panel>
</xp:this.facets>
</xe:djxmHeading>
</xp:panel>
</xe:appPage>
<xe:appPagepageName=“Page2” resetContent=“true” id=“appPage3”>
<xp:panel>
<xe:djxmHeadinglabel=“Page2” back=“Back” moveTo=“Home” id=“djxmHeading3”>
<xp:this.facets>
<xp:panelxp:key=“actionFacet”></xp:panel>
</xp:this.facets>
</xe:djxmHeading>
</xp:panel>
</xe:appPage>
</xe:singlePageApp></xp:view>
This information comes from Sven Hasselbach. I’ve not tried this myself. Use at your own risk.
=====
You can use other Dojo versions on a server by downloading the current version from dojotoolkut.org
You have to unpack it into data/domino/js, rename it to dojo-1.10.1 and then copy the IBM stuff (folders “ibm” and “template”) to it
Resource Aggregation must be disabled and it requires a restart of the server.
Currently have running dojo 1.10.1 on a 8.5.3 Machine with the XSP of 9.0.0
This is more complex because of the resource aggregation
But keep in mind that this affects all apps on the server (the latest Dojo version found wins)
To prevent this, you can give it a “lower” version number and set it in the application in the XSP properties
In the day job I have users that use an iPad to upload photos to an XPages application.
I just learned today that this breaks with iOS8. More information can be found here:
http://www.mobilexweb.com/blog/safari-ios8-iphone6-web-developers-designers
http://stackoverflow.com/questions/25790873/uploading-files-over-http-fails-on-ios-8-gm-safari
http://blog.uploadcare.com/post/97884147203/you-cannot-upload-files-to-a-server-using-mobile-safari
I’m hopeful this is a BUG that will be fix and not something Apple has intentionally done.
For now the plan is to just hide the upload button if you’re running iOS 8. Note we use my fileVault thing which will likely be my next blog post and not the file upload control that comes with XPages.
Below is the quick and dirty code I’m going to try and use to hide the button to iOS 8 users. This will not work most likely for iOS 8.0.1. Since we don”t know if it’ll be fixed then we’ll simply cross that bridge when we come to it.
Note: This code is intended to run on Domino 9.0.1 so I make use of the deviceBean that’s built in.
UPDATE: Made some updates to the code
function isApple8() {
var uAgent = context.getUserAgent().getUserAgent();
if ((deviceBean.isIpad()) || (deviceBean.isIphone())) {
// Note the space after the 8
if (uAgent.indexOf(“8.0 “) > 0) {
// This is iOS 8
return true;
} else {
// This is iOS but NOT version 8
return false;
}
} else {
// this is NOT iOS
return false;
}
}
In this show Greg Reeder, XPage developer returns for part 2 of his series to talk some Java programming and how you might be able to use it to build a logging control for errors and messages.
This is the third of a 3 part series from Greg which I’m publishing all at once due to the length and complexity of the information.
In this show Greg Reeder, XPage developer and new contributor joins the show to talk some Java and how you might be able to use it to build a logging control for errors and messages.
This is the first of a 3 part series from Greg which I’m publishing all at once due to the length and complexity of the information.
I’m really excited to have a NEW contributor today. Please welcome Dan Soares to the show! Well kinds of at least. I’ve been trying to get him on for a LONG time and while I’ve yet to get a video I have received from him a great article and sample database on using resource bundles in XPages.
Thanks Dan!
P.S. If your company blocks videos either from this site or YouTube, please print this article out on the company printer, read it on company time and have a little chuckle when done!
Using resource bundles to store configuration information in your XPages application