[Pydev-cvs] org.python.pydev.help/pydev.sf.net _debug_prefs.contents.html,NONE,1.1 _codecoverage.con
Brought to you by:
fabioz
Update of /cvsroot/pydev/org.python.pydev.help/pydev.sf.net In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17166/pydev.sf.net Modified Files: .cvsignore build.py _Features.contents.html _contentassist.contents.html _credits.contents.html _index.contents.html _codecompletion.contents.html _Roadmap.contents.html _Download.contents.html Added Files: _debug_prefs.contents.html _codecoverage.contents.html _editor_prefs.contents.html _debug.contents.html _run.contents.html _codecompletionsnapshots.contents.html Log Message: Index: .cvsignore =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/.cvsignore,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** .cvsignore 13 Oct 2004 13:37:36 -0000 1.1 --- .cvsignore 20 Oct 2004 16:53:22 -0000 1.2 *************** *** 8,9 **** --- 8,12 ---- refactoring.html Credits.html + codecoverage.html + codecompletionsnapshots.html + run.html --- NEW FILE: _run.contents.html --- To <strong>run a python file</strong> you can go in the navigator, right click it and run.<br> <br> Three run modes are available: <br> <li>Run (normally runs file)</li> <li>Coverage (gathers code coverage statistics)</li> <li>Debug (for debbuging)</li> <br> <br> <IMG src="images/run_py_file.png" border="1" ><br> <br> <br> To <strong>run a python subset of files </strong>you can go in the navigator, right click it and run.<br> <br> For multiple runs two modes are available: <li>Run (normally runs a subset of files)</li> <li>Coverage (runs a subset of files gathering coverage information)</li> <br> <br> <IMG src="images/run_py_folder.png" border="1" > <br> <br> <br> When Running a subset you can choose between <strong>running each file on a separate shell </strong>(and therefore with a different output) or <strong>running each one from a script </strong>(and the script will be responsible for choosing the files to be run (it will receive the directory as an argument). Running with the script will make a single output for all the files. An example script is provided and is be given as the default script.<br><br> <IMG src="images/run_multiple.png" border="1" > Index: _index.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_index.contents.html,v retrieving revision 1.4 retrieving revision 1.5 diff -C2 -d -r1.4 -r1.5 *** _index.contents.html 13 Oct 2004 13:37:06 -0000 1.4 --- _index.contents.html 20 Oct 2004 16:53:22 -0000 1.5 *************** *** 1,56 **** ! <p><STRONG>Pydev </STRONG>is a complete <a target="_blank" href="http://www.python.org"> python</a> development environment for <a target="_blank" href="http://www.eclipse.org"> eclipse</a>.</p> ! <P>It has been created by <B>Aleks Totic</B> as a "getting to know Eclipse project" and is currently maintained by <B>Fabio Zadrozny</B> . </P> ! <P><STRONG>Quick Summary </STRONG> ! <P>Pydev has still not reached 1.0, but it is already stable enough for ! python editing, with features such as:</P> ! <LI> ! Code completion ! <LI> ! Code Folding ! <LI> ! Outline ! <LI> ! Go to definition ! <LI> ! Refactoring (Bicycle Repair Man) ! <LI> ! Debugger ! <LI> ! Etc. (more details can be found at the <a href="Features.html">features</a> page) ! <P><STRONG>More information on the pydev plugin can be found at: </STRONG> ! </P> ! <LI> ! <A href="http://sourceforge.net/mailarchive/forum.php?forum_id=39082">pydev-code</A>: ! Developers issues mailing list. ! <LI> ! <A href="http://sourceforge.net/forum/forum.php?forum_id=293649">users</A>: ! Users bulleting board. ! <LI> ! <A href="http://blogs.osafoundation.org/atotic/cat_work_log.html">Aleks Totic ! weblog</A>: Author personal web-log where sometimes tidbits about the ! development progress are posted. ! <LI> ! <A href="http://pydev.blogspot.com/">Pydev Adventures weblog</A>: Weblog maintained by Fabio Zadrozny with notes about his experiences with the pydev ! development. ! <P><STRONG>Mentions in the press:</STRONG></P> ! <LI> ! <A href="http://www-106.ibm.com/developerworks/library/os-ecant/?ca=drs-tp2604">Python ! development with Eclipse and Ant</A> ! <LI> ! <A href="http://conferences.oreillynet.com/presentations/os2004/moore_python.pdf">Pydev ! at OsCon</A> ! <br> ! <FONT size="2"></FONT> ! <P><STRONG>Hosted at</STRONG> ! </P> ! <a target="_blank" href='http://www.sourceforge.net/projects/pydev/'>Pydev at ! SourceForge</a> ! <p><A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=85796&type=5" width="210" height="62" ! border="0" alt="SourceForge.net Logo"> </A> ! </p> ! </LI> --- 1,49 ---- ! <p> ! <STRONG>Pydev</STRONG> is a complete <a target="_blank" href="http://www.python.org"> python</a> development environment for <a target="_blank" href="http://www.eclipse.org"> eclipse</a>.</p> ! ! <P> ! It has been created by <B>Aleks Totic</B> as a "getting to know Eclipse project" and is currently maintained by <B>Fabio Zadrozny</B> . </P> ! ! <P><STRONG>Quick Summary</STRONG> (Current release is 0.7.1)</p> ! ! <P> ! Pydev has still not reached 1.0, but it is already stable enough for ! python editing, with features such as: ! </P> ! ! <LI><a href="codecompletion.html">Code Completion</a></li> ! <LI><a href="refactoring.html">Refactoring</a> with <A href="http://bicyclerepair.sourceforge.net/">bicycle repair man</A>.</li> ! <LI>Outline</li> ! <LI>Go to definition with <EM>F3</EM> (powered by <A href="http://bicyclerepair.sourceforge.net/">bicycle repair man</A>)</li> ! <LI>Debugger</li> ! <LI><a href="contentassist.html">Content Assistant</a> <EM>(Ctrl+F1)</EM></li> ! <LI><a href="codecoverage.html">Code Coverage</a></li> ! <LI>Etc. (more details can be found at the <a href="Features.html">features</a> page)</li> ! ! ! ! <P><STRONG>More information on the pydev plugin can be found at: </STRONG></P> ! <LI><A href="http://sourceforge.net/mailarchive/forum.php?forum_id=39082">pydev-code</A>: Developers issues mailing list.</li> ! <LI><A href="http://sourceforge.net/forum/forum.php?forum_id=293649">users</A>: Users bulleting board.</li> ! <LI><A href="http://blogs.osafoundation.org/atotic/cat_work_log.html">Aleks Totic weblog</A>: Author personal web-log where ! sometimes tidbits about the development progress are posted.</li> ! <LI><A href="http://pydev.blogspot.com/">Pydev Adventures weblog</A>: Weblog maintained by Fabio Zadrozny with notes about his experiences with the pydev ! development.</li> ! ! ! ! <P><STRONG>Mentions in the press:</STRONG></P> ! <LI><A href="http://www-106.ibm.com/developerworks/library/os-ecant/?ca=drs-tp2604">Python development with Eclipse and Ant</A></li> ! <LI><A href="http://conferences.oreillynet.com/presentations/os2004/moore_python.pdf">Pydev at OsCon</A></li> ! ! ! <br> ! <FONT size="2"></FONT> ! <P><STRONG>Hosted at</STRONG></P> ! <a target="_blank" href='http://www.sourceforge.net/projects/pydev/'>Pydev at SourceForge</a> ! <p><A href="http://sourceforge.net"> <IMG src="http://sourceforge.net/sflogo.php?group_id=85796&type=5" width="210" height="62" border="0" alt="SourceForge.net Logo"> </A></p> Index: _Roadmap.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_Roadmap.contents.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** _Roadmap.contents.html 8 Oct 2004 16:58:34 -0000 1.2 --- _Roadmap.contents.html 20 Oct 2004 16:53:22 -0000 1.3 *************** *** 1,42 **** ! <H3>This are the features I would like to have... (One can wish right?)</H3> <P>The roadmap is still not traced... but if you want to come along and do any of those (or others), feel free... (features already implemented are not here again).</P> ! <LI> ! Make a nicer code completion - not executing code and with a better cache system.</LI> ! <LI> ! Make the content assistant better</LI> ! <LI> ! Code coverage</LI> ! <LI> ! Quick outline (like java does)</LI> ! <LI> ! Package explorer</LI> ! <LI> ! Todo-list</LI> ! <LI> ! Unit-test</LI> ! <LI> ! Interactive shell</LI> ! <LI> ! Wizards (create class / module)</LI> ! <P> </P> <H3>You'd like to give it a try?</H3> ! <P><STRONG></STRONG><FONT face="Times New Roman">You can download the latest source ! from sourceforge. </FONT> ! </P> ! <P><FONT face="Times New Roman">To compile, you need to setthe following preferences:</FONT></P> ! <P><FONT face="Times New Roman">'Plug-In Development:Java Build Path Control:Use ! classpath containers' to true</FONT></P> ! <P><FONT face="Times New Roman">'Plug-In Development:Target Platform' select "this ! application" and enable all plugins.</FONT></P> ! <P><FONT face="Times New Roman">Most of the code is well-documented in javadoc. I try ! to cc every answer to a codingquestion to pydev-code, so you can look there for ! hints too. That's it. If you have not developed Eclipse plugins before, I ! recommend reading the online documentation and trying out a sample plugin. ! Doing some prep work before jumping in will really pay off.</FONT></P> ! <P><FONT face="Times New Roman"><STRONG>Then, it is all up to you.</STRONG></FONT><STRONG> ! </STRONG> ! </P> --- 1,37 ---- ! <H3>This are the features I would like to have... (One can wish right?)</H3> + <P>The roadmap is still not traced... but if you want to come along and do any of those (or others), feel free... (features already implemented are not here again).</P> ! ! <LI>Make a nicer code completion - not executing code and with a better cache system.</LI> ! <LI>Make the content assistant better</LI> ! <LI>Quick outline (like java does)</LI> ! <LI>Package explorer</LI> ! <LI>Todo-list</LI> ! <LI>Interactive shell</LI> ! <LI>Wizards (create class / module)</LI> ! <br> ! <br> ! ! <H3>You'd like to give it a try?</H3> ! ! <P>You can download the latest source ! from sourceforge. </P> ! ! <P>To compile, you need to set the following preferences:</P> ! ! <P>'Plug-In Development: Java Build Path Control: Use classpath containers' to true</P> ! ! <P>'Plug-In Development: Target Platform' select "this application" and enable all plugins.</P> ! ! <P>Most of the code is well-documented in javadoc. I try ! to cc every answer to a codingquestion to pydev-code, so you can look there for ! hints too. That's it. If you have not developed Eclipse plugins before, I ! recommend reading the online documentation and trying out a sample plugin. ! Doing some prep work before jumping in will really pay off.</P> ! ! <P><STRONG>Then, it is all up to you.</STRONG></P> Index: _contentassist.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_contentassist.contents.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** _contentassist.contents.html 8 Oct 2004 16:47:10 -0000 1.1 --- _contentassist.contents.html 20 Oct 2004 16:53:22 -0000 1.2 *************** *** 1,59 **** <H3>Content Assistant</H3> <P>This is still on development, but it can already be useful. Current status is:</P> ! <P> ! If you have a call in the main module, let's say:<BR> ! <BR> ! C()| Ctrl+1 - bring a list of suggestions for assistants (it's still not very ! complete, but it has already proved very usable for me)<BR> ! <BR> ! Or if you have:<BR> ! <BR> ! <FONT face="Courier New" size="2">Class C:<BR> ! <BR> ! ....def a(self):<BR> ! ........self.newMethod()| Ctrl+1 also brings some interesting assistants. </FONT> ! </P> ! <P><FONT face="Courier New" size="2">Whishes:</FONT></P> ! <P><FONT face="Courier New" size="2"></FONT> </P> ! <FONT face="Courier New" size="2">class A: pass<br> ! <br> ! class C:<br> ! <br> ! ....def __init__(self, param): ! <br> ! ........self.newMethod()<- create new method on class C (with params if ! needed)<br> ! ........................<- assign result to new local variable ! <br> ! ........................<- assign result to new field ! <br> ! <br> ! ........a = A()<br> ! ........a.newMethod() <- create new method on class A ! <br> ! ........................<- assign result to new local variable ! <br> ! ........................<- assign result to new field<br> ! <br> ! ........param.b() <- don't show anything.<br> ! <br> ! ........self.a1 = A() ! <br> ! ........self.a1.newMethod() <- create new method on class A (difficult part ! is discovering class)<br> ! ............................<- assign result to new local variable ! <br> ! ............................<- assign result to new field<br> ! <br> ! ........def m(self): ! <br> ! ............self.a1.newMethod() <- create new method on class A ! <br> ! ................................<- assign result to new local variable ! <br> ! ................................<- assign result to new field<br> ! <br> ! ............importcompiler<- move import to global context<br> ! ............NewClass() <- Create class NewClass (Depends on new class ! wizard)<br> </FONT> --- 1,54 ---- <H3>Content Assistant</H3> <P>This is still on development, but it can already be useful. Current status is:</P> ! ! <strong>New content assistants added (0.7.1):</strong><br><br> ! <li>Move imports:</li><br> ! If you have some import on a non global scope, a move to global scope tip appears. It moves the current ! import line to the beggining of the file. ! <br><br> ! <li>Make statement new Class or Method:</li><br> ! If you are in the global scope and write a call (e.g.: NewClass(a, b)), and press Ctrl+1, the following ! tips will appear: <br> ! Make this a new method and make this a new class. ! <br> ! <br><br> ! <strong>Resuming:</strong><BR> ! <BR> ! <FONT face="Courier New" size="2">Class C:<BR> ! <BR> ! ....def a(self):<BR> ! ........self.newMethod()| Ctrl+1 also brings some interesting assistants. <br> ! <br> ! class C:<br> ! <br> ! ....def __init__(self, param):<br> ! ........self.newMethod()<- create new method on class C (with params if needed)<br> ! ........................<- assign result to new local variable<br> ! ........................<- assign result to new field<br> ! <br> ! ........a = A()<br> ! ........a.newMethod() <- create new method on class A<br> ! ......................<- assign result to new local variable<br> ! ......................<- assign result to new field<br> ! <br> ! ........param.b() <- don't show anything.<br> ! <br> ! ........self.a1 = A()<br> ! <br> ! ........self.a1.newMethod() <- create new method on class A (difficult part is discovering class - still not implemented)<br> ! ............................<- assign result to new local variable<br> ! ............................<- assign result to new field<br> ! <br> ! ........def m(self):<br> ! ............self.a1.newMethod() <- create new method on class A (difficult part is discovering class - still not implemented)<br> ! ................................<- assign result to new local variable<br> ! ................................<- assign result to new field<br> ! <br> ! ............import compiler<- move import to global context<br> ! <br> ! <br> ! NewClass() <- Make this a new class <br> ! ...........<- Make this a new method <br> ! ...........<- assign result to new local variable<br> ! ...........<- assign result to new field<br> </FONT> --- NEW FILE: _debug_prefs.contents.html --- <h2>Pydev debugger preferences </h2> <p>Configure your python executables here. By default, pydev will try to run "python".</p> <p><img src="images/db_prefs.gif" width="599" height="326"></p> Index: _codecompletion.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_codecompletion.contents.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** _codecompletion.contents.html 8 Oct 2004 16:47:10 -0000 1.1 --- _codecompletion.contents.html 20 Oct 2004 16:53:22 -0000 1.2 *************** *** 1,7 **** <H3>Code Completion</H3> ! <P>This feature is already usable, but still has to be used with care, as it <STRONG>executes ! the current editor code to get it's completions</STRONG>. That means that one should be very careful on what is put in the global context when using code completion.</P> <P>So, that means that if you put sys.exec("rm -r *") in the top level of any module, it would probably would really delete all you have... Not good --- 1,17 ---- <H3>Code Completion</H3> ! ! <br> ! <strong> Notes for release 0.7.1</strong><br> ! Code completion has some changes in version 0.7.1, most notable, the parameters of a method are also gotten ! when completing and the autocompletion has been completely disabled (mainly because of complaints on the editor ! hanging and because most of the time you don't have valid completions - it only works for the tokens gotten ! from the global scope and on self - so, forget about trying to complete on parameters...). ! <br> ! ! <P>But even with those limitations, this feature is already usable, but still has to be used with care, ! as it <STRONG>executes the current editor code to get it's completions</STRONG>. That means that one should be very careful on what is put in the global context when using code completion.</P> + <P>So, that means that if you put sys.exec("rm -r *") in the top level of any module, it would probably would really delete all you have... Not good *************** *** 10,14 **** makes me feel not so guilty :-) ). </P> ! <P>Aside from that, code completion works on imports, on the current class and on the global context - it uses the current pythonpath in order to do that, so, if you go in python and</P> --- 20,27 ---- makes me feel not so guilty :-) ). </P> ! <br> ! <strong> Now, how to use it:</strong><br> ! <a href="codecompletionsnapshots.html">(Here are some snapshots on the current uses)</a> ! <P>Code completion works on imports, on the current class and on the global context - it uses the current pythonpath in order to do that, so, if you go in python and</P> *************** *** 65,69 **** <P><FONT face="Courier New" size="2"><FONT face="Times New Roman" size="3">Currently code completion does not work on methods after '(' and on any variable that is ! passed in as a parameter == actually it works only on 'self', on the imports ! and on global variables ==</FONT></P> </FONT> --- 78,82 ---- <P><FONT face="Courier New" size="2"><FONT face="Times New Roman" size="3">Currently code completion does not work on methods after '(' and on any variable that is ! passed in as a parameter. Right now it works only on 'self', on the imports ! and on global variables </FONT></P> </FONT> Index: build.py =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/build.py,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** build.py 13 Oct 2004 13:13:52 -0000 1.2 --- build.py 20 Oct 2004 16:53:22 -0000 1.3 *************** *** 1,5 **** - def Template( p_template, p_name ): --- 1,4 ---- *************** *** 23,31 **** Template( '_template.html', 'Roadmap' ) Template( '_template.html', 'codecompletion' ) Template( '_template.html', 'contentassist' ) Template( '_template.html', 'refactoring' ) Template( '_template.html', 'Faq' ) Template( '_template.html', 'Credits' ) ! ! Main() --- 22,36 ---- Template( '_template.html', 'Roadmap' ) Template( '_template.html', 'codecompletion' ) + Template( '_template.html', 'codecompletionsnapshots' ) Template( '_template.html', 'contentassist' ) Template( '_template.html', 'refactoring' ) Template( '_template.html', 'Faq' ) Template( '_template.html', 'Credits' ) ! Template( '_template.html', 'codecoverage' ) ! Template( '_template.html', 'run' ) ! Template( '_template.html', 'debug' ) ! Template( '_template.html', 'debug_prefs' ) ! Template( '_template.html', 'editor_prefs' ) ! ! Main() --- NEW FILE: _codecoverage.contents.html --- <strong>Code coverage is a whole new feature, added on version 0.7.0</strong><br> <br> The data gathered for code coverage is obtained by a module distributed along with pydev, based on the <A href="http://www.ravenbrook.com/project/p4dti/master/test/"> Perforce Defect Tracking Integration Project </a> (actually, it was just slightly modified so that the output and input could be given in other ways). <br> <br> <strong>Code coverage provides the following features:</strong><br> <br> <strong>In the navigator:</strong><br> <li>run a file with code coverage recording <a href="run.html">(right click on python file)</a></li> <li>run multiple files with code coverage recording <a href="run.html">(right click on folder)</a></li> <br> <strong>In code coverage contributed view:</strong><br> <li>clean the code coverage information</li> <li>refresh the code coverage information</li> <li>choose directory to see code coverage information</li> <li>See coverage information for a file or folder + subfolders</li> <li>Double clicking from the coverage dir indicates the lines that were not executed as errors.</li> <br> <br> <IMG src="images/codecoverageview.png" border="1" > <br><br> <strong> Usage:</strong><br> <br> Basically, you do some runs with the code coverage run, then you choose a dir from where you want coverage information and can browse it as much as you want (results for the file or folder + subfolders always on the left).<br> <br> If you want to clear all the runs info, just click on clear on the view (this will not refresh the info already gotten).<br> <br> Now, if you do some more runs and want to refresh it, just call refresh.<br> <br> <strong>Note:</strong> when the view is closed, the information does not reappear. However, it is not lost. You just have to choose the folder again (the information is only lost if you click on Clear). Index: _Download.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_Download.contents.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** _Download.contents.html 8 Oct 2004 16:58:34 -0000 1.2 --- _Download.contents.html 20 Oct 2004 16:53:22 -0000 1.3 *************** *** 1,19 **** <h2>Download:</h2> ! <p>The current release is <b>0.6.1</b> and can be obtained from the sites: ! <li> ! Download from <a target="_blank" href='http://www.sourceforge.net/projects/pydev/'>SourceForge</a>. ! <li> ! Download from <a target="_blank" href="http://pydev.sf.net/updates/">Eclipse ! updates</a></li> ! <h4>Requirements:</h4> ! <li> ! <a href="">Eclipse 3.0</a></li> ! <h4>Installation Instructions:</h4> ! <p class="TODO">Fast install: just go to the eclipse update manager and add update site: <A href="http://pydev.sf.net/updates/">http://pydev.sf.net/updates/</A> (eclipse should do the rest)</p> ! <P class="TODO">An alternative is just downloading the zip file and extracting it yourself in eclipse. If you choose to do it, just make sure the plugins folder is extracted on top of the eclipse plugins folder.</P> - <P class="TODO"> </P> - <P class="TODO"> </P> --- 1,22 ---- <h2>Download:</h2> ! <p>The current release is <b>0.7.1</b> and can be obtained from the sites: ! ! <li>Download from <a href='http://www.sourceforge.net/projects/pydev/'>SourceForge</a>.</li> ! <li>Download from <a href="http://pydev.sf.net/updates/">Eclipse updates</a></li> ! ! ! <h4>Requirements:</h4> ! ! <li><a href="http://www.eclipse.org/">Eclipse 3.0</a> support for previous versions has been discontinued.</li> ! ! ! ! <h4>Installation Instructions:</h4> ! ! <p >Fast install: just go to the eclipse update manager and add update site: <A href="http://pydev.sf.net/updates/">http://pydev.sf.net/updates/</A> (eclipse should do the rest)</p> ! ! <P >An alternative is just downloading the zip file and extracting it yourself in eclipse. If you choose to do it, just make sure the plugins folder is extracted on top of the eclipse plugins folder.</P> --- NEW FILE: _codecompletionsnapshots.contents.html --- <strong> Completing on self (current class - gets attributes too)<br><br><br> <IMG src="images/compl1.png" border="1" > <br><br><br> Completing on the imports (goes for PYTHONPATH)<br><br><br> <IMG src="images/compl2.png" border="1" > <br><br><br> Completing on an import<br><br><br> <IMG src="images/compl3.png" border="1" > <br><br><br> Completing for global tokens<br><br><br> <IMG src="images/compl4.png" border="1" > </strong> Index: _credits.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_credits.contents.html,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** _credits.contents.html 13 Oct 2004 13:13:34 -0000 1.1 --- _credits.contents.html 20 Oct 2004 16:53:22 -0000 1.2 *************** *** 1,15 **** ! <!--StartFragment --> ! <P><STRONG>Pydev</STRONG> has been created by <B>Aleks Totic</B> as a "getting to ! know Eclipse project" and is currently maintained by <B>Fabio Zadrozny</B> . </P> ! <P> Other developers that helped (or still are helping) in ! the development of pydev are: </P> ! <LI> <!--StartFragment --> Dana Moore ! <LI> ! William Wright ! <LI> ! Grig Gheorghiu ! </LI> ! <LI> ! Parhaum Toofanian</LI> --- 1,22 ---- ! <P> ! <STRONG>Pydev</STRONG> has been created by <B>Aleks Totic</B> as a "getting to ! know Eclipse project" and is currently maintained by <B>Fabio Zadrozny</B> . </P> ! ! <P> ! Other developers that helped (or are still helping) in the development of pydev are: </P> ! ! ! <LI>Dana Moore</li> ! <LI>William Wright</li> ! ! <!-- ! Inactive (or did not make significant contributions) ! <P> ! And developers that submitted patches: ! </P> ! ! <LI>Grig Gheorghiu</LI> ! <LI>Parhaum Toofanian</LI> ! --> \ No newline at end of file Index: _Features.contents.html =================================================================== RCS file: /cvsroot/pydev/org.python.pydev.help/pydev.sf.net/_Features.contents.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** _Features.contents.html 8 Oct 2004 16:58:34 -0000 1.2 --- _Features.contents.html 20 Oct 2004 16:53:22 -0000 1.3 *************** *** 1,71 **** ! <h2>Features (release 0.6.1):</h2> ! <p>The pydev is composed of three plug-ins:</p> ! <h3>Editor (org.python.pydev):</h3> ! <li> ! Syntax highlighting ! <li> ! Parser errors marked in the task list ! <li> ! Outline view with imports/functions/classes ! <li> ! Tabs or spaces preference ! <LI> ! Smart indentation ! <li> ! Navigation: keyboard shortcuts to previous or next ! function. <EM>Default: (Ctrl+Shift+Up ! and Ctrl+Shift+Down) </EM> ! <li> ! Comment and uncomment commands (on the popup menu) and ! keybindings. <EM>Default: (Ctrl+3 and Ctrl+Shift+3) </EM> ! <li> ! hyperlinks over functions//import statements ! <li> ! Code folding ! <LI> ! <a href="refactoring.html">Refactoring</a> with <A href="http://bicyclerepair.sourceforge.net/"> ! bicycle repair man</A>. ! <LI> ! <a href="codecompletion.html">Code Completion</a> ! <EM>(Ctrl+Space) </EM> ! <LI> ! Templates Completion <EM>(Ctrl+Space Too) </EM> ! <LI> ! Go to definition with <EM>F3</EM> (powered by <A href="http://bicyclerepair.sourceforge.net/"> ! bicycle repair man</A>) <LI> ! <a href="contentassist.html">Content Assistant</a> ! <EM>(Ctrl+F1)</EM></LI> ! <h3>Debugger (org.python.pydev.debug)</h3> ! <li> ! breakpoints ! <li> ! step in/out/over ! <li> ! multiple threads ! <li> ! variable display ! <li> ! file hyperlinks in the console output (you can click on stack traces) </li> <H3>Help (org.python.pydev.help)</H3> ! <LI> ! Brief documentation in Eclipse format. ! </LI> <H3>Note on code completion</H3> <P>Code completion works on top of a python shell and really <STRONG>executes the code ! you write on the top level on the module</STRONG> , so, beware of what is written in this case (as a rule, you should never initialize a variable to ! something other that None. You should init it to None and then call a ! function to make the real initialization after an <EM>if __name__ == ! '__main__'</EM> statement or inside some other scope, but never in the ! global scope of the module (not only because of code completion, as a simple ! import of that code would do it).</P> <H3>Note on text completion</H3> <P> ! We do not provide text completion ourselves in the plugin, as other ! plugins already provide this. A good suggestion is using the <A href="http://sourceforge.net/projects/lunar-eclipse/"> ! lunar eclipse</A> editor-enhancements plugin. It does not only ! provide text completion, but other very useful enhancements.</P> ! <P> </P> ! <P> </P> --- 1,72 ---- ! <h2>New on 0.7.1:</h2> ! <br> ! <LI><a href="codecoverage.html">Code Coverage</a></li> ! <LI><a href="run.html">Run subset from dir</a> (this is not unit-test, but it can be really useful if you do tests).</li> ! <LI><a href="contentassist.html">New Content Assistants</a> <EM>(Ctrl+F1)</EM></li> <LI> ! Integrated new <a href="refactoring.html">refactorings</a> from <A href="http://bicyclerepair.sourceforge.net/">bicycle repair man</A> ! (inline local variable and extract local variable) </li> + + <br> + <br> + + <h2>Features (release 0.7.1):</h2> + + <p>Pydev is composed of three plug-ins:</p> + + + <h3>Editor (org.python.pydev):</h3> + + <li>Syntax highlighting</li> + <li>Parser errors marked in the task list</li> + <li>Outline view with imports/functions/classes</li> + <li>Tabs or spaces preference</li> + <LI>Smart indentation</li> + <li>Navigation: keyboard shortcuts to previous or next function. <EM>Default: (Ctrl+Shift+Up and Ctrl+Shift+Down) </EM></li> + <li>Comment and uncomment commands (on the popup menu) and keybindings. <EM>Default: (Ctrl+3 and Ctrl+Shift+3) </EM></li> + <li>hyperlinks over functions//import statements</li> + <li>Code folding</li> + <LI><a href="refactoring.html">Refactoring</a> with <A href="http://bicyclerepair.sourceforge.net/">bicycle repair man</A>.</li> + <LI><a href="codecompletion.html">Code Completion</a> <EM>(Ctrl+Space) </EM> </li> + <LI>Templates Completion <EM>(Ctrl+Space Too) </EM></li> + <LI>Go to definition with <EM>F3</EM> (powered by <A href="http://bicyclerepair.sourceforge.net/">bicycle repair man</A>)</li> + <LI><a href="contentassist.html">Content Assistant</a> <EM>(Ctrl+F1)</EM></li> + <LI><a href="codecoverage.html">Code Coverage</a></li> + + + + <h3>Debugger (org.python.pydev.debug)</h3> + + <li>breakpoints</li> + <li>step in/out/over</li> + <li>multiple threads</li> + <li>variable display</li> + <li>file hyperlinks in the console output (you can click on stack traces)</li> + + + + <H3>Help (org.python.pydev.help)</H3> ! ! <LI>Brief documentation in Eclipse format.</li> ! ! <H3>Note on code completion</H3> <P>Code completion works on top of a python shell and really <STRONG>executes the code ! you write on the top level on the module</STRONG> , so, beware of what is written in this case (as a rule, you should never initialize a variable to ! something other that None. You should init it to None and then call a function ! to make the real initialization after an <EM>if __name__ == '__main__'</EM> statement ! or inside some other scope, but never in the global scope of the module (not ! only because of code completion, as a simple import of that code would do it). ! </P> ! ! <H3>Note on text completion</H3> <P> ! We do not provide text completion ourselves in the plugin, as other plugins ! already provide this. A good suggestion is using the <A href="http://sourceforge.net/projects/lunar-eclipse/"> ! lunar eclipse</A> editor-enhancements plugin. It does not only provide text ! completion, but other very useful enhancements. ! </P> --- NEW FILE: _debug.contents.html --- <h2>Pydev debugger </h2> <p>Here it is, try it out. You have: </p> <ul> <li>breakpoints</li> <li>step in/out/over</li> <li>multiple threads</li> <li>variable display</li> </ul> <p>The debugger can be invoked from the standard Eclipse debugger menus in the debug perspective, or through a context menu inside Navigator:</p> <p><img src="images/debugdialog.jpg" width="274" height="214"> or <img src="images/debug_menu.gif" width="328" height="373"></p> <p>Debug settings are configured in the standard dialog </p> <p><img src="images/debug_dialog.gif" width="612" height="434"> </p> <p>Here you can pick your program arguments, etc. The dialog will try to verify that your python interpreter is present. If it is not, go to Preferences:Pydev:Debug and configure a valid python executable.</p> <p>The program output is displayed in the console, and the errors in the console are hyperlinked back to the file:</p> <p><img src="images/debug_console.gif" width="600" height="498"> </p> <p>If you are running under the debugger, you'll get the standard debug interface:</p> <p><img src="images/debugger.gif" width="816" height="543"> </p> <p>See the <a href="http://pydev.sf.net/">pydev website</a> for the latest debugging info. </p> --- NEW FILE: _editor_prefs.contents.html --- <h2>Pydev editor preferences</h2> <p><img src="images/ed_prefs.gif" width="590" height="371"></p> <p><strong>Substitute spaces for tabs</strong>: whether editor should insert spaces when you hit a tab. </p> <p><strong>Assume tab spacing when files contain tabs?</strong>: you'll like this preference if you swing both ways, and mix & match tabs and spaces, When this pref is on, if the file is tab-indented editor will do the right thing and leave your tabs alone. </p> <p><strong>Code folding</strong>: turn this off if you'd like to get back the screen real estate </p> <p><strong>Tab length</strong>: in inches </p> <p><strong>Colors</strong>: are self-explanatary. The default colors have been borrowed from IDLE. </p> |