Avoiding Inline Styles in XPages
Recently there have been discussions about inline CSS in XPages. The absence of anyone mentioning a feature in XPages prompted me to eventually ask about a piece of functionality relevant to this.
XPages App to Web App: Part Seventeen - Lessons Learned
Now the application is built and has been in use for many months. It's time to review experiences and lessons learned.
Lessons Learned from Including Web Components in an Ember.js Application
One of the key skills when working in IT research is the ability to work out how something works, either by looking at the code or being able to see the process behind a button or API call on your screen. The inevitable consequence then is that you understand how things work, you see comparisons between technologies or frameworks, and you begin to identify whether or why something will work or fail. You also gain understanding of various possible approaches and which is the right one. That results in a "lessons learned" blog post like this one.
XPages App to Web App: Part Sixteen: Spots
Now that we've set up the CRUD pages for ships and spots, it's time to put them together. When we search a ship, we'll want to be able to see the spots created for that ship. Now let's set that up.
XPages App to Web App: Part Fifteen - Dialogs
When it comes to creating Ship Spots, one of the pain points I highlighted with the previous application was when a Ship Spot required creating a new Port or a new Country. This required switching to an "admin" area to open a Port form to complete and save; and if the country hasn't been created, it requires additionally switching to a County form to complete and save, before returning to the Port and back to the Ship Spot. Options were cached server-side in viewScope, so launching additional browser windows wasn't an option - the page would still need to be refreshed and entered data lost. We can improve on this.