conductor | an abstraction framework for building composable endpoints | REST library

You can add a new state into your Card Component to control what to show.

You could for example use the event aggreator to send an event or a message from the view model to the shell.

The idea is that the ShellViewModel handles the event by activating the view:

It is pulled from a script tag dynamically. You can use regex on the page source as string (not parsing as html) to pull out the the relevant info.

In this case the pattern used returns all the technical specifications plus some other page info. I parse into json object with jsonlite then extract the technical specifications and finally print the section containing the data you want.

There is a little work left to do to just parse out the values, as shown on screen, from the page placement instructions that are carried alongside the values, for when the page on the website renders:

R:

I finally figured it out. While I hate the factory pattern in Java, it seems necessary in Caliburn Micro and makes sense.

As you've noticed, deleting data from the DB does not immediately free the disk space previously occupied by that data. Virtuoso has an auto-compaction feature which will eventually free space. New data will be loaded into the space previously occupied by deleted data, but of course this reuse will be imperfect. You may be able to free some space by running a CHECKPOINT; or the DB..VACUUM (); procedure. You can also do a backup-dump-and-reload to immediately reclaim disk – though you must temporarily consume substantially more disk space during this process. Indexes can also be dropped and rebuilt, but this does not generally free up very much disk, in itself.

You need to:

I finaly found the solution. The Story how i found it:

The problem is that your read_json(....).text line returns a series, not a dataframe.

A simple fix is to exclude the duplicates in the main query: