The use of Wingide

1.jpg (92.66 KB, download times: 0)

Download attachments save to album

2013-3-12 14:31 Upload
The Wingide user interface consists mainly of three parts: the editing area and two tool areas. Each zone has its own menu options. Edit and Toggle buttons to enable quick switching of documents.
SHIFT +f2 to maximize the editing area

2. Detect if your Python integration environment is correct
Before we start editing the code, we need to first make sure that Wingide has exactly found the Python installer. To check, we need to use the Python Shell tool.
Right-click on the horizontal toolbar--->insert tool-->python shell, you will see the following:

If it is not displayed, or the Python version is not displayed. We can use project---->project properties to specify environment. Specify information such as the running environment for Python.
Now you can run some instances in the Python shell to determine if Python is correct.

3. Establishment of a project
(1) Now it's time to start coding. Project---->new Project to create a new project.
Note that when you create a new project, the current document is closed.
(2) Adding files to the project
Right-click in the empty section of the project and select the relevant options. You can add files and folders that already exist, or you can add new files and folders. Finally, save the project. Save the. wpr file as the name of your project.

In the upper-right corner of the editing area, there is a small button that switches between the circle and the pin.
The circular representation file will remain open until you explicitly close it.
A pin represents a file that, if it has not been edited, is likely to close itself.

4. Set the properties of Python
We can set the search path for Python, as shown in the following figure:


5. Use of the editing area
The editing area has two most important accessibility tools: Code auto prompt and source code analysis tools
Code Auto Tip: You can prompt for possible code without entering all the code
Source Analysis Tools: Help us analyze the code we write ourselves
Open Source Analysis tool: Toolbar right button--->insert tool---->source Assistant

The TAB key selects the first prompt line by default.
If the problem is indented, the wingide will display a wavy red line below the problematic line and then disappear.

6. The use of debugging
You can add breakpoints by clicking the left arrow at the front of each line. Then press the green arrow to start debugging. Wing stops at the breakpoint and displays the parameter information for the debugging.

We can then stack the data tool and check the status of the program.
DEBUG I/O is a place where we communicate with the program, the same as the command line.
7.Exceptions Tools
When our program fails, the tool can display the details of the error.
8.debug probe
When the program is paused, we can use the debug probe to do some work on the program. Also, it contains information about the stack that the program executes to now.
9.watch
When debugging, we can use it to view the data of the program, only need to enter the name of the variable you want to see.
10. Run the Django program
Select Manage, right-click Debug selected, and then enter Runserver in run arguments and click OK. (Will cause the process can not be turned off the problem, plus--noreload on the OK)
Once the user starts the development server with manage.py Runserver, it starts a Django process, which, of course, is a python process if we look at it with PS or Task Manager, but he runs the manage.py.
Let Django not produce child processes and let the parent process run directly as an HTTP server. Fortunately, in the new Django, adding the--noreload option allows Django to do so, and if the old Django may need to modify the source code to do so.