Re: [RFC] File ending for packaged KWin effects and where to put them
On Thursday, February 9, 2012 09:57:32 Martin Gräßlin wrote: > Should such files use the file ending "plasmoid" or should we introduce new > names like "kwineffect", "kwinswitcher", "kwinscript", "kwindecoration"? > Could using "plasmoid" result in problems like the widgets explorer trying > to install the kwineffect when dropped on the desktop? it will be at the very least confusing for the user. i would recommend different suffixes. > The second question I have is about the additional effects. Now that we have > the scripted bindings I want to rewrite a few pure eye-candy effects with > the bindings and move them out of the KWin source tree. Where should they > go? I tend to plasma-addons. if you want them available by synchrotron, then in the synchrotron-sources repository. otherwise i think addons is a good target, yes. > Last but not least: how does this synchrotron work and does it offer > something which would be very useful to distribute our effects, scripts, > etc? yes, it does. i need to complete the client-side integration to make it non- painful to use from such things (e.g. i don't want kwin, plasma-desktop, etc. etc. all implementing this on their own, which they would nominally have to at this point.) i'll rachet this up on my todo list since kwin would now be blocking on it. -- Aaron J. Seigo 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
Re: Re: [RFC] File ending for packaged KWin effects and where to put them
On Thursday 09 February 2012 17:45:03 Weng Xuetian wrote: > On Thu, Feb 9, 2012 at 4:57 PM, Martin Gräßlin wrote: > > Hi workspace developers, > > > > my JavaScript bindings for KWin effects are nearly in place and that > > results in a few questions I wanted to discuss with the greater team. > > > > The scripted effects follow the Plasma Packages structure and I plan to > > have also "normal" KWin scripts use Plasma Package structure as well as > > window decorations and window switcher layouts. > > > > Should such files use the file ending "plasmoid" or should we introduce > > new > > names like "kwineffect", "kwinswitcher", "kwinscript", "kwindecoration"? > > Could using "plasmoid" result in problems like the widgets explorer > > trying to install the kwineffect when dropped on the desktop? > > plasmoid is just a zip rename into .plasmoid, and if ".kwineffect" > will be used, you should add something similar to > /usr/share/mime/application/x-plasma.xml. > > Add new mime-type for kwin effects have a benefit that they can be > assigned to different installer easily, if user want to have a feature > that double click on .kwineffect file and can have it installed. > > > The second question I have is about the additional effects. Now that we > > have the scripted bindings I want to rewrite a few pure eye-candy effects > > with the bindings and move them out of the KWin source tree. Where should > > they go? I tend to plasma-addons. > > > > Last but not least: how does this synchrotron work and does it offer > > something which would be very useful to distribute our effects, scripts, > > etc? > I think you can request a new category for kwin effect on > kde-look.org, currently there is no separate kwin effect category and > all existing third-party effect are seems to be in "KDE Improvement". > Something like "KWin Effects Binary" and "KWin Effects Scripts" should > be added. yes of course, but this does not make sense before the code is written. In fact I want to have the new categories on kde-look hidden till our first 4.9 beta is released :-) Cheers Martin 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
Re: [RFC] File ending for packaged KWin effects and where to put them
On Thu, Feb 9, 2012 at 4:57 PM, Martin Gräßlin wrote: > Hi workspace developers, > > my JavaScript bindings for KWin effects are nearly in place and that results > in a few questions I wanted to discuss with the greater team. > > The scripted effects follow the Plasma Packages structure and I plan to have > also "normal" KWin scripts use Plasma Package structure as well as window > decorations and window switcher layouts. > > Should such files use the file ending "plasmoid" or should we introduce new > names like "kwineffect", "kwinswitcher", "kwinscript", "kwindecoration"? Could > using "plasmoid" result in problems like the widgets explorer trying to > install the kwineffect when dropped on the desktop? plasmoid is just a zip rename into .plasmoid, and if ".kwineffect" will be used, you should add something similar to /usr/share/mime/application/x-plasma.xml. Add new mime-type for kwin effects have a benefit that they can be assigned to different installer easily, if user want to have a feature that double click on .kwineffect file and can have it installed. > > The second question I have is about the additional effects. Now that we have > the scripted bindings I want to rewrite a few pure eye-candy effects with the > bindings and move them out of the KWin source tree. Where should they go? I > tend to plasma-addons. > > Last but not least: how does this synchrotron work and does it offer something > which would be very useful to distribute our effects, scripts, etc? > I think you can request a new category for kwin effect on kde-look.org, currently there is no separate kwin effect category and all existing third-party effect are seems to be in "KDE Improvement". Something like "KWin Effects Binary" and "KWin Effects Scripts" should be added. And KNewStuff3 is very easy to use. http://techbase.kde.org/Development/Tutorials/Collaboration/HotNewStuff/Introduction ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: [RFC] File ending for packaged KWin effects and where to put them
On Thu, Feb 9, 2012 at 9:57 AM, Martin Gräßlin wrote:
> Hi workspace developers,
>
> my JavaScript bindings for KWin effects are nearly in place and that
> results
> in a few questions I wanted to discuss with the greater team.
>
> The scripted effects follow the Plasma Packages structure and I plan to
> have
> also "normal" KWin scripts use Plasma Package structure as well as window
> decorations and window switcher layouts.
>
> Should such files use the file ending "plasmoid" or should we introduce new
> names like "kwineffect", "kwinswitcher", "kwinscript", "kwindecoration"?
> Could
> using "plasmoid" result in problems like the widgets explorer trying to
> install the kwineffect when dropped on the desktop?
>
My opinion.. keep .plasmoid for the actual "widgets" that can be placed on
the desktop.
use the new names ("kwineffect", "kwinswitcher", "kwinscript",
"kwindecoration") for kwin.
Just my 2 cents. I can't comment on the other questions since I know to
little about that.
>
> The second question I have is about the additional effects. Now that we
> have
> the scripted bindings I want to rewrite a few pure eye-candy effects with
> the
> bindings and move them out of the KWin source tree. Where should they go? I
> tend to plasma-addons.
>
> Last but not least: how does this synchrotron work and does it offer
> something
> which would be very useful to distribute our effects, scripts, etc?
>
> Cheers
> 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
[RFC] File ending for packaged KWin effects and where to put them
Hi workspace developers, my JavaScript bindings for KWin effects are nearly in place and that results in a few questions I wanted to discuss with the greater team. The scripted effects follow the Plasma Packages structure and I plan to have also "normal" KWin scripts use Plasma Package structure as well as window decorations and window switcher layouts. Should such files use the file ending "plasmoid" or should we introduce new names like "kwineffect", "kwinswitcher", "kwinscript", "kwindecoration"? Could using "plasmoid" result in problems like the widgets explorer trying to install the kwineffect when dropped on the desktop? The second question I have is about the additional effects. Now that we have the scripted bindings I want to rewrite a few pure eye-candy effects with the bindings and move them out of the KWin source tree. Where should they go? I tend to plasma-addons. Last but not least: how does this synchrotron work and does it offer something which would be very useful to distribute our effects, scripts, etc? Cheers Martin 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
