Active Topics
-
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 3 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 15 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 15 hrs ago - more...
| The Following 6 Users Say Thank You to rinigus For This Useful Post: | ||
|
2018-07-09
, 08:59
|
|
Posts: 60 |
Thanked: 459 times |
Joined on Jan 2017
@ Innopolis, Russia
|
#102
|
Originally Posted by rinigus
Oh....now on nemomobile work 2-4 people...in now i just wont update all code...if you want help -welcome
Looking good!
However, I wonder whether there is much point in using maliit1 anymore. It seems that nemomobile is one of few (only one?) who has stick to that with others moving over to maliit2.
Since Jolla doesn't seem to be excited in releasing their keyboard*as an open-source project, as pointed out by sledges on one of the recent meetings, we probably need to find some other keyboard (maliit2?) to get fully open-sourced solution. If maliit2 is adopted by nemo, we could easily extend it with our latest presage predictor work which would benefit UT as well.
If wished, we could also sailfishify maliit2 and provide is as a competition. Which is obviously 'a great way' of spending enormous developers time which is pouring into Nemo and SFOS.
However, from the POV of efficiency, it maybe better to join more recent development and not try to patch up maliit1.
Now we have many critical bugs and many bugged applications...
| The Following 5 Users Say Thank You to neochapay For This Useful Post: | ||
|
|
2018-07-09
, 14:36
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#103
|
Originally Posted by neochapay
I can imagine that there are many critical bugs and the team behind is rather small. Hence the warning regarding the use of outdated keyboard component and its further development. But, if you do need to switch to Russian keyboard layout today, its probably easier to hack it together on maliit1
Oh....now on nemomobile work 2-4 people...in now i just wont update all code...if you want help -welcome
As for joining the effort - not yet. I am busy with maintaining own software and have few ideas that I would like to explore first to make it better. However, I did make sure that it should be easy to port the maps server to Nemo by adding QtQuick GUI as one of the frontends. As far as I understand, that should help. And, when working on something, looking on whether it can be applied to Nemo as well - such as work on keyboard predictor. But, yeah, sorry, would prefer not to get involved directly, yet, and work on other projects.
| The Following 4 Users Say Thank You to rinigus For This Useful Post: | ||
|
|
2018-07-11
, 12:44
|
|
Posts: 60 |
Thanked: 459 times |
Joined on Jan 2017
@ Innopolis, Russia
|
#104
|
Okay...now we have booster for nemomobile components: https://git.merproject.org/neochapay...ents/tree/nemo
And add boosting into libglacierapp: https://github.com/nemomobile-ux/lib...25eec93b24e1a3
Now applications start faster but we need to change all .desktop files i do it at this night
And add boosting into libglacierapp: https://github.com/nemomobile-ux/lib...25eec93b24e1a3
Now applications start faster
but we need to change all .desktop files i do it at this night
|
|
2018-07-12
, 11:31
|
|
Posts: 60 |
Thanked: 459 times |
Joined on Jan 2017
@ Innopolis, Russia
|
#105
|
Can you help me with i18n? Add plz another keyboard here https://github.com/neochapay/plugins...ile/layouts.js as mr
| The Following 2 Users Say Thank You to neochapay For This Useful Post: | ||
|
|
2018-07-12
, 19:44
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#106
|
Originally Posted by neochapay
PR created
Can you help me with i18n? Add plz another keyboard here https://github.com/neochapay/plugins...ile/layouts.js as mr
|
|
2018-07-12
, 20:59
|
|
Posts: 172 |
Thanked: 353 times |
Joined on Nov 2014
|
#107
|
Originally Posted by juiceme
Weird that you stripped away all accented characters. Isn't it a bit hard to type e.g. names with non-Finnish characters etc.? Sure you can always change the layout to another language but that seems just dumb IMHO. Or does Glacier UI have dead keys?
PR created
| The Following 3 Users Say Thank You to tmi For This Useful Post: | ||
|
|
2018-07-13
, 06:22
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#108
|
Originally Posted by tmi
You are correct, I was too hasty to flush the accents because finnish, like the rational language it is has none of those!
Weird that you stripped away all accented characters. Isn't it a bit hard to type e.g. names with non-Finnish characters etc.? Sure you can always change the layout to another language but that seems just dumb IMHO. Or does Glacier UI have dead keys?
I'll add them back and make another request.
| The Following User Says Thank You to juiceme For This Useful Post: | ||
|
|
2018-07-13
, 06:31
|
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#109
|
Originally Posted by juiceme
And done.
I'll add them back and make another request.
| The Following 2 Users Say Thank You to juiceme For This Useful Post: | ||
|
|
2018-07-16
, 08:22
|
|
Posts: 60 |
Thanked: 459 times |
Joined on Jan 2017
@ Innopolis, Russia
|
#110
|
Add application template for developing nemo applications over sailfish sdk https://github.com/nemomobile-ux/nemo-template-app
| The Following 6 Users Say Thank You to neochapay For This Useful Post: | ||
 |
| Tags |
| glacierui, nemo mobile |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 12:12.
However, I wonder whether there is much point in using maliit1 anymore. It seems that nemomobile is one of few (only one?) who has stick to that with others moving over to maliit2.
Since Jolla doesn't seem to be excited in releasing their keyboard*as an open-source project, as pointed out by sledges on one of the recent meetings, we probably need to find some other keyboard (maliit2?) to get fully open-sourced solution. If maliit2 is adopted by nemo, we could easily extend it with our latest presage predictor work which would benefit UT as well.
If wished, we could also sailfishify maliit2 and provide is as a competition. Which is obviously 'a great way' of spending enormous developers time which is pouring into Nemo and SFOS.
However, from the POV of efficiency, it maybe better to join more recent development and not try to patch up maliit1.