maemo.org - Talk
Page 70 of 88 « First 606869 70 717280 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms (https://talk.maemo.org/showthread.php?t=87764)

freemangordon 2013-07-19 05:49
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by shmerl (Post 1360029)
The same what? Switch to Qt and RPM was in Meego. Mer continues it. Nothing new in this aspect. You are several years late to complain.
Oh, I am not complaining. I am talking about the behavior here - one has something that is working fine (or almost), but he throws it through the window because of some blurry reasoning. Instead of polishing what he already has. The point is - IMO it is wrong to make such a major change when you are on a hurry to release a device, as it will delay that release. No matter how good you are.

The reference to GTK and .deb was in that regard - Nokia did the same when all of us were expecting the step 5/5. And we all know what the result was/is.

shmerl 2013-07-19 06:22
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
What was working fine, you mean Harmattan? Jolla has no way to reuse that, since it's closed (Nokia controlled). Jolla is using what's available - Mer + Nemo which are open and which use Qt and RPM all the way since Meego was using them. Therefore Jolla didn't throw anything out - on the contrary, they are building on the accumulated effort. There is really no novelty here. Mer exists for a while already, basically even before Meego was officially abandoned.

qwazix 2013-07-19 06:25
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by MartinK (Post 1360004)
@wayland vs X11
There is still the issue of network transparency. While not really that important in out case (mobile/embedded application development), it still stands that it is something X11 has and Wayland is lacking so far.

Yes, this has been already discussed elsewhere quite heavily and yes, it should be possible to do it with Wayland using pixel scrapping.

But it still stands there is no such implementation in the current Wayland/Weston implementation.

Network transparency use-cases
From personal experience these work just fine on local (100 Mb Ethernet) network & are quite handy(as the application context stays on one machine, but the application can be used on many other machines):
  • graphical terminal emulators
  • Geany (wrote my bachelors thesis like this) and other editors
  • Thunderbird
  • Inkscape
  • modRana :)
http://www.youtube.com/watch?v=RIctzAQOe44
According to this, X in it's current implementation is not network transparent, and wayland does remoting.

qwazix 2013-07-19 06:26
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by freemangordon (Post 1360030)
Oh, I am not complaining. I am talking about the behavior here - one has something that is working fine (or almost), but he throws it through the window because of some blurry reasoning. Instead of polishing what he already has. The point is - IMO it is wrong to make such a major change when you are on a hurry to release a device, as it will delay that release. No matter how good you are.

The reference to GTK and .deb was in that regard - Nokia did the same when all of us were expecting the step 5/5. And we all know what the result was/is.
Regardless, I couldn't agree more.

edit: however the reasoning isn't blurry at all. Making 60fps is really hard with X (try scrolling in harmattan with vkb open for example) and debugging is way easier using wayland.

Dave999 2013-07-19 06:53
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by jalyst (Post 1359744)
Yeah but they've only gone this way because the Sailfish_Alliance (remember that, WTF ever happened to it!?) has taken so freaking long to get off the ground.
If they had stopped "fart-arsing" around MONTHS ago, both projects could be working on the same UI/UX now, or very soon...
Sailfish alliance working with future interruptions.
I think it's a product of lacking constant strategy and changing CEO too often. Either way, I'm sure even jolla understudy it pretty lame to have an alliance when you are on your own. That's why it's dead/quiet.

freemangordon 2013-07-19 11:37
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by shmerl (Post 1360034)
What was working fine, you mean Harmattan? Jolla has no way to reuse that, since it's closed (Nokia controlled). Jolla is using what's available - Mer + Nemo which are open and which use Qt and RPM all the way since Meego was using them. Therefore Jolla didn't throw anything out - on the contrary, they are building on the accumulated effort. There is really no novelty here. Mer exists for a while already, basically even before Meego was officially abandoned.
No, I meant what was shown a couple of months ago and what there is an alpha SDK for. Sailfish.

@qwazix: sure it is not, but if n900 with its old SGX530 and crappy drivers is capable to stream video from the main camera to GL texture with > 40-50 fps while the window is in the tasknav, just imagine what newer HW/drivers are capable of.

shmerl 2013-07-19 13:35
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
freemangordon: Qt 5 + Wayland vs Qt 4.8 + X11? I personally think it's great they went with Wayland. Sitting on X11 is getting annoying already, and if they can squeeze EGL drivers for Wayland from their SoC manufacturer - it's a really great achievement. I really hope they aren't going to use Wayland based on libhybris with bionic drivers in their own handset.

pali 2013-07-19 13:45
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by shmerl (Post 1360112)
I really hope they aren't going to use Wayland based on libhybris with bionic drivers in their own handset.
Why then they worked on libhybris and support to use android drivers??

shmerl 2013-07-19 14:03
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
pali: To ease porting Sailfish to crippled hardware, where no glibc drivers are available and there is no way to influence manufacturer to release them and no open drivers either. Hopefully in their own case they can get something since they plan a significant volume of production.

Sailfish isn't supposed to be limited to Jolla's handset only.

marbleuser 2013-07-19 16:01
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
 
Quote:
Originally Posted by mikecomputing (Post 1359995)
Seriously it sounds more like people want X11 to tell others "hey I can run foobar X11 app on my phone" even if that X11 app will be a pointless toy cause it is unusable on a phone anyway.
so in other words if they bought out 2 versions of sailfish
1. no x11 compatibility 'consumer version'
2. x11 compatibility 'backward compatible version' capable of running x11(read old qt4/gtk2 apps), then you'd buy the consumer version?

yeah....... no.

edit: can someone confirm/deny that as a result of no x11 , that all those python maemo/meego apps that we all love can't be ported, and all new apps will need to to be re/written in c++?

don't you like any of those msemo/meego apps mikecompting?


All times are GMT. The time now is 22:01.
Page 70 of 88 « First 606869 70 717280 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8