SoConcepts

[Aaron J. Seigo]

On Thursday 19 February 2009, Chani wrote:
> On February 19, 2009 12:26:10 Aaron J. Seigo wrote:
> > On Wednesday 18 February 2009, Chani wrote:
> > > > 	* savable containments: save / restore to file individual
> > > > containments or entire layouts; both locally for later restoration as
> > > > well as external export for sharing with others.
> > >
> > > is this really enough work for a soc project?
> >
> > if the "nice way to share with others" is added to it and the
> > requirements are to provide usable UI interaction for all steps, i think
> > so. it's certainly not a HUGE project, though.
> >
> > > btw, when I was thinking about it during tokamak, I realised that
> > > stashing them locally is easiest to do by simply leaving them in the
> > > appletsrc with a flag to disable them - no need to go mucking about
> > > with files. sharing with other people would be different, of course. :)
> >
> > the flag idea is elegant, but then there are two different code paths:
> > one for the "i'm just going to stash this one away for my own use later"
> > and one for "i'd like to share these with others / i'm sharing this one
> > from my friend".
>
> the idea was to not need a filedialog unless the user is exporting them. so
> when I want to load a containment, I don't think "now where the heck did I
> put that thing?" - I just get a list of stashed containments and can load
> one easily.

the filenames can be generated automatically and the files stored in 
$APPDATA/layouts/ or whatever.

> > for a dialog that shows all available but not-active containments, this
> > would make a difference to the amount of and cleanliness of the code.
>
> how would a dialog show non-active containments if tehy're saved somewhere
> else? are you thinking of having some folder in .kde for them?

bingo :)

> ...I suppose that would be a way to avoid filedialogs and have them not in
> the appletsrc. 

more bingo :)

> but then when you load them, does that file get deleted? or

i think so, yes.

> > it would also be a bit less surprising in the case one clears out their
> > plasma-desktop* configs to not have them remain in the config file.
>
> maybe, maybe not. although it seems I've got plasma stuff in share/apps/
> already, so cleaning out plasma config isn't as trivial as it used to be.

what stuff is in share/apps/ that affects the plasma settings?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090219/6e711dc0/attachment.sig