knowledgepixels / nanodash / 35330653258

package com.knowledgepixels.nanodash.component.menu;

import com.knowledgepixels.nanodash.ApiCache;

import com.knowledgepixels.nanodash.MagicQueryParams;

import com.knowledgepixels.nanodash.NanodashSession;

import com.knowledgepixels.nanodash.NanopubElement;

import com.knowledgepixels.nanodash.NavigationContext;

import com.knowledgepixels.nanodash.QueryResult;

import com.knowledgepixels.nanodash.Utils;

import com.knowledgepixels.nanodash.View;

import com.knowledgepixels.nanodash.ViewDisplay;

import com.knowledgepixels.nanodash.component.GuidedChoiceItem;

import com.knowledgepixels.nanodash.component.RefreshingResultPanel;

import com.knowledgepixels.nanodash.domain.AbstractResourceWithProfile;

import com.knowledgepixels.nanodash.domain.IndividualAgent;

import com.knowledgepixels.nanodash.domain.Space;

import com.knowledgepixels.nanodash.page.ExplorePage;

import com.knowledgepixels.nanodash.page.PublishPage;

import com.knowledgepixels.nanodash.page.QueryPage;

import com.knowledgepixels.nanodash.page.ViewResultsPage;

import com.knowledgepixels.nanodash.template.TemplateData;

import org.apache.wicket.Component;

import org.apache.wicket.ajax.AjaxRequestTarget;

import org.apache.wicket.ajax.attributes.AjaxCallListener;

import org.apache.wicket.ajax.attributes.AjaxRequestAttributes;

import org.apache.wicket.ajax.markup.html.AjaxFallbackLink;

import org.apache.wicket.extensions.ajax.markup.html.AjaxLazyLoadPanel;

import org.apache.wicket.markup.html.WebMarkupContainer;

import org.apache.wicket.markup.html.link.BookmarkablePageLink;

import org.apache.wicket.markup.html.link.ExternalLink;

import org.apache.wicket.markup.html.link.Link;

import org.apache.wicket.markup.repeater.Item;

import org.apache.wicket.markup.repeater.data.DataView;

import org.apache.wicket.markup.repeater.data.ListDataProvider;

import org.apache.wicket.model.Model;

import org.apache.wicket.request.mapper.parameter.PageParameters;

import org.eclipse.rdf4j.model.IRI;

import org.nanopub.extra.services.QueryRef;

import java.util.List;

import java.util.Optional;

/**

 * A dropdown menu panel for view displays, replacing the "^" source link.

 * Provides options to show the query, adjust the view display, and see its declaration.

 */

public class ViewDisplayMenu extends BaseDisplayMenu {

    /**

     * Constructs a ViewDisplayMenu.

     *

     * @param id           the Wicket component ID

     * @param viewDisplay  the view display this menu acts on (must have a non-null nanopub)

     * @param queryRef     the query reference used by this view display, or null for a

     *                     query-less view (a header view), which hides the

     *                     query-dependent entries (show query, full screen). "refresh now"

     *                     stays: since issue #654 it brings the view definition up to date

     *                     too, which is the whole of what a header view has to refresh.

     * @param pageResource the page-level resource used to determine whether "adjust" is visible

     * @param viewActions  the view-level actions to show as top entries (may be empty)

     */

    public ViewDisplayMenu(String id, ViewDisplay viewDisplay, QueryRef queryRef, AbstractResourceWithProfile pageResource, List<QueryResult.MenuAction> viewActions) {

        // View-level actions become the top entries of the menu, followed by a

        // separator and then the standard view-display options below.

            @Override

            protected void populateItem(Item<QueryResult.MenuAction> item) {

                // A label that starts with a leading symbol/emoji renders that as the entry icon.

                } else {

                }

        };

        }

        // Full-screen version of this view on the standalone view-results page, with the

        // current query parameters carried along (magic ones excluded — the results page

        // re-binds them from the session, so carrying them would duplicate the bindings).

                @Override

                protected void onConfigure() {

                    // Self-referential on the full-screen page itself.

            };

        }

        // Determine whether "adjust" should be visible for this user on this page

            }

        }

        // Determine supersede vs derive based on whether this user's pubkey matches the nanopub's.

        // These are only needed when showAdjust is true (i.e. pageResource is non-null).

                    + "&template-version=latest"

        }

        // "edit view display" only makes sense for an actual view-display nanopub (one with

        // a resolved view IRI). Built-in views rendered directly — e.g. a space's About-tab

        // meta-views (roles/members/presets/view-displays) — have no view-display nanopub,

        // and neither do views supplied by a preset assignment, so it is hidden for those.

        // "deactivate view display" additionally covers preset-supplied views: a deactivation

        // nanopub for the view's kind takes precedence over the preset (latest-wins per kind

        // in AbstractResourceWithProfile.filterViewDisplays), so it works without a display

        // nanopub of its own.

        // Label (with its leading icon) comes from the markup body, so no label arg here.

                new PageParameters()

            }

                    + "&template-version=latest"

        }

        // Label (with its leading icon) comes from the markup body, so no label arg here.

        // The version of the view definition this display is showing. A newer one can have

        // been published since the page was built, which "refresh now" checks for below.

        // Refreshes this one view where it stands. Re-rendering the whole page would work too,

        // but it takes the reader back to the top of it, away from the view they were looking

        // at — and re-runs everything else on the page for a refresh they asked of one view.

            @Override

            public void onClick(Optional<AjaxRequestTarget> target) {

                // A header view has no query, and so nothing to mark outdated here — its

                // whole content comes from the view definition re-checked just below.

                // Bringing a view up to date is not only a matter of re-running its query:

                // the view definition itself can have been superseded since this page was

                // built, and neither the memoized resolution nor the version the page's

                // structure resolved to would notice on their own (issue #654).

                    // A new version can change everything the display is made of — its query,

                    // its columns, its actions, its width — which is more than the piece on

                    // screen can be patched into. The version in use comes from the page's

                    // structure (the get-view-displays query resolves it server-side), so the

                    // structure is what has to be asked again: the same route the page-level

                    // "refresh now" takes, with the current structure kept on screen under a

                    // spinner until the refreshed one lands.

                }

                    // Not every view display puts results in the page. A query-form view

                    // shows a form, and the results it leads to live on the page it submits

                    // to; a header view has no query at all. Either way there is nothing

                    // here to bring up to date once the view definition has been re-checked

                    // above (and, for the form, its query marked outdated for the next

                    // submit). Re-rendering the page on top of that would repaint everything

                    // for no visible change — which is what made query-form views, alone

                    // among the display types then offering a refresh, flicker on every one.

                }

                // A view is not always what stands in the page: while it waits for its first

                // results it is inside Wicket's lazy-loading panel, and while it is being

                // brought up to date inside a RefreshingResultPanel. Either way the wrapper

                // is the piece that has to be replaced — replacing what is inside it would

                // leave the wrapper around it and address an element the browser does not

                // have, so nothing would change on screen and the markup left behind would

                // keep linking to components that are no longer there.

                }

                    // No Ajax, nothing to rebuild, or nothing in the page to replace: fall

                    // back to re-rendering the page.

                }

                // The replacement has to answer to the id the browser already has, or the

                // Ajax response would update an element that is not there and leave the old

                // markup — and its links, by then removed from the page — on screen.

        };

        // Offered wherever there is something to bring up to date. That used to mean a query,

        // but since issue #654 the refresh re-resolves the view definition as well, which is

        // all a query-less header view consists of — so it is offered there too.

}