KDevelop/Meeting2011: Difference between revisions
Appearance
< KDevelop
No edit summary |
No edit summary |
||
Line 157: | Line 157: | ||
* remove Ctrl-T or bind it to what Ctrl-N does | * remove Ctrl-T or bind it to what Ctrl-N does | ||
* Ctrl-N should open new file in a new tab | * Ctrl-N should open new file in a new tab | ||
Revision as of 15:53, 3 June 2011
Randa 2011 KDevelop Meeting
Agenda
Thu
- get up with an agenda
Plugins
requirements for plugins in extragear/kdevelop/*:
- kdereview
- maintainer
- releasable
- unit tests (and none failing)
plugins to merge:
- kdevplatform/
- controlflowgraph
- TODO: investigate status, get out of kdereview
- execute script
- TODO: investigate status, get into kdereview
- controlflowgraph
- kdevelop/
- qmake
- TODO: Milian: investigate status, get into kdereview
- qmake
- kdevelop/plugins/
- merge php/php-docs
- TODO: Milian
- css
- TODO: investigate status, get into kdereview
- execute browser
- TODO: investigate status, get into kdereview
- xdebug
- TODO: investigate status, get into kdereview
- merge php/php-docs
notes on /plugins:
- not a single big repo (devs against it)
- TODO: document easy "build-all" process on techbase
note for developers: kdevplatform API breakages must be fixed in every stable repo, i.e. everything in https://projects.kde.org/projects/extragear/kdevelop must be compiling
Build Bot & Unit Testing
- TODO: Get a build bot running
- either on every commit (much work)
- or at least once a day (single to implement)
- TODO: Get a unit test bot running
- requirements:
- no failing unit tests (XFAIL is OK)
- no agressive performance tests (time limit, memory limit, ...)
- requirements:
- TODO: investigate cdash
- kdelibs dashboard is down, not a good impression
- TODO: ask PovAddict on his experience with build bot + unit tests
Gluon
- try to rebase gluoncreator on kdevplatform
- put improvements into the platform
- plugin based diff-viewer (i.e. to compare designer files, images, ...)
- improved history viewer (timeline, ...)
- alternatively try to reuse parts of kdevplatform in gluoncreator
- problem: kdevplatform (rightly so!) expect full kdevplatform availability
Unit Tests
developers:
- never submit failing unit tests (use QEXPECT_FAIL)
- try to run unit tests regularily
Wed
Project Dashboard
saving/sharing:
- opt-in 'save to project file' which is shared to users via project.kdev4
- good for users opening the project the first time in kdevelop
- by default save changes to dashboard in .kdev4/ folder
plasmoids:
- vcs commit log (provided by vcs plugin)
- file contents view
- webslide
- feedreader
use cases:
- project website news (feed reader)
- project resources: bugtracker, mailing list, ... (webslide / file contents view)
- recent commits (vcs plugin)
Session Dashboard
- read-only
- only shown when no view exists, esp. on first start
- contents:
- recent sessions
- recent projects
- recent files
- open new file/session/project
Tue
Fri
Sat
Sun
Mon
Thu
- wrap up & leave home
Discussion TODO
not so controversial
- [DONE] merge control flow into kdevplatform
- [DONE] merge qmake into kdevelop
- [DONE] extra-plugins module: css, execute-script, execute-browser, andreas' custom project manager, ...
- gluon integration
- handle rename/delete of file in editor view
- handle switching branch -> reload open (changed) files
- port mailing list to kde infrastructure
- improve website / wikis / ...
- promotion part
- integrate wiki documentation
controversial
- browser-like tabs
- welcome page
- drag&drop
- merge aliex's thesis work
very controversial
- destroy areas
- chromium-like UI
Hacking TODO
- remove/disable/fix failing unit tests
- fix QWarnings (esp. timer issues etc.)
- Milian: http://bugreports.qt.nokia.com/browse/QTBUG-16558 - fixed in Qt 4.8.0
- go through review requests
- extended cli support (open in existing instance)
- requires extended dbus interface
- krunner integration (session)
Browser-like Tabs TODO
- remove Ctrl-T or bind it to what Ctrl-N does
- Ctrl-N should open new file in a new tab