Quantcast
Channel: XPages and more
Viewing all 628 articles
Browse latest View live
↧

Bootstrap Plugins in XPages Part XIII - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (5)

June 8, 2016, 2:12 pm
$
0
0
In my previous blog post I described how to install Bootstrap plugins using Node and Bower, the setup of SourceTree , the placing (positioning) of the Bower files and the final installation of the Bootstrap plugins (Packages) into the XPages application. In this blog post we take a closer look at the imported files in the XPages application when using Bower to install Packages (Bootstrap Plugins). This blog post is also an introduction to a deep dive into Bower including a number of solutions in order to download only the files that are necessary for the specific Bootstrap Plugin in an XPages application.

Bootstrap Plugins in XPages
Part I : Bootstrap-select - A jQuery plugin that utilizes Bootstrap's dropdown.js
Part II : Bootstrap FileStyle - Customization of input file for Bootstrap
Part III : Dialog Boxes using Bootbox
Part IV : Awesome Bootstrap Checkbox
Part V : jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes
Part VI : jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes (2)
Part VII : MagicSuggest A Multiple Selection Combobox
Part VIII : Bootstrap Maxlength
Part IX : Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (1)
Part X : Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (2)

Before we take a closer look at the imported files first some considerations that have to be taken into account when using Bower to install Packages.
First of all, any changes in the source code of the packages is futile. The next update will override everything. So, for example, no more throwing components out of Bootstrap to reduce size because we don't need them.
Secondly the package we are searching for might not exists. We do not have a lot of options in this case and will still have to revert back to the good old find, download, extract and copy way.
Finally when using a standard Bower install based on a bower.json file and a .bowerrc file, Bower installs entire repositories. This means that all files from the repository are imported and NOT only the files that are needed for a specific Package (Bootstrap Plugin) to make it work in an application.
This is a major disadvantage of the standard installation of Bootstrap Plugins using Bower.

Let's take a closer look at the Select2 files we imported in the previous blog post. Based on the bower.json file we used, Select2 4.0.3 has been installed in the On-Disk Project (ODP) after running 'bower install'.

{
    "name": "bower4xpages",
    "version": "1.7.9",
    "dependencies": {
        "bootstrap": "latest",
        "moment": "latest",
        "select2": "latest",
        "fontawesome": "latest"
    },
    "private": true
}


After syncing the ODP (On-Disk Project) with the NSF in the Domino Designer (DDE) the following files have been imported in the Select2 folder in the XPages application.


However, to use Select2 within an XPages application we only need the files in the dist folder.


For me personally this is not the desired outcome. A large number of files have been installed in the NSF that are completely unnecessary for the functioning of the Bootstrap plugin in an XPages application. In the next blog posts we take a deep dive into Bower and provide some solutions how to grab only the files which are really needed for a Bootstrap Plugin when using Bower for installing Packages in XPages applications.
↧
Search

Bootstrap Plugins in XPages Part XIV - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (6)

June 9, 2016, 2:11 pm
$
0
0
In the previous blog post we examined the imported files in the XPages application when using Bower to install Packages (Bootstrap Plugins). We noticed that Bower installs entire repositories and not just the files that we need. In this blog post a first introduction to bower-installer for installing Packages in an XPages application. bower-installer is a tool for installing bower dependencies that won't include entire repos. Although Bower works great as a light-weight tool to quickly install browser dependencies, it currently does not provide much functionality for installing specific "built" components for the client. As mentioned before Bower installs entire repositories and that is not what we want!
If bower install is run on a configuration file (bower.json), the entire repository will be pulled down and copied into a specific directory (.bowerrc). This repository is often quite large, when probably only a built js and css file are needed.
In this blog post I will describe the first basic usage of bower-installer and the first steps to get only the files we need in the On-Disk Project and, after sync with the NSF, in the XPages application.

Bootstrap Plugins in XPages
Part I : Bootstrap-select - A jQuery plugin that utilizes Bootstrap's dropdown.js
Part II : Bootstrap FileStyle - Customization of input file for Bootstrap
Part III : Dialog Boxes using Bootbox
Part IV : Awesome Bootstrap Checkbox
Part V : jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes
Part VI : jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes (2)
Part VII : MagicSuggest A Multiple Selection Combobox
Part VIII : Bootstrap Maxlength
Part IX : Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (1)
Part X : Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (2)
Part XIII - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (5)

Using bower-installer
First, we need to install the bower-installer package. For the installation we use Node and npm to install bower-installer globally. Open the Node command prompt and enter: npm install -g bower-installer. After installing, the simplest way to use bower-installer is to specify the path you would like to use. bower-installer will try to grab the relevant, main, files, but if it can’t because the main files aren’t defined, then there is always a possibility to override with the specific files you want.

Bower.json file
The second step is to create a bower.json file. Bower installer provides an easy way for the main files to be installed or moved to one or more locations. Simply add to the bower.json an install key and path attribute. In the example below I use Select2 as only dependency in the bower.json file (for demonstration purpose only). The bower.json file should look similar to the following example below. Furthermore no .bowerrc file is used in order to prevent that the entire repository will be installed in the On-Disk Project.

{
  "name": "Bower4Xpages",
   "description": "Bower",
  "private": true,
  "ignore": [
    "**/.*",
    "node_modules",
    "bower_components",
   "test",
    "tests"
  ],
  "install" : {
  "path" : "bowertestodp/webcontent"
  },
  "dependencies": {
  "select2": "latest"
    }
}

Run bower-installer
From the Node command prompt, in the same directory as the bower.json file, enter: bower-installer


After installation, two directories have been created in the SourceControl directory where the On-Disk Project directory is included.
First a new bower_components directory has been created outside the On-Disk Project directory. This directory contains the entire repository of Select2 including a Select2 bower.json file which contains the main files which have been installed in the On-Disk Project directory. 



So based on the bower.json file in the Select2 repository in the bower_components directory ONLY the Select2 main files have been installed in the On-Disk Project in the directory WebContent/Select2 based on the created bower.json file in step 2 (install path).


The Select2 bower.json file includes the following installation information for bower-installer. The files select2.js and core.scss are the main Select2 files in the Select2 bower.json file.

{
  "name": "select2",
  "description": "Select2 is a jQuery based replacement for select boxes. It supports searching, remote   data sets, and     infinite scrolling of results.",
  "main": [
  "dist/js/select2.js",
  "src/scss/core.scss"
  ],
  "repository": {
  "type": "git",
   url": "git@github.com:select2/select2.git"
  },
  "homepage": "https://github.com/ivaynberg/select2",
  "version": "4.0.3",
  "_release": "4.0.3",
   "_resolution": {
   "type": "version",
   "tag": "4.0.3",
   "commit": "566c7846fbf8c3b7674346f26d0ee872c0a77629"
  },
  "_source": "https://github.com/ivaynberg/select2.git",
  "_target": "*",
  "_originalSource": "select2"
}

The final result after sync the On-Disk Project with the NSF in Domino Designer (DDE). Only the main files are installed in the XPages application.


This is a significant step forward and already works a lot better than the standard Bower installation but we still don't have all the files we need to make Select2 work in an XPages application. Problem is also that a lot of registered components (packages) for Bower do not include a bower.json configuration. Therefore, Bower does not know about any "main files" and therefore, by default bower-installer doesn't know about them either. Finally we have a problem with the bower_components directory. This directory is included in the git repository and also in SourceTree and will be synced with the NSF. So for now the bower_components directory should be removed after running bower-installer in Node and before syncing with the NSF. It will be recreated when running bower-installer again in Node.
But there is a solution for these problems. bower-installer can override an existing main file path or provide a non-existant one. In the next blog post a closer look at overriding the main files and installing multiple main files using bower-installer.
↧
↧

Webinar - Using Bootstrap Plugins in XPages including Bower - Git - Node - SourceTree and More

June 12, 2016, 2:09 pm
$
0
0
This Thursday my second webinar, Expanding XPages with Bootstrap Plugins for Ultimate Usability is scheduled. Registration is open on the T.L.C.C. website.


Content of the Webinar
Develop highly user friendly responsive web (XPages) applications by making use of Bootstrap and JQuery Plugins as Select2, DateTimePickers, Multiselect, Confirmation, Modals, Popovers and Notifications for ultimate usability based on the latest versions of these plugins, including solutions for the AMD problem.
Furthermore the installing of Bootstrap plugins in XPages Applications will be discussed. A demonstration will be given of the 'classic' way to implement Bootstrap Plugins within XPages Applications but also by using Bower, Node, Git and Source Tree.
Expect more of XPages Applications and go beyond the basics. Comprehensive demos of several plugins are shown during this webinar.

Main topics during this Webinar are:
Introduction
Top Resources for XPages and Bootstrap
Implementation External Bootstrap Plugins
AMD (Asynchronous Module Definition)
Demo's Bootstrap Modals, LightBox, Unite Gallery, Select2, Multiselect, DateTimePickers, Viewer and More
Bower for XPages -Demo
Reusable Bootstrap Fields 


For more information: XPages Webinar Series with T.L.C.C and Teamstudio
Missed a Webinar? Look here for the recorded webinars.
↧

Bootstrap Plugins in XPages Part XV - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (7) - Overriding main files

June 14, 2016, 2:56 pm
$
0
0
In the previous blog post I have given a brief introduction of bower-installer. bower-installer is a tool for installing bower dependencies that won't include entire repos. The problem which has been encountered with bower-installer in the previous blog post was that not all files which were required for the package (Bootstrap plugin) were installed in the On-Disk Project based on the bower.json file of the Package itself. For this problem there is an easy solution.

Bootstrap Plugins in XPages
Part 01 - Bootstrap-select - A jQuery plugin that utilizes Bootstrap's dropdown.js
Part 02 - Bootstrap FileStyle - Customization of input file for Bootstrap
Part 03 - Dialog Boxes using Bootbox
Part 04 - Awesome Bootstrap Checkbox
Part 05 - jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes
Part 06 - jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes (2)
Part 07 - MagicSuggest A Multiple Selection Combobox
Part 08 - Bootstrap Maxlength
Part 09 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (1) - Bower
Part 10 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (2) - DDE
Part 13 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (5) - Bower Files
Part 14 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (6) - Introduction bower-installer

As mentioned before, a lot of registered components for bower do not include bower.json configuration. Therefore, bower does not know about any "main files" and therefore, by default bower-installer doesn't know about them either. Bower-installer can override an existing main file path or provide a non-existant one.
In the following Select2 is used as an example. For Select2 at least the files 'select2.js' and 'select2.css' are required to make the plugin work in an XPages application.
For this the bower.json file has to be changed so that the necessary files are installed in the On-Disk Project and the bower.json file of Select2 itself (in the bower_components directory) will be overwritten.
In many situations it is necessary to install multiple files from a single component, like Select2. This can be accomplished by providing an Array instead of a String inside the hash sources of the bower.json file. To install multiple files the bower.json file should look like this

{
  "name": "Bower4Xpages",
  "description": "Bower",
  "private": true,
  "dependencies": {
  "select2": "latest"
    },
  "install": {
        "path":  "bowertestodp/webcontent",      
  "sources" : {
      "select2": [
      "bower_components/select2/dist/css/select2.css",
      "bower_components/select2/dist/css/select2.min.css",
      "bower_components/select2/dist/js/select2.js",
      "bower_components/select2/dist/js/select2.min.js"
       ]
      }  
   }
}

After running bower-installer in Node only the required files, indicated in the bower.json file, are now installed in the On-Disk Project in the directory WebContent..


Directoy WebContent in the On-Disk Project.


This solves the first problem concerning the files which are really necessary for the packages.
In the next blog post the solution to the second problem, the bower_components directory (including some other files), that should not be included in the Source Tree and the On-Disk Project.

↧

#NewWayToLearn - XPages And Boostrap Webinar - Expanding XPages with Bootstrap Plugins including Node, Git, Bower and SourceTree

June 17, 2016, 4:28 am
$
0
0

This webinar was part of the of technical enablement program for IBM Business Partners, #NewWayToLearn. For more information: X.1.2 Expanding XPages with Bootstrap Plugins for ultimate usability.

Content of the Webinar
Develop highly user friendly responsive web (XPages) applications by making use of Bootstrap and JQuery Plugins as Select2, DateTimePickers, Multiselect, Confirmation, Modals,Popovers and Notifications for ultimate usability based on the latest versions of these plugins, including solutions for the AMD problem. Furthermore the installing of Bootstrap plugins in XPages Applications will be discussed. Expect more of XPages Applications and go beyond the basics and create applications that nobody ever thought possible using XPages. Comprehensive demos of several plugins are shown during this webinar.

A recording of this webinar is available on the #NewWayToLearn website: Recorded Webinar. You can also download the recorded webinar, Download Recorded Webinar. This was my first webinar so be a little generous in your judgment and I must admit I'm a better writer than speaker but I at least have participated in the program.


↧
↧

Quick Tip: GetDocumentByUnid Method in LotusScript Agents

June 17, 2016, 7:06 am
$
0
0


In the past period we were frequently faced with the 4091 error message, 'Invalid universal id' using the LotusScript GetDocumentByUNID method in an Agent.
In the specific Notes Database Application some Query definitions were used where the DocumentUnid was stored in an environment variable. The Unid was then used in an Agent to display the results of the Query definition in a Folder. Problem we frequently encountered was the error 4091 Message: Invalid universal id”
The method getDocumentByUNID NotesDatabase class returns the appropriate document for the UniversalUnid passed as argument, but it does not return Nothing if it does not find the document but the error 4091. Also it may return an irrelevant "ghost" Lotus Notes document, also known as a deletion stub.
By a colleague we were pointed to the following LotusScript function, DatabaseGetDocumentByUnid. We added this function in a Script Library and adjusted the corresponding Agent accordingly. The result: no more 4091 errors!

Function DatabaseGetDocumentByUnid (db As NotesDatabase, unid$) As NotesDocument
On Error 4091 Resume Next
Set DatabaseGetDocumentByUnid = Nothing
Set DatabaseGetDocumentByUnid = db.GetDocumentByUnid(unid$)
If Err = 4091 And ( DatabaseGetDocumentByUnid Is Nothing ) Then
Err = 0
Set DatabaseGetDocumentByUnid = Nothing
Exit Function
End If
If DatabaseGetDocumentByUnid Is Nothing Then
Set DatabaseGetDocumentByUnid = Nothing
Exit Function
End If
If DatabaseGetDocumentByUnid.Size = 0 Or DatabaseGetDocumentByUnid.UniversalID = "" Or DatabaseGetDocumentByUnid.IsDeleted Then
Set DatabaseGetDocumentByUnid = Nothing
Exit Function
End If
End Function

More information about How to correctly use the GetDocumentByUnid method in LotusScript: TechTarget - SearchDomino
↧

Domino 9.0.1 Fix Pack 6 Interim Fix 1 available for download on IBM Fix Central

June 19, 2016, 10:01 am
$
0
0


9.0.1 FP6 IF1 is available for only W64, Linux64, and AIX64 platforms. 9.0.1 FP6 IF1 will be a requirement for the upcoming on-premise release of IBM mail support for Microsoft Outlook.


NRBYAA2G9G
C&S APIs - If CalUpdateEntry adds an attendee for the series, only the first instance is updated

NRBYAAJJJ3
Meetings across DST boundaries from C&S APIs or IBM mail support for Microsoft Outlook (IMSMO) show bogus times if server is not in client timezone.

NRBYAABTGX
Cached profile documents causing high shared memory consumption during IMSMO long run

Downloads:
Domino 9.0.1 Fix Pack 6 Interim Fix 1 W64
Domino 9.0.1 Fix Pack 6 Interim Fix 1 Linux64
↧

Demo Database Webinar Expanding XPages with Bootstrap Plugins including Node and Bower

June 19, 2016, 2:13 pm
$
0
0
On June 16th T.L.C.C. and Teamstudio have given me the opportunity to conduct a webinar, Expanding XPages with Bootstrap Plugins for Ultimate Usability. A big thank you to Paul Della-Nebbia and Howard Greenberg from T.L.C.C. and Courtney Carter from Teamstudio.


Content of the Webinar
Develop highly user friendly responsive web (XPages) applications by making use of Bootstrap and JQuery Plugins as Select2, DateTimePickers, Multiselect, Confirmation, Modals, Popovers and Notifications for ultimate usability based on the latest versions of these plugins, including solutions for the AMD problem.
Furthermore the installing of Bootstrap plugins in XPages Applications will be discussed. A demonstration will be given of the 'classic' way to implement Bootstrap Plugins within XPages Applications but also by using Bower, Node, Git and Source Tree.
Expect more of XPages Applications and go beyond the basics. Comprehensive demos of several plugins are shown during this webinar.

Demo Database
In this blog post the corresponding demo database can be downloaded.  In this demo database you can find numerous examples of Bootstrap Plugins in an XPages application such as Select2, Bootstrap DateTimePicker, MultiSelect, FontAwesome Checkboxes, Notifications, Models, Galleries and Reusable Bootstrap Fields including validation.
In several examples in the demo database you can find a link to the corresponding blog post on XPages and More. In the demo database there are also some examples included concerning the AMD Fix.
Download Webinar Demo Database

Some remarks: The current version of the demo database uses the OpenNTF Bootstrap4XPages plugin. Next month I will publish a new version of the demo database based entirely on the OpenNTF Extension Library with more examples of Bootstrap and jQuery plugins in XPages applications. With this new version also a demonstration video will be published. Furthermore the demo database is set up for demonstration purposes only. Check the Custom Controls or XPages for the code examples.
Below some examples from the Demo Database.

Download Webinar Demo Database
↧
Search

Notes Domino XPages Communities and XPages Top Resources

June 20, 2016, 2:24 pm
$
0
0


As you may know, I am Moderator of the Google+ XPages Community (and Curator of Collaboration Today). Together with the owner Rob Bontekoe, my old XPages teacher, the Google+ XPages community was founded some years ago.
The aim of this community is to promote XPages as a development tool and sharing information about XPages, Notes Domino and IBM XPages for Bluemix.

At this time, the community has 506 members and is still expanding!
If you are not yet a member of this community and want to be kept informed of the latest news and if you want to share news about Notes Domino and XPages then join the Google+ XPages Community now.
The more members the more news and the more it is shared within our amazing community.

Link to the Google+ XPages Community : XPages Community


There are a lot of great Notes Domino and XPages resources available. Below my favorite resources, news aggregators and blogs.

1. NotesIn9 - David Leedy
This site mostly focused on Web development by primarily using XPages technology from IBM Domino Servers but you never know when other technology might show up.

2. Collaboration Today
Collaboration Today is a news aggregator for IBM Collaboration Solutions professionals covering news about various IBM products like IBM Connections, IBM Domino, IBM WebSphere Portal etc. and cross product topics like mobile, cloud and analytics.

3. Planet Lotus
Planet Lotus is an aggregation of Lotus related blogs and news. It acquaints those interested in the Lotus Blogosphere with the best blogs out there. 278 Lotus blogs updated hourly.

4. XPages.info
Get started with XPages, Downloads, Demos, Resources and Videos.
XPages is a web and mobile application development platform. It allows IBM Lotus Notes data as well as data from relational and other data sources to be displayed to browser clients on all platforms.
The programming model is based on standards and common web development skills like JavaScript, Ajax, the Dojo Toolkit, Server-side JavaScript, and JavaServer Faces. XPages leverages IBM Lotus Domino functionality, like its NoSQL document-oriented database.

5. Stackoverflow
A great resources for questions and answers about XPages. Just search for XPages or for a specific part of XPages. Stackoverflow is a language-independent collaboratively edited question and answer site for programmers.

6. Notes Domino XPages development forum

7. OpenNTF
OpenNTF was launched in 2002 by committed members of the Lotus Notes/Domino community. The organization provided a hosting site for sharing applications and useful code for the Notes and Domino platform. Projects have included full blown client and web applications, rich client plugins, administrative tools and more. Over the years the scope of OpenNTF has expanded, to include IBM Sametime, IBM Connections, IBM Connections Cloud, IBM Forms, IBM Websphere Portal and beyond. In 2015 we anticipate including content for the IBM Bluemix platform.

8. Slack XPages Community

My favorite and highly recommended blogs:

- Oliver Busse
- Xcellerant - Brad Balassaitis
- Xomino - Mark Roden
- XPageDeveloper - Fredrik Norling
- Notes Speak - Steve Zavocki
- LinQed - Mark Leusink
- Intec Blog - Paul Withers
↧
↧

Replay Webinar Expanding XPages with Bootstrap Plugins for Ultimate Usability including Node and Bower

June 20, 2016, 3:42 pm
$
0
0
On June 16th my Webinar 'Expanding XPages with Bootstrap Plugins for Ultimate Usability' was organized by T.L.C.C and Teamstudio. For those who missed this webinar below the content, demo database, slides and video. I would like to thank Paul Della-Nebbia and Howard Greenberg from T.L.C.C. and Courtney Carter from Teamstudio for giving me this opportunity. I hope I get a second opportunity for a second webinar to go more deeply into Bower and bower installer to install Bootstrap and jQuery plugins in XPages.

Content of the Webinar
Develop highly user friendly responsive web (XPages) applications by making use of Bootstrap and JQuery Plugins as Select2, DateTimePickers, Multiselect, Confirmation, Modals, Popovers and Notifications for ultimate usability based on the latest versions of these plugins, including solutions for the AMD problem.
Furthermore the installing of Bootstrap plugins in XPages Applications will be discussed. A demonstration will be given of the 'classic' way to implement Bootstrap Plugins within XPages Applications but also by using Bower, Node, Git and Source Tree.
Expect more of XPages Applications and go beyond the basics. Comprehensive demos of several plugins are shown during this webinar.


Demo database
The corresponding demo database can be downloaded via this link: Demo Database Webinar
In this demo database, you can find numerous at examples or Bootstrap Plugins in an XPages application zoals Select2, Bootstrap DateTimePicker, Multi Select, Font Awesome Check Boxes, Notifications, Models, galleries and Reusable Bootstrap Fields-including validation.
In several at examples in the demo database, you can find a link to the blog post correspondance thing on XPages and More. In the demo database there are some usefull examples included Concerning the AMD Fix.


Video and slides



↧

Bootstrap Plugins in XPages Part XVI - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (8) - Using .gitignore

June 22, 2016, 2:14 pm
$
0
0
In the previous blog posts I have given a brief introduction of bower-installer and how to install only the files needed for the specific Bootstrap or jQuery plugin to make it work in an XPages application based on a bower.json file. In this blog post I will describe the solution to the last problem which with the use of bower-installer did came forward, the bower_components directory, that should not be included in SourceTree and the On-Disk Project. bower-installer is a tool for installing bower dependencies that won't include entire repositories.

Bootstrap Plugins in XPages
Part 01 - Bootstrap-select - A jQuery plugin that utilizes Bootstrap's dropdown.js
Part 02 - Bootstrap FileStyle - Customization of input file for Bootstrap
Part 03 - Dialog Boxes using Bootbox
Part 04 - Awesome Bootstrap Checkbox
Part 05 - jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes
Part 06 - jQuery and JavaScript AMD (Asynchronous Module Definition) Fixes (2)
Part 07 - MagicSuggest A Multiple Selection Combobox
Part 08 - Bootstrap Maxlength
Part 09 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (1) - Bower
Part 10 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (2) - DDE
Part 13 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (5) - Bower Files
Part 14 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (6) - Introduction bower-installer
Part 15 - Using Node.js - Bower - Git and SourceTree to install Bootstrap Plugins (7) - Overriding main files

Create a local .gitignore file
To ensure that the bower_components directory is not included in SourceTree and the On-Disk Project we can use a relatively simple solution, a local .gitignore file.
Basically a gitignore file specifies intentionally untracked files that Git should ignore. .gitignore is a file which lists files and directories that should not include as part of a repository.
.gitignore interprets direct filenames and wildcards (both of which are recursive, front and back). This recursive behavior can be stopped by adding a leading / to the line. Certain files can also be excepted from wildcards by using the ! syntax.
Files already tracked by Git are not affected. Each line in a gitignore file specifies a pattern. When deciding whether to ignore a path, Git normally checks gitignore patterns from multiple sources, with a specific order of precedence, from highest to lowest. For more info about the patterns see the Git documentation.

In this example I use only one line in the .gitignore file to ignore the bower_components directory.
First create a .gitignore.txt file with the following line:
bower_components/
Next save the .gitignore.txt file in the local work directory, the Source Control directory, do not position the file in the On-Disk Project directory, and open the Windows Command Prompt (Press “Win + X”, and select Command Prompt, or Command Prompt (Admin) to open the Command Prompt). Finally rename the .gitignore.txt file to .gitignore by typing ren .gitignore.txt .gitignore
The Source Control directory should now look like this:


SourceTree
After running bower-installer in Node the bower_components directory is created in the local Source Control direcory.


With the positioning of the .gitignore file in the local Source Control directory the bower_components directory will not be added to the repository in SourceTree.


Domino Designer
After refreshing the On-Disk Project (ODP) in the Domino Designer (DDE) and syncing the ODP with the NSF file the bower_components folder is also not added to the XPages application simply because the bower_components directory is not present in the ODP by the existence of the .gitignore file!


The simple .gitignore file solves the last problem using bower-installer for installing Bootstrap and jQuery plugins in XPages applications.
Conclusion, there is a very simple solution to get only the files you need for the specific packages without installing the entire repository of these packages. So go beyond the basics for a clean design without entire repositories in your XPages applications!
↧

IBM Client Application Access 1.0.1 (ICAA) Enhancements

June 26, 2016, 4:18 am
$
0
0
IBM® Client Application Access (ICAA) is a small, stand-alone application that allows you to work with your IBM Notes® and IBM Domino® applications. It is supported on Microsoft Windows and Mac OS systems.


ICAA is integrated with IBM Verse and IBM SmartCloud® Notes web mail clients. For on-premises users, ICAA is integrated with IBM iNotes®. When you use one of these brower-based mail clients and receive an email that contains a link or button to a Notes application, you can click the link or button to open the application in ICAA. You can also open ICAA by clicking its icon on the Desktop. From ICAA, you can open your browser-based mail client to access your mail.
Along with local applications, IBM® Client Application Access supports applications on older IBM Domino® server versions, for example, 8.0.x and 8.5.x. However, using Domino version 9.0 or later version is recommended so that you can take advantage of the latest enhancements.

IBM® Client Application Access (ICAA) and IBM Notes® release 9.0 or later can co-exist on your system. In this case, you can use either Notes or ICAA. When you open an application and Notes is not running, the application is opened in ICAA.
The following table describes dual-client installation scenarios, both supported and unsupported.


ICAA 1.0.1 includes the following enhancements and is available for download:
  • To provide an improved user experience, ICAA runs as a stand-alone application on both Mac OS and Microsoft Windows. Previously, ICAA on Windows ran in a browser.
  • Support is added for all @commands.
  • For improved IBM Verse integration, it offers a look and feel consistent with the Verse user interface.
  • ICAA can now co-exist with IBM® Notes® 9.0 or 9.0.1. When you install ICAA and Notes is already installed, Notes stays on your computer and ICAA uses the Notes data directory.

For more information, see the IBM Client Application Access 1.0.1 documentation. For download search for Part Number WIN CNA9XEN.
↧

Bootstrap Plugins in XPages Part XVII - Using Node.js, Bower, Git and SourceTree to install Bootstrap Plugins (9) - Recap

June 28, 2016, 2:17 pm
$
0
0
In this final blog post about installing Bootstrap Plugins in XPages Applications using Node, Git, SourceTree and bower-installer a recap of the previous blog posts. Main objective is to install only those files that are required for the Bootstrap or jQuery plugin to make it work in an XPages application and NOT the entire repository of these packages. So go beyond the basics for a clean design without entire repositories in your XPages applications!
In the following, a brief recap of the requires steps to use bower-installer for installing Bootstrap and jQuery plugins in XPages applications.

1. The basic structure of the environment 
To install Bootstrap and jQuery Plugins in XPages applications using bower-installer first a basic environment needs to be setup. bower-installer requires Node, Node Package Manager (npm) and Git. For the basic environment Node.js, Git, SourceTree and bower-installer needs to be installed on the local system.


2. Create Local Repository Directories
After the setup of the basic environment the local repository directory needs to be created. First create a local directory SourceControl, or another name of your own choice, on your system. This will be the local repository. The folder can be created, for example, in the My Documents directory. Next create in the SourceControl folder a new directory Git and a new directory Hg. Open the Git directory and create a new directory BowerForXPages. Open the BowerForXPages directory and create a sub-directory Bower4XPagesODP. The ODP (On-Disk Project) is placed in a subdirectory of the Git project directory so the .git directory will not be synced with the NSF. The names of the work- and ODP directories can be customized to your own preferences.


3. Domino Designer
In the Domino Designer first create a new XPages Application, in this example, BowerForXPages.
Next step is to setup the BowerForXPages application for Source Control in the Domino Designer. In the Domino Designer (DDE) select Team Developement - Set Up Source Control for this Application.


Enter a Project name in the next screen and deselect the option 'Use default location'. Enter as folder location the directory BowerForXPagesODP.


4. SourceTree
The next step is to create a new repository in SourceTree. Open SourceTree. Select File - Clone / New. Next select the Tab + Create New Repository and select as Repository Type 'Git'. Select the folder BowerForXPages in the Destionation Path and select Create. Do NOT select the Bower4XPagesODP folder.


The new repository in SourceTree has now been created.


5. Bower-installer
For the installation of bower-installer use Node and npm to install bower-installer globally. Open the Node command prompt and enter: npm install -g bower-installer.
Next create a bower.json file that only installs the files needed for the package, in this example Select2, to work in an XPages application.

{
  "name": "Bower4Xpages",
  "description": "Bower",
  "private": true,
  "dependencies": {
  "select2": "latest"
    },
  "install": {
        "path":  "bowertestodp/webcontent",    
  "sources" : {
      "select2": [
      "bower_components/select2/dist/css/select2.css",
      "bower_components/select2/dist/css/select2.min.css",
      "bower_components/select2/dist/js/select2.js",
      "bower_components/select2/dist/js/select2.min.js"
       ]
      }
   }
}

6. Create a local .gitignore file
To ensure that the bower_components directory, which is created after running bower-installer in Node, and the locally created bower.json and .gitignore files are not included in SourceTree and the On-Disk Project you can use a relatively simple solution, a local .gitignore file.
First create a .gitignore.txt file with the following lines (use Notepad or Notepad ++):
bower_components/
bower.json
.gitignore
Next save the .gitignore.txt file in the local work directory. Do not position the file in the On-Disk Project directory. Next open the Windows Command Prompt (Press “Win + X”, and select Command Prompt, or Command Prompt (Admin) to open the Command Prompt). Finally rename the .gitignore.txt file to .gitignore by typing ren .gitignore.txt .gitignore

Place the bower.json file and the .gitignore file in the BowerForXPages directory.


After running bower-installer in Node only the required files, indicated in the bower.json file, are now installed in the On-Disk Project in the directory WebContent.


The WebContent Folder in the On-Disk Project in the SourceControl directory.


With the positioning of the .gitignore file in the local Source Control directory the bower_components directory and the locally created bower.json and .gitignore files are NOT added to the repository in SourceTree.


The last step is to refesh the On-Disk Project (right click ODP - Refresh) in the DDE (Package Explorer) and next select the option Synch with NSF (right click on ODP in the Package Explorer - Team Development - Synch with NSF). Only the selected files are installed in the XPages application!


Conclusion, there is a very simple solution to get only the files you need for the specific packages without installing the entire repository of these packages. So go beyond the basics for a clean design without entire repositories in your XPages applications!
↧
↧

Domino 9.0.1 Fix Pack 6 Interim Fix 2 available for download on IBM Fix Central

July 2, 2016, 3:07 am
$
0
0

Security Bulletin: IBM Domino is affected by an XStream XML information disclosure - CVE-2016-3674 (technote 1985960).
IBM Domino includes a version of XStream which could allow a remote attacker to obtain sensitive information, caused by an error when processing XML external entities.


Vulnerability Details
CVE-ID: CVE-2016-3674
Description: XStream could allow a remote attacker to obtain sensitive information, caused by an error when processing XML external entities. By sending specially-crafted XML data, an attacker could exploit this vulnerability to obtain sensitive information.
CVSS Base Score: 5.3 
CVSS Temporal Score: for more information  https://exchange.xforce.ibmcloud.com/vulnerabilities/111806 
CVSS Environmental Score*: Undefined 
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)

Affected Products and Versions
  • IBM Domino 9.0.1 FP6 IF1 and earlier releases 
  • IBM Domino 9.0. IF4 and earlier releases
  • IBM Domino 8.5.3 FP6 IF13 and earlier releases
  • IBM Domino 8.5 release

Remediation/Fixes


More information : Security Bulletin
Fix Download Link : Download Links for Domino 9.0.1 Fix Pack Interim Fixes
Fix Central Download Link: Domino 9.0.1 Fix Pack 6 Interim Fix 2

Customers who remain on the following releases may open a Service Request with IBM Support and reference SPR KLYHA8XLA2 for custom fixes.
  • IBM Domino 9.0.1 FP6 IF1 and earlier releases
  • IBM Domino 9.0 IF4 and earlier releases
  • IBM Domino 8.5.3 FP6 IF13 and earlier releases
  • IBM Domino 8.5 release

Get Notified about Future Security Bulletins
Subscribe to My Notifications to be notified of important product support alerts like this.
↧

Quick IBM Notes - XPages Tip: Comparing, Replacing and Restoring Design Elements with Local History using the Text Compare Editor in Domino Designer

July 3, 2016, 3:49 am
$
0
0
Last week something went completely wrong with some resources (design elements) in a modified design of an XPages application. Luckily Domino Designer has a very powerful feature, Local History. A standard Eclipse functionality of extremely great value. By using the Compare, Replace and Restore Resources functions with Local History using the Text Compare Editor the problems were quickly resolved. Below is a brief description of this very powerful feature in the Domino Designer.

A local edit history of a resource (design element), for example a Notes form, Custom Control or an XPage, is maintained when a resource is created or has been modified and saved. Each time a design element is modified and saved, a copy is saved so that the current design element can be replaced or restored with a previous edit or delete. It is also possible to compare the contents of all the local edits. Each edit in Local History is uniquely represented by the date and time the design element was saved. Only resources (design elements) have a local history; projects and folders do not.

Local History Settings
The Local History default settings can be modified by selecting Preferences - General - Workspace - Local History in the Domino Designer (DDE).


Comparing resources with Local History
To compare a design element (unmanaged Workbench resource) with a state in the Local History the following steps can be executed:
In one of the Navigation Views, select the design element (resource) that you want to compare with a local history state, for example a Custom Control or an XPage.
From the resource's pop-up menu, select Compare With> Local History. The Compare with Local History page opens.


Select a state in the Local History List. 


The Text Compare Editor opens.


Options Text Compare Editor
Click the Select Next Change and Select Previous Change buttons to browse the changes made between the state in the local history and the Workbench resource.
Copy all Non-Conflicting Changes from Right (Local History) to Left.
Copy Current Change form Right to Left
Next Difference
Previous Difference
Click OK when you are finished.

Replacing a resource with Local History
To replace a design element  with a state in the Local History the following steps can be executed: 
In one of the Navigation Views, select the design element (resource) that you want to replace with a local history state. From the resources pop-up menu, select Replace with> Local History. The Replace from Local History page opens.


Select a state from the Local History List. The Text Compare Editor opens.


Select the state you want to replace, and click Replace.

It is also possible to restore deleted design elements from local history. From the resource's pop-up menu, select Restore from Local History. The Restore From Local History dialog opens showing all files that were previously contained in the selected folder or project and all of their sub-folders.


So there is an easy way in the Domino Designer to compare, replace and restore one or more design elements with Local History in case something went completely wrong in the application design.
↧
Search

IBM Traveler 9.0.1.12 Now Available for Download on IBM Fix Central

July 13, 2016, 10:16 am
$
0
0
An upgrade package for IBM Traveler 9.0.1.12 server is now available on Fix Central.
A full installation package will be available on Passport Advantage by July 21, 2016. Relevant links are included below, including links to two new  Security Bulletins that were released today in conjunction with 9.0.1.12.
Below the Fix List for IBM Traveler 9.0.1.12 server.


Links for more information about IBM Traveler 9.0.1.12 server
List of APAR fixes
Fix Central Download link


9.0.1.12 Release Notes
Passport Advantage part numbers
Security Bulletin: XML External Entities Injection Vulnerability in IBM Traveler (CVE-2016-3039)
Security Bulletin: IBM Traveler installer impacted by vulnerability in InstallAnywhere (CVE-2016-2542)
↧

Quick XPages Tip - XPages ViewPanel Hide Empty Start and End Rows using CSS

July 20, 2016, 7:34 am
$
0
0
Last week I was faced with an annoying problem with the presentation of a simple XPages View in an iframe on an IPad. In this case I was only using a simple ViewPanel. As Application Theme I used Bootstrap 3. In the View properties I disabled the Pagers for the Header and Footer. However, when displaying the view in the browser there always were unnecessary empty leading and closing rows generated around the ViewData. So I posted a question on Stackoverflow. Below the simple code of the XPage with the ViewPanel.

Code XPage
<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
<xp:panel>
<xp:viewPanel id="viewPanel1" rows="5">
<xp:this.data>
<xp:dominoView var="view1" viewName="Contact"></xp:dominoView>
</xp:this.data>
<xp:viewColumn columnName="firstname" id="viewColumn1">
<xp:viewColumnHeader value="First Name" id="viewColumnHeader1">
</xp:viewColumnHeader>
</xp:viewColumn>
<xp:viewColumn columnName="lastname" id="viewColumn2">
<xp:viewColumnHeader value="Last Name" id="viewColumnHeader2">
</xp:viewColumnHeader>
</xp:viewColumn>
<xp:viewColumn columnName="Subject" id="viewColumn3">
<xp:viewColumnHeader value="Subject" id="viewColumnHeader3">
</xp:viewColumnHeader>
</xp:viewColumn>
</xp:viewPanel></xp:panel>
</xp:view>

Displaying the XPage in the browser an empty leading and closing row were generated around the ViewData.


There is a very simple solution for this problem using a styleSheet.
First create a new stylesheet (or add the line below to an existing stylesheet) and enter the following line in the stylesheet:

table.viewClass> tbody >tr:first-child, table.viewClass > tbody > tr:last-child {display: none;}

In the All properties section of the ViewPanel add the CSS class (viewClass) in the viewStyleClass (last one of the Styling Section).


Add the styleSheet to the Custom Control or XPages and the empty leading en ending row will now be 'hidden'.

<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
<xp:this.data>
<xp:dominoDocument var="document1" formName="Contact"></xp:dominoDocument>
</xp:this.data>
<xp:this.resources>
<xp:styleSheet href="/viewheaderfooter.css"></xp:styleSheet>
</xp:this.resources>
<xp:panel>
<xp:viewPanel id="viewPanel1" rows="5"viewStyleClass="viewClass">
<xp:this.data>
<xp:dominoView var="view1" viewName="Contact"></xp:dominoView>
</xp:this.data>
<xp:viewColumn columnName="firstname" id="viewColumn1">
<xp:viewColumnHeader value="First Name" id="viewColumnHeader1">
</xp:viewColumnHeader>
</xp:viewColumn>
<xp:viewColumn columnName="lastname" id="viewColumn2">
<xp:viewColumnHeader value="Last Name" id="viewColumnHeader2">
</xp:viewColumnHeader>
</xp:viewColumn>
<xp:viewColumn columnName="Subject" id="viewColumn3">
<xp:viewColumnHeader value="Subject" id="viewColumnHeader3">
</xp:viewColumnHeader>
</xp:viewColumn>
</xp:viewPanel>
</xp:panel>
</xp:view>

The final result in the browser.


There are other solutions like using a theme but for me this solution works great because I always use styleSheets in my XPages Applications. Thanks to Renaud Thiévent for the CSS solution.
↧
↧

XPages Tip: XPages Extlib DataView Control sets “display:none;” style when Extra Column has Empty Value

July 25, 2016, 4:04 am
$
0
0
Last week I came across an very annoying problem with the DataView from the OpenNTF XPages Extension Library. In a new XPages Application the DataView from the XPages Extension Library (Release 16) is used to display the data. The DataView contains a Summary Column, a Category Column and some Extra Columns. In the DataView some of the Extra Columns have no default values and are, if no values are entered in these fields, 'empty' Columns. The XPages Application uses Bootstrap 3 as Application Theme.



The problem with the empty Extra Columns in the DataView from the OpenNTF XPages Extension Library is that these Columns are rendered with the style="display:none;". This also means that the values of the remaining Columns shift in the DataView.



Below an example of the DataView from the XPages Extension Library in case
one or two Extra Columns are included with an 'empty' value. The values of the remaining Extra Columns shift in the DataView.



There are some 'solutions' available for instance by adding a Custom Converter to the Extra Columns and replace the empty value by a space. My preference goes out to a CSS solution which needs to be implemented only once in the XPages Application by adding the following line in a styleSheet (custom.css):

.table > tbody > tr > td   {
display: table-cell !important;
}

The final result is that the empty Extra Columns are displayed in the DataView and the
Extra Columns not shift anymore.



Perhaps this can be solved in a future release of the XPages Extension Library.
↧

New Notes Domino - XPages - Web Developer Position

July 30, 2016, 9:35 am
$
0
0
Time moves on and the possible end of my current temporary Notes Domino - XPages - Web Developer project is approaching. At the moment I am therefore looking for a new job as a Notes Domino -  XPages - Web Developer.



During the past year I was mainly occupied with classic Notes Domino development, XPages and Front-End Web development. Throughout the past few years I gained a lot of experience with, among others, HTML (5), CSS, Java, JavaScript, jQuery, SQL, XML, LotusScript, Formula Language, JSON and XSP. Furthermore I have a lot of experience with REST services, Git, Source Tree, Node, Bower and Bootstrap.
Currently I am also Moderator of the Google+ XPages Community and Curator of Collaboration Today.
You can find me on the Social Media as well, Twitter, Google+, XPages and More and Acclaim.

At the moment I'm open to a new challenge as a (Web) Developer. So hire me!
For further information please look at my LinkedIn profile.

↧

Notes Domino 9.0.2 and Notes Domino 9.0.1 Fix Pack 7

July 30, 2016, 10:20 am
$
0
0

The next release of Notes Domino will not be the long-awaited Notes Domino 9.0.2 release but the Notes Domino 9.0.1 Fix Pack 7 release, which is scheduled for September (details available in the Fix List).


Positive news is that there will be an official announcement by IBM in September 2016 with an update to the lifecycle policy for IBM Notes and Domino 9.0.x. So maybe there will be an announcement for the long-awaited release of Notes Domino 9.0.2.
IBM remains committed to Notes and Domino and has recently released additional functionality, including IBM Client Application Access and IBM mail support for Microsoft Outlook.  IBM also plans to release IBM Verse On-Premises later this year.
For more information: Update coming soon to the lifecycle policy for Notes & Domino 9.0.x
↧
Viewing all 628 articles
Browse latest View live
Search