On Thursday, 2012-09-06, Aaron J. Seigo wrote:
> in the same way that every application that opens files stored on disk
> needs to support file open/read/write. in reality, very few of our
> applications make direct libc calls to achieve this and instead rely on
> (much) higher level libraries to
On Thursday, September 6, 2012 14:22:28 Kevin Krammer wrote:
> Without checking the implementation details I would have guessed that
> "allowing content to be introspected" needs support for that introspection
> in every single application
in the same way that every application that opens files s
On Thursday, 2012-09-06, Aaron J. Seigo wrote:
> On Thursday, September 6, 2012 12:47:16 Kevin Krammer wrote:
> > The problem with that (as far as I can tell) is that this would not be
> > available to non-KDE apps, which (again as far as I understand) is the
> > case of the thread starter.
>
> if
On Thursday, September 6, 2012 12:47:16 Kevin Krammer wrote:
> The problem with that (as far as I can tell) is that this would not be
> available to non-KDE apps, which (again as far as I understand) is the case
> of the thread starter.
if the issue was non-KDE apps, this would be an interesting s
On Wednesday, 2012-09-05, Aaron J. Seigo wrote:
> what that would do in this case is instead of implementing (non-standard)
> means to set desktop wallpapers in N applications, N applications simply
> start advertising what content the user is focused on so that other parts
> of the system can rea
On Wednesday, September 5, 2012 17:50:28 Michael Pyne wrote:
> Does this actually change the wallpaper for the default containment though,
> or is more work still needed on that end?
we have code that changes the wallpaper given an arbitrary image URL. it needs
to be put into (or accessed from) a
