Changes between Version 18 and Version 19 of ProjectIdeas

Timestamp:

03/23/11 14:25:22 (2 years ago)

Author:

Sewi

Comment:

--

ProjectIdeas

@@ -50 +50 @@
 The task is to add about 30 test cases to provide a good coverage of Padre via the actions system.
 As this has never been tested full probably the action system itself will need further extension
-to be able to test various important features of Padre.
+to be able to use arguments for actions and test various important features of Padre.
 
+Possible mentor: Sebastian Willing (developer of Padre, wrote the initial action system of Padre)
 
 == Implementing automated tests using Dogtail ==
@@ -111 +112 @@
 Related #501, #1031, #1044, #1045
 
+Possible mentor: Sebastian Willing (developer of Padre)
+
 == MacOSX Support ==
 
@@ -119 +122 @@
 
 SVN, Git and maybe others
+
+The SVN Plugin of Padre supports all basic SVN functions and some extended. The following tasks still need to be done:
+
+ * Update the GIT plugin (any maybe others) to support all basic functions like the SVN plugin does
+
+The following tasks could be added:
+
+ * Add Padre::File::SVN, maybe Padre::File::GIT and maybe others to allow Padre to access files directly on the VCS server.
+   * Read/Open file would be checkout/update
+   * Save would be commit
+ * Add a file rename capability to Padre (changing the filename of an open tab) and let the version control plugins also process the change.
 
 == Social plugins ==
@@ -132 +146 @@
 [wiki:Features/PerlTidy]
 
+ * Configure PerlTidy using the Padre::Plugin::PerlTidy and save the values in a perltidy.rc in the project root dir
+
 == GUI for the Perl Critic ==
 
 [wiki:Features/PerlCritic]
 
+== Configure projects ==
+
+Most configuration settings may also appear in a project-specific padre.yml config file in the project root dir. An example is found in the Padre source project dir in trunk.
+
+Tasks:
+ * Add flags to the config option definitons to reflect which option could be project-specific
+ * Re-use the existing configuration dialog ("Preferences 2.0") showing only project specific settings and save them to the project config file
+ * Write tests that check if the project preferences are used only for files of this project (as far as possible)
+   * Example: Open a file from a project and one without a project. Use the actionqueue to push a "tab" into each of them and save them. The test script could check if the project-specific and global tab width has been respected.
+