Difference between revisions of "User:Vincent/todo list"

From Lazarus wiki
Jump to navigationJump to search
(DB markov data for fpcbot)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
This is a list of things I hope to work on the coming time, so you can see I have great ideas. ;-)
 
This is a list of things I hope to work on the coming time, so you can see I have great ideas. ;-)
 
+
* Improve Lazarus release building process:
* <strike>update fpdoc on lazarus-ccr, so that the lcl pages link to the rtl pages.</strike>
+
**<strike>create a tool for automating building Lazarus releases. The current process requires me to login on several build machines, switch to the correct tag and start the release building. I hope to improve this using [http://xp-dev.com/wiki/133998/Homepage BLR].</strike> Lazarus 0.9.30.2 and 0.9.30.4 and its release candidates were built with BLR.
* <strike>create lazarus snapshots for linux rpms</strike>
+
** Add md5sum checking to confirm that all uploads have been done correctly.
* <strike>update this wiki site to 1.5</strike>
+
* create a tool to select revisions to be merged to the fixes branch from the [http://www.freepascal.org/~vincents/avail.log available revision list]
* <strike>move translation support from lazarus to the LCL (maybe it can be added to the FCL eventually).</strike>
+
** I started this, source is in svn at http://svn.xp-dev.com/svn/vsnijders-merge-tool/
 +
* make deb snapshots and put them in a lazarus-unstable repository
 +
** after testing by users, those debs can be moved to the existing lazarus-testing repository
 
* create a test suite, that can be run unattended, for example after a nightly build or before a release.
 
* create a test suite, that can be run unattended, for example after a nightly build or before a release.
 
** make test scripts with [http://www.autohotkey.com autohotkey] on windows.
 
** make test scripts with [http://www.autohotkey.com autohotkey] on windows.
 
** <strike>automate it all with fpcunit</strike>
 
** <strike>automate it all with fpcunit</strike>
 
** upload the testresults on a [http://www.hu.freepascal.org/lazarus/testresults/results.xml html page], so that there is a kind of dash board
 
** upload the testresults on a [http://www.hu.freepascal.org/lazarus/testresults/results.xml html page], so that there is a kind of dash board
** find alternatives for autohotkey on *nix
+
** find alternatives for autohotkey on *nix, maybe [http://code.google.com/p/autokey/ autokey]. Another alternative [http://wizzup.org/simba/ Simba], written with fpc for both Windows and Linux.
 
* find out how to setup mediawiki multilingual
 
* find out how to setup mediawiki multilingual
 
* [http://www.lazarus.freepascal.org/index.php?name=PNphpBB2&file=viewtopic&p=6373#6373 improve language detection]
 
* [http://www.lazarus.freepascal.org/index.php?name=PNphpBB2&file=viewtopic&p=6373#6373 improve language detection]
 
* create documentation (stubs) for lcl/widgetset. Here details for implementing a widgetset interface can be added, such as assumptions on what the LCL expects. It can help porting the LCL to a new widget set.
 
* create documentation (stubs) for lcl/widgetset. Here details for implementing a widgetset interface can be added, such as assumptions on what the LCL expects. It can help porting the LCL to a new widget set.
* create snapshots based on last released fpc (beside fpc svn head). I will start working on this, once fpc 2.0.4 has been released.
 
* <strike>restructure win32 installation, so that cross compilation packages can be added more easily</strike>
 
* <strike>cross compiler installers for win32</strike> see ftp://ftp.hu.freepascal.org/pub/lazarus/cross.
 
 
* creating a source based installer for win32. User can select packages and if they want to have rtl with debug info.
 
* creating a source based installer for win32. User can select packages and if they want to have rtl with debug info.
 
* write a database backend for FPCBots markov response generator to replace the in-memory stringlists and file persistant storage.
 
* write a database backend for FPCBots markov response generator to replace the in-memory stringlists and file persistant storage.
 +
* Improve help integration in the IDE
 +
** easier installation of local help
 +
** make local version of IDE help
 +
** make help browser ready (robust enough) for use in big ide
 +
** better search (port Lucene?), OTOH chm search works fine
  
 
----
 
----
 
If you have suggestions or comments, feel free to add them to the [[User_talk:Vincent/todo_list|talk page]].
 
If you have suggestions or comments, feel free to add them to the [[User_talk:Vincent/todo_list|talk page]].

Latest revision as of 21:02, 3 April 2012

This is a list of things I hope to work on the coming time, so you can see I have great ideas. ;-)

  • Improve Lazarus release building process:
    • create a tool for automating building Lazarus releases. The current process requires me to login on several build machines, switch to the correct tag and start the release building. I hope to improve this using BLR. Lazarus 0.9.30.2 and 0.9.30.4 and its release candidates were built with BLR.
    • Add md5sum checking to confirm that all uploads have been done correctly.
  • create a tool to select revisions to be merged to the fixes branch from the available revision list
  • make deb snapshots and put them in a lazarus-unstable repository
    • after testing by users, those debs can be moved to the existing lazarus-testing repository
  • create a test suite, that can be run unattended, for example after a nightly build or before a release.
    • make test scripts with autohotkey on windows.
    • automate it all with fpcunit
    • upload the testresults on a html page, so that there is a kind of dash board
    • find alternatives for autohotkey on *nix, maybe autokey. Another alternative Simba, written with fpc for both Windows and Linux.
  • find out how to setup mediawiki multilingual
  • improve language detection
  • create documentation (stubs) for lcl/widgetset. Here details for implementing a widgetset interface can be added, such as assumptions on what the LCL expects. It can help porting the LCL to a new widget set.
  • creating a source based installer for win32. User can select packages and if they want to have rtl with debug info.
  • write a database backend for FPCBots markov response generator to replace the in-memory stringlists and file persistant storage.
  • Improve help integration in the IDE
    • easier installation of local help
    • make local version of IDE help
    • make help browser ready (robust enough) for use in big ide
    • better search (port Lucene?), OTOH chm search works fine

If you have suggestions or comments, feel free to add them to the talk page.