On Tuesday 14 April 2009, Emdek wrote: > On Tuesday 14-04-2009 01:17:05 Aaron J. Seigo wrote: > > On Monday 13 April 2009, Emdek wrote: > >> On Monday 13-04-2009 19:26:52 Aaron J. Seigo wrote: > >> > On Sunday 12 April 2009, Emdek wrote: > >> >> On Sunday 12-04-2009 18:18:01 Aaron J. Seigo wrote: > >> >> >> - show titles of windows when showing multiple previews; > >> >> > > >> >> > will this fit nicely? look nice? could we do it with QToolTips on > >> > >> the > >> > >> >> > previews? > >> >> > >> >> I'm using it already in my applet and it looks good I think: > >> >> > >> >> http://kde-look.org/CONTENT/content-pre1/99737-1.png > >> > > >> > and for really long titles? i suppose you just elide the text? > >> > >> No, currently I'm not, but I should (I want to move to standard tool > >> tips > >> so I'm not touching this part of code now ;-)). So if the text is tool > >> long > >> the we could use that kind of gradient like in Tasks applet and the show > >> full text in tool tip for tool tip > > > > sounds good. maybe we don't even need the tooltip? in practice just the > > starting bit (as wide as the thumbnail itself) would be enough? > > Right, maybe we should allow to make it maximum two rows or one is enough > (and it is easier to do)? > > >> (my friend that works on STasks applet > >> proposed marque animation for it). ;-) > > > > ew.. maybe on mouse over? but certainly not as a default. i can just > > imagine > > the visual effect of having 3 or more dancing strings :) > > Yes, of course for mouse over, but I'm not sure if I want to see in my tool > tip move other than from live preview of window with video or something (by > the way, maybe tool tips in Tasks applet shouldn't auto hide, at least when > we have previews?). ;-) > > >> >> So now we need clear list of needed signals and then start to work. > >> > >> ;-) > >> > >> > hoverEnter(const KUrl &) > >> > hoverLeave(const KUrl &) > >> > activated(const KUrl &) > >> > >> And what about these (mostly activation for WId, with used mouse button, > >> rest of them is much less useful I think)? > > > > ah, right, ... hm. we could have two signals: > > > > void activate(const KUrl &); // the common, easy case > > void activated(cost KUrl &, Qt::MouseButton, Qt::ModifierKey); > > And information about WId etc. would be passed as KUrl or I'm missing > something?
yes, i think we'd just pass it as a specially crafted url, e.g. window://### mildly silly but effective ;) it'll only be for in-application use and not for passing around between applications, so it's ok. > ;-) I think that it is better to have one signal with more > parameters, if someone don't need more information he will just use > Q_UNUSED in slot connected to it. sure ... > > it's not overly difficult; if you're up for it, i can help you through > > it e.g. > > on irc ... if not, i can try and work this part out for you. > > Talk on IRC could be useful (but eight hours difference between timezones > could be a problem ;-)). i'm often there at odd (for my timezone) hours > And I'm not sure if I could finish this before > hard freeze (I'm not familiar with event filters). So maybe I'll better > focus on these smaller tasks, like preview glowing on hover (maybe using > animation code from ComboBox), image preview (probably renaming private > WindowPreview class to PreviewWidget or something like that and adding > method to set pixmap, maybe setPixmapToPreview()?), try to add possibility > to show tool tip centered (setCentered(bool) for ToolTipContent? or maybe > more generic setAlignment(Qt::Alignment)?) and experiment with window > titles for multiple previews. sure thing .. it all needs to get done :) -- 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
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
