 |
|
|
|
|
|
|
|
:: Tech Support :: Contact Us :: About Us :: |
||||||
|
|
|
|
|
|
|
|
:: Tech Support :: Contact Us :: About Us :: |
||||||
Yes. See PEG for Linux for a list of Linux distributions.
PEG® is a portable embedded GUI library, API, and set of development tools that are designed to help you create a professional quality GUI for your real-time, multi-tasking embedded application. PEG® includes three libraries - PEG Pro, PEG+, and C/PEG.
PEG for Linux is a derivative of PEG that has been designed to run on any Linux distribution. PEG for Linux also uses the WindowBuilder Development Tool, which has integrated FontCapture and ImageConvert tools . This allows PEG for Linux to support GUI development on a Linux host running the X11 Windowing System.
PEG is licensed on a per-developed-product basis with usually no royalty fees. A standard license allows you to make up to 10,000 production units.
For more information see Licensing.
There are usually no royalty fees. This makes PEG perfect for projects with constrained budgets.
For more information see Licensing.
The cost of a PEG license depends on the type of license that is purchased. To receive a price quote please contact Sales. For license information see Licensing.
The package includes the PEG class library; example application programs; set of development tools including either PEG WindowBuilder with integrated ImageConvert and FontCapture (PEG+ 2.x and PEG Pro), or the PEG Developers Toolkit that includes WindowBuilder, FontCapture, and ImageConvert (C/PEG and PEG+ 1.x); hardware interface objects for common video configurations and input devices; screen driver templates; string functions; RTOS integration documentation and user documentation.
Yes, a variety of PEG demos that run on a PC or reference platform are available on the Demos page.
Yes, PEG supports supports two-byte character sets such as Cyrillic, Han, Katakana, and Hiragana.
Yes, PEG's exclusive CompositeFont technology supports the use of very large character sets in memory-limited applications.
PEG is delivered with two fonts, Menu Font and System Font. You can use the FontCapture utility that comes with PEG to produce any number of additional fonts.
We would NOT recommend that you capture and use a copyrighted Windows font unless you first contact the font manufacturer and obtain permission to use the font in this manner.
For a list of free and commercial font sources see Fonts Links.
Yes, PEG can be enhanced or simplified to suit your needs. PEG makes it easy to design a unique user interface and distinguish your product from the competition.
The development toolset includes either PEG WindowBuilder with integrated FontCapture and ImageConvert (PEG+ 2.x and PEG Pro), or the PEG Developers Toolkit, including WindowBuilder, FontCapture, and ImageConvert (C/PEG and PEG+ 1.x). PEG is the only GUI product on the market that offers such a complete set. These tools will significantly reduce your development time.
For more information see Development Tools.
Yes, we offer customer training at our corporate headquarters or your location. To make arrangements for a training session contact sales@swellsoftware.com.
PEG is designed to work on any embedded CPU. Due to performance requirements PEG runs best on a 16-bit or better CPU running at 16 MHz or higher.
See Target Processors for more information.
Yes, although it is not normally included in the package. Contact support@swellsoftware.com to receive a copy.
Yes, although it is not normally included in the package. Contact support@swellsoftware.com to receive a copy.
PEG+ 2.x (and newer) releases and all PEG Pro releases now include the WindowBuilder Development tool for creating and configuring the UI as well as integrating color, font, string, and image resources. FontCapture has been integrated into the Resource Manager of the WindowBuilder Development Tool and works in much the same way as it did in it's original incarnation.
PEG+ 2.x (and newer) releases and all PEG Pro releases now include the WindowBuilder Development tool for creating and configuring the UI as well as integrating color, font, string, and image resources. ImageConvert has been integrated into the Resource Manager of the WindowBuilder Development Tool and is no longer included as a seperate development tool.
Yes, we provide screen driver templates that support CPU embedded controllers and those with hardware acceleration capabilities.
Yes, because the majority of PEG's library is hardware independent and its hardware interface objects are well defined. The library’s portability has been verified because PEG applications are running on most of the common embedded processors.
Yes, PEG supports a variety of popular reference platforms.
For more information see Reference Platforms.
For devices that are not on the list, we provide screen driver templates to help you create your own driver. Using a template, your will only need to write three functions; GetVideoAddress(), SetupPalette(), and ConfigureController().
For controllers that are not on the list, we provide screen driver templates to help you create your own driver. The templates support both external and internal (CPU embedded) controllers including those with hardware acceleration capabilities.
PEG supports all standard input devices including mouse/joystick, touch screen, keyboard/keypad, and soft keys.
A set of screen driver templates is provided for 1-bpp (monochrome) through 24-bpp (TrueColor RGB) video output and screen resolutions of 1 x 1 to 65535 x 65535 pixels. They are designed to work with any CPU architecture that supports direct, linear access to the video memory buffer.
PEG is fully integrated with RTOS messaging, memory management, and synchronization services. PEG input devices are interrupt driven and use RTOS services to communicate user-input information to the GUI. This yields the lowest possible overhead and the only true real-time multi-tasking GUI environment available.
For more information see RTOS Support.
No, PEG does not need a file system for normal operation.
PEG is fully integrated with RTOS messaging, memory management, and synchronization services. PEG input devices are interrupt driven and use RTOS services to communicate user-input information to the GUI. This yields the lowest possible overhead and the only true real-time multi-tasking GUI environment available.
For more information see RTOS Support.
Yes, because PEG makes no assumptions about the software environment. OS-specific dependencies are encapsulated and well documented. Included are examples that you can use to create new interface classes for any environment.
For more information see RTOS Support.
Yes, PEG can be run standalone without a multi-tasking kernel. This model is often used in smaller, less complex applications.
Yes. See PEG for Linux for a list of Linux distributions.
The cost of a PEG Pro license depends on the type of license purchased. To receive current pricing information contact Sales. For license information, see Licensing.
A minimum PEG Pro footprint requires roughly 220K of code space, 4K of stack, and 2K of dynamic memory. A typical full-featured PEG Pro GUI requires roughly 240K of code space, 4K of stack, and 8K of dynamic memory.
Yes, you can download a PEG Pro evaluation copy after we have received a signed evaluation agreement. You can print and sign the form here: Evaluation Request form.
Yes, in addition to Latin character sets, PEG Pro supports two-byte character sets (such as Cyrillic, Han, Katakana, Hiragana) and UNICODE string encoding. PEG Pro’s exclusive CompositeFont technology supports the use of very large character sets in memory-limited applications. PEG Pro also includes a String Table Editor and set of compiler-independent “C” string library functions.
Yes, this is achieved primarily by abstracting all hardware-dependent functionality. The vast majority of the PEG Pro library is completely hardware-independent relying on well-defined hardware interface objects to provide a consistent, simple, and reliable set of I/O methods.
PEG Pro is designed to work with any EC++ compiler/debugger combination and on any embedded CPU. For multi-tasking environments, the target's RTOS must support the means for inter-task communication via messages. It is also useful if the RTOS includes support for periodic timer interrupt services and semaphore protection of critical code sections. These RTOS features are typically found in commercial-quality RTOSs.
You can download the latest release if you have a valid technical support contract and a user ID and password.
Yes, if you have a valid technical support contract and a user ID and password.
Yes, the latest drivers are available at Drivers.
PEG Pro has been verified with a variety of popular C++ compilers.
PEG Pro supports a rich and growing compliment of GUI object types. Contact us for a full list.
PEG Pro’s drawing primitives are useful to perform custom drawing at the application level. They can be invoked at any time by your application level software.
The cost of a PEG+ license depends on the type of license purchased. To receive current pricing information contact Sales. For license information, see Licensing.
A minimum PEG+ footprint requires roughly 150K of code space, 4K of stack, and 2K of dynamic memory. A typical full-featured PEG GUI requires roughly 170K of code space, 4K of stack, and 8K of dynamic memory.
Yes, you can download a PEG+ evaluation copy after we have received a signed evaluation agreement. You can print and sign the form here: Evaluation Request form.
Yes, in addition to Latin character sets, PEG+ supports two-byte character sets (such as Cyrillic, Han, Katakana, Hiragana) and UNICODE string encoding. PEG+’s exclusive CompositeFont technology supports the use of very large character sets in memory-limited applications. PEG+ also includes a String Table Editor and set of compiler-independent “C” string library functions.
Yes, this is achieved primarily by abstracting all hardware-dependent functionality. The vast majority of the PEG+ library is completely hardware-independent relying on well-defined hardware interface objects to provide a consistent, simple, and reliable set of I/O methods.
PEG+ is designed to work with any EC++ compiler/debugger combination and on any embedded CPU. For multi-tasking environments, the target's RTOS must support the means for inter-task communication via messages. It is also useful if the RTOS includes support for periodic timer interrupt services and semaphore protection of critical code sections. These RTOS features are typically found in commercial-quality RTOSs.
You can download the latest release if you have a valid technical support contract and a user ID and password.
Yes, if you have a valid technical support contract and a user ID and password.
Yes, the latest drivers are available at Drivers.
PEG+ has been verified with a variety of popular C++ compilers.
PEG supports a rich and growing compliment of GUI object types. Contact us for a full list.
PEG+’s drawing primitives are useful to perform custom drawing at the application level. They can be invoked at any time by your application level software.
The cost of a C/PEG license depends on the type of license purchased. To receive current pricing contact Sales. For license information, see Licensing.
A minimum C/PEG footprint requires roughly 90K of code space, 4K of stack, and 2K of dynamic memory. A typical full-featured C/PEG GUI requires roughly 100K of code space, 4K of stack, and 8K of dynamic memory.
Yes, you can download a C/PEG evaluation copy after we have received a signed evaluation agreement. You can print and sign the form here: Evaluation Request form
Yes, in addition to Latin character sets, C/PEG supports two-byte character sets (such as Cyrillic, Han, Katakana, Hiragana) and UNICODE string encoding. C/PEG’s exclusive CompositeFont technology supports the use of very large character sets in memory-limited applications. C/PEG also includes a String Table Editor and set of compiler-independent “C” string library functions.
Yes, this is achieved primarily by abstracting all hardware-dependent functionality. The vast majority of the C/PEG library is completely hardware-independent relying on well-defined hardware interface objects to provide a consistent, simple, and reliable set of I/O methods.
C/PEG is designed to work with any C compiler/debugger combination and on any embedded CPU. For multi-tasking environments, the target's RTOS must support the means for inter-task communication via messages. It is also useful if the RTOS includes support for periodic timer interrupt services and semaphore protection of critical code sections. These RTOS features are typically found in commercial-quality RTOS's.
You can download the latest release if you have a valid technical support contract and a user ID and password.
Yes, if you have a valid technical support contract and a user ID and password.
Yes, the latest drivers are available at Drivers
C/PEG has been verified with a variety of popular C compilers.
C/PEG supports a rich and growing compliment of GUI object types. Contact us for a full list.
C/PEG’s drawing primitives are useful to perform custom drawing at the application level. They can be invoked at any time by your application level software.
