Re: Moving KDE Connect out of playground

2015-09-15 Thread Nicolás Alvarez
2015-09-15 12:01 GMT-03:00 Albert Vaca : > To put an example of a similar case, Windows 10 completely removed the "Help > Center" and now it sends you online to the MS site if you need help. "Windows 8 is truly the first Windows version made for the Internet era... I had to

Re: Moving KDE Connect out of playground

2015-09-15 Thread Jeremy Whiting
"I've let it there as a testimony of the dark side of wikis." <-- me adds that to his quote book. As a brand new user of KDE Connect if we had a user manual I would look in it to see why for some reason the connection between KDE Connect and my android phone who's name is "Jeremy's LG Phone" is

Re: Adding further modules to api.kde.org

2015-09-15 Thread Martin Graesslin
Hi Allen, is there anything I can do to help get the documentation updated? I want to include KWayland in inqlude (patch is prepared) and I find a little bit embarrassing for KDE to have the api docs to point to http://kde.martin-graesslin.com/kwayland/index.html Cheers Martin On Thursday,

Re: RFC: Enabling -DECM_ENABLE_SANITIZERS='address' in jenkins

2015-09-15 Thread André Wöbbeking
On Thursday 10 September 2015 22:36:10 Albert Astals Cid wrote: > We have this nice ECM module that gives us the option to compile with ASAN. > > I'd like to propose that we enable it by default in jenkins. > > This way we get all the autotests run with ASAN and potentially catch more >

Review Request 125236: FindQt4: Use CHECK_CXX_SYMBOL_EXISTS instead of CHECK_C_SYMBOL_EXISTS.

2015-09-15 Thread Raphael Kubo da Costa
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125236/ --- Review request for Build System and kdelibs. Repository: kdelibs

Re: Moving KDE Connect out of playground

2015-09-15 Thread Jeremy Whiting
I see your points and actually agree. I'm completely ok with having help go to some online documentation on userbase. I see the requirement for offline/included help documentation to be going down lately as you say and completely moot for kdeconnect since it technically requires an internet

Re: Moving KDE Connect out of playground

2015-09-15 Thread Luigi Toscano
On Tuesday 15 of September 2015 08:01:44 Albert Vaca wrote: > I don't think that having "descriptive documentation" (more about this > later) is that important nowadays, and IMO users will likely google for > help way before they use the help button when they find issues. Since most > people I

Re: Moving KDE Connect out of playground

2015-09-15 Thread Albert Vaca
I don't think that having "descriptive documentation" (more about this later) is that important nowadays, and IMO users will likely google for help way before they use the help button when they find issues. Since most people I talked to in Randa agreed with me on this, I'm a bit surprised to find

Re: SIC/BIC in Frameworks (NOT)

2015-09-15 Thread Ben Cooksley
On Tue, Sep 15, 2015 at 12:42 AM, Scarlett Clark wrote: > I guess I forgot to turn back on clean workspace? We were debugging qt5.5. > I > Am so sorry, been traveling home. No worries, it's all fixed now :) > Scarlett Cheers, Ben > > On Sep 14, 2015 12:59 PM,

Re: Moving KDE Connect out of playground

2015-09-15 Thread Luigi Toscano
On Tuesday 15 of September 2015 09:06:40 Jeremy Whiting wrote: > I see your points and actually agree. I'm completely ok with having > help go to some online documentation on userbase. I see the > requirement for offline/included help documentation to be going down > lately as you say and

Re: Moving KDE Connect out of playground

2015-09-15 Thread Albert Astals Cid
El Dimarts, 15 de setembre de 2015, a les 08:01:44, Albert Vaca va escriure: > I don't think that having "descriptive documentation" (more about this > later) is that important nowadays, and IMO users will likely google for > help way before they use the help button when they find issues. Since

Re: Moving KDE Connect out of playground

2015-09-15 Thread Christoph Feck
On Tuesday 15 September 2015 02:13:17 Aleix Pol wrote: > Regarding the documentation, we discussed it briefly during the > sprint and we have the feeling that the documentation for such a > project would look more like a simple placeholder or something > easily outdated than anything. Furthermore,