Re: [SailfishDevel] A kickoff meeting about SailfishOS, open source, collaboration, way forward @ 15 April, 15:00 UTC
W dniu 07.04.2014 23:18, Robin Burchell pisze: But don’t let that criticism of an individual tar an entire company, 80+ people with their own opinions, minds, and thoughts by the same brush - especially if you expect those same people to listen to your thoughts. No one is tarring an entire company if that would be the thing I wouldn't be writing in my previous mail: "I think many people want good like you said" and (in context of those actions I criticize) "in some heads" (some != most/all) With all respect Robin but I think you are a bit overreacting here. I can write that Jolla does everything perfect, but that would be with harm to your company. I try to be fair as possible, you can ask Stskeeps what I've done together with a friend a week ago when some guy on the conference during his talk gave a clearly false and unfair statement about Jolla. Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] QMagnetometer info from Jolla
Hi Lorn, Thanks. I found the show_magneticflux.py example and modified it to use PyQt5 and QtSensors. I see that it gives me sensible raw values, but the geo-corrected values do not change - and it is geo-corrected values I am trying to access. When I modify my code to access raw values, it's OK. I'm not sure how to check the sensorfw version or where to find journal logs - if you can advise me on this I will send this information. Regards, Robin. ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A kickoff meeting about SailfishOS, open source, collaboration, way forward @ 15 April, 15:00 UTC
On 07 Apr 2014, at 16:11, Filip Kłębczyk wrote: > "We don't want the community to work on the bugs and take our jobs!". I don’t know any of the context of the discussion you’re referring to, so I won’t say anything about that particular case. I will say this: You’re of course free to criticise whatever you want. But don’t let that criticism of an individual tar an entire company, 80+ people with their own opinions, minds, and thoughts by the same brush - especially if you expect those same people to listen to your thoughts. Taking an offensive stance is a great way to elicit defensive reactions unnecessarily (and unhelpfully). ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A kickoff meeting about SailfishOS, open source, collaboration, way forward @ 15 April, 15:00 UTC
W dniu 06.04.2014 23:11, Robin Burchell pisze: On 05 Apr 2014, at 10:21, Thomas B. Rücker mailto:tho...@ruecker.fi>> wrote: Reading this I can't help but wonder if Jolla now claims ownership of Mer/Nemo then. Even with fancy hat changing. Bringing this discussion up in a strictly Sailfish context implies this. I think you’ve read a little much into things, but I’d like to point out the obvious here: Jolla are doing the majority of the work in these two projects. So purely in terms of governance and technical knowledge, they are in a position of quite a bit of power. Now, that having been said, the work on these projects has always (without exception) been done in the public realm, with the aim of collaborating with others, Maybe the aim was collaborating with the outside world, but practical implementation of that aim was far away from how it should look like and what community expected. to some degrees of success. We’ve seen people make tools/hacks/fixes around that stuff, and that’s great. It might be improvable, but it’s a positive thing already. I would say many of those hacks were despite all odds and Jolla not helping or even setting up ridiculous obstacles, where things could have been done the easy way, but not instead "dirty" hacks were the only possibility. A bit of an example of general attitude from a bit different area is if you want Sailfish OS source code you need to ask for a CD/DVD whereas it could also have been put online, which would save time and money for both sides. Well in the end tbr uploaded it, but frankly speaking it shouldn't be his job to make things easier, but in Jolla own interest. I see it as kind of attitude - if we don't know what to do in a company, let's use old Nokia ways of solving problems (even if they are nowadays something awkward or some corpo-ridiculousness that doesn't fit into something you would expect from a startup). Community can forgive a lot - annoying bugs, simcard holder problems, sudden reboots and other stuff which can happen to every company releasing a new product, but on condition that such company really cares about community and makes things easier for collaboration, not harder. That should especially be taken into account that some of the community memebers, were actively spreading word about Jolla and how this company is very open and unlike. I don't want to look at some of my friends eyes who bought Jolla after my recommendation and say "Well it's not that open in terms of collaboration as they promised, sorry it seems we've been misleaded". I guess what I’m trying to say is that, from a strictly open source point of view, the ones doing the work dictate the direction - one could even say this implies ownership, yes. But on the other hand, while I can’t speak for the entire company, I (and the folks I know and work with on a daily basis) have collaboration and cooperation at heart, even if execution could be improved on - which is what provided the impetus for this thread. I think many people want good like you said, but on the other side community clashes with such employees comments (when asking for issues list/bugs/roadmap of Nemo MW): "We don't want the community to work on the bugs and take our jobs!". It shows the problem "community helping == taking our jobs" existing in some heads. And yes I can even look for who said sth like that on IRC in one of the Jolla related public channels if you don't believe such statements were said by your colleagues. Regards, Filip ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] Landscape mode in Sailfish?
ok I have managed to rotate my display and convert the touch co-ordinates
but I have a lot flashes on the screen. I presume it has to do with the
call to glScissor
At some places in my code I call glScissor and glGetIntegerv modify and
retrieve the scissor box. If I don't call these there is no problem I have
no flashes but obviously my rendering is wrong as I render outside my
rectangle.
Does the rotation matrix (either in projection or model view mode) affect
the glScissor and glGetIntegerv calls or do I have to manually calculate
the rotation for the scissor box?
The code I use for scissoring is:
//-
RECT Presenter::ClippingRegion() const
{
RECT rc;
SetRect( &rc, 0, 0, mnScreenWidth, mnScreenHeight);
if ( glIsEnabled(GL_SCISSOR_TEST) )
{
GLint clip[4];
glGetIntegerv( GL_SCISSOR_BOX, &(clip[0]) );
SetRect( &rc, clip[0], clip[1], (clip[0]+clip[2]), (clip[1]+clip[3] );
}
return rc;
}
//-
void Presenter::ClippingRegion(const RECT& rc)
{
glEnable( GL_SCISSOR_TEST );
GLsizei width = rc.right - rc.left;
GLsizei height = rc.bottom - rc.top;
GLint x = rc.left;
GLint y = rc.top;
GLint y_modified = mnScreenHeight-(y+height);
glScissor(x, y_modified, width, height);
}
Where in the above code RECT is a struct similar to Microsoft's RECT and
SetRect(left, top, right, bottom) is a function similar to Microsoft's for
setting left, top, right and bottom co-ordinates for a RECT.
So do I have to calculate the rotation for the parameters or is it
automatically done by the rotation matrix?
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] Question creating full screen SDL window
Hi,
I've submitted a patch for this to upstream SDL now:
https://bugzilla.libsdl.org/show_bug.cgi?id=2481
For testing the changes, RPMs with the change applied are available here:
http://repo.merproject.org/obs/home:/thp:/sdl2/1.0.4.20_armv7hl/armv7hl/
You can install RPM files with "pkcon install-local ".
Downstream PR:
https://github.com/nemomobile-packages/libsdl/pull/1
HTH :)
Thomas
On 2014-04-04 18:57, Iosif Hamlatzis wrote:
I have different behaviour creating a full screen SDL window between
Sailfish OS and other mobile platforms I have tested.
I am using the same source code below:
SDL_Window* pWindow = SDL_CreateWindow("", 0, 0, 0, 0,
SDL_WINDOW_OPENGL|SDL_WINDOW_FULLSCREEN|SDL_WINDOW_SHOWN);
int ActualScreenWidth_ = -1;
int ActualScreenHeight_ = -1;
SDL_GetWindowSize(pWindow, &ActualScreenWidth_, &ActualScreenHeight_);
In all cases including Sailfish OS I get the correct width and height of the
device, but (yes there is a but) on Sailfish OS nothing is drawn on screen when
I later try to render an image. I have tested this on the emulator and on the
actual device. Also I have tested this not only with my code but also with code
I've found athttps://github.com/thp/sdl2-opengles-test
If I modify my code to:
SDL_Window* pWindow = SDL_CreateWindow("", 0, 0, 0, 0,
SDL_WINDOW_OPENGL|SDL_WINDOW_FULLSCREEN|SDL_WINDOW_SHOWN);
int ActualScreenWidth_ = -1;
int ActualScreenHeight_ = -1;
SDL_GetWindowSize(pWindow, &ActualScreenWidth_, &ActualScreenHeight_);
*SDL_DestroyWindow(pWindow);*
pWindow = SDL_CreateWindow("",
0, 0,
*ActualScreenWidth_, ActualScreenHeight_*,
SDL_WINDOW_OPENGL|SDL_WINDOW_FULLSCREEN|SDL_WINDOW_SHOWN);
Which I think is strange since in the first place the*pWindow* I get from the
first call is valid and the values I get from querying the window size
correspond to the device's resolution.
Besides the first code snippet works on all platforms I've tested from plain PC
to mobile platforms such as webOS. BlackBerry (PlayBook and BB10) and iOS
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
On 07.04.2014 10:25, Andrew den Exter wrote: We're switching over to using the plugin as part of updating to Qt 5.2. That won't be part of the immediately pending update, but probably the one after that. Andrew Thanks for this info. Stefan ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
> Am 20.03.2014 08:03, schrieb Stefan Brand: > Hello, > > Are there any news on this issue? ETA for a working QML VideoOutput as > Viewfinder (=inclusion of the plugin in Sailfish) or a supported > viewfinder element in an allowed import? We're switching over to using the plugin as part of updating to Qt 5.2. That won't be part of the immediately pending update, but probably the one after that. Andrew ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] How to access the viewfinder of the QCamera?
Hello again, Am 20.03.2014 08:03, schrieb Stefan Brand: Hello, Am 18.02.2014 09:57, schrieb Andrew den Exter: Hi, As the Sailfish.Media 1.0 import is not allowed for applications in harbour, is there any way to write an application using the Camera with a Viewfinder in QML that would pass harbour QA at the moment? Or do we have to wait for the adapted VideoOutput? The adaptation is in the form of a plugin to QtMultimedia and the code is now up on github at https://github.com/nemomobile/nemo-qtmultimedia-plugins. Hopefully that will be of some help to you while we work to get that into an update. it seems this plugin was not part of the last update (10.4.20), at least VideoOutput is still not working with the camera for me. Is there any ETA for this to arrive in an official update, so proper use of the camera inside apps becomes possible? Or is there any way to implement something like this plugin inside an app without breaking harbour rules (as it seems now, the plugin uses libraries that are not allowed in harbour apps either). Are there any news on this issue? ETA for a working QML VideoOutput as Viewfinder (=inclusion of the plugin in Sailfish) or a supported viewfinder element in an allowed import? Regards, Stefan Brand ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] A kickoff meeting about SailfishOS, open source, collaboration, way forward @ 15 April, 15:00 UTC
>Jolla are doing the majority of the work in these two projects. So purely in terms of governance and technical knowledge, they are in a position of quite a bit of power. Now, that having been said, the work on these projects has always >(without exception) been done in the public realm, with the aim of collaborating with others, to some degrees of success. We've seen people make tools/hacks/fixes around that stuff, and that's great. It might be improvable, but it's a >positive thing already. >I guess what I'm trying to say is that, from a strictly open source point of view, the ones doing the work dictate the direction - one could even say this implies ownership, yes. But on the other hand, while I can't speak for the entire >company, I (and the folks I know and work with on a daily basis) have collaboration and cooperation at heart, even if execution could be improved on - which is what provided the impetus for this thread. The "dictation of direction" is a side-effect of evolution - as in, Jolla is the main contributor *because* Jolla relies on Mer/Nemo for Sailfish, *because *Jolla has needs for features / bug fixes etc. This is not dictatorship, this is more like innovation IMO. Jolla is a company, heck, even a DEVICE VENDOR nowadays (thanks to the OH) and as such, has it's own development plan. OpenRepos is what comes as close to Maemo-extras as it can nowadays, I believe. People are free to install whatever they want on their Jolla, but Jolla needs to follow up on their development. On Mon, Apr 7, 2014 at 12:11 AM, Robin Burchell wrote: > > On 05 Apr 2014, at 10:21, Thomas B. Rücker wrote: > > Reading this I can't help but wonder if Jolla now claims ownership of > Mer/Nemo then. Even with fancy hat changing. Bringing this discussion up > in a strictly Sailfish context implies this. > > > I think you've read a little much into things, but I'd like to point out > the obvious here: > > Jolla are doing the majority of the work in these two projects. So > purely in terms of governance and technical knowledge, they are in a > position of quite a bit of power. Now, that having been said, the work on > these projects has always (without exception) been done in the public > realm, with the aim of collaborating with others, to some degrees of > success. We've seen people make tools/hacks/fixes around that stuff, and > that's great. It might be improvable, but it's a positive thing already. > > I guess what I'm trying to say is that, from a strictly open source > point of view, the ones doing the work dictate the direction - one could > even say this implies ownership, yes. But on the other hand, while I can't > speak for the entire company, I (and the folks I know and work with on a > daily basis) have collaboration and cooperation at heart, even if execution > could be improved on - which is what provided the impetus for this thread. > > Power doesn't necessarily mean dominance. > > There are other downstream projects relying on Mer and I'd expect this > to be discussed with them, in a completely "vendor neutral" setting. Mer > used to be big about this, before it got dragged into a "ship a product" > race of one of the involved parties. > > > This is open source. We can't dictate what other people do. And if we're > polite, we talk first, of course. I do think that some of the things you > were replying to are about addressing a very real problem, though, which is > that contributing to Nemo (and Sailfish, Mer, and the surrounding universe) > has a lot of rough edges. It won't be a panacea, but it's something to > start thinking on. > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
