Compiling schemas not part of the application template
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Quickly |
New
|
Undecided
|
Unassigned |
Bug Description
I am trying to work on a Quickly project created after the ubuntu-application template from PyDev. Now, this process is currently quite hard for several reasons:
- there is no "entry python script" that can be launched simply (the bin/<project_name> is the same name as the main code module which causes attribute errors, it doesn't have a .py extension etc.)
- the settings schemas are handled inside the quickly run command which makes the program depend on quickly; running just the bin/<project_name> in a terminal causes a missing schema error
In my oppinion, a partial solution would be:
- create a script called bin/<project_
- add the snippet from quickly's run.py to compile the schemas to this dev_launcher:
### BEGIN inserted from Quickly's run.py
# Compile schema if present
schemapath = os.path.
if os.path.
subprocess.
### END
This still requires from the user to append ":/path/
All in all, I think the goal should be for the project generated from a Quickly template to be completely autonomous of Quickly itself for all development runs, tests etc. to enable various workflows for this and not just manually editing the files and using a terminal.
Ideally the Eclipse's .project file could be generated as well to enable the user to import the project straight to Eclipse. It's 2 XML files, really nothing complicated. Something like 'quickly ide' to launch it comes to mind :)
description: | updated |
Hi Dražen
You spotted a design feature in quickly, it acts as its own ide and is tightly coupled with gedit . The quickly developers have even made a few trys at getting quickly to automatically load some ide extensions into gedit. The projects built with quickly are really only complete and stand alone after they are packaged. Using the source tree requires you use quickly run.
You have discovered the steps needed to integrate with eclipse but as there are many ide choices I suggest we look at using 'quickly add pydev' as the suitable command.
What I suggest for getting your perfect work flow is to create a toolkit for pydev integration quickly/ templates/ ubuntu- application/ add.py ~/quickly- templates/ toolkit templates/ toolkit/ store templates/ toolkit/ store/pydev. py
$ quickly quickly ubuntu-cli toolkit
copy the add.py command from ubuntu-application into your toolkit
$ cp /usr/share/
$ mkdir ~/quickly-
then put the necessary code mentioned above into ~/quickly-
After that you can run
$ quickly -t toolkit add pydev
within any of your projects. When the "add pydev" command is perfected submit a patch, then you won't need the "- t toolkit" parameter.