On October 22, 2009 20:57:43 Yuen Hoe Lim wrote:
> Oh yeah, since this thread is still running, I have a question - how
> exactly is saving supposed to work in PlasMate again? I haven't really
> been thinking about it and just kinda assumed that it'd be like a regular
> editor - you edit, edit,
Oh yeah, since this thread is still running, I have a question - how exactly
is saving supposed to work in PlasMate again? I haven't really been thinking
about it and just kinda assumed that it'd be like a regular editor - you
edit, edit, save (the file), next file, edit, save, and so on, and when
>
> er, the preview is a live interactive preview, not just an image, right?
>
Yeah it is.
so if there's a tabbing system, great. but i don't want to see it end up
> where
> one can only see the code OR the plasmoid. that's simply inane.
>
Hmmm so we have a previewer dock AND a previewer tab? No
>
> The "disadvantage" would be, that there's no preview area next to his
> editor. But it seems it would only be a picture of the latest
> save-point anyway.
"picture"?
er, the preview is a live interactive preview, not just an image, right?
personally the only time I see myself *not* enjoying
On Thursday 22 October 2009, Riccardo Iaconelli wrote:
> On Monday 19 October 2009 16:53:28 Adenilson Cavalcanti wrote:
> > Which brings the question: blur, drop shadows and others should be
> > provided by plasma. Should we provide a common effects set of classes? I
> > think so (not sure if this
On Tuesday 20 October 2009 22:12:59 Adenilson Cavalcanti wrote:
> Regarding 'b' (effects), there are some nice effects in KDE (e.g. mirroring
> icons in KDE splash screen, soft drop shadows around plasmoids, etc) that
> maybe could be interesting to make available to normal users. But this is
>
On Monday 19 October 2009 16:53:28 Adenilson Cavalcanti wrote:
> Which brings the question: blur, drop shadows and others should be provided
> by plasma. Should we provide a common effects set of classes? I think so
> (not sure if this is out of topic).
>
Isn't already http://api.kde.org/kdesup
On October 22, 2009, Stephen Kelly wrote:
> In Akonadi I just create an EntityTreeModel which has api for all of that
> stuff. If I can forward those calls to plasma somehow, that would be good,
> but I need a starting point. Do I create my model in a Applet, or a Data
> Engine etc?
you're actuall
On October 22, 2009, Michael Rudolph wrote:
> The "disadvantage" would be, that there's no preview area next to his
> editor. But it seems it would only be a picture of the latest
> save-point anyway.
right, so that you can play with it and work on the code at the same time.
having to switch back
On Thursday 22 October 2009, Stephen Kelly wrote:
> Marco Martin wrote:
> > On Thursday 22 October 2009, Stephen Kelly wrote:
> >> Hi,
> >>
> >> I'm trying to get notes from Akonadi onto a plasma workspace.
> >>
> >> I've been reading some of the apidocs and I can't figure out if I need a
> >> data
Marco Martin wrote:
> On Thursday 22 October 2009, Stephen Kelly wrote:
>> Hi,
>>
>> I'm trying to get notes from Akonadi onto a plasma workspace.
>>
>> I've been reading some of the apidocs and I can't figure out if I need a
>> data engine, whether I need one Plasma::Applet per note, whether I
On Thursday 22 October 2009, Stephen Kelly wrote:
> Hi,
>
> I'm trying to get notes from Akonadi onto a plasma workspace.
>
> I've been reading some of the apidocs and I can't figure out if I need a
> data engine, whether I need one Plasma::Applet per note, whether I need a
> 'manager' plasmoid t
Hi,
I'm trying to get notes from Akonadi onto a plasma workspace.
I've been reading some of the apidocs and I can't figure out if I need a
data engine, whether I need one Plasma::Applet per note, whether I need a
'manager' plasmoid that manages all others, keeping them up to date, and
adding/r
On Mon, Oct 19, 2009 at 21:20, Aaron J. Seigo wrote:
> On October 18, 2009, Michael Rudolph wrote:
>> On Sun, Oct 18, 2009 at 18:22, Marco Martin wrote:
>> > not sure about making it an overlay: has it enough "value" to be always
>> > shown or can be usually hidden and shown only when needed?
>>
>> there's a maintenance responsibility for
>> things you put into kde. i'm at the point with this control panel that if it
>> isn't improved for 4.4 i will be removing it.
>
> For the record I have worked to maintain this code. And I have committed to
> fixing
> these bugs for the 4.4 release and
>> There is a severe issue with setting Desktop Details:
>> https://bugs.kde.org/show_bug.cgi?id=182823
>> https://bugs.kde.org/show_bug.cgi?id=205330
>
> this doesn't require a usability test to figure out, it requires the author of
> this control panel to fix his code. there's a maintenance respo
16 matches
Mail list logo
