Schedule View not displayed for Schedulable Events

[megoth]

You can create events, but the Schedule Event is not shown for the newly created files

[brownhoward]

To replicate:

1. Log into a Pod on https://dev.inrupt.net.
2. Create a Schedulable Event.
3. Enter a name for the event.

Expected Behaviour

1. The Schedulable Event pane is displayed allow me to see the details of the event.

Actual Behaviour

1. 2 turtle files are created in the named folder: details.ttl and results.ttl.
2. No custom pane is displayed allowing me set the details of the event.

[michielbdejong]

I'll have a look

[SharonStrats]

I think this should fix it #567 - there are two issues. The one where SchedulePane wasn't rendering which that PR fixes.

The second issue is that folder-pane hard codes index.ttl#this for passing to the label function of each pane here.

So when findtypeURIs are called here to find the label nothing is found because the class (type of resource) in the turtle is in the details.ttl#event.

The reason an index.ttl#this file is not created is that schedulePane uses options.useExisting instead of options.newInstance so from the main folder-pane view when creating a new App useExisting is blank here and only creates a details.ttl file and a results.ttl file.

Some points

when schedule creates another schedule from inside its own UI, it does not set useExisting it just passes [{ thisInstance, newBase }]at [schedulePane.js:492]So useExisting is mainly there for when some other pane, especially meeting, wants schedule to attach to an existing subject.

useExisting is not part of the generic creation flow; it is a pane-to-pane convention, and in your current setup it mainly comes from meeting pane when it provisions subtools

[SharonStrats]

This PR in folder-pane will allow old SchedulePane's created without the index.ttl#this file creation to be viewed SolidOS/folder-pane#166

This PR in solid-panes adds creation of index.ttl#this to mintNew and also looks for both when finding types in the label function #576

[SharonStrats]

This needs to be discussed, not sure if we need the second PR or not.