User talk:Jstaniek: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
__TOC__ | |||
== TODOs == | == TODOs == | ||
*Check [[Development/Tutorials/Localization/Unicode]] content against the Qt4 API, check the theory against Wikipedia's Unicode page. | *Check [[Development/Tutorials/Localization/Unicode]] content against the Qt4 API, check the theory against Wikipedia's Unicode page. |
Revision as of 17:05, 11 January 2007
TODOs
- Check Development/Tutorials/Localization/Unicode content against the Qt4 API, check the theory against Wikipedia's Unicode page.
KDElibs.com and developernew.kde.org coexistence
- Mind if I copy the build info over from kdelibs.com to here under Getting_Started/Build/Unstable_Version-Windows, and then could you review it for current correctness? Thanks --CuCullin 16:13, 11 January 2007 (CET)
- I do not recommend making redundant copies of http://www.kdelibs.com. The content there is under heavy development now. I won't be able to maintain another wiki (I already have FOUR :) ). We can make a move (not a copy) to kdelibs once KDE4 buildsystem is stable. Why? Because many steps are common and we want to share them between targets. For now the instructions are even splitted between msvc and mingw compilers, what's not optimal for maintenance.
According to my vision: eventually, kdelibs.com will be more ISVs-oriented while *.kde.org stays oriented at the community in general. -- jstaniek 17:27, 11 January 2007 (CET)
- I do not recommend making redundant copies of http://www.kdelibs.com. The content there is under heavy development now. I won't be able to maintain another wiki (I already have FOUR :) ). We can make a move (not a copy) to kdelibs once KDE4 buildsystem is stable. Why? Because many steps are common and we want to share them between targets. For now the instructions are even splitted between msvc and mingw compilers, what's not optimal for maintenance.