Changes between Version 18 and Version 19 of ProjectIdeas


Ignore:
Timestamp:
Mar 23, 2011, 2:25:22 PM (3 years ago)
Author:
Sewi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectIdeas

    v18 v19  
    5050The task is to add about 30 test cases to provide a good coverage of Padre via the actions system. 
    5151As this has never been tested full probably the action system itself will need further extension 
    52 to be able to test various important features of Padre. 
     52to be able to use arguments for actions and test various important features of Padre. 
    5353 
     54Possible mentor: Sebastian Willing (developer of Padre, wrote the initial action system of Padre) 
    5455 
    5556== Implementing automated tests using Dogtail == 
     
    111112Related #501, #1031, #1044, #1045 
    112113 
     114Possible mentor: Sebastian Willing (developer of Padre) 
     115 
    113116== MacOSX Support == 
    114117 
     
    119122 
    120123SVN, Git and maybe others 
     124 
     125The SVN Plugin of Padre supports all basic SVN functions and some extended. The following tasks still need to be done: 
     126 
     127 * Update the GIT plugin (any maybe others) to support all basic functions like the SVN plugin does 
     128 
     129The following tasks could be added: 
     130 
     131 * Add Padre::File::SVN, maybe Padre::File::GIT and maybe others to allow Padre to access files directly on the VCS server. 
     132   * Read/Open file would be checkout/update 
     133   * Save would be commit 
     134 * Add a file rename capability to Padre (changing the filename of an open tab) and let the version control plugins also process the change. 
    121135 
    122136== Social plugins == 
     
    132146[wiki:Features/PerlTidy] 
    133147 
     148 * Configure PerlTidy using the Padre::Plugin::PerlTidy and save the values in a perltidy.rc in the project root dir 
     149 
    134150== GUI for the Perl Critic == 
    135151 
    136152[wiki:Features/PerlCritic] 
    137153 
     154== Configure projects == 
     155 
     156Most 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. 
     157 
     158Tasks: 
     159 * Add flags to the config option definitons to reflect which option could be project-specific 
     160 * Re-use the existing configuration dialog ("Preferences 2.0") showing only project specific settings and save them to the project config file 
     161 * Write tests that check if the project preferences are used only for files of this project (as far as possible) 
     162   * 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. 
     163