On Sunday, May 27, 2012 20:17:01 Aaron J. Seigo wrote:
> On Saturday, May 26, 2012 15:03:11 Thomas Pfeiffer wrote:
> > I finally had my first chance to see Maliit Active live in action (on
> > Mer),
> > and it generally I like it a lot!
>
> huzzah!
>
> > Even though the keys are currently way too
Aaron/Thomas Hi,
Thomas, we spoke about this on IRC over the weekend an I took an action to
make a list of the issues in the way of Mer based Plasma Active builds and
to coordinate any resources we can get to fixing them.
Could you any anyone else with issues please reply with a ordered list of
M
On 29.05.2012 13:24, Aaron J. Seigo wrote:
to be perfectly honest, there should be no further effort put into the meego
images. effort there takes effort away from Mer, and it's like dragging two dead
horses behind the cart :)
I understand that.
I admit I was being a bit egocentric there: I nee
On Monday, May 28, 2012 18:39:24 Thomas Pfeiffer wrote:
> On Saturday 26 May 2012 14:22:50 Thomas Pfeiffer wrote:
> > However, since with the latest Mer x86 devel image I can update without
> > trashing my system again, so I will try Mer again and will try to help
> > getting it stable on x86 so we
On Saturday 26 May 2012 14:22:50 Thomas Pfeiffer wrote:
> However, since with the latest Mer x86 devel image I can update without
> trashing my system again, so I will try Mer again and will try to help
> getting it stable on x86 so we can ditch Meego soon.
It seems like getting Mer usable on a We
On Sunday 27 May 2012 20:17:01 Aaron J. Seigo wrote:
> > Even though the keys are currently way too small on the Mer x86 image on a
> > Wetab (partly because they are not dpi-aware yet, partly because the
>
> yes, size is the next thing we need to tackle in the integration ...
+1
> > However sin
On Saturday, May 26, 2012 15:03:11 Thomas Pfeiffer wrote:
> I finally had my first chance to see Maliit Active live in action (on Mer),
> and it generally I like it a lot!
huzzah!
> Even though the keys are currently way too small on the Mer x86 image on a
> Wetab (partly because they are not dpi
On Monday 21 May 2012 19:26:08 Marco Martin wrote:
> yeah, now sizes are still mostly hardcoded as the old qml one i started on
> (size is smaller to adapt to vivaldi)
> i plan to use dpi there as well.
I finally had my first chance to see Maliit Active live in action (on Mer), and
it generally I
On Friday 25 May 2012 21:21:40 Marco Martin wrote:
> On Friday 25 May 2012, Lamarque V. Souza wrote:
> > > I just tried this and it seems to have been correctly written into the
> > > correct %gconf.xml, but I still get the same warnings and still no
> > > keyboard popping up
> > >
> > > :(
> >
On Friday 25 May 2012, Lamarque V. Souza wrote:
> > I just tried this and it seems to have been correctly written into the
> > correct %gconf.xml, but I still get the same warnings and still no
> > keyboard popping up
> >
> > :(
>
> libmaliit-keyboard-plugin.so was compiled against Qt 4.8.
Em Thursday 24 May 2012, Thomas Pfeiffer escreveu:
> On Thursday 24 May 2012 14:24:40 Marco Martin wrote:
> > On Thursday 24 May 2012, Thomas Pfeiffer wrote:
> > > This is what I get when I execute maliit-server& (after doing the
> > > things above):
> > >
> > > WARNING: QObject::connect: Cannot c
On Thursday 24 May 2012 14:24:40 Marco Martin wrote:
> On Thursday 24 May 2012, Thomas Pfeiffer wrote:
> > This is what I get when I execute maliit-server& (after doing the things
> > above):
> >
> > WARNING: QObject::connect: Cannot connect
> > Plasma::EffectWatcher::destroyed() to (null)::_k_x11
On Thursday 24 May 2012, Thomas Pfeiffer wrote:
>
> This is what I get when I execute maliit-server& (after doing the things
> above):
>
> WARNING: QObject::connect: Cannot connect
> Plasma::EffectWatcher::destroyed() to (null)::_k_x11FilterDestroyed()
> WARNING: void MIMPluginManagerPrivate::add
On Thursday 24 May 2012 11:15:11 Marco Martin wrote:
> just to get an idea where things may go wrong, try to do the whole procedure
> (that should already be done in scripts, that's weird)
>
> in konsole
> export QT_IM_MODULE=Maliit
> export QML_IMPORT_PATH=/usr/lib/kde4/imports
> killall maliit-
On Thursday 24 May 2012, Thomas Pfeiffer wrote:
> On Thursday 24 May 2012 00:06:29 Lamarque V. Souza wrote:
> > Em Wednesday 23 May 2012, Thomas Pfeiffer escreveu:
> > > On Monday 21 May 2012 19:26:08 Marco Martin wrote:
> > >
> > > I updated my Meego Devel image today, it installed Maliit & Co bu
On Thursday 24 May 2012 00:06:29 Lamarque V. Souza wrote:
> Em Wednesday 23 May 2012, Thomas Pfeiffer escreveu:
> > On Monday 21 May 2012 19:26:08 Marco Martin wrote:
> >
> > I updated my Meego Devel image today, it installed Maliit & Co but the
> > keyboard does not show up. Do I need to change a
Thomas Hi,
could you try to remove /home/mer/.kde and a reboot afterwards?
Cheers
Maurice
On May 23, 2012 at 8:48 PM Thomas Pfeiffer wrote:
> On Monday 21 May 2012 19:26:08 Marco Martin wrote:
>
> I updated my Meego Devel image today, it installed Maliit & Co but the
> keyboard does not s
Em Wednesday 23 May 2012, Thomas Pfeiffer escreveu:
> On Monday 21 May 2012 19:26:08 Marco Martin wrote:
>
> I updated my Meego Devel image today, it installed Maliit & Co but the
> keyboard does not show up. Do I need to change a config file or do
> something else for it to work?
When I
On Monday 21 May 2012 19:26:08 Marco Martin wrote:
I updated my Meego Devel image today, it installed Maliit & Co but the
keyboard does not show up. Do I need to change a config file or do something
else for it to work?
___
Active mailing list
Active@k
On Tuesday, May 22, 2012 00:09:49 Aaron J. Seigo wrote:
> On Monday, May 21, 2012 19:26:08 Marco Martin wrote:
> > that qml version not yet, the framework supports it (used to do the
> > numeric
> > keypad on the N9)
> > the qml version of maliit still needs a lot of bindings to be feature
> > comp
On Monday, May 21, 2012 19:26:08 Marco Martin wrote:
> that qml version not yet, the framework supports it (used to do the numeric
> keypad on the N9)
> the qml version of maliit still needs a lot of bindings to be feature
> complete with the old c++ version on the n9 as i hear, so more features
>
On Monday 21 May 2012 19:26:08 Marco Martin wrote:
> yeah, now sizes are still mostly hardcoded as the old qml one i started on
> (size is smaller to adapt to vivaldi)
> i plan to use dpi there as well.
Nice, I'm looking forward to it :)
> > I see two possible uses for the extra space on larger
On Monday 21 May 2012, Thomas Pfeiffer wrote:
> On 21.05.2012 17:56, Marco Martin wrote:
> > Hi all,
> > first of all sorry for the big cross posting but is a topic that is
> > important to all 3 lists.
>
> (Since I think my comments are Plasma Active specific, I only replied to
> our list)
>
> >
On 21.05.2012 17:56, Marco Martin wrote:
Hi all,
first of all sorry for the big cross posting but is a topic that is important
to all 3 lists.
(Since I think my comments are Plasma Active specific, I only replied to our
list)
Now that i had a bit of time to play with it, i got a plasma-theme
Hi all,
first of all sorry for the big cross posting but is a topic that is important
to all 3 lists.
As we discussed on irc a couple of times, in the Plasma Active project we
would like to use Maliit as system for the virtual keyboard.
Now that i had a bit of time to play with it, i got a plas
25 matches
Mail list logo
