Visit Gigasoft's Web Site
ProEssentials v11 Help

Common Question 2

How do I get started?

 

1: Skim Over This Content

The more you study the Getting Started and Documentation sections, the smoother your first implementation will proceed. We've designed this content so developers (and AI assistants) can easily find answers to most common charting tasks.

 

AI-Powered Technical Assistance:

ProEssentials includes Python scripts and JSON data files designed for use with AI-assisted development. We call this AI Tool-Augmented Dynamic Context. Following these instructions will give you a local AI assistance resource capable of answering general technical support questions and writing ProEssentials code for your projects. It's still young, but it's remarkably effective with Claude Opus 4.6 Extended—it can almost answer technical support as well as we can, in some aspects, better, as it will write example code. As of this writing, don't waste your time with anything other than Claude Opus 4.6 Extended. Opus 4.6 IS the only model to use. 

Our ProEssentials11/ai-data folder provides coverage for C#, MFC C++, OCX development in Access, and Embarcadero Delphi/Builder VCL development. We primarily trained on .NET WinForm content, but the AI assistance strategy understands VCL/OCX differences and knows our low-level DLL calls.

Our recommended AI is the Claude AI web browser interface. Take advantage of the historic downloads folder to track the evolution of your work, and always ask Claude to give you content you can paste directly into your project. Version its output if you're asking for a repeated function or file.

 

Setup:

1) Create a New Project within the Claude web UI.
2) Add the knowledge .txt and .py files as knowledge context files.  As of this writing, it will take 12% of your file space.  You likely won't need the pe-cpp-api or vcl/ocx files. 
3) Generally, do not add the larger JSON files into knowledge context—instead, drag these into a conversation once it starts.
4) For Excel, Access, or Delphi/Builder development, you'll want to drag in our full example project main form/unit code files (they can be zipped) so the AI can cross-reference with our allExamples JSON. Generally, adding files once the conversation starts is the trick to getting more data into your conversation. 

 

Starting a Conversation:

Prompt Claude from the Main Project "First Prompt" area with:

"I have a question. I will supply more files within the conversation. Review my knowledge files (starting with pe-tool-instructions for critical rules to always follow) and tell me when ready for more files and my question."

The conversation will start and the screen will change. Drag in our ai JSON files and any additional files as noted above. Then submit your real prompt:

"Given my project files (pe- knowledge files and py scripts) and the files I've uploaded in this conversation, using the ProEssentials API, how do I [do, create, or write] xxxxxxxx using the ProEssentials API and language xxxxx? Optionally use the xxxxxx [Unit3.pas (or 6, etc.)] and cross-reference with allExamples to help provide me an answer with xxxxxxxx code. Always double-check your answer or code against included resources, no hallucinations."

Use this process repeatedly. It's best to start a new conversation with each question, or whenever a conversation has gone through a few rounds of questions and answers.

Understanding ProEssentials' terminology, demos, and features lets you craft stronger prompts.

 

2: Run Our PeDemo

The PeDemo executable optionally launches at the end of product installation. You'll also find GigaPrime2D and GigaPrime3D demos showcasing 3D surfaces, 2D contours, and line rendering—engineered for the fewest CPU/GPU cycles and the fastest rendering available.

Default Install Location: C:\ProEssentials11\Demo

The default example (030) demonstrates many features in a larger context, but most other examples focus on showing individual capabilities clearly.

Recommended First Examples: Start with examples 000, 100, 200, 300, and 400 to build foundational understanding.

Export Feature: The demo includes functionality to automatically export and create a TestBed example project from any individual example—great for quick experimentation.

 

3: Browse the Source Code Examples

PeDemo is replicated in example project source code across multiple languages and frameworks. These examples are your best resource for copying working code, and they also support the export/create TestBed functionality.

  • ProEssentials11/WINUI-C#.NET10
  • ProEssentials11/C#.NET
  • ProEssentials11/C#.NET80
  • ProEssentials11/WPF-C#.NET
  • ProEssentials11/WPF-C#.NET80
  • ProEssentials11/VB.NET
  • ProEssentials11/VC
  • ProEssentials11/Delphi
  • ProEssentials11/Access
  • ProEssentials11/Labview

 

4: Configure Your Project References

For .NET projects, we recommend using our local NuGet packages installed with the product. Even better: update your project file's Reference / Hint section to point directly to our .NET 8.0 assemblies.

Recommended Configuration: Open any demo .NET project in Notepad and search for Gigasoft.ProEssentials to see how we directly reference assemblies. We also recommend using our x64 assemblies for best performance and most transparent deployment.

Regarding deployment, when using our smaller x64 assemblies, you will deploy our native PEGRP64I.DLL along with your EXE.

ProEssentials is unique being 100% native low-level Direct2D/Direct3D/GdiPlus with a .NET wrapper which renders to the device context and/or window's display memory. Gigasoft's future is moving toward adding 100% native ARM and native Linux/MacOS. 

 

5: Take Baby Steps

Don't immediately implement ProEssentials into your production project.

First, create the types of charts you need in a separate test project—possibly using random data. Once you've gained a few hours of experience, integrate into your main application.

This approach also means you'll have a minimal test project ready if you need to contact our support team for assistance.

 

6: Navigate the API Reference

The .NET Reference (top center .Net heading) is the easiest way to explore our full feature list. It's the definitive source for property and method details.

For C++ pure DLL developers: Use the Contents Tab at the top-left of the help system, navigate to Reference, then Alphabetic Listing.

 

7: Need Help Replicating a Design?

Send our support team an example image or sketch of the chart you want to create. We'll point you to all the relevant features and properties needed to replicate it.

Contact Support