Files
galaxy/client/src/components/History
..
2024-05-28 14:30:19 +02:00
2024-05-27 19:07:22 +02:00
2024-01-24 11:42:46 +01:00

History Panel Component Tree

This is not intended to be a complete listing, but a general idea of how the components are intended to interact with each other.

<Index :history="history">
    <!-- if main history selected -->
    <CurrentHistory :history="history">
        <HistoryNavigation />
        <HistoryDetails />
        <HistoryMessages />
        <HistoryOperations />

        <!-- Uses a virtual scroller plugin to render all ContentItems and throttles the scrolling pace by limiting
        the frequency and magnitude of offset changes. -->
        <listing>

            <!-- The ContentItem renders a row in the list, showing the title, some attributes,
            and basic operation buttons such as display and edit for either a dataset or a collection.
            This component needs to be very efficient since it is re-rendered by the virtual scroller plugin. -->
            (<ContentItem />)

                <!-- Is shown for datasets upon expansion, can be inefficent in comparison to the ContentItem component. -->
                <DatasetDetails />
        </Listing>
    </CurrentHistory>

    <!-- When a collection is selected for viewing, send in a 
    breadcrumbs list of collections the user has selected -->
    <CurrentCollection :selected-collections="breadcrumbs">
        <CollectionNavigation />
        <CollectionDetails />
        <CollectionOperations />

        <!-- As above, the same virtual scroller and ContentItem component is being used to render the elements. -->
        <listing>
            (<ContentItem />)
                <DatasetDetails />
        </Listing>
    </CurrentCollection>
</Index>