All Categories (1-6 of 6)

1. Allow people to test a tool that is installed but not published?

   Closed | Responses: 0

   I have a tool which the admin has installed but I have not yet published. I'm wondering how I can allow VHub users (that I decide) to gain access to the tool for testing/feedback...

   https://vhub.org/answers/question/43

2. Create a Hub Tool with Rappture Builder

   This set of instructions takes you through creating and deploying a Hub tool based on C code. It describes how to use the Rappture builder to quickly create a GUI to deploy your tool on the Hub.For...

   https://vhub.org/kb/Development/create_a_hub_tool_with_rappture_builder

3. Tool Development Workflow

   This workflow describes how a vHub user may develop, test, troubleshoot, and deploy a new tool on the vHub site. This workflow assumes the user has developed the tool using the C language; the tool...

   https://vhub.org/kb/Development/tooldevelopmentworkflow

4. Hub Tool Directory Structure

   When developing tools, use the recommended Hub tool directory structures and save yourself some grief.Hub Application Space Directory StructureThis is the actual directory structure of your...

   https://vhub.org/kb/Development/directorystructure

5. Hub tool directory structure

   When developing tools, use the recommended Hub tool directory structures and save yourself some grief. Hub Application Space Directory Structure This is the actual directory structure of your...

   https://vhub.org/wiki/Hubtooldirectorystructure

6. Hub Tool Directory Structure

   19 Sep 2012 | Posted by Jeanette Sperhac

   When developing tools, use the recommended Hub tool directory structures and save yourself some grief. ==Hub Application Space Directory Structure== This is the actual directory structure of your...

   https://vhub.org/members/2153/blog/2012/09/hub-tool-directory-structure