|
Teradata Viewpoint Portlet Development Kit (PDK) is the starting point for building portlets for the Viewpoint platform. The PDK is a set of APIs, user interface widgets, styles and other assets that allow you to develop portlets for Teradata Viewpoint. It also contains documentation, code samples, how-to's and other reference materials to help in that endeavor.
,
17 Jun 2009
|
|
|
The Widgetopa portlet demonstrates the various display paradigms available to the developer through the use of Teradata Viewpoint widgets.
,
21 May 2009
| 4 comments
|
|
|
When you create a new portlet project using the PortletGenerator, the project will contain an Ant based build system. You can use the following ant targets to build and deploy your portlet:
,
21 May 2009
|
|
|
This tutorial describes how to deploy a portlet into the Viewpoint Development Portal.
,
21 May 2009
| 4 comments
|
|
|
This tutorial steps through install the Teradata Viewpoint Development Portal, a cut-down version of Viewpoint, on your local desktop machine. These instructions are specifically for Windows, though the PDK has been validated to work on Mac OS X, Linux, and Solaris.
,
21 May 2009
| 6 comments
|
|
|
To begin, we'll install the Viewpoint Development Portal, a cut-down version of the full Viewpoint release, onto your local desktop. Then we'll deploy the sample portlet, and finally we'll take a guided tour of the Widgetopia portlet.
,
20 May 2009
|
|
|
The Viewpoint Portlet Development Kit (PDK) is a set of APIs, user interface widgets, styles and other assets that allow you to develop portlets for Teradata Viewpoint. The PDK also includes a "lite" version of Viewpoint that you can run on your desktop. You can download Viewpoint PDK here.
,
20 May 2009
|
|
|
The Ant-based build system used to build and deploy portlets in the PDK is the same system used internally at Teradata by Viewpoint developers. One of the facets of this build system is that, for Teradata developers, the build system will try to download the latest development versions of certain artifacts over HTTP from an internal Teradata service. For non-Teradata developers, that Teradata service is not accessible, but the Ant script should recognize this and continue regardless.
,
20 May 2009
|
|