Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Commit

Permalink
updated wrong image links :/
Browse files Browse the repository at this point in the history
  • Loading branch information
jcaillon committed Feb 23, 2019
1 parent ad42af2 commit cd1ab5b
Show file tree
Hide file tree
Showing 5 changed files with 34 additions and 34 deletions.
6 changes: 3 additions & 3 deletions docs/md/code-explorer.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,12 @@

* The code explorer acts as an improved `function list`, well known to the notepad++ users. It displays the structure of the program and provides a quick way to jump from a code's portion to another (left click an item to get redirected to it) :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/256db7f8-8d57-11e5-9924-93fa3d87e83e.png)
![image](content_images/256db7f8-8d57-11e5-9924-93fa3d87e83e.png)

* The code explorer provides way more information than your usual function list ; and it can sometimes be overwhelming. You can reduce the amount of information at any time by expanding/collapsing one or all categories :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/5771f858-8d58-11e5-85f8-1b4e343da4b4.png)
![image](content_images/5771f858-8d58-11e5-85f8-1b4e343da4b4.png)

* You can also filter the items by typing a word in the text-box available for this end :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/8e34ca6e-8d58-11e5-9ffb-e954cb291fcc.png)
![image](content_images/8e34ca6e-8d58-11e5-9ffb-e954cb291fcc.png)
14 changes: 7 additions & 7 deletions docs/md/custom-themes.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,25 +11,25 @@ Two topics are discussed here:

This kind of theme only concerns the part of notepad++ where the text is edited:

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/cb7fbc4c-f141-11e5-8225-acf88bb9a434.png)
![image](content_images/cb7fbc4c-f141-11e5-8225-acf88bb9a434.png)

You can edit the foreground/background color and font weight of any type of keywords displayed in your progress files.

By default, you can only select through a limited amount of options in the `OPTIONS` > `COLOR SCHEMES` page of the application, as shown below :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/20e375d4-f142-11e5-8325-de15031f30e9.png)
![image](content_images/20e375d4-f142-11e5-8325-de15031f30e9.png)

To be able to define your own themes, you first need to **EXPORT** the internal list of themes into an external file that you will be able to edit.

For that, go to the `OPTIONS` > `SHARE/EXPORT CONFIG` page:

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/56247266-f142-11e5-9ceb-1c863041a5f2.png)
![image](content_images/56247266-f142-11e5-9ceb-1c863041a5f2.png)

Click the export ![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/66fd7c40-f142-11e5-9b9d-8a16d11edfde.png) button of the line **Syntax highlighting themes list**. The file is now exported:
Click the export ![image](content_images/66fd7c40-f142-11e5-9b9d-8a16d11edfde.png) button of the line **Syntax highlighting themes list**. The file is now exported:

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/874cd9fa-f142-11e5-9870-a0399102d6df.png)
![image](content_images/874cd9fa-f142-11e5-9870-a0399102d6df.png)

You can open the file in Notepad++ by clicking left on the open button ![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/0e75380e-f144-11e5-98c0-b8015017ff69.png). When your modifications are done, click the import button ![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/244dbc96-f144-11e5-8056-0615be74f5dd.png) to apply your changes.
You can open the file in Notepad++ by clicking left on the open button ![image](content_images/0e75380e-f144-11e5-98c0-b8015017ff69.png). When your modifications are done, click the import button ![image](content_images/244dbc96-f144-11e5-8056-0615be74f5dd.png) to apply your changes.

Read the exported files for more information

Expand All @@ -39,6 +39,6 @@ The application themes define the colors of every interfaces of 3P. This include

Follow the same procedure as for the syntax themes to define your own colors. You have to export the line **Application themes list** instead of the **Syntax highlighting themes list**:

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/9f97f862-f144-11e5-93d6-0614c8ad6f12.png)
![image](content_images/9f97f862-f144-11e5-93d6-0614c8ad6f12.png)

Read the exported file for more information!
2 changes: 1 addition & 1 deletion docs/md/file-explorer.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

* The file explorer has several purposes, the first one is to show the user the errors on a specific file after a compilation, a check syntax or a prolint :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/file_explorer_filestatus.png)
![image](content_images/file_explorer_filestatus.png)

* The user can quickly navigate to the next/previous error, it can also clear all the error (this only has a visual effect obviously; 3P doesn't code for you... yet)

Expand Down
8 changes: 4 additions & 4 deletions docs/md/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

Everything starts with 3P's main menu :

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/getting-started-0.png)
![image](content_images/getting-started-0.png)

All 3P's features are accessible from this menu, this is the main entry point. Once you are familiar with the software, you can use the direct shortcuts.

Expand All @@ -27,12 +27,12 @@ Read the info below concerning the page `SET` > `ENVIRONMENT` :

*The following screenshots might not be up to date with the latest version of 3P, however the general idea will still be true*

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/getting-started-1.png)
![image](content_images/getting-started-1.png)

---

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/getting-started-2.png)
![image](content_images/getting-started-2.png)

---

![image](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/getting-started-3.png)
![image](content_images/getting-started-3.png)
38 changes: 19 additions & 19 deletions docs/md/set-environment.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,61 +28,61 @@ For that, you need to provide :

You can define *one or more* **application(s)** and for each of them, you can define *one or more* **suffixes** (a sub-level of an application).

![2016-04-27_105412](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/67c1c01a-0c67-11e6-9a5c-17fd9a2dada6.png)
![2016-04-27_105412](content_images/67c1c01a-0c67-11e6-9a5c-17fd9a2dada6.png)

For instance :
I have several clients, I develop a different application for each of them.
For each application, I have a version in development, one being tested by my client and a last one that is an exact copy of the app in production for debug purposes.

This is the idea behind those two lists

![2016-04-27_110118](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/76a2c854-0c67-11e6-9226-07565977a2f4.png)
![2016-04-27_110118](content_images/76a2c854-0c67-11e6-9226-07565977a2f4.png)

## Configure a new environment ##

### 1st step : create a new env ###

Use the following buttons to modify or create a new environment : ![2016-04-27_110547](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/03e2fbee-0c68-11e6-85bd-933b7fa03b35.png) ![2016-04-27_110544](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/03dea62a-0c68-11e6-9441-fedf09950b85.png)
Use the following buttons to modify or create a new environment : ![2016-04-27_110547](content_images/03e2fbee-0c68-11e6-85bd-933b7fa03b35.png) ![2016-04-27_110544](content_images/03dea62a-0c68-11e6-9441-fedf09950b85.png)

*Hint : you can right click the ![2016-04-27_110547](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/03e2fbee-0c68-11e6-85bd-933b7fa03b35.png) button to copy the current environment!*
*Hint : you can right click the ![2016-04-27_110547](content_images/03e2fbee-0c68-11e6-85bd-933b7fa03b35.png) button to copy the current environment!*

### 2nd step : name it ###

First things first, you have to define the name of your *application*. If you need it / want it, you can also create sub items (suffixes) for this application, and give it a label to quickly identify it.

![2016-04-27_111103](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/bdb0fd3c-0c68-11e6-93a7-063468ca39d1.png)
![2016-04-27_111103](content_images/bdb0fd3c-0c68-11e6-93a7-063468ca39d1.png)

### 3rd step : set the prowin32 path ###

Provide the windows path to your prowin32.exe executable. It is usually located in : `%progress_install_dir%\dlc\bin\prowin32.exe`

![2016-04-27_111239](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/f89ca374-0c68-11e6-9014-ff62f5f75fef.png)
![2016-04-27_111239](content_images/f89ca374-0c68-11e6-9014-ff62f5f75fef.png)

### 4th step : set your local directory ###

Provide the path to the folder where your application sources are located :

![2016-04-27_111616](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/7904c7c6-0c69-11e6-8133-fc6ce853a459.png)
![2016-04-27_111616](content_images/7904c7c6-0c69-11e6-8133-fc6ce853a459.png)

### 5th step : set your propath ###

There are two ways of setting your PROPATH :

![2016-04-27_111801](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/b9716f62-0c69-11e6-8977-c3b1854fae6b.png)
![2016-04-27_111801](content_images/b9716f62-0c69-11e6-8977-c3b1854fae6b.png)

*No matter which of the following methods is used, the propath can be specified as relative path. In that case, the root directory is your local directory!*

#### First method ####

You can provide the path to the progress `.ini` file, that usually contains a section `[Startup]` with the key `PROPATH` :

![2016-04-27_112004](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/0145f7fe-0c6a-11e6-9e01-8fe15cc2d2bf.png)
![2016-04-27_112004](content_images/0145f7fe-0c6a-11e6-9e01-8fe15cc2d2bf.png)

#### Second method ####

Or you can directly provide of list of folders / .pl to use in your PROPATH :

![2016-04-27_112717](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/066fd730-0c6b-11e6-8b9d-d8592527aefd.png)
![2016-04-27_112717](content_images/066fd730-0c6b-11e6-8b9d-d8592527aefd.png)

In this example, my PROPATH will be :

Expand All @@ -94,37 +94,37 @@ In this example, my PROPATH will be :

Again, two ways or configuring your database(s) connection(s) :

![2016-04-27_113446](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/114a4a54-0c6c-11e6-86c8-3e7eaa73047b.png)
![2016-04-27_113446](content_images/114a4a54-0c6c-11e6-86c8-3e7eaa73047b.png)

#### First method ####

You can choose to use a parameter file `*.pf` that contains the connection parameters.
In that case, 3P lets you have a *list* of files so you can quickly switch the current .pf to use (once again, you can only have 1 item in your list!). Use the following buttons to handle this list : ![2016-04-27_113619](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/47624092-0c6c-11e6-8619-44262232c874.png)
In that case, 3P lets you have a *list* of files so you can quickly switch the current .pf to use (once again, you can only have 1 item in your list!). Use the following buttons to handle this list : ![2016-04-27_113619](content_images/47624092-0c6c-11e6-8619-44262232c874.png)

Add a new item ![2016-04-27_113800](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/823c5694-0c6c-11e6-813a-83f9f296ab96.png), set a name and the path to this `*.pf` file as shown below :
![2016-04-27_113943](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/c19d5626-0c6c-11e6-8716-94c0866f28f9.png)
Add a new item ![2016-04-27_113800](content_images/823c5694-0c6c-11e6-813a-83f9f296ab96.png), set a name and the path to this `*.pf` file as shown below :
![2016-04-27_113943](content_images/c19d5626-0c6c-11e6-8716-94c0866f28f9.png)

#### Second method ####

You can also choose to define the connection parameters for *one or more* databases directly in the interface :

![2016-04-27_114159](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/2fe8d6dc-0c6d-11e6-9302-baf211ef1efe.png)
![2016-04-27_114159](content_images/2fe8d6dc-0c6d-11e6-9302-baf211ef1efe.png)

This example will connect to two different databases.

#### Once the connection is set! ####

When your database connection is set properly, you can click this button ![2016-04-27_114415](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/61b7fdd2-0c6d-11e6-904f-f0bed498be02.png) to download the database structure and get the autocompletion on tables/fields/sequences!
When your database connection is set properly, you can click this button ![2016-04-27_114415](content_images/61b7fdd2-0c6d-11e6-904f-f0bed498be02.png) to download the database structure and get the autocompletion on tables/fields/sequences!

If everything went well, the button will turn green ![2016-04-27_114529](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/99998860-0c6d-11e6-9e8d-c9ff02151c3a.png), meaning that the autocompletion is activated. You can click it again to update the autocompletion if you database structure is changed.
If everything went well, the button will turn green ![2016-04-27_114529](content_images/99998860-0c6d-11e6-9e8d-c9ff02151c3a.png), meaning that the autocompletion is activated. You can click it again to update the autocompletion if you database structure is changed.


### 7th step : set your compilation folder ###

You can choose to compile your programs and move the .r file next to your source file, or move the .r to a particular location using the following toggle :
![2016-04-27_113135](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/a28390ee-0c6b-11e6-811e-4654f48b906d.png) ![2016-04-27_113143](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/a2856108-0c6b-11e6-99b8-dfba15082b98.png)
![2016-04-27_113135](content_images/a28390ee-0c6b-11e6-811e-4654f48b906d.png) ![2016-04-27_113143](content_images/a2856108-0c6b-11e6-99b8-dfba15082b98.png)

![2016-04-27_113004](https://raw.githubusercontent.com/jcaillon/3P/gh-pages/content_images/690c9ef0-0c6b-11e6-9a9f-07697b2cb304.png)
![2016-04-27_113004](content_images/690c9ef0-0c6b-11e6-9a9f-07697b2cb304.png)

*Hint : Use the compilation path plus the page `SET > COMPILATION PATH` to fully customize the way your files are compilated and choose a different compilation folder for each particular file!*

0 comments on commit cd1ab5b

Please sign in to comment.