Theo's Forum

IT-Consultant: José Roca (PBWIN 10+/PBCC 6+) (Archive only) => CSED Editor => Topic started by: José Roca on July 11, 2011, 11:33:27 PM

Title: CSED Editor 1.03
Post by: José Roca on July 11, 2011, 11:33:27 PM
 
A programmer's editor for the PB/WIN and PB/CC compilers. It uses Scintilla as the editing component.

Key Features


What is new in this version

Version 1.03 fixes the following issues:

- Modified the code to remove tabs.
- Option 'Reload Previous File Set at Start' works again.
- Previews implement users default font settings.
- FASTPROC functions weren't being displayed in the codefinder.
- The toolbar Save button did not activate when pasting code.

I also have updated the code templates and added new ones.

Installation

To install the editor, just unzip CSED103_RELEASE.RAR in the folder of your choice. Preserve folder structure when unzipping.
Title: CSED Editor 1.03: Codetips
Post by: José Roca on July 11, 2011, 11:36:07 PM
 
Codetips for the version 2.03 of my Windows API Headers for PBWIN 10.02 and PBCC 6.02.

Unzip it in the CSED_CODETIPS folder of the CSED editor.
Title: CSED Editor 1.03: External Tools
Post by: José Roca on July 11, 2011, 11:36:47 PM
 
The External Tools toolbar button launches a program that allows to create and manage a database with the names and paths of external tools, including .chm and .pdf files.


The .chm and .pdf files will be displayed in the Guides menu, and the .exe files in the Tools menu.
Title: CSED Editor 1.03: Source Code
Post by: José Roca on July 11, 2011, 11:46:37 PM
 
Source code of the CSED editor. To compile it, version 10.02 of the PowerBASIC for Windows compiler and version 2.03 of my Windows API Headers are required.

Permission is granted to develop new versions of the editor as long as the source code is made freely available in this forum or elsewhere.

Enjoy coding these features that are indispensable to you and aren't available in the current version of the editor.

The code of the editor is also an excellent example of how to use the classes and wrappers provided in the Windows API Headers package.