Re: Kickoff-QML and classic launcher

2011-12-22 Thread Nowardev-Team
2011/12/23 Markus Slopianka > On Donnerstag 22 Dezember 2011 12:54:37 Nowardev-Team wrote: > > > > sure i have not problem but how :D right now i have done kde3 panel :P > > Please don't call it that way. It should be referred to as Classic panel > or something like > that to be in line with curr

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Markus Slopianka
On Donnerstag 22 Dezember 2011 12:54:37 Nowardev-Team wrote: > > sure i have not problem but how :D right now i have done kde3 panel :P Please don't call it that way. It should be referred to as Classic panel or something like that to be in line with current wording. ___

Re: Review Request: Reset time format upon user request

2011-12-22 Thread Commit Hook
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103434/#review9163 --- This review has been submitted with commit 68ec5f077e20afe09def

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Aaron J. Seigo
On Thursday, December 22, 2011 12:54:37 Nowardev-Team wrote: > sure i have not problem but how :D right now i have done kde3 panel :P well, what we'd do is set you up with a commit account: http://techbase.kde.org/Contribute/Get_a_Contributor_Account then you could make a subdirectory in

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Nowardev-Team
2011/12/22 Aaron J. Seigo > On Thursday, December 22, 2011 10:58:41 Nowardev-Team wrote: > > layout right now, > > > > svn export --force > > > https://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/pl > > asma/layout-templates/ > > ok. craaaAAAaazy idea time! well, not re

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Aaron J. Seigo
On Thursday, December 22, 2011 10:58:41 Nowardev-Team wrote: > layout right now, > > svn export --force > https://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/pl > asma/layout-templates/ ok. craaaAAAaazy idea time! well, not really, but it sounds more fun that way. ;)

Re: Re: Kickoff-QML and classic launcher

2011-12-22 Thread Martin Gräßlin
On Thursday 22 December 2011 11:32:20 Nowardev-Team wrote: > http://kde-apps.org/content/show.php/Plasma+Panels+Collection+?content=14758 > 9 http://www.youtube.com/watch?v=o_qR-7FQHxc very nice :-) signature.asc Description: This is a digitally signed message part. ___

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Nowardev-Team
2011/12/22 Marco Martin > On Thursday 22 December 2011, Nowardev-Team wrote: > > > : > > :) i did a lots of panels btw.. mm i could try to make classic kde3 > > > > layout right now, > > > > svn export --force > > > https://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/p >

Re: Kickoff-QML and classic launcher

2011-12-22 Thread Marco Martin
On Thursday 22 December 2011, Nowardev-Team wrote: > : > :) i did a lots of panels btw.. mm i could try to make classic kde3 > > layout right now, > > svn export --force > https://plasma-panels-script.googlecode.com/svn/trunk/usr/share/kde4/apps/p > lasma/layout-templates/ cool :D so the op

Re: Re: Kickoff-QML and classic launcher

2011-12-22 Thread Nowardev-Team
2011/12/22 Martin Gräßlin > On Wednesday 21 December 2011 18:25:51 Aaron J. Seigo wrote: > > On Tuesday, December 20, 2011 20:51:32 Martin Graesslin wrote: > > > My personal favorite is option 3. > > > > 3 is a good solution imho ... except that it will break people's > > installations who have k

Re: qtcomponents documentation

2011-12-22 Thread Sebastian Kügler
Hey, On Wednesday, December 21, 2011 12:14:58 Antonis Tsiapaliokas wrote: > what i would like we end up with is auto generated html instead of copying > and paste every single one in techbase ;) > > Hello, i have create an api tool for the components. You can download it > from > here http://quic

Re: Re: Kickoff-QML and classic launcher

2011-12-22 Thread Martin Gräßlin
On Wednesday 21 December 2011 18:25:51 Aaron J. Seigo wrote: > On Tuesday, December 20, 2011 20:51:32 Martin Graesslin wrote: > > My personal favorite is option 3. > > 3 is a good solution imho ... except that it will break people's > installations who have kde-workspace but not kdeplasma-addons i