Skip to content
This repository has been archived by the owner on Jan 29, 2018. It is now read-only.

Changed the few English errors in readme.md #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Changed the few English errors in readme.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,46 +19,46 @@ IN the meantime, nothing stops you from compiling 6pad++ yourself.

Main distinctive features of 6pad++ includes :

* Edit multiple files in a tabbed interface, and/or in multiple instances of the program, as you wish
* Edit multiple files in a tabbed interface and or in multiple instances of the program.
* Manage most popular character encodings as well as less popular ones; up to 150 if your version of windows supports them all.
* Search and replace using perl-like regular expressions (provided by boost::regex).
* Open files at lightning speed, even for big files of a few dozends megabytes.
* Prevent opening a file twice in different tabs or windows, and automatically refereshing file's contents when modified in another external program.
* Use pipes to quickly read results of DOS command, or simply send them input without making temporary files
* Open files at lightning speed, even for files larger than a few dozen megabytes.
* Prevent opening a file twice in different tabs or windows, and automatically refreshing file's contents when modified in another external program.
* Use pipes to quickly read the results of DOS commands, or simply send them input without making temporary files
* Customize and extend the editor to fit your needs and liking, with a fully functional python 3 scripting API.

# Story

Since a long time, I have been frustrated by default windows' notepad because of its lake of functionalities for developers.
There are of course dedicated text editors especially made for developers, but I wheither find them too heavy, or not as accessible as I would like with a screen reader.
For a long time, I have been frustrated with the default notepad on Windows because of its lack of functionality for developers.
There are, of course, dedicated text editors especially made for developers, but I either find them too heavy, or not as accessible as I would like with a screen reader.

For example, notepad2 and notepad++ are very lightweight, but only partially accessible. Screen readers don't always behave as they should, or don't always read what they need to.
IN the opposite side, complete integrated developement editors like eclipse are known to be not so badly accessible, but they are most of the time too heavy, take time to start up, and aren't that suited to have a quick look at small files and other notes.
On the opposite side, complete integrated development editors like eclipse are known to be pretty accessible, but they are too heavy for most tasks, take too long to start up, and aren't that suited for a quick look at small files and or notes.

There effectively already exist a text editor made for screen reader users, it is called [EdSharp](http://empowermentzone.com/EdSharp.htm).
However, I find its interface not as easy as it is said; menus are especially full of rarely used features, are quite randomly mixed up, and it lakes an obvious way of customizing the whole thing with scripts in an easy way. And, of course, I don't program in C#.
There is already a text editor made for screen reader users, it is called [EdSharp](http://empowermentzone.com/EdSharp.htm).
However, I find that its interface is not that easy to use. The menus are full of rarely used features, they are quite randomly mixed up and EdSharp lacks an obvious way to script one's own functionality. On top of that, I don't program in C#.

# Changes from 6pad

Main changes compared to 6pad are:
The main changes from 6pad are:

* 6pad++ is in C++11 instead of C99
* 6pad++ is scriptable in python 3.4 instead of lua 5.1.4
* Dropped PCRE API in favor of boost::regex; in practice it makes very few differences.

You can have a look at the [old 6pad repository](http://github.com/qtnc/6pad) if you wish. That old 6pad is no longer maintained.
You can have a look at the [old 6pad repository](http://github.com/qtnc/6pad) if you wish. But the old 6pad is no longer maintained.

# Code organization

* In the *core* directory, is the code for the 6pad++ DLL (qc6pad10.dll). This is separated from the main executable so that plugins can be written in C++. If you want to write a C++ plugin for 6pad++, you need to import this library.
* IN the *main* directory is the code of the main 6pad++ executable.
* IN *doc* folder, are documentations about the final product and the associated python API. This documentation is auto-generated from markdown files using pandoc.
* IN *doc* folder, is documentation about the final product and the associated python API. This documentation is auto-generated from markdown files using pandoc.
* In *lib* folder, are python libraries or DLLs, needed for the python 3.4.2 runtime.
*In *plugins* subfolder, are 6pad++ plugins programmed in python. Read each subfolder's readme for more info.
* In *addons* folder, are 6pad++ extension DLLs programmed in C++, and their associated source code. Read each subfolder's readme for more info.
* IN *extensions* folder, are python extensions; they are completely independent and might be used outside 6pad++. Read each subfolder's readme for more info.

Note 1: 6pad++ binary is compiled with MinGW/GCC 4.8.1 in 32-bit mode. If you want to make C++ plugins that can be used seamlessly with the base distribution, you must use that exact same compiler and settings.
This is because Visual Studio's and GCC's ABI aren't eachother compatible.
Note 1: The 6pad++ binary is compiled with MinGW/GCC 4.8.1 in 32-bit mode. If you want to make C++ plugins that can be used seamlessly with the base distribution, you must use that exact same compiler and settings.
This is because Visual Studio's and GCC's ABI are not compatible with one another.

Note 2: 6pad++ binary is linked with msvcr100.dll instead of msvcrt.dll. This is an obligation because python34.dll has also been linked with msvcr100.dll and I don't have any control on python34.dll. This python34.dll, as well as the whole python library found in python34.zip, have been taken unmodified from the default python 3.4 windows installer available at <http://www.python.org/>. I just removed completely useless python modules.
Note 2: 6pad++ binary is linked with msvcr100.dll instead of msvcrt.dll. This is an obligation because python34.dll has also been linked with msvcr100.dll and I don't have any control on python34.dll. This python34.dll, as well as the whole python library found in python34.zip, have been taken unmodified from the default python 3.4 windows installer available at <http://www.python.org/>. I just removed the completely useless python modules.