Re: plasma-framework in kdereview
Hi Everyone, Indeed, there was an intention to use some plasma components in Skrooge, but it never materialized in any official release. Today, this is mostly abandoned code, to my disappointment, but I never committed myself enough on finishing this part... As far as Skrooge is concerned, you may change anything you want in libplasma for kf5, we will either adapt, or consider a totally different approach, using QML. Guillaume Le vendredi 25 avril 2014, 19:49:05 Marco Martin a écrit : > On Friday 25 April 2014 19:16:43 Kevin Ottens wrote: > > > I think these statements show you totally ignore the history behind > > libplasma or how applications can use it... They (at least Amarok, not 100% > > sure for Skrooge) benefit from the component model used in libplasma: > > packages, dataengines, plugins. > > Skrooge used a kpart (that i want to get eventually ported) that basically > loaded a corona, so having an area with widgets is pretty easy > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Get me started on solving bug 314831
Hi all, I am hit by bug https://bugs.kde.org/show_bug.cgi?id=314831, and it seems to be specific to french translation. I'd like to make an attempt at solving it. My first idea would be to look at some translation files, maybe there will be something obvious, but unsure where to start. Can someone give me pointers to where I can find the .po for the notification plasmoid ? Thanks :) Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Accessing a C++ dataengine from a QML plasmoid
Le lundi 4 février 2013 21:58:31 vous avez écrit :
> Le lundi 4 février 2013 15:56:00 Michail Vourlakos a écrit :
> > Στις 30/01/2013 11:38 μμ, ο/η Guillaume DE BURE έγραψε:
> > > Le mercredi 30 janvier 2013 22:20:13 Marco Martin a Γ©crit :
> > >> On Wednesday 30 January 2013, Guillaume DE BURE wrote:
> > >>> However, I am not completely clear how to access it in QML. Userbase
> > >>> seems
> > >>> to say it should be possible:
> > >>> http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataModel
> > >>>
> > >>> So I made an attempt that looks like this, but that does not work:
> > >>> https://projects.kde.org/projects/extragear/office/skrooge/repository/revis
> > >>> ions/plasma-dashboard/entry/plugins/applet/account-qml/contents/ui/main.qml
> > >>>
> > >>> Can anybody help me ? Thanks in advance :)
> > >> banksSource.data["Accounts"] is directly the data
> > >>
> > >> for the model:
> > >>
> > >> PlasmaCore.DataModel {
> > >> dataSource: banksSource
> > >> sourceFilter: "Accounts"
> > >> }
> > >>
> > >>
> > > Thanks Marco... However, not sure I fully understood you. Did you mean I
> > > should write it like this :
> > I think you should change it to:
> >
> > Item {
> > id: mainWidget
> >
> > // Connect to our dataengine
> > PlasmaCore.DataSource {
> > id: banksSource
> > engine: "skgdataengine"
> > interval: 0
> > connectedSources: ["Accounts"]
> > }
> >
> > // Use a modelProxy for easy filtering / sorting
> > PlasmaCore.SortFilterModel {
> > id: banksModel
> > sourceModel: PlasmaCore.DataModel {
> > dataSource: banksSource
> > /// sourceFilter: "Accounts" // I think this is not needed
> > because you use only one source
> > }
> > }
> >
> > // Put all accounts in a Column
> > ListView {
> > anchors.fill: parent
> > model: banksModel
> >
> > delegate: Text {
> > text: model["type"]
> > }
> > }
> > }
>
> Thanks for the suggestion, Michail, but it doesn't change anything... I'm
> starting to think QML doesn't like me ;(
>
> Or maybe the fact that all this is running contained in Skrooge breaks the
> whole dataengine / plasmoid magic in QML ?
>
>
Marco saved me on IRC, I was missing the keyRoleFilter: ".*" in the DataModel.
I somehow assumed that leaving it empty was equivalent to this, but it was not
the case.
Thanks :)
--
Skrooge, a free, Open Source, personal finances software for linux, Mac OS,
Windows
http://skrooge.org
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Accessing a C++ dataengine from a QML plasmoid
Le lundi 4 février 2013 15:56:00 Michail Vourlakos a écrit :
> Στις 30/01/2013 11:38 μμ, ο/η Guillaume DE BURE έγραψε:
> > Le mercredi 30 janvier 2013 22:20:13 Marco Martin a Γ©crit :
> >> On Wednesday 30 January 2013, Guillaume DE BURE wrote:
> >>> However, I am not completely clear how to access it in QML. Userbase seems
> >>> to say it should be possible:
> >>> http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataModel
> >>>
> >>> So I made an attempt that looks like this, but that does not work:
> >>> https://projects.kde.org/projects/extragear/office/skrooge/repository/revis
> >>> ions/plasma-dashboard/entry/plugins/applet/account-qml/contents/ui/main.qml
> >>>
> >>> Can anybody help me ? Thanks in advance :)
> >> banksSource.data["Accounts"] is directly the data
> >>
> >> for the model:
> >>
> >> PlasmaCore.DataModel {
> >> dataSource: banksSource
> >> sourceFilter: "Accounts"
> >> }
> >>
> >>
> > Thanks Marco... However, not sure I fully understood you. Did you mean I
> > should write it like this :
> I think you should change it to:
>
> Item {
> id: mainWidget
>
> // Connect to our dataengine
> PlasmaCore.DataSource {
> id: banksSource
> engine: "skgdataengine"
> interval: 0
> connectedSources: ["Accounts"]
> }
>
> // Use a modelProxy for easy filtering / sorting
> PlasmaCore.SortFilterModel {
> id: banksModel
> sourceModel: PlasmaCore.DataModel {
> dataSource: banksSource
> /// sourceFilter: "Accounts" // I think this is not needed
> because you use only one source
> }
> }
>
> // Put all accounts in a Column
> ListView {
> anchors.fill: parent
> model: banksModel
>
> delegate: Text {
> text: model["type"]
> }
> }
> }
Thanks for the suggestion, Michail, but it doesn't change anything... I'm
starting to think QML doesn't like me ;(
Or maybe the fact that all this is running contained in Skrooge breaks the
whole dataengine / plasmoid magic in QML ?
--
Skrooge, a free, Open Source, personal finances software for linux, Mac OS,
Windows
http://skrooge.org
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Accessing a C++ dataengine from a QML plasmoid
I am really thinking that something in my dataengine prevents my QML plasmoid
from accessing the data. For example, my C++ plasmoid correctly displays the 3
lines it is supposed to, when the QML version does not display anything.
I tried to dig more the issue, and discovered that banksModel.count returns 1,
instead of 3... Is there anything special that needs to be done in a dataengine
in order that a QML plasmoid can access its data ?
Le mercredi 30 janvier 2013 22:38:15 Guillaume DE BURE a écrit :
> Le mercredi 30 janvier 2013 22:20:13 Marco Martin a écrit :
> > On Wednesday 30 January 2013, Guillaume DE BURE wrote:
> > > However, I am not completely clear how to access it in QML. Userbase seems
> > > to say it should be possible:
> > > http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataModel
> > >
> > > So I made an attempt that looks like this, but that does not work:
> > > https://projects.kde.org/projects/extragear/office/skrooge/repository/revis
> > > ions/plasma-dashboard/entry/plugins/applet/account-qml/contents/ui/main.qml
> > >
> > > Can anybody help me ? Thanks in advance :)
> >
> > banksSource.data["Accounts"] is directly the data
> >
> > for the model:
> >
> > PlasmaCore.DataModel {
> > dataSource: banksSource
> > sourceFilter: "Accounts"
> > }
> >
> >
>
> Thanks Marco... However, not sure I fully understood you. Did you mean I
> should write it like this :
>
>
> Item {
> id: mainWidget
>
> // Connect to our dataengine
> PlasmaCore.DataSource {
> id: banksSource
> engine: "skgdataengine"
> interval: 0
> connectedSources: ["Accounts"]
> }
>
> // Use a modelProxy for easy filtering / sorting
> PlasmaCore.SortFilterModel {
> id: banksModel
> sourceModel: PlasmaCore.DataModel {
> dataSource: banksSource
> sourceFilter: "Accounts"
> }
> }
>
> // Put all accounts in a Column
> ListView {
> anchors.fill: parent
> model: banksModel
>
> delegate: Text {
> text: banksSource.data["Accounts"]["type"]
> }
> }
> }
>
> If yes it doesn't seem to work either... Or am I missing something obvious ?
>
>
>
>
--
Skrooge, a free, Open Source, personal finances software for linux, Mac OS,
Windows
http://skrooge.org
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Accessing a C++ dataengine from a QML plasmoid
Le mercredi 30 janvier 2013 22:20:13 Marco Martin a écrit :
> On Wednesday 30 January 2013, Guillaume DE BURE wrote:
> > However, I am not completely clear how to access it in QML. Userbase seems
> > to say it should be possible:
> > http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataModel
> >
> > So I made an attempt that looks like this, but that does not work:
> > https://projects.kde.org/projects/extragear/office/skrooge/repository/revis
> > ions/plasma-dashboard/entry/plugins/applet/account-qml/contents/ui/main.qml
> >
> > Can anybody help me ? Thanks in advance :)
>
> banksSource.data["Accounts"] is directly the data
>
> for the model:
>
> PlasmaCore.DataModel {
> dataSource: banksSource
> sourceFilter: "Accounts"
> }
>
>
Thanks Marco... However, not sure I fully understood you. Did you mean I should
write it like this :
Item {
id: mainWidget
// Connect to our dataengine
PlasmaCore.DataSource {
id: banksSource
engine: "skgdataengine"
interval: 0
connectedSources: ["Accounts"]
}
// Use a modelProxy for easy filtering / sorting
PlasmaCore.SortFilterModel {
id: banksModel
sourceModel: PlasmaCore.DataModel {
dataSource: banksSource
sourceFilter: "Accounts"
}
}
// Put all accounts in a Column
ListView {
anchors.fill: parent
model: banksModel
delegate: Text {
text: banksSource.data["Accounts"]["type"]
}
}
}
If yes it doesn't seem to work either... Or am I missing something obvious ?
--
Skrooge, a free, Open Source, personal finances software for linux, Mac OS,
Windows
http://skrooge.org
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Accessing a C++ dataengine from a QML plasmoid
Hi all, Reading the documentation on userbase did not really help me on understanding what is going wrong on what I'm trying to achieve, maybe one of you will be able to help. Some context: For years, I've been trying to use plasma inside Skrooge to manage our dashboard. Long story short, I've somehow managed to get something ruunning in C++, but would like to move to QML, as this is clearly the way to go. The problem: I have a dataengine running inside Skrooge, that fetches data from the .skg file (which is in fact, an SQLite file). This dataengine is written in C++, and the relevant code can be found there: https://projects.kde.org/projects/extragear/office/skrooge/repository/revisions/plasma-dashboard/entry/skg_dataengine/skgdataengine.cpp#L97 As you can see this dataengine contains a source "Accounts", for which keys are an account name, and values are a QHash containing other account properties. Accessing this data from a C++ plasmoid works well (code: https://projects.kde.org/projects/extragear/office/skrooge/repository/revisions/plasma-dashboard/entry/plugins/applet/account/accountskroogoid.cpp) However, I am not completely clear how to access it in QML. Userbase seems to say it should be possible: http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataModel So I made an attempt that looks like this, but that does not work: https://projects.kde.org/projects/extragear/office/skrooge/repository/revisions/plasma-dashboard/entry/plugins/applet/account-qml/contents/ui/main.qml Can anybody help me ? Thanks in advance :) Guillaume -- Skrooge, a free, Open Source, personal finances software for linux, Mac OS, Windows http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Re: Re: Review Request: Change activity by rolling the mouse wheel over the showActivityManager widget.
Le mardi 27 décembre 2011 22:09:33 Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= a écrit : > On Tuesday 27 December 2011 21:49:24 Guillaume DE BURE wrote: > > I use the keyboard shortcut (meta + tab) quite often. However I remember > > once someone (maybe, marco ?) proposed an "exposé like" effect, with > > activities as rows, and desktop as columns. That could be extremely useful, > > especially for dragging windows between desktop / activities. Does that > > still sound like a good idea ? Would it be difficult to do ? > There is one problem with that: when an activity is closed we do not know > which windows are there. If an activity is suspended we most likely due not > have a pixmap for this window as the driver discarded it for the long time > unmapped window. So unless someone has a genious idea how to get thumbnails of > non existing windows, it will be difficult to implement :-) Thought this was just relevant for running activities... But maybe you could start activities from there also ? No sure you would need preview for non running activities, that might just confuse the user, no ? > > (The genious idea might be as simple as storing screenshots from the window > when it got closed, activity switched, whatever. 4.9 will hopefully see nice > QML bindings in KWin, so that might be implementable. Help welcome) > > Cheers > Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Review Request: Change activity by rolling the mouse wheel over the showActivityManager widget.
Le mardi 27 décembre 2011 15:58:31 Sebastian =?ISO-8859-1?Q?K=FCgler?= a écrit : > On Tuesday, December 27, 2011 14:11:34 Marco Martin wrote: > > On Tuesday 27 December 2011, Simone Gaiarin wrote: > > > To fix the two problem it is just necessary to add a configuration > > > dialog to the plasmoid in a such way that the user must intentionally > > > enable this feature before use it. What do you think about this > > > solution? I'll work on it. > > > > no, adding a configuration option for every potentially problematic feature > > is a too easy shortcut that has been done too much in the past, and is a > > thing we are finally manage to get out of. > > > > as i said, a solution can be a combination of: > > a) make the activity switching way more intuitive, with animations, an osd > > that says the activity name for an instant, in any case something obvious > > b) only cycle troucg runnung activities (and by default there is only one > > running activity) so if someone never seen them/doesn't use them, doesn't > > get anything with the mouse wheel > > > > this may or may not be intuitive enough, but is important to avoid the > > shortcut of "just throwing another configuration option in" > > One could also make it a hover interface, a bit like opening a QMenu while the > mouse is over that button (but not directly underneath it, as that makes > interaction harder). Or maybe fold the button out to a list of activities when > clicked (a bit like the devicenotifier does it). > > One of the problems I see is that the Activity Switcher still feels a bit too > modal, the switcher is also in my normal usage often at least half a screen > away from my mouse, and in the case of the toolbox, even across the entire > screen. The activity switcher in the panel has a much better position. I use the keyboard shortcut (meta + tab) quite often. However I remember once someone (maybe, marco ?) proposed an "exposé like" effect, with activities as rows, and desktop as columns. That could be extremely useful, especially for dragging windows between desktop / activities. Does that still sound like a good idea ? Would it be difficult to do ? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: Skrooge plasma dashboard: stuck with QML
Le mercredi 21 décembre 2011 10:52:48 Viranch Mehta a écrit : > 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. Probably :) but these unstable packages are a good balance between bleeding edge and easy installation. > > > > > > 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. Yes, that worked, thanks :) Any explanation on why the basic width / height didn't work ? > > > > > > 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. Noted. > > > > > > 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. Thanks for the advice, but I found something else that suits my needs quite well : PlasmaComponents.ListItem :) Since it is already a MouseArea, I guess implementing the highlight there will be easier. > > Cheers, > Viranch Thanks for the help, I pushed the changes if someone is interested. ___ 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: Re: qtcomponents documentation
Le samedi 17 décembre 2011 15:52:33 Daker Fernandes Pinheiro a écrit : > Sounds like a good plan. > > Daker Fernandes Pinheiro > > > > 2011/12/17 Aaron J. Seigo > > > On Saturday, December 17, 2011 18:11:06 Marco Martin wrote: > > > On Saturday 17 December 2011, Aaron J. Seigo wrote: > > > > On Saturday, December 17, 2011 13:39:05 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. > > > > > > > > and ideas / preferences on when and where? > > > > > > well, was actually more thinking about an irc meeting, kinda like > > bugdays, > > > next week (or after the christmasy things if better for people) > > > > perhaps set up a doodle for people to register their preferred times and > > then > > we can promote it on our blogs? Not sure whether I'll be able to help, but for what it's worth, I've started using these components in the skrooge plasma dashboard. So far, I've made progresses using source code, Daker's gallery, and his help on IRC. Having doc on this would be extremely helpful :) > > > > -- > > 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 > > > > ___ > > Plasma-devel mailing list > > Plasma-devel@kde.org > > https://mail.kde.org/mailman/listinfo/plasma-devel > > > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Use Klocale in QML ?
Hi there, Is it possible to use KLocale in QML ? Specifically, I need the formatMoney method. Looked in the doc and in various QML examples, but couldn't find information. Thanks :) Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: QML widget for the Skrooge plasma dashboard
Le lundi 5 décembre 2011 11:25:56 Viranch Mehta a écrit : > Hi, > > On Mon, Dec 5, 2011 at 12:50 AM, Guillaume DE BURE < > guillaume.deb...@gmail.com> wrote: > > > > > file:///.../main.qml:36: Unable to assign [undefined] to QString text > > > > That would indicate that there is no source connected, right ? So what did > > I > > do wrong ? > > > > The DataSource has no property called "count". Hence [undefined]. You can > have a look at the API here: > http://techbase.kde.org/Development/Tutorials/Plasma/QML/API#DataSource Ah yes, thanks, messed up with the dataModel property... I read again this page, so I hope I'm not making other obvious mistakes ! > > Also, since you've already declared connectedSources in the DataSource, you > don't need to redo it inside Component.onCompleted ;) Yes, that was duplicated as a desperate attempt at getting some data from the dataengine :) I think I am now connected to my dataengine, let's see if I can manage to loop through its data ;) > > Cheers, > Viranch Thanks for the help, Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
QML widget for the Skrooge plasma dashboard
Hi there, As I realize that my C++ skills are so very limited, QML appears like the perfect mean to get a nice looking skrooge plasma dashboard. However, I can't seem to get any data from the skrooge dataengine, and I can't figure out what is wrong. This very simple code should display "1" in the widget : http://paste.kde.org/154886/ When adding the widget to the dashboard, I get the following message in the konsole: file:///.../main.qml:36: Unable to assign [undefined] to QString text That would indicate that there is no source connected, right ? So what did I do wrong ? Could it be linked to the fact that the dataengine, plasma dashboard and widgets are all confined inside skrooge (they are not accessible from, for example, the desktop) ? Thanks for any suggestion, Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
plasma dashboards and plasma evolution
Hi list, With the heavy work ongoing in plasma, woud you say it is safer to wait for 4.8 ? I would have liked to pick up again the topic for skrooge, probably using QML, but was wondering if the timing is suitable ? Do you think that the work already done, or that we could start (we develop using latest stable workspace), could be incompatible with whatever ends up in 4.8 ? Or maybe it is a good timing because there might be some evolutions because of plasma dashboards specific needs integrated in 4.8 ? Thanks in advance for your advices :) Guillaume -- Skrooge, a free, Open Source, personal finances software http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: plasma kpart theming
I really like that look :) indeed, it gives the skrooge dashboard a very slick look ! I can't say I'm bothered by the background, as ivan says. Anyway, thanks for this initiative, I'm sure it will help skrooge and other applications create great dashboards ! That being said, we still have a bit of work before having a usable plasma dashboard in skrooge, but we'll get there :) Guillaume Le 23 janv. 2011 23:20, "Marco Martin" a écrit : Hey all, today i hacked a bit around graphical styling of the Plasma kpart, that includes making svgs and fixing the newspaper containment/kpart code where needed (as result newspaper sucks a bit less on the desktop, yay ;))... here it is: http://i.imgur.com/11ySf.png the style (there are still some glitches, is to polish it up) is in playground, the patches are committed just in part. The rationale is that the application dashboard for sure shouldn't look like a desktop at all (that is how would look definitely more dirty and more confising) it rather should look like a document with quick recap info. so yes, in that screenshot it looks like a friggin' website and that's exactly the intent ;) some important points: * the background is the same as the konqueror/kmail/etc "start page", *not* configurable (i think the plasma theme graphic used there would make more sense in those pages as well compared to the current old broken desktop theme) * the plasma theme has at the moment exactly 2 elements and uses where possible native widgets (the backgrounds will also use native colors with the new stylesheet support in Svg) * the newspaper has a big background for all applets (that is the main thing that makes it a "document" rater than "crome": that iage is not available in the default theme, so it will continue to -not- be there in an "usual" case now, apart from feedback from artsy people, my greatest concerns is the usage if soo big pixmaps (the wallpaper and the big newspaper svg background) that makes quite a memory usage, but i think from the final look it's worth it. Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Colour scheme problems after revision 1185467
Le samedi 16 octobre 2010 17:38:02, Marco Martin a écrit : > On Saturday 16 October 2010, Ivan Cukic wrote: > > Hi, > > > > The colour scheme for Plasma::Label is not working anymore - just test with > > any dark theme. > > > > I think the issue is the folloing: > that commit was made because an old Qt bug as fixed, i.e. the propagation of > the palette to proxy widget, > but > this works prfectly propacating the *system* colors > plasma doesn't use the system color scheme, so a manual sync with Thmeme > should still be needed By the way that commit fixed an issue I had where I needed to do label->nativeWidget()->setPalette(palette); This is now fixed, and this works: label->setPalette(palette); Sorry Aaron for not coming back earlier, I had issues with my KDE trunk :/ Guillaume ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Using a dataengine inside Skrooge
Le vendredi 10 septembre 2010 20:58:13, Aaron J. Seigo a écrit : > On Friday, September 10, 2010, Guillaume DE BURE wrote: > > I've implemented very roughly the dataengine, it is able to read data > > through SQL Select instructions, store it using setData. Now, I do I > > access it from widgets ? I mean, are the techbase tutorials still > > applicable in this case ? > > yes. this is a major concept behind DataEngines: although different inside, > the visualizations (e.g. a widget) uses all them the same way. :) Oh cool, that should be quite simple, then :) > > > extragear/office/skgdataengine. Per default, it is disabled in Skrooge's > > extragear/office/skrooge/skgdataengine .. in case anyone else goes looking :) Oops, yes, sorry for the typo :p > > it looksing good... some small suggestions/issue: > > * it's missing a sourceRequestEvent method; in the case of this DataEngine > its > implementation would be very simple: return updateSourceRequest(source); > > * perhaps make "Accounts" and "Incomes & Expenditures" static const QString's > in the .cpp file so that you don't have to worry about typos in the strings > that are duplicated in sources() and updateSourceEvent(const QString &); > common source of errors in DataEngines. Ah thanks :) Correcting right now... -- Skrooge, a personal finances manager for KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Using a dataengine inside Skrooge
Hi, In the frame of developping a plasma dashboard for skrooge, I'm trying to create a dataengine that will provide data to the widgets displayed in this dashboard. The dataengine will extract the data from the skrooge file currently opened (the file is in fact an SQLite file), and present it for widgets to use. I've implemented very roughly the dataengine, it is able to read data through SQL Select instructions, store it using setData. Now, I do I access it from widgets ? I mean, are the techbase tutorials still applicable in this case ? If anyone is interested, the dataengine code is in extragear/office/skgdataengine. Per default, it is disabled in Skrooge's main CMakeLists.txt, so you need to uncomment line 79 in this file to actually compile it. Thanks in advance :) Guillaume -- Skrooge, a personal finances manager for KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Skrooge plasma dashboard
Le mardi 17 août 2010 20:35:43, Aaron J. Seigo a écrit : > On Tuesday, August 17, 2010, Guillaume DE BURE wrote: > > 2) I know you didn't use a dataengine for now. That's OK. But still I'd > > agreed 10% > I guess I still have 90% of convincing to do, then :p -- Skrooge, a personal finances manager for KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Skrooge plasma dashboard
Le lundi 16 août 2010 19:09:05, siddharth sharma a écrit : > hey Guillaume & Stephane > > Please see this screen shot, Guillaume i am able to fetch data into Plasma > applets have a look. now we have 6 applets workin on dashboard :) > > yay :) > > regards > Siddharth > > Hi Siddharth, Nice work :) A few additional comments from my side: 1) Comments ! Please comment your code, this is especially important in a community work where everyone can review / correct / enhance your code. 2) I know you didn't use a dataengine for now. That's OK. But still I'd like you to have a try on it. A dataengine makes it significantly easier to write dashboard widgets, because the person writing the widget doesn't have to know the SQL queries useful for retrieving information. At the moment, the way to collect information that is displayed is coded inside the widget. If we want to provide easier writing of new widgets, dataengine is the way to go. Here is something I would like you to investigate : - How does the dataengine collect data from various skrooge plugins (remember that the dashboard makes no assumption as to which skrooge plugins are available) ? Or is it up to each plugin to push its information to the dataengine ? - Or maybe each skrooge plugin provides its own dataengine ? - Or maybe the dataengine is found at the skgbankmodeler level, and hence knows already all relevant information from the SQLite database 3) Regarding widgets, there are two options I'd like you to evaluate: - We assume that widgets live independantly from plugins, and that they depend only on information found in the dataengine. This is very similar to the desktop plasmoids, they *usually* do not depend on another app being installed, only on some dataengine information - Or each plugin provides its own set of widgets. This makes it less open as far as contribution goes: it won't be easy for new skrooge contributors to discover where to put code for new widgets. This option is how it currently works in the Dashboard1 (the non-plasma dashboard). A bit of design to do for you there... :) CC'ing the plasma folks in case they want to be involved :D Cheers, Guillaume PS: Siddharth, if you're not yet subscribed to the plasma mailing list, please do it *now* ! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Containment view
Le jeudi 01 avril 2010 20:19:30, todd rme a écrit : > As discussed earlier, I am working on the containment viewer > application, which will allow people to test-run containments in a > similar manner to the plasmoid viewer. I am very interested by this, it might prove very useful for Skrooge (See our GSOC idea : http://community.kde.org/GSoC/2010/Ideas#Plasma_Dashboard_in_Skrooge). Where can I find the code ? Thanks, Guillaume -- Skrooge, a personal finances manager powered by KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: gsoc ideas page
Le Mercredi 24 Février 2010 13:06:07, Aaron J. Seigo a écrit : > On February 24, 2010, Chani wrote: > > http://community.kde.org/GSoC/2010/Ideas > > yes, we should try to get a few items up there at least. note that there are > plasma related items for skrooge and kontact there as well. maybe we could > brainstorm a bit here at tokamak as well I can't come to tokamak, and I can't find time for IRC (doing some fixing in the house ;) ), but if I can be of help, mail me or phone me (wound send phone by private email). Siddharth, since you wish to work on that GSOC subject, you may want to talk with Aaron and the Gang of Plasmers* for plasma related discussions. [*] Sounds like a raggae band \o/ !!! -- Skrooge, a personal finances manager powered by KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Help adding plasma in Skrooge
Le Mercredi 10 Février 2010 23:03:22, Aaron J. Seigo a écrit : > > Thanks guys. Created an entry in http://community.kde.org/GSoC/2010/Ideas. > > I wrote it with my previously mentionned limited knowledge, so feel free > > to tear it apart and transform it into a plasma only project if more > > appropriate :D > > i'd love to see Skrooge get a SoC project (i'm quite excited by the advent of > the finance apps) and would be happy to ensure that it gets all the plasma > mentoring help it needs. > > we could co-mentor it, with one Plasma person and one Skrooge person (you?) > mentoring the project from the two sides of it. > > can't wait! i hope a student picks this one up! > > Well, I've already been contacted by a nice guy from India who wants to take on it. Fastest volunteering on earth oO I'm also very excited about all this =D ! Guillaume -- Skrooge, a personal finances manager powered by KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Help adding plasma in Skrooge
Le Mardi 09 Février 2010 22:27:37, Marco Martin a écrit : > On Tuesday 09 February 2010, Aaron J. Seigo wrote: > > On February 9, 2010, Guillaume DE BURE wrote: > > > Or maybe the whole thing could be a GSOC subject ? > > > > it would make a good one, yes, especially if the goal was to create a > > dashboard widget that any application could use easily (kontact may want > > something similar, for instance). that really is the bulk of the work > > outside of writing the "skroogeoids". > +1 Thanks guys. Created an entry in http://community.kde.org/GSoC/2010/Ideas. I wrote it with my previously mentionned limited knowledge, so feel free to tear it apart and transform it into a plasma only project if more appropriate :D Guillaume -- Skrooge, a personal finances manager powered by KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Help adding plasma in Skrooge
Hi everyone, Skrooge currently has a module called Dashboard that contains several widgets showing various information about your financial situation. We implemented that using standard KDE/Qt technologies, but it always looked to me like a plasma view with "skroogoids" inside. We've started a plasma implementation of it (disabled in CMakeLists.txt), but I realize using plasma inside applications is not yet a common feature (Amarok being a very noticable exception), hence not yet documented. After some rather pathetic attempts, I realize I don't have enough experience to do this on my own: I hardly do any coding in Skrooge, and Stephane, the main developper is busy with other subjects. I was wondering if someone here would like to give a hand with this ? This would also be an opportunity to add more tutorials on techbase.kde.org to help other apps getting started should they need plasma. What we need at this stage is (with my understanding of plasma, I may be wrong on some points): * implement a newspaper view that will receive skroogoids. * write a dataengine providing data from the current skrooge file (which is in fact an SQLite database). * create some skroogoids that should be displayed in the newspaper view. Ability to display them on the desktop, without skrooge being opened is something to be discussed (a skrooge file may be password protected using QCA, no idea how this could be handled). * save the dashboard config inside the Skrooge file (currently not supported by plasma, IIRC) Or maybe the whole thing could be a GSOC subject ? Guillaume -- Skrooge, a personal finances manager powered by KDE 4.x http://skrooge.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
