On Tuesday 28 January 2014, Marco Martin wrote:
> Hi all,
>
> New prototype, completely different direction :) (and that's one i
> actually like)
>
> mart/AppletAttached branch.
If someone wants to test,
mart/AppletAttached in kde-workspace has almost all the applet ported to this
(we should d
On Wednesday 29 January 2014, Marco Martin wrote:
> On Wednesday 29 January 2014, David Edmundson wrote:
> > Parts I don't understand:
> >
> > In compactRepresentationCheck
> > when we are loading the compact version we still call
> > createFullRepresentationItem(). I assumed we wanted to avoid th
On Wednesday 29 January 2014, David Edmundson wrote:
> Parts I don't understand:
>
> In compactRepresentationCheck
> when we are loading the compact version we still call
> createFullRepresentationItem(). I assumed we wanted to avoid that.
yeah, good catch, that has to be corrected.
> It would
On Tue, Jan 28, 2014 at 9:14 PM, Marco Martin wrote:
> Hi all,
>
> New prototype, completely different direction :) (and that's one i actually
> like)
The parts I like:
- a split of AppletInterface acting just as an interface and a new
class handing the QtQuick UI.
- The relevant properties a
On Wednesday, January 29, 2014 10:49:38 Marco Martin wrote:
> On Wednesday 29 January 2014, Sebastian Kügler wrote:
> > On Wednesday, January 29, 2014 00:06:45 Marco Martin wrote:
> > > So, the import of the applet can have its own containment instance (not
> > > even a qml containment, just a dum
On Wednesday 29 January 2014, Sebastian Kügler wrote:
> On Wednesday, January 29, 2014 00:06:45 Marco Martin wrote:
> > So, the import of the applet can have its own containment instance (not
> > even a qml containment, just a dumb containment = new
> > Plasma::Containment())
> >
> > then if we m
On Wednesday, January 29, 2014 00:06:45 Marco Martin wrote:
> So, the import of the applet can have its own containment instance (not even
> a qml containment, just a dumb containment = new Plasma::Containment())
>
> then if we manage to make its configgroup child of the systray config
> group,
On Tuesday 28 January 2014, Sebastian Kügler wrote:
> Hey,
>
> On Tuesday, January 28, 2014 21:14:10 Marco Martin wrote:
> > New prototype, completely different direction :) (and that's one i
> > actually like)
> >
> > mart/AppletAttached branch.
> > the root item of an applet can still be whate
Hey,
On Tuesday, January 28, 2014 21:14:10 Marco Martin wrote:
> New prototype, completely different direction :) (and that's one i actually
> like)
>
> mart/AppletAttached branch.
> the root item of an applet can still be whatever item one wants, just as
> current master, but plasmoid becomes a
Hi all,
New prototype, completely different direction :) (and that's one i
actually like)
mart/AppletAttached branch.
the root item of an applet can still be whatever item one wants, just as
current master,
but plasmoid becomes an attached property, so it would be possible to do
things like
Item
That QML demo seems to work awesomely \o/
I also fully support trying to get rid of AppletInterface.
Code comments on the cpp. (I know it's a work in progress, but I like
to stalk you)
You have compactRepresentation properties twice.
I assume the second one is meant to be the compactRepre
On Friday 17 January 2014, Eike Hein wrote:
> General comment: Please note that these size hints aren't only
> there so the shell can decide which representation to pick, but
> at times also do things like:
on how the size hints would go and get propagated:
I would use the "Layout" attached prope
On Sat, Jan 18, 2014 at 3:17 PM, Martin Graesslin wrote:
> On Saturday 18 January 2014 14:31:41 Mark Gaiser wrote:
>> On Sat, Jan 18, 2014 at 8:58 AM, Martin Graesslin
> wrote:
>> > On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote:
>> >> I guess my arguments for going with the "Plasmoid" na
On Saturday 18 January 2014 14:31:41 Mark Gaiser wrote:
> On Sat, Jan 18, 2014 at 8:58 AM, Martin Graesslin
wrote:
> > On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote:
> >> I guess my arguments for going with the "Plasmoid" name rather then
> >> "Applet" are just ignored then?
> >> Sebas d
On Sat, Jan 18, 2014 at 8:58 AM, Martin Graesslin wrote:
> On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote:
>>
>> I guess my arguments for going with the "Plasmoid" name rather then
>> "Applet" are just ignored then?
>> Sebas did gave "some" (few lines) explanation before my bunch of
>> arg
On Sat, Jan 18, 2014 at 10:56 AM, Marco Martin wrote:
> On Saturday 18 January 2014, Mark Gaiser wrote:
>
>> > ___
>> > Plasma-devel mailing list
>> > Plasma-devel@kde.org
>> > https://mail.kde.org/mailman/listinfo/plasma-devel
>>
>> I guess my arguments
On Saturday 18 January 2014, Mark Gaiser wrote:
> > ___
> > Plasma-devel mailing list
> > Plasma-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/plasma-devel
>
> I guess my arguments for going with the "Plasmoid" name rather then
> "Applet" are
On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote:
>
> I guess my arguments for going with the "Plasmoid" name rather then
> "Applet" are just ignored then?
> Sebas did gave "some" (few lines) explanation before my bunch of
> arguments. Yet i still think "Plasmoid" would suit it better.
I th
On Saturday 18 January 2014 01:11:54 Mark Gaiser wrote:
> I guess my arguments for going with the "Plasmoid" name rather then
> "Applet" are just ignored then?
Mark, I doubt Marco meant any disrespect; discussing the name
just isn't really a priority while we're trying to work out the
semantics. K
On Fri, Jan 17, 2014 at 9:25 PM, Marco Martin wrote:
> On Friday 17 January 2014, Marco Martin wrote:
>> Applet {
>>
>> compactRepresentation: Component {
>> PlasmaComponents.Button {
>> text: i18n("Click me")
>> onClicked: plasmoid.expanded = !plasmoid.expanded
On Friday 17 January 2014, Marco Martin wrote:
> Applet {
>
> compactRepresentation: Component {
> PlasmaComponents.Button {
> text: i18n("Click me")
> onClicked: plasmoid.expanded = !plasmoid.expanded
> }
> }
>
> fullRepresentation: Component {
On Friday 17 January 2014, Eike Hein wrote:
> General comment: Please note that these size hints aren't only
> there so the shell can decide which representation to pick, but
> at times also do things like:
>
> * Set useful default sizes (e.g. for popups from panels) *before*
> appearance.
> * A
General comment: Please note that these size hints aren't only
there so the shell can decide which representation to pick, but
at times also do things like:
* Set useful default sizes (e.g. for popups from panels) *before*
appearance.
* Affect interaction behavior (e.g. lock down resizing in on
On Thu, Jan 16, 2014 at 12:59 PM, Sebastian Kügler wrote:
> On Wednesday, January 15, 2014 20:36:24 Mark Gaiser wrote:
>> On Wed, Jan 15, 2014 at 6:19 PM, Marco Martin wrote:
>> > On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:
>> >> As for the Applet name. Why that name? I'm making a pl
On Wednesday, January 15, 2014 20:36:24 Mark Gaiser wrote:
> On Wed, Jan 15, 2014 at 6:19 PM, Marco Martin wrote:
> > On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:
> >> As for the Applet name. Why that name? I'm making a plasmoid, right?
> >> So name it as such:
> >> Plasmoid {
> >>
> >
On Wed, Jan 15, 2014 at 6:19 PM, Marco Martin wrote:
> On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:
>
>> As for the Applet name. Why that name? I'm making a plasmoid, right?
>> So name it as such:
>> Plasmoid {
>> ...
>> }
>>
>> That is also easier to explain to a user:
>> "To create
On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:
> As for the Applet name. Why that name? I'm making a plasmoid, right?
> So name it as such:
> Plasmoid {
> ...
> }
>
> That is also easier to explain to a user:
> "To create a plasmoid you have to create a root QML item named
> Plasmoid
On Wed, Jan 15, 2014 at 4:43 PM, Mark Gaiser wrote:
>
> But why?
> What's the reasoning behind that?
>
> If you learn QML from scratch you start with:
> Item {
> ...
> }
>
> or
>
> Rectangle {
> ...
> }
>
> Or if you make a application to look native with the controls:
> ApplicationWindow {
>
On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:
> I don't think KDE should add another one:
> Applet {
> ...
> }
and in KWin I recently added:
KWin.Switcher {
...
}
and I love it. So much cleaner code base. Exactly same thing as proposed here:
non-visual QObject as root element.
C
On Tue, Jan 14, 2014 at 11:35 PM, Marco Martin wrote:
> On Wednesday 15 January 2014 00:01:35 Mark Gaiser wrote:
>> Hi Marco,
>
> First, to be clear is not *my* proposal per se, is the proposal we came up at
> the sprint.
>
>> So if i get it right you propose that every plasmoid - in QML - will
>>
Code comment:
Make sure you default m_minimumWidth and the others to something in
the ctor and check your usage of width when you mean height :)
It might be a good idea to have a default property of type
QmlListProperty so that Applets can have child objects in the
QML for all their models/shared
On Wednesday 15 January 2014 00:01:35 Mark Gaiser wrote:
> Hi Marco,
First, to be clear is not *my* proposal per se, is the proposal we came up at
the sprint.
> So if i get it right you propose that every plasmoid - in QML - will
> at the very least have this:
>
> Item {
>
> Applet {
> m
On Tue, Jan 14, 2014 at 8:14 PM, Marco Martin wrote:
> Hi all,
> those are some notes in a probable API change that will probably happen (let's
> discuss!) on how QML plasmoids are written.
>
> The problem:
> * plasmoids needs some properties in the root object, such as minimumWidth,
> maximumWidt
On Tuesday 14 January 2014 20:14:55 you wrote:
> * everything that needs to always exist is stuff like model and dataengines
> (therefore not graphical) this will have to be child of the root Applet
> item. (another proposal was to make another property that contains it)
> * another thing i was th
Hi all,
those are some notes in a probable API change that will probably happen (let's
discuss!) on how QML plasmoids are written.
The problem:
* plasmoids needs some properties in the root object, such as minimumWidth,
maximumWidth, compactRepresentation..
* the user has to declare *and* implem
35 matches
Mail list logo
