> the important motivator for nepomuk is "applications using it". aka
> "relevance".
I agree on this one, I just wanted to point out that our usage of Nepomuk is
not that advanced, thrilling or anything to be a driving force for devels. As
for relevance, your statement stands ;)
> how can i say
Hi folks,
As you may already know, we are going to have Akademy-BR in next
weekend and I was
wondering about taking some hours and two or three developers to work
on Plasmate.
So, you guys wanting to point out some required feature/improvement would be
great. Is the plasmate webpage up to date ?
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/3470/#review4821
---
Ship it!
looks good (modulo the tooltip thing); the other comments ar
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/3470/
---
Review request for Plasma.
Summary
---
this factors out the appletbrowser c
On March 31, 2010, Ivan Čukić wrote:
> > can we get together on irc soon and do a once-over of this and then get
> > it moved into kdereview?
>
> Ok, I'll try to be online tomorrow. If not, then the weekend?
sounds great; i'll be around :)
> > if we work around subsystems because "they don't wor
> can we get together on irc soon and do a once-over of this and then get it
> moved into kdereview?
Ok, I'll try to be online tomorrow. If not, then the weekend?
> if we work around subsystems because "they don't work well yet" then the
> odds they ever will work well goes down as there is less
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard.kde.org/r/2636/#review4818
---
I am sorry it took so long for me to answer, I simply overlooked your
> > After the time comes when we can rely on nepomuk 24/7, we can remove
> > the caching kded service since all of this is hidden behind the API.
>
> if we work around subsystems because "they don't work well yet" then the
> odds they ever will work well goes down as there is less reason /
> moti
On Wednesday 31 March 2010, Aaron J. Seigo wrote:
> On March 30, 2010, Chani wrote:
> > AppletIconWidget? it does all its own painting, and has some odd-looking
> > sizing code,
>
> i suppose you are refering to resizeEvent? if so, it simply reserves enough
> space for one line of text below the i
On March 26, 2010, Ivan Čukić wrote:
> - all manager signals converted into listener objects
this is the registeredActivityControllers stuff in the kded service? if so:
turns out that dbus signals aren't as bad as i had been led to believe. it
turns out that some of kdelibs were using certain d
On March 30, 2010, Chani wrote:
> AppletIconWidget? it does all its own painting, and has some odd-looking
> sizing code,
i suppose you are refering to resizeEvent? if so, it simply reserves enough
space for one line of text below the icon and makes the icon size big enough
to fill the rest.
>
On March 31, 2010, daithe...@free.fr wrote:
> I'd rather put the whole "mode access" to a dedicated panel that wouldn't
> change.
this is the home page.
> And keep the controls in the top bar or wherever you want. (I'm
that's the idea.
> still not convinced that a common control bar is the bes
On March 31, 2010, daithe...@free.fr wrote:
> menu (or whatever you call it, for me it's just a menu) has to be the same
> everywhere.
it isn't a menu, it's a contextual controls bar.
it can't be the same everywhere, since neither the context is consistent nor
could we fit everything on there wit
Hi there,
Thanks for your answer Christophe,
- "Christophe Olinger" a écrit :
> On Wed, Mar 31, 2010 at 12:31 PM, wrote:
>
> >
> > About the top bar discussion, I would strongly recommend not to do
> that. A menu (or whatever you call it, for me it's just a menu) has to
> be the same ev
On Wed, Mar 31, 2010 at 12:31 PM, wrote:
>
> About the top bar discussion, I would strongly recommend not to do that. A
> menu (or whatever you call it, for me it's just a menu) has to be the same
> everywhere.
I do not really agree here. When viewing pictures, I do not neet a
seek slider and
On Wednesday 31 March 2010 09:37:30 Alexis Ménard wrote:
> > The key is really to support commodity hardware, things people already
> > have or can get rather inexpensively and turn it into a media center
> > with little effort (basically install PMC, and hook up the TV to it).
>
> And why not tar
Hi guys,
- "Christophe Olinger" a écrit :
> I'll try to update the wiki page today adding the things we discussed
> here and also the StateMachine Rewriting.
About the top bar discussion, I would strongly recommend not to do that. A menu
(or whatever you call it, for me it's just a menu)
On Wednesday 31 March 2010, Sebastian Kügler wrote:
> SVN commit 1109276 by sebas:
>
> New class to interact with a Wiimote
>
> The class uses the cwiid library from http://abstrakraft.org/cwiid/
> to detect the wiimote, read its settings and receive events.
>
> Currently supported:
> - buttons
On Tue, Mar 30, 2010 at 12:42 PM, Sebastian Kügler wrote:
> On Monday 29 March 2010 21:02:06 Aaron J. Seigo wrote:
>> thoughts?
>
> I don't agree with the "PMC should target notebooks" as primary usecase bit.
> I really
> think that this thing should be developed to have its UI run on a TV,
> pr
19 matches
Mail list logo
