Git Product home page Git Product logo

Comments (9)

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
Yes indeed this is one of the most significant needs that are not implemented 
yey

Original comment by [email protected] on 8 Jan 2007 at 3:27

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
You could add for the moment a simple project manager
e.g. a simple xml or text file with the names of the .py files that integrate 
the
project and the name of the main project file if there is one.

Maybe the extension name of this files could be, .psp (pyscripter project) or 
.pyp
(python project)


Original comment by [email protected] on 26 Apr 2007 at 1:34

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
2joseooma:
The ".psp" extension is already used for Python Server Pages.
See http://www.modpython.org/live/current/doc-html/pyapi-psp.html

Original comment by [email protected] on 16 Oct 2007 at 2:45

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
What do you mean by "project manager"?

Original comment by [email protected] on 20 Oct 2007 at 12:32

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
I agree with  billiejoex, "project manager" might not be the best name for the 
feature because of its ambiguity, to me this rather sounds as a Role, not a 
Feature.
Project Explorer, or Workspace would probably be more familiar to those who 
have 
used other IDE's.

Original comment by [email protected] on 31 Oct 2007 at 10:51

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
Note that project management in PyScripter should be usable with version 
control. For
example, when you save a project file, the data in the project file should not 
be
user-specific. For user specific information you should create a second .user 
file
(just like visual studio).

In addition, project management should use relative paths when possible since
absolute paths are never guaranteed to be identical across multiple machines.

I'm probably stating the obvious here, however I just want to make sure this 
feature
isn't taking a turn for the worst. I also see the word "workspace" mentioned 
here
which in every case I've seen doesn't work very well in version control due to 
the
project data files themselves containing inappropriate data.

Examples of things you DON'T want in project files:
- Open Windows
- Caret positions in each window
- Usernames, absolute paths, operating system or machine specific data

Things you DO want in project files:
- Files added to the project (relative paths)
- script (.py) file that is executed when debug is activated

Things you'd put in a user config file (which is also generated along with the
project file):
- Debug settings (command line parameters, etc).
- Open windows, caret positions, etc.

Original comment by [email protected] on 17 Dec 2007 at 10:41

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
Fixed in version control.

>>Things you DO want in project files:
>>- Files added to the project (relative paths)
>>- script (.py) file that is executed when debug is activated
This is exactly what is saved in the project file:
- Files organised in folders (path can be absolute or relative)
- Run configurations (could be more than one, i.e.  Normal, unittest, client 
server etc.)

Original comment by pyscripter on 20 Dec 2007 at 12:34

  • Changed state: Fixed

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
What do you mean by "Fixed in version control"? Are you saying that you had to 
make
these changes? Or that the project management already worked the way I had 
described it?

In addition, what do you do about user-specific settings? How do you save those 
(if
at all)?

Original comment by [email protected] on 20 Dec 2007 at 5:20

from pyscripter.

GoogleCodeExporter avatar GoogleCodeExporter commented on July 29, 2024
It means that the Project Explorer has been implemented and will be available 
in the
next version.

User specific settings (open files, etc.) are saved anyway in PyScripter.ini 
which is
located at the user's %APPDATA%\PyScripter directory.

Original comment by pyscripter on 20 Dec 2007 at 10:16

from pyscripter.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.