PFC Guide Titlebar
HomeFAQLinksPFCMAGExtensionsDownloadWhat's NewSearch

Contribution Guidelines



By contributing any material you are agreeing that:

  1. You have sufficient rights to distribute the material.
  2. This material can be used by anyone without any legal or financial obligations.

In other words any contributions to this site will become public domain.

But enough legalese, the details for contributing and PFC Extensions / New Services are listed below.


FAQ / Tips

The guidelines for FAQ contributions are simple. Send an email to submit@pfcguide.com with:

Category.

Try to select one of the categories listed on the PowerBuilder Foundation Class FAQ page. If you do not see a fit on the FAQ page send us a suggestion.

Problem statement.

A single sentence summary of the problem. Can be phrased as a question. This will be used in a Table of Contents at the top of the page. Keep it short and to the point.

Problem description and solution.

This is where you can elaborate on problem description. Provide code samples and anything else that may help you illustrate your solution.


Extensions / New Services

The guidelines for submission of service extensions or new services may be summarized in four categories:

What Why How Where

What

The Service Name

For an extension provide a name of the existing PFC service. If it's a new service give it a logical name.

Why

The Problem statement.

A small paragraph describing the need for the specific service or extension.

How

The description of the solution and the service implementation.

Describe the techniques used, provide code samples. Description should provide enough detail so that the reader may understand the service purpose and the implementation without opening the objects in PowerBuilder.

Where

A zipped PBL with the PFE version of all objects that were created or modified.

For example for a new datawindow service you may need to include a u_dw, n_cst_dwsrv_yourservice, and a n_tr.

Please remember to test any submissions. The submitted extensions will be given a revision number to allow for future enhancements / bug fixes.

Send the above to submit@pfcguide.com.


For information or suggestions about this web site please contact webmaster@pfcguide.com

Revised: February 15, 2004 03:58 AM.