Re: qtcomponents documentation
On Saturday 17 December 2011, Marco Martin wrote: Hi all, I think we should do a real documentation sprint for the plasma qtcomponents, to have a good api doc for the 4.8 release. I have now merged the branch plasma-components-doc as the documentation was already good (and avoiding conflicts with master) I have to say congratulations to who woked on it, let's complete and make it rock for 4.8 ;) looking at the doodle, the date/time that seems better is thursday 22 at 10:00 am CET (09AM UTC) and go on from there the afternoon too, so there will be people that have to go but then lamarque and daker can come by later, so let's take that date -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Breadcrumbs in Kickoff
On Tuesday, December 20, 2011 00:33:20 4ernov wrote: unclear why you so against to approve such a work. i think it is perfectly fine if you wish to create a modified kickoff and ship it as a separate plasmoid. this is what we've done for a few different plasmoids, including the tasks plasmoid (and that's ended up turning out rather well for everyone i think :). i do not want plasma desktop to become a collection of everyone's pet features with a thousand configuration tweaks. the back button was not serving everyone well (we got lots of feedback on it ...) and the breadcrumbs are more consistent with what we see elsewhere (file dialog, dolphin, ..) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Kickoff-QML and classic launcher
Hi all, in case this mail appears twice, please excuse. It seems to me like Akonadi ate my mail :-( given that master is going to open soon, I have been thinking about merging the Kickoff-QML branch to master. Most is done only minor parts are missing except the classic menu. Due to the fact that I had to fix the models first I doubt that the classic menu would compile or work. Now you can imagine that I am not really interested in working on it :-) So a few questions to discuss: * Do I have to provide a working classic menu in order to merge the Kickoff branch? If yes, would a QML port be OK or should I fix the C++ code? * Would it be acceptable to have classic menu broken for some time and do the porting later on? * Would it be acceptable to drop the classic menu completely? This would be more consistent with the general concept of having only one applet per area. Optionally the classic menu could be re-added in Plasma-Addons just like Lancelot. My personal favorite is option 3. What do you think? Cheers Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Breadcrumbs in Kickoff
On 20 дек 2011 11:20:23 Aaron J. Seigo wrote: On Tuesday, December 20, 2011 00:33:20 4ernov wrote: unclear why you so against to approve such a work. i think it is perfectly fine if you wish to create a modified kickoff and ship it as a separate plasmoid. this is what we've done for a few different plasmoids, including the tasks plasmoid (and that's ended up turning out rather well for everyone i think :). No, I mean a contribution with config option or something which can return the Back button. I don't think it's perfect idea to fork kickoff because of one function. i do not want plasma desktop to become a collection of everyone's pet features with a thousand configuration tweaks. Exactly. I agree. But as I remember Martin said that we're discussing only config option and reverting to Back button wasn't an option. I think, nobody also wants Plasma desktop to become a collection of wrong decisions, it's even worse. the back button was not serving everyone well (we got lots of feedback on it ...) I didn't say the Back button was ideal. I think a serious usability research should be performed to find the better solution instead of it. And I can't believe any usability expert could suggest breadcrumbs instead of back button as it's just against the basic things one could learn in usability. and the breadcrumbs are more consistent with what we see elsewhere (file dialog, dolphin, ..) That's right. But there're areas (URL string in browser, date and time string in clock applications, rich text editors etc.) where breadcrumbs look more natural but in spite of it it's not used there. Yes, it will probably make something more consistent but will spoil things in many other areas. I don't think consistency is the key factor here. As to me, my solution is: keep both Back button and breadcrumbs. Here's my arguments: - no config and no tweaks required - users can use both ways - no redundancy or duplication as it's just two methods to reach the same result (there're thousands of examples with such implementations, e.g. same features in main menu, toolbar and context menus in one application) - minimum of code required I don't mean that it's a bad code or something and I respect all the efforts of Martin and whole Plasma team to improve navigation, to find some better decisions. But I think such a things should be discussed especially given a significant number of critical comments. If something was wrong I don't see any problems to solve it. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Skrooge plasma dashboard: stuck with QML
Hi Guys, I know you're in the process of updating the QML. Maybe some of my questions will get their answers from there, or maybe they will help identifying where some additional clarifications might be needed. My code is in: https://projects.kde.org/projects/extragear/office/skrooge/repository/show?rev=plasma- dashboard (in the plasma-dashboard branch) The QML code that is the subject of this mail is in plugins/applet/advice-qml I'm doing this in 4.7.90 (unstable archlinux packages) 1) widget size: --- even though I specified the widget size, if the dashboard contains only QML widgets, they appear with a very small width: http://wstaw.org/m/2011/12/20/plasma-desktopVB1577.png http://wstaw.org/m/2011/12/20/plasma-desktopav1577.png As soon as I add a C++ widget, the size is correctly computed: http://wstaw.org/m/2011/12/20/plasma-desktopbb1577.png If I remove the C++ widget, the size gets wrong again. Any idea what could be the cause for this ? 2) PlasmaComponents.Label font size: -- For some reason, the font size there is significantly larger than in basic QML Text component. Any idea why ? 3) ListView highlight: --- With the aforementionned code, I can't seem to get the expected behaviour on highlighting items in the list. Any idea why ? Thanks in advance for any help, and keep up the good work. I'm already hooked at QML :) Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: folderview broken
On Tuesday 20 Dec 2011 9:06:59 PM Zé wrote: 2011/12/20 Shantanu Tushar Jha shaan...@gmail.com: Hi, For the debug messages Sujith is asking, can you try the following and pastebin/attach the output, 1. run kdebugdialog and check all the checkboxes and press ok 2. run plasmoidviewer folderview and wait for sometime after folderview is shown. 3. copy the output on the terminal and send it I can not do it anymore since i have reverted that commit, like i have already stated, but if you doubt of what i say, im sure you will have more news about this from kde users in a near time. I didn't say that I am doubting what you're saying, I just want to find the reason why its not working. Its usually very helpful if people running kde from sources help in debugging :) Thanks It would be more apropriated if you could answer following the thread and not answer in the top breaking the order. This can help you - http://matt.might.net/articles/how-to-email/ Thanks :) On Mon, Dec 19, 2011 at 9:25 AM, sujith h sujit...@gmail.com wrote: On Mon, Dec 19, 2011 at 3:04 AM, Zé mmode...@gmail.com wrote: 2011/12/18 Zé mmode...@gmail.com: 2011/12/18 sujith h sujit...@gmail.com: On Sun, Dec 18, 2011 at 3:44 PM, Zé mmode...@gmail.com wrote: 2011/12/18 sujith h sujit...@gmail.com: Hi, Can you please share the debug message? For me its working fine. Sujith H On Sun, Dec 18, 2011 at 7:02 AM, Zé mmode...@gmail.com wrote: The commit you did in kde-baseapps (SHA c4baf7897e541bc070d1425583370830d3ffa414) as completly broken icons in screen. Now doesnt appear any icons in screen using folderview... -- Salutem, Zé What debug message??? Create a new user and check it. Sorry I cannot reproduce this problem. I had tested it by creating a new user. For me it works fine. Can you please let me know what was the method followed, so that I can help you. Sujith H -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé I had to revert your commit and rebuild kde-baseapps to have back icons available on screen. So please do the necessary steps to put the code you submited built and running. Some times we think we have done the necessary but in the end theres some missing, this has happened with me, so please update your git master, build it and isntall it. We are only humans :) -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé Just to remind you that i have build with and without your comit and i have created a new user in both cases. Are you trying to access remote site or local host? I had not done anything for local host. If you are trying to access the remote host, can you please share the URL for that, so that I can also try. -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Breadcrumbs in Kickoff
On 01/-10/-28163 11:59 AM, Alexey Chernov wrote: As to me, my solution is: keep both Back button and breadcrumbs. Here's my arguments: - no config and no tweaks required - users can use both ways - no redundancy or duplication as it's just two methods to reach the same result (there're thousands of examples with such implementations, e.g. same features in main menu, toolbar and context menus in one application) - minimum of code required I don't mean that it's a bad code or something and I respect all the efforts of Martin and whole Plasma team to improve navigation, to find some better decisions. But I think such a things should be discussed especially given a significant number of critical comments. If something was wrong I don't see any problems to solve it. Alexey, you have two of KDE's smartest people (Aaron and Martin) in agreement that we probably want to provide this via the Back Button on the Mouse. (Less new code, less confusion, less maintenance headache.) That's the option on the table, with tentative +1 assessments. Would that alternative be INADEQUATE, in a REALLY IMPORTANT way? If it's got a defect, I really don't see it. Please advise. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Skrooge plasma dashboard: stuck with QML
On Wed, Dec 21, 2011 at 4:55 AM, Guillaume DE BURE guillaume.deb...@gmail.com wrote: I'm doing this in 4.7.90 (unstable archlinux packages) You should probably move to KDE compiled from git source. 1) widget size: --- even though I specified the widget size, if the dashboard contains only QML widgets, they appear with a very small width: http://wstaw.org/m/2011/12/20/plasma-desktopVB1577.png http://wstaw.org/m/2011/12/20/plasma-desktopav1577.png As soon as I add a C++ widget, the size is correctly computed: http://wstaw.org/m/2011/12/20/plasma-desktopbb1577.png Try adding X-Plasma-DefaultSize=600,600 in metadata.desktop and instead of width/height: 600 in main.qml, do the following: property int minimumWidth: 600 property int minimumHeight: 600 This might produce expected behavior. 2) PlasmaComponents.Label font size: -- For some reason, the font size there is significantly larger than in basic QML Text component. Any idea why ? You can simply use Text component wherever you just want to display text. 3) ListView highlight: --- With the aforementionned code, I can't seem to get the expected behaviour on highlighting items in the list. Any idea why ? The highlight follows the currentItem. So you need to add a MouseArea in your delegate with hoverEnabled: true and onEntered: list.currentIndex = index This will make the hovered item your list's current item and the highlight will follow it. Cheers, Viranch ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: folderview broken
Hi, On Wed, Dec 21, 2011 at 10:46 AM, Zé mmode...@gmail.com wrote: 2011/12/21 Shantanu Tushar jhahon...@gmail.com: On Tuesday 20 Dec 2011 9:06:59 PM Zé wrote: 2011/12/20 Shantanu Tushar Jha shaan...@gmail.com: Hi, For the debug messages Sujith is asking, can you try the following and pastebin/attach the output, 1. run kdebugdialog and check all the checkboxes and press ok 2. run plasmoidviewer folderview and wait for sometime after folderview is shown. 3. copy the output on the terminal and send it I can not do it anymore since i have reverted that commit, like i have already stated, but if you doubt of what i say, im sure you will have more news about this from kde users in a near time. I didn't say that I am doubting what you're saying, I just want to find the reason why its not working. Its usually very helpful if people running kde from sources help in debugging :) Currently im building qt-4.8.0 official release and i have my hands in several other projects, so i cant go back building with your commit to show you the output. Im sure will appear some one complaining soon. But i dont understand why you cant do it yourself. Obviously I've tried it myself, and so have few more people, and it works fine. I wouldn't bother you otherwise. Anyway, I understand that you are busy right now, it will be nice if you can do it whenever you become free :) Thanks Currently im not subscribed to plasma devel ML, so i cant have it in CC. I have also reported this problem to Aseigo, maybe he could also help on this matter. No problem, I am just keeping the list in sync :) It would be more apropriated if you could answer following the thread and not answer in the top breaking the order. This can help you - http://matt.might.net/articles/how-to-email/ Thanks :) On Mon, Dec 19, 2011 at 9:25 AM, sujith h sujit...@gmail.com wrote: On Mon, Dec 19, 2011 at 3:04 AM, Zé mmode...@gmail.com wrote: 2011/12/18 Zé mmode...@gmail.com: 2011/12/18 sujith h sujit...@gmail.com: On Sun, Dec 18, 2011 at 3:44 PM, Zé mmode...@gmail.com wrote: 2011/12/18 sujith h sujit...@gmail.com: Hi, Can you please share the debug message? For me its working fine. Sujith H On Sun, Dec 18, 2011 at 7:02 AM, Zé mmode...@gmail.com wrote: The commit you did in kde-baseapps (SHA c4baf7897e541bc070d1425583370830d3ffa414) as completly broken icons in screen. Now doesnt appear any icons in screen using folderview... -- Salutem, Zé What debug message??? Create a new user and check it. Sorry I cannot reproduce this problem. I had tested it by creating a new user. For me it works fine. Can you please let me know what was the method followed, so that I can help you. Sujith H -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé I had to revert your commit and rebuild kde-baseapps to have back icons available on screen. So please do the necessary steps to put the code you submited built and running. Some times we think we have done the necessary but in the end theres some missing, this has happened with me, so please update your git master, build it and isntall it. We are only humans :) -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé Just to remind you that i have build with and without your comit and i have created a new user in both cases. Are you trying to access remote site or local host? I had not done anything for local host. If you are trying to access the remote host, can you please share the URL for that, so that I can also try. -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com -- Salutem, Zé ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: folderview broken
On Wed, Dec 21, 2011 at 10:46 AM, Zé mmode...@gmail.com wrote: 2011/12/21 Shantanu Tushar jhahon...@gmail.com: On Tuesday 20 Dec 2011 9:06:59 PM Zé wrote: 2011/12/20 Shantanu Tushar Jha shaan...@gmail.com: Hi, For the debug messages Sujith is asking, can you try the following and pastebin/attach the output, 1. run kdebugdialog and check all the checkboxes and press ok 2. run plasmoidviewer folderview and wait for sometime after folderview is shown. 3. copy the output on the terminal and send it I can not do it anymore since i have reverted that commit, like i have already stated, but if you doubt of what i say, im sure you will have more news about this from kde users in a near time. I didn't say that I am doubting what you're saying, I just want to find the reason why its not working. Its usually very helpful if people running kde from sources help in debugging :) Currently im building qt-4.8.0 official release and i have my hands in several other projects, so i cant go back building with your commit to show you the output. Im sure will appear some one complaining soon. But i dont understand why you cant do it yourself. Sorry I had tried it and I was not able to reproduce this issue on my system. If I could have reproduced it I would have solved it :) Currently im not subscribed to plasma devel ML, so i cant have it in CC. I have also reported this problem to Aseigo, maybe he could also help on this matter. It would be more apropriated if you could answer following the thread and not answer in the top breaking the order. This can help you - http://matt.might.net/articles/how-to-email/ Thanks :) On Mon, Dec 19, 2011 at 9:25 AM, sujith h sujit...@gmail.com wrote: On Mon, Dec 19, 2011 at 3:04 AM, Zé mmode...@gmail.com wrote: 2011/12/18 Zé mmode...@gmail.com: 2011/12/18 sujith h sujit...@gmail.com: On Sun, Dec 18, 2011 at 3:44 PM, Zé mmode...@gmail.com wrote: 2011/12/18 sujith h sujit...@gmail.com: Hi, Can you please share the debug message? For me its working fine. Sujith H On Sun, Dec 18, 2011 at 7:02 AM, Zé mmode...@gmail.com wrote: The commit you did in kde-baseapps (SHA c4baf7897e541bc070d1425583370830d3ffa414) as completly broken icons in screen. Now doesnt appear any icons in screen using folderview... -- Salutem, Zé What debug message??? Create a new user and check it. Sorry I cannot reproduce this problem. I had tested it by creating a new user. For me it works fine. Can you please let me know what was the method followed, so that I can help you. Sujith H -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé I had to revert your commit and rebuild kde-baseapps to have back icons available on screen. So please do the necessary steps to put the code you submited built and running. Some times we think we have done the necessary but in the end theres some missing, this has happened with me, so please update your git master, build it and isntall it. We are only humans :) -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- Salutem, Zé Just to remind you that i have build with and without your comit and i have created a new user in both cases. Are you trying to access remote site or local host? I had not done anything for local host. If you are trying to access the remote host, can you please share the URL for that, so that I can also try. -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel -- Shantanu Tushar(UTC +0530) http://www.shantanutushar.com -- Salutem, Zé -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: qtcomponents documentation
Should i convert the doc into mediawiki style? -- Giorgos Tsiapaliwkas (terietor) KDE Developer terietor.gr ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Breadcrumbs in Kickoff
On Wednesday 21 December 2011 00:51:45 Alexey Chernov wrote: On 20 дек 2011 11:20:23 Aaron J. Seigo wrote: On Tuesday, December 20, 2011 00:33:20 4ernov wrote: unclear why you so against to approve such a work. i think it is perfectly fine if you wish to create a modified kickoff and ship it as a separate plasmoid. this is what we've done for a few different plasmoids, including the tasks plasmoid (and that's ended up turning out rather well for everyone i think :). No, I mean a contribution with config option or something which can return the Back button. I don't think it's perfect idea to fork kickoff because of one function. but that's the point. Now in a month someone else wants something completely different. Then it's still not the perfect idea to fork Kickoff because of one function. A month later the next config option creeps in and another one and another one. And a nice small applet becaume a Frankenstein. Either you decide that no non-valid config options go in or you have discussions about it each other day. i do not want plasma desktop to become a collection of everyone's pet features with a thousand configuration tweaks. Exactly. I agree. But as I remember Martin said that we're discussing only config option and reverting to Back button wasn't an option. I think, nobody also wants Plasma desktop to become a collection of wrong decisions, it's even worse. Yes, I said we can discuss the need of a config option. For that we require good arguments why such an option is required. That has not yet presented here. Neither we can do it, nor but it was there is a good argument. the back button was not serving everyone well (we got lots of feedback on it ...) I didn't say the Back button was ideal. I think a serious usability research should be performed to find the better solution instead of it. And I can't believe any usability expert could suggest breadcrumbs instead of back button as it's just against the basic things one could learn in usability. So you are a usability expert? I didn't know that. I am no usability expert, because of that I do not argue with usability. (Just look through my mails you will nowhere find that I say the breadcrumbs are better and the back button is worse from a usability point of view). If you have not studied usability, I would appreciate that you don't pull such arguments. It a serious field of research and we should not do like we know better. As to me, my solution is: keep both Back button and breadcrumbs. Here's my arguments: - no config and no tweaks required - users can use both ways - no redundancy or duplication as it's just two methods to reach the same result (there're thousands of examples with such implementations, e.g. same features in main menu, toolbar and context menus in one application) I'm sorry but all your examples are bad ones. Let's consider them: * main menu is normally dropped. Finding an option there is a complicated task. See for example Unity which basically removed the menu completely. * context menu you have to explicitly trigger, you have to know that the functionality is there. With Kickoff we are talking about two always visible and directly reachable UI elements. This is something completely different. We also have to consider how close these UI elements are. Given the new QML design they would border each other. That is one of my main concerns that it visually clutters the view, makes them inconsistent (only one of four views uses the back button) and confusing. I don't see why the average user would need this always there. To me this looks like you realized that you don't get your config option and now you try to adjust your argument ;-) - minimum of code required this is just not true. This would significantly increase the code size. See my other mail on that subject. As I wrote I expect an increase of code size for one QML file by at least 10 %. I don't mean that it's a bad code or something and I respect all the efforts of Martin and whole Plasma team to improve navigation, to find some better decisions. But I think such a things should be discussed especially given a significant number of critical comments. If something was wrong I don't see any problems to solve it. Which significant number of critical comments? How many users have commented here in the thread and reported bugs? 5? 10? 20? We are talking about a feature which will be used by millions of users. If we get to a thousand users complaining we can start to think about significant numbers. A small anectode: we had a recent event in the state where I live. In our state capital the German government and the Deutsche Bahn want to build a new station. It will take many years to build it and will cost several billions €. Over the last year there were many demonstrations in the captial with thousands of people protesting against the station. Since the last election the state is governed by a prime minister of the
