On Sat, Jan 19, 2013 at 5:10 AM, nerdopolis
wrote:
> Hi.
>
> I played around in Weston with the Pixman renderer enabled, and it seems
> that using the Weston window rotate feature seems to result in some
> interesting glitches (as well as the Weston zoom animation).
>
> This is a screenshot of an
Hi.
I played around in Weston with the Pixman renderer enabled, and it seems that
using the Weston window rotate feature seems to result in some interesting
glitches (as well as the Weston zoom animation).
This is a screenshot of an attempt to rotate a window.
http://imagebin.org/243342___
Hi Martin,
This is really shaping up, nice work. I have a few comment about the output
configuration section, please see below.
On Fri, Jan 18, 2013 at 10:44 AM, Martin Minarik <
minari...@student.fiit.stuba.sk> wrote:
> changes:
> - launcher path, passing environment variables and parameter
>
changes:
- launcher path, passing environment variables and parameter
- indent modeline example
---
man/Makefile.am|9 +-
man/weston.ini.man | 332
2 files changed, 338 insertions(+), 3 deletions(-)
create mode 100644 man/weston.ini.
On 01/18/2013 01:01 PM Philip Withnall wrote:
On Fri, 2013-01-18 at 13:09 +0200, Pekka Paalanen wrote:
Why not discover that device via udev? That would avoid any hard-coded
paths. And you could do an fbdev_output_create() on all fbdev devices
you find.
Good idea. It's not on my list of priori
On Fri, 2013-01-18 at 13:09 +0200, Pekka Paalanen wrote:
> > > Why not discover that device via udev? That would avoid any hard-coded
> > > paths. And you could do an fbdev_output_create() on all fbdev devices
> > > you find.
> >
> > Good idea. It's not on my list of priorities though, since I (co
On Thu, 17 Jan 2013 17:22:08 +0100
Martin Minarik wrote:
> - Update to latest automake
> - Spaces in INI are significant
> - elaborate on data types, by pq
> - mention type of value for each key
> - automake weston modules dir path
> - remove [shell] type=
> - animation= no animation other
On Fri, 18 Jan 2013 10:45:27 +
Philip Withnall wrote:
> Hi David,
>
> Thanks for the review. Replies inline, and a new patch coming up soon.
>
> On Wed, 2013-01-16 at 21:22 +0100, David Herrmann wrote:
> > Hi Philip
> >
> > I like the simple design of this. I don't think we need to share m
Here's an updated version of the fbdev backend, with fixes made in
response to the helpful comments by David, Pekka and Vasily. The main
differences in this version are improved error handling, better support
for different frame buffer pixel formats, and various small bits of
cleanup.
This patch i
On Wed, 2013-01-16 at 12:02 +0200, Pekka Paalanen wrote:
> What do you have in mind for polishing? If it is the evdev and VT code
> sharing between several backends, you will find that the android
> backend will make it not so nice. IMO we could merge fbdev backend, and
> refactor code later.
I mo
Hi David,
Thanks for the review. Replies inline, and a new patch coming up soon.
On Wed, 2013-01-16 at 21:22 +0100, David Herrmann wrote:
> Hi Philip
>
> I like the simple design of this. I don't think we need to share much
> of the code as it's pretty simple.
>
> I haven't checked all of it, b
With the Android backend gone, there is no C++ code anymore. Remove
support for C++ in the build.
Signed-off-by: Pekka Paalanen
---
configure.ac |8 ++--
1 files changed, 2 insertions(+), 6 deletions(-)
diff --git a/configure.ac b/configure.ac
index a2e8e27..f9075ae 100644
--- a/configu
The Android backend has been fairly unused, since we do not have
projects actively using it. It gets basic build testing as part of the
normal build, but runtime testing it takes a considerable effort, and so
I have not done that in a long time. The code is slowly rotting, and
with new emerging bac
13 matches
Mail list logo
