(changing title as the other thread was freaking huge and a bit bikesheddy).
seems the man-plasmaenginexplorer in workspace/doc/plasma-desktop has
not been moved out, along with the tool itself in that move, tereitor,
care to fix? (i don't have that cloned)
--
Shaun Reich,
KDE Software Developer
On Tuesday 28 August 2012 10:06:54 Sebastian Kügler wrote:
> > Also, Plasmate (again afaik) is not done using kdevplatform, I have been
> > told since day 1 that it will be at some point but apparently it is not. I
> > don't know if kdevplatform is the solution but what I know is that we need
> > t
On Tuesday 28 August 2012 10:37:10 Marco Martin wrote:
> yeah, but disappointing indeed that all parts of kdesdk are still in svn,
> some of the apps still seem to have regular commits, so is not even
> "because unmaintained"
> in that repo there is something that i would definitely want, and some
On Tuesday, August 28, 2012 10:37:10 Marco Martin wrote:
> i would like again a repo like that with all needed (did i already
> mentioned i'm definitely not a fan of micro git repos?;)
> that may include plsmate, plasma tools and some of the tools in kdesdk,
> intersection between those that make
On Tuesday 28 August 2012, Sebastian Kügler wrote:
> > Plasmate only allows to create plasmoids javascript based afaik and it is
> > desgined to do only that (which is cool). Imho it is wy far from
> > being an sdk.
>
> Plasmate is not a complete SDK for everything, sure. The point here is no
Hey,
On Monday, August 27, 2012 10:17:21 Alex Fiestas wrote:
> > > Since we are adding "yet another" repo, our tools will be segregated
> > > across
> > > more repositories, making worse the already not ideal situation.
> >
> > The idea is to consolidate all those development tools into one repo,
On Monday 27 August 2012 14:25:30 Giorgos Tsiapaliokas wrote:
> On 27 August 2012 11:17, Alex Fiestas wrote:
> > Plasmate only allows to create plasmoids javascript based afaik and it is
> > desgined to do only that (which is cool). Imho it is wy far from being
> > an
> > sdk.
>
> A side note
On 27 August 2012 11:17, Alex Fiestas wrote:
>
> Plasmate only allows to create plasmoids javascript based afaik and it is
> desgined to do only that (which is cool). Imho it is wy far from being
> an
> sdk.
>
A side note here, it is also able to
1. create datanengines, themes, runners, wind
On Saturday 25 August 2012 18:19:37 Sebastian Kügler wrote:
> On Tuesday, August 21, 2012 19:42:16 Alex Fiestas wrote:
> > I have changed my mind on this topic with the following conclusion (hope
> > it
> > is useful for future actions).
>
> I think it is =)
>
> > The main reason why I don't lik
On Tuesday, August 21, 2012 19:42:16 Alex Fiestas wrote:
> I have changed my mind on this topic with the following conclusion (hope it
> is useful for future actions).
I think it is =)
> The main reason why I don't like this movement is because it adds an extra
> dependency for the random KDE h
I have changed my mind on this topic with the following conclusion (hope it is
useful for future actions).
The main reason why I don't like this movement is because it adds an extra
dependency for the random KDE hacker that wants to do something. This hacker
will compile everything so he will h
On Mon, Aug 20, 2012 at 11:01 AM, Giorgos Tsiapaliokas
wrote:
> Also just out of curiosity why I didn't saw any objections back in
> February/March?
>
> http://mail.kde.org/pipermail/plasma-devel/2012-March/018838.html
> http://mail.kde.org/pipermail/plasma-devel/2012-March/018838.html
>
> P.S.: y
On Mon, Aug 20, 2012 at 11:57 AM, Marco Martin wrote:
> On Monday 20 August 2012, Alex Fiestas wrote:
>>
>> I agree with aleix, typical example is Designer and Creator or Assistant.
>>
>> In the QML area, people are being forced to use Creator because the tools
>> aren't exported as a different to
On Monday 20 August 2012, Alex Fiestas wrote:
>
> I agree with aleix, typical example is Designer and Creator or Assistant.
>
> In the QML area, people are being forced to use Creator because the tools
> aren't exported as a different tool, and that pisses people off (all
> emacs,vim,kdevelop,kat
Also just out of curiosity why I didn't saw any objections back in
February/March?
http://mail.kde.org/pipermail/plasma-devel/2012-March/018838.html
http://mail.kde.org/pipermail/plasma-devel/2012-March/018838.html
P.S.: yes this is the second time that we discuss this change
--
Giorgos Tsiapal
On 20 August 2012 02:32, Alex Fiestas wrote:
>
> I agree with aleix, typical example is Designer and Creator or Assistant.
>
> In the QML area, people are being forced to use Creator because the tools
> aren't exported as a different tool, and that pisses people off (all
> emacs,vim,kdevelop,kate
On 20 August 2012 02:15, Aleix Pol wrote:
>
> That's a packaging decision. The Plasmate should depend on the plasma
> tools.
The Plasmate IDE will depend on the plasma tools, either if they are in the
kde-workspace or in
the plasmate repo.
> > From a technical point of view,
> > those are a fe
On Mon, Aug 20, 2012 at 1:32 AM, Alex Fiestas wrote:
> On Monday 20 August 2012 01:15:07 Aleix Pol wrote:
>> On Fri, Aug 17, 2012 at 5:20 PM, Giorgos Tsiapaliokas
>>
>> wrote:
>> > On 17 August 2012 16:24, Aleix Pol wrote:
>> >> Hi,
>> >> I don't really see the point of doing that. I don't see w
On Monday 20 August 2012 01:15:07 Aleix Pol wrote:
> On Fri, Aug 17, 2012 at 5:20 PM, Giorgos Tsiapaliokas
>
> wrote:
> > On 17 August 2012 16:24, Aleix Pol wrote:
> >> Hi,
> >> I don't really see the point of doing that. I don't see why it's
> >> better not to have them in kde-workspace is it t
On Fri, Aug 17, 2012 at 5:20 PM, Giorgos Tsiapaliokas
wrote:
>
>
> On 17 August 2012 16:24, Aleix Pol wrote:
>>
>> Hi,
>> I don't really see the point of doing that. I don't see why it's
>> better not to have them in kde-workspace is it troublesome for anyone?
>
>
> From an aesthetic point of vie
On 19 August 2012 08:13, Shantanu Tushar Jha wrote:
>
> Well you cannot, if you want both plasmoidviewer and plasmate to be able
> to use it, you'll have to move the stuff to some qwidget (or maybe a
> KPart?) so that they can share it.
>
>>
>> 2. Some tools when they are used as standalone applic
On Fri, Aug 17, 2012 at 8:50 PM, Giorgos Tsiapaliokas wrote:
>
>
> On 17 August 2012 16:24, Aleix Pol wrote:
>>
>> Hi,
>> I don't really see the point of doing that. I don't see why it's
>> better not to have them in kde-workspace is it troublesome for anyone?
>>
>
> From an aesthetic point of vi
If there aren't any new replies in this thread until Monday morning,
I will push the changes into master.
Regards,
Giorgos
--
Giorgos Tsiapaliokas (terietor)
KDE Developer
terietor.gr
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde
Can I proceed with the change?
--
Giorgos Tsiapaliokas (terietor)
KDE Developer
terietor.gr
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On 17 August 2012 16:24, Aleix Pol wrote:
>
> Hi,
> I don't really see the point of doing that. I don't see why it's
> better not to have them in kde-workspace is it troublesome for anyone?
>
>From an aesthetic point of view,
Q: Hello, where are the plasma tools? I want to create a new plasmoid.
On Mon, Aug 13, 2012 at 4:40 PM, Giorgos Tsiapaliokas
wrote:
> Hello,
>
> my GSoC tasks included to move the plasma tools(those are
> kde-workspace/plasma/generic/tools) into plasmate.
> In order to do that I will use the "git subtree" command.
>
> With git subtree I will make a copy of kde-worksp
If nobody complains about the change, tomorrow morning I will merge
terietor/tools into master and I will git rm
kde-workspace/plasma/generic/tools
--
Giorgos Tsiapaliokas (terietor)
KDE Developer
terietor.gr
___
Plasma-devel mailing list
Plasma-devel@
I have just pushed a new branch in plasmate named terietor/tools.
In this branch I have moved everything from
kde-workspace/plasma/generic/tools to plasmate/ .
(I haven't modified the kde-workspace repository)
I have created this branch in order to get more feedback about the move.
Is there anyth
On Thursday 16 August 2012, Sebastian Kügler wrote:
> Hey,
>
> First of all: if anybody objects to having these tools (plasmoidviewer,
> etc.) not shipped with kde-workspace anymore, speak now or forever hold
> your peace.
>
> :)
>
i think that is makes sense
--
Marco Martin
2012/8/16 Sebastian Kügler
> Hey,
>
> First of all: if anybody objects to having these tools (plasmoidviewer,
> etc.)
> not shipped with kde-workspace anymore, speak now or forever hold your
> peace.
> :)
>
Agreed.
>
> On Monday, August 13, 2012 17:40:39 Giorgos Tsiapaliokas wrote:
> > my GSoC
Hey,
First of all: if anybody objects to having these tools (plasmoidviewer, etc.)
not shipped with kde-workspace anymore, speak now or forever hold your peace.
:)
On Monday, August 13, 2012 17:40:39 Giorgos Tsiapaliokas wrote:
> my GSoC tasks included to move the plasma tools(those are
> kde-w
Hello,
my GSoC tasks included to move the plasma tools(those are
kde-workspace/plasma/generic/tools) into plasmate.
In order to do that I will use the "git subtree" command.
With git subtree I will make a copy of kde-workspace/plasma/generic/tools
into plasmate and then
I will remove with git rm
32 matches
Mail list logo
