Hi,
sorry had no network connection yesterday.
On Thursday, May 24, 2012 06:51:32 AM Agocs Laszlo.P wrote:
> Hi,
>
> Please do not merge the plug-ins. A monolithic "evdev" monster plug-in is
> not desirable and would certainly not classify as "generic" anymore.
>
> The "static device discovery"
Hi Jorgen,
On Thu, May 24, 2012 at 11:12 PM, Jørgen Lind wrote:
>
>> I think that's a valid point :-) They are all inside qtbase because of
>> convenience. The build system wasn't and still isn't very friendly
>> when it comes to creating separate modules.
>
> I honestly dont understand this poin
> I think that's a valid point :-) They are all inside qtbase because of
> convenience. The build system wasn't and still isn't very friendly
> when it comes to creating separate modules.
I honestly dont understand this point. And why does it have to be a
submodule. Cant it just be a git repo wi
Hey Jorgen,
I also like the idea of "default" plugins where eglfs will default to
loading support for the keyboard and an input device. I think having
some kind of heuristic for this will probably be gross, hacky and
harder to fathom than Girish's current approach which is baking it in.
There are
Hi Jorgen/Laszlo,
On Thu, May 24, 2012 at 12:26 AM, Jørgen Lind wrote:
> On Wed, May 23, 2012 at 11:54:18PM -0700, ext Girish Ramakrishnan wrote:
>> Hi,
>>
>> On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
>> > I think we should focus on keeping eglfs as small as possible, but
>> > keeping
On quarta-feira, 23 de maio de 2012 23.54.18, Girish Ramakrishnan wrote:
> Many of the boards come with very specific rootfs/linux. It's hard to
> install stuff on them. udev support is either there or not there. That
> doesn't mean you cannot plug devices into them, you can. Just that
> udev isn't
Regarding the input plugins: Once you reach a certain level of
complexity (that is, you need tighter integration between the input
subsystems and graphics, need device-specific workarounds, need to
support special embedded setups, etc.), you will find it easier and more
productive to simply fo
On Wed, May 23, 2012 at 11:54:18PM -0700, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
> > I think we should focus on keeping eglfs as small as possible, but
> > keeping the readability of the code, so that the entry level for "extending"
> > eglfs
Hi,
On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
> I think we should focus on keeping eglfs as small as possible, but
> keeping the readability of the code, so that the entry level for "extending"
> eglfs will be low.
>
I think this is the first thing that needs to be discussed :-)
We h
Hi
> The initial issue with our current input handling for platforms like eglfs,
> which do not handle input on its own, is, that we have input plugins for
> mouse/keyboard/touch (evdev), which are seperate from each other.
> So one needs to specify "-plugin evdevkeyboard" on the commandline in o
velopment-bounces+laszlo.p.agocs=nokia@qt-project.org
[development-bounces+laszlo.p.agocs=nokia@qt-project.org] on behalf of
Zellner Johannes (Nokia-DXM/SiliconValley)
Sent: Wednesday, May 23, 2012 11:36 PM
To: development@qt-project.org
Subject: [Development] Fixing input for eglfs and friends
Hi,
as we are working on better support of embedded devices in Qt, we also are
tapping into the input handling.
The initial issue with our current input handling for platforms like eglfs,
which do not handle input on its own, is, that we have input plugins for
mouse/keyboard/touch (evdev), whi
12 matches
Mail list logo
