Dev-c++ Gui Designer

  1. C++ Gui Development
  2. Dev-c++ Gui Designer Online
  3. C++ Gui Example

  • Fully-featured PowerShell editor.
  • Visually create PowerShell GUI tools.
  • Convert scripts into executable (.exe) files.
  • Create MSI installers.
  • Create modules from your existing functions or help files.
  • Create advanced functions using the Function Builder.
  • Create windows services using PowerShell.
  • Monitor script performance and memory usage.
  • Script with cmdlets from a remote machine.
  • Universal Version Control with Git integration.
  • Integrated PowerShell consoles (32-bit & 64-bit).
  • Comprehensive script debugger.
  • Remote debugging.
  • Multi-file and module debugging.
  • 32-bit and 64-bit PowerShell integration.
  • Built-in PowerShell help.
  • Supports Windows PowerShell and PowerShell 7.
  • Code Formatting.
  • Prevent loss of work with the File Recovery feature.

To create a GUI for your windows and dialogs in PyQt, you can take two main paths: you can use Qt Designer, or you can hand code the GUI in plain Python code. The first path can dramatically improve your productivity, whereas the second path puts you in full control of your application’s code. This IDE, written in Delphi is the right place for beginners. It isn't perfect and it allows you 'holes' and 'bugs' in your program.Thats why its good for beginners. VS2005 wouldnt compile most of the code, which Dev-C does. Information and Download HERE. SOME LINUX IDE's: -Code::Blocks.

PowerShell Studio is the premier editor and tool-making environment for PowerShell. This single tool will meet all your scripting needs. Work the way YOU want with PowerShell.

Create graphical tools using PowerShell with the easy to use GUI designer. Eliminate the need to write hundreds of lines of code manually. Utilize PowerShell Studio’s templates and pre-wired controls to create advanced GUIs in no time. Create PowerShell script modules in minutes with PowerShell Studio. Easily convert your existing functions to a distributable module. PowerShell Studio features a robust editor with syntax coloring, reference highlighting, bookmarking, code formatting, and code completion. Create, edit, and manage code snippets to enhance your script development.

The script packager offers advanced options and platform selections to deliver solutions targeted at specific environments. You can restrict packages by domain, machine, user, platform, and MAC address to avoid unauthorized script execution. Create MSI installers to distribute your scripts, executables, and modules. Use custom actions to handle special instances such as open files after install.

PowerShell Studio’s Performance Monitor visually tracks the performance of your script by displaying real-time memory and CPU usage. Console, Scripts, Script Modules or GUI Forms—PowerShell Studio will meet all your Windows PowerShell scripting needs.

Key Features

PowerShell Script Editor

Features a robust editor with syntax coloring, reference highlighting, bookmarking, code formatting, and code completion. Create, edit and manage code snippets. Script with cmdlets from remote modules.

Function Builder

Create advanced functions easily, including cmdlet and parameter attributes and comment-based help. The Function Builder inserts the correct syntax for you.

GUI Designer

The Enhanced Form Designer makes GUI design fast and easy. Eliminate the need to manually write hundreds of lines of code. Use pre-wired controls to create advanced GUIs.

Script Debugger

Run and debug scripts and entire modules, locally and remotely. Quickly debug, fix, and verify any problems you may encounter. Support for conditional breakpoints.

Multiplatform Support¹

Provides support for 32-bit and 64-bit versions of PowerShell within a single application. Runs scripts with elevated privileges and in STA / MTA mode.

Create Executables and Installers

Convert your script into executables. Create MSI installers. Fine-tune custom access privileges, elevations, and platforms. Run 32-bit and 64-bit executable files with Windows PowerShell installed.

Create Modules

Create a PowerShell script module in minutes by selecting from your existing functions. PowerShell Studio keeps manifest maintenance to a minimum by auto-exporting functions and ps1xml files for you.

Performance Monitor

Visually tracks your script’s performance by displaying real time memory and CPU usage. Displays the performance results of the last three sessions side-by-side.

PowerShell Console

The integrated PowerShell console switches between 32-bit and 64-bit while maintaining your session. PowerShell Studio allows you customize and add consoles to the panel.


Use projects to manage multi-file scripts, create multi-form GUIs, and script modules. Keep your projects synchronized with the files on disk for easy project management.

Universal Version Control

Our Universal Version Control backs up and versions your files so you don’t lose your work. Integrates the IDE with GIT repositories.


Features browsers for PowerShell commands, functions, WMI objects, .NET objects and databases.

¹ 64-bit execution and debugging require a 64-bit operating system.

A modernized version of Dev-C++

This web page is written from the perspective of the primary project admin Nuklear ZelphDesigner. Whenever 'I' is referenced it is the opinion or observation of that specific developer. This page has replaced the old website which was out-of-date and also meant to be replaced but it never actually happened. I know this page is ugly, I hope to get a nice looking replacement website up fairly soon

Status of the wxDevIDE project

Currently Tony is updating SVN. He is updating the code base to be wxDev-C++7.4 instead of the vanilla which was the initial version in the repository. Some of this work had already been committed.
Nuklear Zelph is busy with his text editor project.
I have actually been working on it in the background for several years and its the reason that XSTC came into being. The project is not any big deal except that it is the new home for eXtended Styled Text Control(XSTC) and The MultiBook which is a neat notebook component. Both of these are dependencies of the editor plugin module for wxDevIDE. (As we don't want to get stuck using just one edit control if our needs change in the future or whatever reasons may arise.) Also I am doing some work on the IDE, My hope is to make a minimalist version that will load a project and build it on both windows and Linux.
Tony also has a couple other projects related to the IDE as well. One parses a wxWidgets project and produces an XML document, it is aimed at helping wxDev-C++ users migrate to wxDevIDE. Another is a C++ version of the package manager. This is going to have all the same functionality of the Pascal version with some improvements. That package manager will be used in wxDevIDE.

A brief history

I started open source development right out of high school. My C++ class was IMO the biggest waist of time ever. I had taken a Pascal class a few years before and I already knew what I was doing. I also tried M$-VC6 and I hated it. I've had some other experiences with M$ products and I just don't have a very great opinion of them. The Operating System however I do like.
So being a fresh graduate I started looking around for options. GNU GCC was easy to find and I liked their paradigms, so I adopted MinGW as my compiler. Shortly thereafter I found Dev-C++. I offered my assistance but unfortunately the project was dying out by then. I had decided to build cross platform software as I was interested in Linux and I didn't want my projects to be stuck on windows. Having Looked around for toolkits wxWidgets and GTK+ where the top two on my list of options. I was unaware of QT at the time but learned later that is is also a very popular toolkit. wxWidgets won out because of the perceived ease of use with a uniform api across the whole and because it was just one library compared to several for GTK. I became very interested in doing something with GTK later on and I've started drafting a GUI for xine-lib that will use a skinning technology similar to Windows Media Player. In time I looked at many IDEs####' for MinGW and I always went back to Dev-C++.
Having found wxWidgets I had issues with getting it to work with Dev-C++ and I was not savvy enough to fix those yet. I looked at the forums and found the wxDev-C++ project. I cannot count myself as a core developer to the wxDev-C++ project as I have not done much for it, I did create most of the XRC exporting code which got me in the door. Having found the project and realizing the vanilla project was dead I wanted to help out, hence the XRC contribution. I wanted to see Dev on Linux and I learned that some of the other developers did too. It wasn't till after Guru(the creator of the designer) retired from the project that I really got serious about porting Dev. I checked out Kylix about a year before it was no longer available but it turned out to be a bust anyway. Lazarus was not feature complete enough yet to be a viable option. Also it made a lot more sense to port Dev to C++ as it was made for C++ in the first place.
Having had a great deal of wxWidgets and C++ experience by the time I was thinking about really doing something about Dev's cross platform issues I had no problem with porting it to wxWidgets. Doing so made a lot of sense as the form designer was made for it and that would also give us the opportunity to make a WYSIWYG version. So I started asking the other developers what they thought about porting and wxDevIDE happened.

What happened next:

Initially when the proposal of porting Dev-C++ to C++ the wxDev-C++ development team agreed that it was a worthwhile goal. One of the contributors, Sof.t came forward with a set of code that he had written. It was a wxWidgets port of the vanilla version of Dev. ( After some discussion it was determined that the licence for the new project should be under the wxWindows licence.
The main goal was to duplicate the GUI while revamping the internals. there are some design flaws in Dev-C++ that we hope to remedy. One of the most obvious is that the main procedure is enormous. Dev currently does not support workspaces, does not support build targets, the integrated debugger in vanilla is broken. the wx version is much better but still has some problems that could be worked on. obviously there are more differences between the vanilla and wx versions. originally the proposal of adding build time macros for adding the form designer into Dev was given to Colin Laplace. He didn't like the Idea of binding his project to one specific designer, so that didn't not happen. Shortly thereafter the project went silent and the version stuck at
as a side note I do recall some discussion about adding a plugin system to Dev that would allow the form designer to be added, however this obviously never came into fruition.
After the wxDev-C++ developer discussion I started the wxDevIDE project. We then discussed a lot of things and decided that the editor component in the new IDE should not be dependant on one specifically. we decided to use wxScintilla and make use of its api as our interface api for the editor plugin component. I had built eXtended Styled Text Control(XSTC) and it looked like a good option for the editor component. we also decided that the current form designer needed a complete rewrite. obviously it needs to be built with wxWidgets, but we also wanted to use an XML template system that would allow wxWidgets api updates to be easy to maintain. also several flavors could be provided without the problems of having each component in the designer export its own code. (which is also a maintenance headache.)
Tony started a project to help create forms for the new IDE. the form designer it was decided would use XRC XML
with some extensions for the necessary information that XRC did not handle which would be needed by the designer. a new package manager written in C++ had already been started at the time of the new IDE project creation. the sources that Sof.t had put forward where committed to SVN. shortly thereafter an update that fixed compilation issues was committed. as wxDev-C++ was in the middle of a development cycle focus shifted back to getting that release out. Dev-c++ Gui Designer(7.3) I then had some things change and could not continue with the project for some time. As I am the primary admin things basically fell apart. since then another release has come out (7.4), Tony found a solution to dragging buttons and other controls that would crash in GTK but work in Windows.

What now?

at present I put up a project for a text editor I have been building off and on. I have not gotten too far on an actual app as I keep getting side tracked with things like XSTC and The MultiBook. XSTC was moved to that project space from wxCode. a notebook component I started some time ago was also put up on that project space and a color button like the one used in Dev-C++ that I built on a whim as I had no better place to distribute it. The project will do a lot of the legwork for the editor plugin for the IDE as well as maintain a few of the dependencies.
Although there are no files in the release system I plan to remedy that very soon. A windows binary showing the current state of the project will be put on the file release system. I also hope to get the code to build and run on Linux and put up a binary for that as well.
the focus of the project at present is basically continuing the work that was started by

C++ Gui Development

Sof.t and continue porting the Delphi code. Since the developer who built the plugin system for wxDev has moved on to the ReactOS project we don't have an 'expert' on that subject anymore. I will be completing the editor module that I started and will integrate it into the current code base. I also hope to get a bare-bones project working as well. (load a project into the IDE, and build it) hopefully on both Windows and Linux.

Dev-c++ Gui Designer Online

once the editor module is in a usable state a branched GUI will be started to take its place in the new IDE. this will support AUI

C++ Gui Example

, will be designed with a future plugin system in mind so changing the UI elements is a simple matter not a chore. Also the new form designer will use this as an application base for a standalone version of the designer. in the future the main IDE will probably have a build macro to trim it down for use as the standalone app for the form designer.