Rough KDevelop 4.6 Planning

[Milian Wolff]

Hey there, while we are talking about 4.5, I'd like to get some input on what 
you think we should do for 4.6 eventually.

Personally, for 4.6, I hope to land the two big refactorings I'm working on 
currently:

On one hand the Path stuff in the sharedurls branch which promises a much more 
straight forward *and* efficient (local/remote) Path handling in KDevelop. 

Secondly, I started another interesting refactoring on the weekend related to 
our ItemRepositories. Looking some more at IndexedString, I managed to cleanup 
its API (removing potential encoding pitfalls) while also speeding it up quite 
considerably (about factor of 2 for string serialization, and about 20% for 
string deserialization). I will concentrate on landing the IndexedString 
refactoring first, then also hope to repeat the optimizations there for the 
other item repositories, and - while at it - cleaning up the mess of code that 
is itemrepository.{h,cpp}. I'm confident that by writing tests and using our 
existing tests, I can keep this working without any big breakages.

These two should result in a very noticeable performance gain, both memory and 
speed wise.

After that is done, I hope to have some time to investigate the "KDevelop 
commandline" idea we had at the Vienna sprint - lets see.

What do you guys have in mind?

Cheers
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20121218/060c511c/attachment.sig>