Makes sense. Thanks. I think the important aspect is that any given page in a Web app will be composed of multiple resources, if that's of any significance for the design.
A root resource would render the menus while navigating between other resources will change whatever is shown in the main section of that page. And maybe adding context specific items on the side menu... Sent from Nine ________________________________ From: Holger Knublauch <hol...@topquadrant.com> Sent: Thursday, 5 August 2021 07:58 To: topbraid-users@googlegroups.com Subject: Re: [topbraid-users] DASH: Preselecting viewers for NodeShape On 2021-08-05 4:53 am, Tomasz Pluskiewicz wrote: My goal is to be able to create bespoke UI by extending shapes and DASH. I think that the generic tabular display of resources is not enough and we can actually aim for a more fine-tuned user experience. I suppose portability will be a little sacrificed in such scenario. Not sure yet, I'm still trying to wrap my head around what is and what is not a good idea. At the moment I'm starting with a UI shell built using IBM Carbon Design System. Here's an example from their storybook. Looking at this, I'd assume that a root resource, served from an API, would fill in the top menu and sidebar. This could be by rendering two sh:Group with well known identifiers. That root resource could directly link to its shape (or provide it inline). Maybe instead of selecting the viewer from the shape itself, it would be better to select it based on a specific "entrypoint" type. </> a hydra:Entrypoint ; hydra:title "IBM [Platform]" ; dash:shape [ # navigation link properties ] . This way, given a hydra:Entrypoint, an app could be able to choose multiple layouts... What do you think? >From a specification point of view I don't see this as much of a difference >between IBM's layout and single-column form-based layout. Wouldn't it be >sufficient to annotate the property groups or individual properties with hints >that the specific property can then use? E.g. ex:ibmCarbonDesignLayoutInfo=... >while the default rendering may ignore those? Holger > > środa, 4 sierpnia 2021 o 04:59:14 UTC+2 Holger Knublauch napisał(a): >> >> I guess the default rendering of focus nodes is form-based. That's what the >> rest of the SHACL-based form vocabulary supports, e.g. through sh:group and >> sh:order. >> >> I assume you want a mechanism to say that instances that are target of a >> given node shape should be rendered completely differently? Would you have >> examples of such renderings, and how would they be portable? I guess >> ex:SpecializedViewer itself would need to carry more information to be >> generally useful. If it's indeed just specialized, I guess the receiving >> platform can just introduce its own property (which is probably better >> anyway to separate concerns). >> >> For anyone just following this topic from the side lines, this is about >> http://datashapes.org/forms.html >> >> Holger >> >> >> On 2021-08-04 6:38 am, Tomasz Pluskiewicz wrote: >>> >>> Hello >>> >>> I notice that dash:viewer has its range limited to sh:PropertyShape. >>> >>> What do you think about relaxing this so that a NodeShape (specifically >>> useful for a top shape being rendered) could also be specified explicitly >>> like >>> >>> <> dash:shape [ >>> a sh:NodeShape ; >>> dash:viewer ex:SpecializedViewer ; >>> ] >>> >>> Best, >>> Tom >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "TopBraid Suite Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to topbraid-user...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/topbraid-users/89a10c54-6884-4e07-a758-59536f9c60c3n%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to topbraid-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/42c05325-59ee-43c6-9938-ce6d02cb5e15n%40googlegroups.com. -- You received this message because you are subscribed to a topic in the Google Groups "TopBraid Suite Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/zYkschuPBrY/unsubscribe. To unsubscribe from this group and all its topics, send an email to topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/25321f85-498f-1750-5b26-1f0f0d4f0fc9%40topquadrant.com. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/u2mc91i7gcq84sju7jkn23j6.1628143789817%40email.android.com.
