For an efficient KDevelop sprint

Sven Brauch svenbrauch at googlemail.com
Mon May 30 14:11:32 UTC 2011


Hey there!

Here's my list (everything is related to python language support):

 - Fix severe problems:
        * Crashes (can do that myself, I guess) -- won't be too much work
        * flickering! (need help)
        * dedent/indent must trigger reparse (KDevelop change required)
        * better handling of parser errors
        * address some miscellaneous problems with highlighting
        * default arguments are totally buggy
        * handling of unsure types is buggy / not implemented, too

 - Implement important features:
        * (more) sophisticated type guessing, especially for parameters!
        * "jump to error" support for output console (need help, no
idea how to do this)
        * make it easy to configure a launch (need help)
        * implement a documentation generator (means, something that uses
          pydoc / online documentation / whatever to generate
documentation files for binary libs like numpy)
        * track type of list contents
        * implement a predeclarationbuilder / parse twice (need advice)

 - Nice to have:
        * show weather imported files exist, and show the path when
moving the mouse over them
        * reverse type guessing ("oh, it's used as an int, so it's
probably one")
        * proper lambda function support

See you soon!
Sven

2011/5/30 Milian Wolff <mail at milianw.de>:
> Aleix Pol, 27.05.2011:
>> Hi guys!
>> The sprint is approaching and I guess it would be interesting to create a
>> list of things to be treated in the sprint. We'll get a lot of hacking time
>> but also it would be interesting to exchange a little the projects views.
>> Our codebase is quite stable right now and there are some architectural
>> problems that probably should be addressed and I guess that Randa is the
>> best place for that.
>>
>> My proposal would be to create a small list with things that you want to
>> solve during the meeting so that in the beginning we can discuss about them
>> when appropriate and decide about them.
>>
>> If anybody has a better idea about how to manage that, it would be
>> interesting to know about it too and if there's someone interested on some
>> problem being solved but is not coming, please tell us so, so that we can
>> think about it :).
>
> my list so far:
>
> talking:
> - 4.3 release
> - plasma-based stuff aliex developed last gsoc
> - alpha-style releases of some stuff in quanta
>
> hacking:
> - proper "move" support for for abstractfilemanagerplugin
> - cpp stuff (enum support, c++0x, ...)
> - navi menu resorting
> - close view on delete
> - rename view on file rename
> - maybe finally some improved namespace support for php
> - ...
>
> bye
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>




More information about the KDevelop-devel mailing list