oneui | A frontend tool to debug backend supporting OneBot protocol

You use the xe:bootstrapResponsiveConfiguration as configuration for your ApplicationLayout. That does not combine well with the OneUI theme. Theme and ApplicationLayout must be of the same family.

So either use a bootstrap theme or use the oneuiApplication layout (but the latter does not have a collapsible left column)

Get the session with

If you monitor the web traffic (F11->Network Tools in Chrome), you'll see that that information isn't actually located 'within' the page - it's loaded with a POST request to an internal inventory endpoint:

The above pictures show the POST request and the response, respectively. So, because this data isn't generated from the actual GET request to the laptop's page, you have two options:

1. Mimic the POST request. This is borderline unethical, because Microsoft has the system set up in this way to minimize unnecessary traffic. On the other hand (and this may earn me some downvotes), I don't think something like this is going to affect Microsoft's servers too much. Mimicking the POST request would require you to find out what is sent to the server and how to structure that request. All of this information can be found within the POST request that I posted if you scroll through it and use your noggin.

2. Use selenium (the Python module, not the piece of software). This uses a browser, so it'll generate exactly what you see in the browser, though you'll have to give it a second to allow the site to make that POST request. After that, you could use BeautifulSoup as you were before to scrape the relevant information. This way would be significantly easier in terms of time that it'll take if you don't know how to replicate POST requests.

Good luck!

ExtLibX has a Bootstrap 4 experimental release https://openntf.org/main.nsf/project.xsp?r=project/XPages%20ExtLibX/releases/A8498784907DA6D386257F6200465E8F. That was a release looking for people to use it and give feedback of anything not working. I think most developers have focused on the Bootstrap 3 codestream because Bootstrap 4.0.0 is still not yet in beta (although 99% complete as of today at https://github.com/twbs/bootstrap/milestones).

If you are committed to 4.0.0, I would recommend using that and giving feedback. The componentised approach of XPages makes so much sense and is what other frameworks tend to use, because if the HTML required changes, it only needs changing once for all instances of the component, rather than everywhere for every instance of the old HTML code.

If you're able to clone the repository and run it against a local server, to be able to troubleshoot in Eclipse, even better. (My recent NotesIn9 on OpenNTF Domino API Starter Servlet gives the setup instructions. Following that video, I imported core ExtLib and was able to build it with any other configuration changes.)

The version number 9.01.v08.00 indicates that the server is running IBM Domino 9.0.1 Feature Pack 8 and this version includes XPages Extension Library V17.