862 create a basketdesign table that represents the specific instance…

… of a basket that we are modifying it will be based on a basket entry but can be customized to what the user needs (#948)

* #862 Fixed test versions to abstract out clock.

* #862 Added Viewport scoped rpc service to test.

* #862 Added ability to edit baskets join service.

docs/rpc/Viewport_rpc.md

@@ -0,0 +1,11 @@
+import { SvgDottySeparator } from "@site/src/components/SvgDottySeparator";
+
+# RPC Calls
+
+<SvgDottySeparator style={{marginBottom: 32}}/>
+
+## Viewport RPC
+
+```scala
+In Progress
+```

docs/rpc/rpc.md

@@ -4,20 +4,33 @@ import { SvgDottySeparator } from "@site/src/components/SvgDottySeparator";
 
 <SvgDottySeparator style={{marginBottom: 32}}/>
 
-## Menus
+## Overview of RPC
 
-[Menu Items](Menu_items.md) act upon a `table`, `selection`, `row` or `cell` (these are called `scope`).
+There are two scopes where rpc services can be defined: 
 
-Once a `menu item` is registered by a server side [`provider`](../providers_tables_viewports/providers.md), it will be automatically displayed when user right-clicks on the corresponding Vuu Grid component.
+- Global Scope - these are services that can be called without a viewport being created. 
+- Viewport Scope - these are services that are created when a user creates a viewport
 
-Menu items may have filter expressions (applied for each individual row) that determine for which rows they are visible. If a menu item is visible, it can be invoked. On invocation, depending on the `scope` the RPC handler will receive context information about what are we acting upon.
+## Global Scope - RPC Services
+
+[RPC Services](service.md) allow us to expose server-side functionality to a Vuu client over a low-latency web-socket connection.
+
+The Vuu client framework can discover and programmatically call these services over the WebSocket. While there is no generic UI for invoking/inspecting REST services, many components (such as the Autocomplete Search) use  services as an implementation mechanism.
+
+## Global Scope - REST Services
 
-## RPC Services
+[REST Services]() allow us to expose server-side functionality to a Vuu client. Each service is modeled in REST-ful resource fashion, and can define the following standard verbs: `get_all`, `get`, `post`, `put`, `delete`
 
-[RPC Services](service.md) allow us to expose server-side functionality to a Vuu client over a low-latency connection.
 
-The Vuu client framework can discover and programmatically call these services over the WebSocket. While there is no generic UI for invoking/inspecting REST services, many components (such as the Autocomplete Search) use REST services as an implementation mechanism.
+## Viewport Scope - Menu Items
+[Menu Items](Menu_items.md) act upon a `table`, `selection`, `row` or `cell` (these are called `scope`).
+
+Once a `menu item` is registered by a server side [`provider`](../providers_tables_viewports/providers.md), it will be automatically displayed when user right-clicks on the corresponding Vuu Grid component.
+
+Menu items may have filter expressions (applied for each individual row) that determine for which rows they are visible. If a menu item is visible, it can be invoked. On invocation, depending on the `scope` the RPC handler will receive context information about what are we acting upon.
 
-## REST Services
+## Viewport Scope - RPC Calls
+[Viewport RPC](Viewport_rpc.md) calls are specific service methods that we want to call on a viewport we've created. They are specific i.e. the UI component needs
+to understand the type of call that is being called. In that way they should be used in functionally specific UI components. 
 
-[REST Services](#) allow us to expose server-side functionality to a Vuu client. Each service is modeled in REST-ful resource fashion, and can define the following standard verbs: `get_all`, `get`, `post`, `put`, `delete`
+They implicitly have access to the viewport and its associated tables that they are being called on.