*** nahka has quit IRC | 00:07 | |
*** jayrulez has joined #sailfishos | 00:14 | |
*** yunta has quit IRC | 00:19 | |
*** yunta has joined #sailfishos | 00:20 | |
*** piggz has joined #sailfishos | 00:23 | |
*** piggz has quit IRC | 00:33 | |
*** triggerhappy has joined #sailfishos | 00:41 | |
*** piee has joined #sailfishos | 00:41 | |
*** piee has quit IRC | 00:46 | |
*** M4rtinK has quit IRC | 01:06 | |
*** XeN has joined #sailfishos | 01:16 | |
*** kaxing has joined #sailfishos | 02:11 | |
*** simathur has joined #sailfishos | 03:11 | |
*** lpotter has quit IRC | 03:13 | |
*** simathur has quit IRC | 03:16 | |
*** simathur has joined #sailfishos | 03:16 | |
*** diegoyam has quit IRC | 03:39 | |
*** furikku has joined #sailfishos | 03:58 | |
*** martyone has joined #sailfishos | 03:59 | |
*** ericcc has joined #sailfishos | 04:01 | |
*** VitaBushido_ has joined #sailfishos | 04:03 | |
*** piee has joined #sailfishos | 04:05 | |
*** Custodian has joined #sailfishos | 04:07 | |
*** piee has quit IRC | 04:22 | |
*** Eismann_ has quit IRC | 04:37 | |
*** f3an0r has joined #sailfishos | 04:43 | |
*** VDVsx has quit IRC | 04:58 | |
*** maninc has joined #sailfishos | 04:58 | |
*** VDVsx has joined #sailfishos | 05:07 | |
*** lpotter has joined #sailfishos | 05:08 | |
*** ericcc_ has joined #sailfishos | 05:12 | |
*** louisdk has quit IRC | 05:14 | |
*** ericcc has quit IRC | 05:14 | |
*** maninc has quit IRC | 05:17 | |
*** maninc has joined #sailfishos | 05:19 | |
*** jayrulez has quit IRC | 05:26 | |
*** maninc has quit IRC | 05:30 | |
*** dhbiker has joined #sailfishos | 05:38 | |
*** vogon has joined #sailfishos | 05:42 | |
*** dhbiker has quit IRC | 05:43 | |
*** dhbiker has joined #sailfishos | 05:43 | |
*** vogon has quit IRC | 05:53 | |
*** triggerhappy has quit IRC | 06:04 | |
*** triggerhappy has joined #sailfishos | 06:05 | |
*** Pat_o has joined #sailfishos | 06:08 | |
*** VitaBushido_ has quit IRC | 06:17 | |
*** maninc has joined #sailfishos | 06:26 | |
*** f3an0r has quit IRC | 06:28 | |
*** maninc has quit IRC | 06:31 | |
*** Pali has joined #sailfishos | 06:32 | |
*** maninc has joined #sailfishos | 06:33 | |
*** Sfiet_Konstantin has joined #sailfishos | 06:45 | |
*** jjanvier has joined #sailfishos | 06:52 | |
*** ericcc has joined #sailfishos | 06:56 | |
*** toartist has joined #sailfishos | 06:59 | |
*** ericcc_ has quit IRC | 07:00 | |
*** jpetersen has joined #sailfishos | 07:01 | |
*** Xruxa has joined #sailfishos | 07:04 | |
*** gabriel9|work has joined #sailfishos | 07:04 | |
*** b0bben has joined #sailfishos | 07:15 | |
*** niqt has joined #sailfishos | 07:17 | |
*** itbaron has joined #sailfishos | 07:19 | |
*** martyone_ has joined #sailfishos | 07:20 | |
*** martyone has quit IRC | 07:21 | |
*** f3an0r has joined #sailfishos | 07:29 | |
*** njeiseck has joined #sailfishos | 07:35 | |
*** martyone_ has quit IRC | 07:36 | |
*** martyone has joined #sailfishos | 07:37 | |
*** huanming has joined #sailfishos | 07:38 | |
huanming | Hey, I got a problem when building sailfishos example project named componentgalley. It says that "Fatal: SailfishOS-i486-x86 is an invalid sb2 target". | 07:39 |
---|---|---|
huanming | Can anyone help me? | 07:39 |
huanming | My os is windows 8 professional | 07:39 |
huanming | it is a 64-bit operating system | 07:40 |
*** maninc has quit IRC | 07:41 | |
Yaniel | hmm sounds like your toolchain is misconfigured or something.. | 07:41 |
Yaniel | lbt^ | 07:41 |
huanming | the message in the window "compile output" is " The process "C:\Users\*\AppData\Roaming\SailfishAlpha\mer-sdk-tools\MerSDK\SailfishOS-i486-x86\qmake.cmd" exited with code 1. | 07:45 |
huanming | Error while building/deploying project new (kit: MerSDK-SailfishOS-i486-x86) | 07:45 |
huanming | When executing step 'qmake' " | 07:45 |
kaltsi | huanming: which sdk version? Is it the qt5 alpha? Did you have the first alpha installed previously? | 07:45 |
huanming | no, i have not installed any alpha version yet. | 07:46 |
Yaniel | there are only alpha versions of the sailfish SDK | 07:46 |
huanming | sorry, i have not installed any alpha version before | 07:47 |
huanming | it is the qt5 alpha | 07:47 |
*** Pat_o has quit IRC | 07:47 | |
huanming | i have installed on my os now | 07:47 |
kaltsi | ok.. I don't have a windows machine to test it on here myself.. do you see the virtualbox machines running.. the emulator and the MerSDK build machine? | 07:48 |
*** maninc has joined #sailfishos | 07:48 | |
*** Pat_o has joined #sailfishos | 07:48 | |
huanming | both of them run well | 07:48 |
kaltsi | huanming: have you tried restarting windows after you ran the installer? :) | 07:54 |
*** Pat_o has quit IRC | 07:54 | |
huanming | hmm, i have not restarted it yet | 07:55 |
huanming | should i restart it now? | 07:56 |
kaltsi | don't know if it helps.. you could also try to ask on the sailfish-devel mailing list, which might have more users with windows 8.. but do try restarting | 07:56 |
huanming | ok, i try restarting now | 07:57 |
*** huanming has quit IRC | 07:57 | |
*** b0bben has quit IRC | 08:01 | |
*** nahka has joined #sailfishos | 08:03 | |
*** f3an0r has quit IRC | 08:05 | |
*** b0bben has joined #sailfishos | 08:05 | |
*** huanming has joined #sailfishos | 08:06 | |
huanming | I have restarted my windows 8 | 08:07 |
huanming | but the result is still the same | 08:07 |
*** njeiseck has left #sailfishos | 08:07 | |
kaltsi | do you get it also with the default template application? "File/New file or project" -> SailfishOS Qt Quick Application etc.. | 08:08 |
aknight | there are 2 icons in the lower-left for connecting the ide to the vms | 08:11 |
huanming | i have created one project as you said, but the result is the same | 08:11 |
aknight | they must be in a "red" state to be working | 08:12 |
huanming | i have followed the instruction in the website step by step | 08:12 |
kaltsi | huanming: ok sad to hear it, I wish I had a windows machine to test it myself | 08:13 |
huanming | well, thank you all the same. it seems that it does not work on my windows, and now i am going to try it on my linux | 08:14 |
*** huanming has quit IRC | 08:17 | |
aknight | i have no problems under windows 8, except that the SailfishOS "mode" doesn't really work | 08:19 |
*** Pat_o has joined #sailfishos | 08:19 | |
aknight | but building/deploying works fine | 08:19 |
aknight | you just need to activate the vms using the lower-left buttons | 08:19 |
*** maninc has quit IRC | 08:30 | |
*** exec_s has joined #sailfishos | 08:33 | |
*** Pat_o has quit IRC | 08:38 | |
*** cxl000 has joined #sailfishos | 08:40 | |
*** fk_lx has left #sailfishos | 08:41 | |
*** maninc has joined #sailfishos | 08:42 | |
*** t7 has joined #sailfishos | 08:43 | |
*** f3an0r has joined #sailfishos | 08:44 | |
*** maninc has quit IRC | 08:44 | |
*** arcean has joined #sailfishos | 08:46 | |
auri__ | Aard: ping | 08:49 |
*** cxl000 has quit IRC | 08:50 | |
*** Pat_o has joined #sailfishos | 08:52 | |
Aard | auri__: pong | 08:57 |
*** cxl000 has joined #sailfishos | 08:57 | |
*** ericcc_ has joined #sailfishos | 08:59 | |
*** b0bben has quit IRC | 09:01 | |
*** ericcc has quit IRC | 09:03 | |
*** Pat_o has quit IRC | 09:03 | |
*** b0bben has joined #sailfishos | 09:04 | |
*** maninc has joined #sailfishos | 09:06 | |
*** tg has quit IRC | 09:09 | |
*** tg has joined #sailfishos | 09:11 | |
*** Superpelican has joined #sailfishos | 09:17 | |
*** b0bben has quit IRC | 09:25 | |
Superpelican | SfietKonstantin:Would it be more efficient to specify the size of a QVector at declaration time? | 09:31 |
Superpelican | instead of just doing a QVector<int> myvector | 09:31 |
Superpelican | and then insert/push_back all the ints? | 09:32 |
Superpelican | Sfiet_Konstantin: ^ | 09:32 |
Sfiet_Konstantin | Superpelican: what are you trying to do ? | 09:33 |
Sfiet_Konstantin | (and I think you can) | 09:33 |
Superpelican | Sfiet_Konstantin:eh | 09:33 |
Sfiet_Konstantin | (or you can do plain C, but that's useless in modern computing) | 09:33 |
Superpelican | well it's not very easy to explain | 09:33 |
Superpelican | I've thought of arrays too | 09:34 |
Sfiet_Konstantin | Superpelican: reading the docs (once again), you can see that QVector have a constructor taking an int for size | 09:34 |
Sfiet_Konstantin | so ... | 09:34 |
Superpelican | but I need to be able to remove things during runtime from my array/vector | 09:34 |
Superpelican | yes I know | 09:34 |
Yaniel | plain C and useless? | 09:34 |
Superpelican | I'm reading the docs | 09:34 |
Superpelican | and also in Qt Creator as you suggested ;) | 09:34 |
Sfiet_Konstantin | Yaniel: nope, but if you want efficiency, better use plain C | 09:34 |
Superpelican | but | 09:35 |
Superpelican | my question is | 09:35 |
Sfiet_Konstantin | but the gain in memory by allocating an array of 4 entries and a QVector is negligeable in modern computing with gigs of ram | 09:35 |
*** b0bben has joined #sailfishos | 09:35 | |
Superpelican | well I wouldn't say that mobile devices have unlimited resources | 09:35 |
Sfiet_Konstantin | Superpelican: they have ~1 gig of ram | 09:35 |
Superpelican | but still | 09:35 |
Superpelican | my question is... | 09:35 |
Sfiet_Konstantin | well do you really think that a bunch of int will take too much space | 09:36 |
Superpelican | would it be faster/less space consuming/more efficient | 09:36 |
Sfiet_Konstantin | Superpelican: it will be more efficient | 09:36 |
Sfiet_Konstantin | but depends on the size of your array | 09:36 |
Sfiet_Konstantin | vectpr | 09:36 |
Superpelican | well it's 10 ints | 09:36 |
Sfiet_Konstantin | preallocate is _always_ more efficient | 09:36 |
Superpelican | I'll just show you the code | 09:36 |
Superpelican | ok | 09:36 |
Sfiet_Konstantin | however, it might not be _much more_ efficient | 09:37 |
Yaniel | 10 ints? just use whatever is easy | 09:37 |
Sfiet_Konstantin | Yaniel: yes, we are not talking about 10^n ints :) | 09:37 |
Superpelican | So it's more efficient | 09:37 |
Superpelican | wait | 09:37 |
Superpelican | I'll make a paste | 09:37 |
Sfiet_Konstantin | depending on the operations as well | 09:37 |
Sfiet_Konstantin | insert in vector ? or only append prepend ? | 09:38 |
Sfiet_Konstantin | how much, how is the data set expected to grow etc. | 09:38 |
Sfiet_Konstantin | Superpelican: btw, in your case, QVector is enough, but for generic case, QList might be better | 09:40 |
Sfiet_Konstantin | especially storing classes / structs | 09:40 |
Superpelican | Sfiet_Konstantin:http://paste.kde.org/p43aa92e7/ | 09:41 |
Superpelican | oh and the push_back is insert/append at the end of the vector | 09:41 |
Superpelican | not somewhere in between | 09:41 |
Sfiet_Konstantin | more efficient | 09:41 |
Superpelican | it's just about filling the vector with 1,2,3 etc. | 09:41 |
Sfiet_Konstantin | but for 10 ints the gain is unnoticiable | 09:41 |
Superpelican | Sfiet_Konstantin:What is more efficient? | 09:42 |
Sfiet_Konstantin | preallocating | 09:42 |
Superpelican | so that is QVector<int> myvector(10)? | 09:42 |
Sfiet_Konstantin | it is always more efficient, since you don't recreate memory chunks etc | 09:42 |
Sfiet_Konstantin | yes | 09:42 |
Superpelican | ok | 09:42 |
Superpelican | Sfiet_Konstantin:And would removing things during runtime cost a lot? | 09:43 |
Superpelican | performance/memory-wise? | 09:43 |
Superpelican | eh | 09:43 |
Superpelican | I mean .erase() | 09:43 |
Superpelican | or whatever it is called in Qt | 09:43 |
Superpelican | haven't read the whole QVector doc | 09:43 |
Sfiet_Konstantin | Superpelican: yes, it costs "a lot" | 09:43 |
Superpelican | Sfiet_Konstantin:Should I rewrite my program again? | 09:43 |
Sfiet_Konstantin | basically when you do an insertion / removal, in memory, the whole list is copied | 09:43 |
Sfiet_Konstantin | no | 09:44 |
Superpelican | so I can use a plain C array? | 09:44 |
Sfiet_Konstantin | please no | 09:44 |
Sfiet_Konstantin | :P | 09:44 |
Sfiet_Konstantin | NEVER | 09:44 |
Superpelican | It would make it more complicated | 09:44 |
Sfiet_Konstantin | if you have C++ conveinent containers, NEVER use plain C | 09:44 |
Sfiet_Konstantin | it costs "a lot" | 09:44 |
Sfiet_Konstantin | basically a few cycles of CPU, and some memory | 09:44 |
Sfiet_Konstantin | because you recreate a whole list | 09:44 |
Superpelican | :nod: | 09:44 |
Sfiet_Konstantin | it is actually also what's happen when you append, but in a lesser impact | 09:45 |
Sfiet_Konstantin | ie, if you do an insert / erase, you have a O(n) complexity | 09:45 |
Sfiet_Konstantin | still, for a CPU going at 1 Ghz, it consts nothing in time | 09:45 |
Superpelican | I've never understood the O notation | 09:45 |
Sfiet_Konstantin | <1ms | 09:45 |
Sfiet_Konstantin | n is the number of elements in your list | 09:45 |
Sfiet_Konstantin | O(n) means costs C x n atomic operations like allocate memory, set a variable in memory, free memory etc | 09:46 |
Sfiet_Konstantin | O(..) means constant times what's inside your brackets | 09:46 |
*** b0bben has quit IRC | 09:46 | |
Sfiet_Konstantin | so if you have a list of 10 elements, removing one in the middle will cost in average c x 10 operations, (c is most likely 3 or 4) | 09:46 |
Superpelican | What's the C then? | 09:47 |
Sfiet_Konstantin | (1 for allocate, one for copy, one for free) | 09:47 |
Sfiet_Konstantin | well, c is useless if your n is huge | 09:47 |
*** maninc has quit IRC | 09:47 | |
Sfiet_Konstantin | if n is 10^50, then if c is 2 or 5 don't depend much | 09:47 |
Sfiet_Konstantin | because you might want to save from the n | 09:47 |
*** mikhas has joined #sailfishos | 09:47 | |
Sfiet_Konstantin | like if you go from 2 x n to 5 x log(n), then you save a lot | 09:48 |
Sfiet_Konstantin | 2 x 10^50 or 5 x 50 | 09:48 |
Superpelican | Sfiet_Konstantin:The docs say QList is better for insertions and removals in the middle of the array/vector/list? | 09:49 |
Sfiet_Konstantin | but basically, your program is about n = 10 here | 09:49 |
Superpelican | should I use those? | 09:49 |
Sfiet_Konstantin | so nothing problematic | 09:49 |
Sfiet_Konstantin | QList is better because instead of copying the data represented by T it copies a pointer on T | 09:49 |
*** Pat_o has joined #sailfishos | 09:49 | |
Sfiet_Konstantin | that's better if sizeof(T) > sizeof(T*) | 09:49 |
Superpelican | but a pointer is as big as an int | 09:49 |
*** b0bben has joined #sailfishos | 09:49 | |
Sfiet_Konstantin | exact | 09:49 |
Superpelican | so that probably won't have much benefit | 09:50 |
Sfiet_Konstantin | so in your case QList<int> will cost more memory | 09:50 |
Sfiet_Konstantin | so stick with QVector | 09:50 |
Superpelican | So it'll only work if you have a list of structs or something like that? | 09:50 |
Sfiet_Konstantin | but about writing in C, if you do your algo bad, the C perf can be worse than the C++ perf, so stick with Qt's containers. They are quite optimized | 09:50 |
Sfiet_Konstantin | Superpelican: yes | 09:50 |
Superpelican | ok | 09:50 |
Sfiet_Konstantin | so, in your case, do whatever you want | 09:51 |
Superpelican | I'm currently reading a book about C pointers etc. | 09:51 |
Superpelican | a pretty nice one | 09:51 |
Sfiet_Konstantin | because basically it will cost you really nothing | 09:51 |
Sfiet_Konstantin | :) | 09:51 |
*** dhbiker has quit IRC | 09:51 | |
Superpelican | Sfiet_Konstantin:http://shop.oreilly.com/product/0636920028000.do | 09:51 |
Superpelican | they were 50% off last week | 09:52 |
Sfiet_Konstantin | these books are usually good | 09:52 |
Superpelican | and they're DRM-free :D | 09:52 |
Superpelican | I also bought a C and C++ pocket reference | 09:52 |
Superpelican | they were 3 euro each | 09:52 |
Superpelican | with the 50% off :D | 09:53 |
Sfiet_Konstantin | :P | 09:53 |
Superpelican | will always come in handy :) | 09:53 |
Sfiet_Konstantin | well, my C C++ refs are the internet | 09:53 |
Sfiet_Konstantin | and I learnet pointer on the internet | 09:53 |
Sfiet_Konstantin | everything is on the internet | 09:53 |
Superpelican | well | 09:53 |
Superpelican | the book I have is very in depth | 09:53 |
Superpelican | I doubt you'll find something like that on the web | 09:54 |
Sfiet_Konstantin | Superpelican: well, dunno | 09:54 |
Sfiet_Konstantin | true that books are useful. I got some books of algorithm | 09:54 |
Sfiet_Konstantin | but it is just my case that I self-taught close to everything related to code | 09:55 |
Superpelican | well I'm self teaching myself everything too :P | 09:55 |
Superpelican | of course | 09:55 |
Superpelican | well | 09:55 |
Superpelican | with a lot of help | 09:55 |
*** Pat_o has quit IRC | 09:55 | |
Sfiet_Konstantin | :P | 09:55 |
Superpelican | from for example you | 09:55 |
Superpelican | and the nice books ;) | 09:55 |
Superpelican | but other than that | 09:56 |
Nicd- | I haven't really found any programming books useful | 09:56 |
Nicd- | most are really boring and often outdated already | 09:56 |
Superpelican | Sfiet_Konstantin:Out of curiousity: do you use complex C++ things like polymorphism, multiple inheritance and virtual functions daily? | 09:57 |
Superpelican | Nicd-:Do you think this one is outdated and useless too: shop.oreilly.com/product/0636920028000.do :P | 09:58 |
Sfiet_Konstantin | Superpelican: yes | 09:59 |
Sfiet_Konstantin | multiple inheritance yes, a lot: but in a JAVA style | 09:59 |
Summeli | I guess that those are pretty basic things if you're writing an app with c++ | 09:59 |
Sfiet_Konstantin | with interfaces most of the time | 09:59 |
Sfiet_Konstantin | virtual functions, of cause | 09:59 |
Superpelican | ah I see | 09:59 |
Sfiet_Konstantin | polymorphism as we | 10:00 |
Sfiet_Konstantin | well | 10:00 |
Sfiet_Konstantin | Summeli: not multiple inheritance, especially that in Qt it is not always doable, because of the impossibility to do diamond like inheritance graph | 10:00 |
Summeli | Sfiet_Konstantin: ok, with Qt you usually don't need that | 10:01 |
Sfiet_Konstantin | Summeli: yes :) | 10:01 |
*** Morpog_PC has joined #sailfishos | 10:01 | |
*** ericcc_ has quit IRC | 10:02 | |
Superpelican | Sfiet_Konstantin:So polymorphism I actually the same as what I've done with QObject * QMLrootobject = view.rootObject() | 10:02 |
Superpelican | ? | 10:02 |
Nicd- | Superpelican: maybe not outdated but uselss to me, yes | 10:02 |
Sfiet_Konstantin | Superpelican: yep | 10:02 |
Sfiet_Konstantin | Nicd-: well, not useless, virtual functions are essential | 10:03 |
Nicd- | Sfiet_Konstantin: I was talking about the book Superpelican mentioned | 10:03 |
Superpelican | Sfiet_Konstantin:But why would you use virtual functions | 10:04 |
*** lpotter has quit IRC | 10:04 | |
Superpelican | instead of a single function | 10:04 |
Superpelican | that has an if-else statement | 10:04 |
Superpelican | and calls 2 other functions | 10:04 |
Superpelican | I've also heard that they can be slow | 10:04 |
Superpelican | Is that true? | 10:04 |
Summeli | Superpelican: interfaces are usually pure virtuals | 10:04 |
Summeli | in c++ | 10:04 |
Superpelican | you mean UIs? | 10:04 |
Superpelican | or interfaces of classes? | 10:05 |
Summeli | no, I mean like interfaces in java | 10:05 |
Superpelican | like public slots/functions | 10:05 |
Superpelican | ? | 10:05 |
Superpelican | s/functions/methods | 10:05 |
Summeli | yes, you can use slots in Qt | 10:05 |
Summeli | but in c++ you usually just writi virtual int foo()=0; | 10:06 |
Superpelican | ? | 10:06 |
Nicd- | Superpelican: the performance implications of birtual functions are negligible. they are not the place you should go looking at when optimizing | 10:06 |
Sfiet_Konstantin | Superpelican: well, if you do inheritance, it is usual to have virtual functions | 10:06 |
Nicd- | virtual* | 10:06 |
Sfiet_Konstantin | Nicd-: there is the cost of resolving the vtable etc | 10:07 |
*** Aard has quit IRC | 10:07 | |
Summeli | Sfiet_Konstantin: yes, it's like couple cycles :) | 10:07 |
Nicd- | Sfiet_Konstantin: there is but it is nothing you should worry about unless you are in the business of writing high frequency trading software :P | 10:08 |
Sfiet_Konstantin | Summeli: in pure C they don't exist | 10:08 |
Sfiet_Konstantin | :D | 10:08 |
Sfiet_Konstantin | Nicd-: or HPC | 10:08 |
*** martyone has quit IRC | 10:08 | |
Summeli | Shapeshifter: yes, but you can just implemetn that with sturcts and function pointers | 10:08 |
Summeli | Sfiet_Konstantin even :P | 10:08 |
Nicd- | if you are doing really high performance stuff, you are usually at the level to understand these things anyway | 10:08 |
Nicd- | so if you need to ask "are virtual functions slow", chances are it doesn't matter to you | 10:09 |
Summeli | I have once ported a c-library where they implemented the polymorphism with structs and function pointers, it was pretty fun | 10:09 |
Sfiet_Konstantin | well, in my daily time, virtual functions are useless | 10:09 |
Sfiet_Konstantin | Summeli: hehe | 10:09 |
Sfiet_Konstantin | don't know if it is really better | 10:09 |
Superpelican | Nicd-:So you mean I don't need virtual functions? | 10:09 |
*** martyone has joined #sailfishos | 10:09 | |
Superpelican | by: "so if you need to ask "are virtual functions slow", chances are it doesn't matter to you" | 10:10 |
*** Aard has joined #sailfishos | 10:10 | |
*** maninc has joined #sailfishos | 10:11 | |
Nicd- | no | 10:11 |
Nicd- | I mean their performance is good enough to not matter to you | 10:11 |
Nicd- | the things you should worry about are elsewhere | 10:11 |
Superpelican | Sfiet_Konstantin:This has a red line under it: "QVector<int> tables(10);" | 10:13 |
Superpelican | I've done it exactly like in the docs | 10:13 |
Superpelican | "QVector<QString> vector(200);" from the docs | 10:13 |
Sfiet_Konstantin | try to compile ? | 10:13 |
Superpelican | built-in Qt Creator | 10:13 |
Sfiet_Konstantin | and maybe the redline comes from a ";" that was forgotten in the previous line | 10:14 |
Sfiet_Konstantin | etc | 10:14 |
Superpelican | Sfiet_Konstantin:When I hover over the line it says "unexpected token 'C'" | 10:16 |
Superpelican | s/C/( | 10:16 |
Sfiet_Konstantin | does it compile ? | 10:16 |
Superpelican | no | 10:17 |
Superpelican | But that seems to be related to other things | 10:17 |
Sfiet_Konstantin | go figureout | 10:17 |
*** zenvoid has joined #sailfishos | 10:18 | |
Superpelican | "error: expected identifier before numeric constant" | 10:20 |
Superpelican | and "20: error: expected ',' or '...' before numeric constant" | 10:22 |
Superpelican | on the same line | 10:22 |
*** arcean has quit IRC | 10:23 | |
Superpelican | Sfiet_Konstantin:http://paste.kde.org/p45598c77/ | 10:24 |
Superpelican | can't find anything wrong | 10:25 |
*** exec_s has quit IRC | 10:26 | |
Sfiet_Konstantin | Superpelican: are you kidding me ? | 10:29 |
Superpelican | no | 10:29 |
Sfiet_Konstantin | you are calling a constructor when declaring a variable | 10:29 |
Sfiet_Konstantin | :/ | 10:29 |
Sfiet_Konstantin | you should call the constructor in the constructor of Logic | 10:30 |
Sfiet_Konstantin | ... | 10:30 |
Superpelican | Sfiet_konstantin:from the docs: "QVector<QString> vector(200);" | 10:30 |
Summeli | you should declare it like QVector* myvector; | 10:30 |
Summeli | and then initialize that in the constructor for example | 10:30 |
Superpelican | Summeli:Why a pointer? | 10:30 |
Superpelican | nvm | 10:31 |
Summeli | Superpelican: because you can not call the constructor in declaration | 10:31 |
Summeli | you can move that code to the contructor of the object | 10:32 |
Superpelican | ok | 10:32 |
*** Shaan7 has quit IRC | 10:34 | |
Sfiet_Konstantin | no need of a pointer Superpelican and Summeli | 10:38 |
Sfiet_Konstantin | just declare QVector<int> myVector; | 10:39 |
Sfiet_Konstantin | and in the constructor do myVector = QVector<int>(20) | 10:39 |
*** maninc has quit IRC | 10:39 | |
*** kjokinie has quit IRC | 10:40 | |
Summeli | that'll work too | 10:40 |
*** kjokinie has joined #sailfishos | 10:40 | |
*** b0bben has quit IRC | 10:40 | |
Nicd- | Sfiet_Konstantin: shouldn't it be in the initialization list? | 10:41 |
*** Shaan7 has joined #sailfishos | 10:42 | |
Sfiet_Konstantin | Nicd-: it is not mandatory (and you can put it in the initialization list) | 10:42 |
Sfiet_Konstantin | like myVector(QVector<int>(20)) | 10:42 |
Nicd- | is using the initialization list normal/good practice? | 10:42 |
Sfiet_Konstantin | but sometimes I like using the = notation. It is clear, and still call the constructor | 10:42 |
Superpelican | yay | 10:42 |
Sfiet_Konstantin | Nicd-: it is, but it is efficiency vs clearness | 10:43 |
Superpelican | my Jolla T-Shirt has left Finland | 10:43 |
Sfiet_Konstantin | I prefer to have clean code, even if it is less efficient | 10:43 |
Superpelican | it must now be traveling to Germany in a dinghy | 10:43 |
Sfiet_Konstantin | (especially that the compiler is able to fix the case of using = in constructor by not initializing twice) | 10:43 |
Nicd- | it seems there is an anwser: http://stackoverflow.com/a/926795 | 10:44 |
Sfiet_Konstantin | Nicd-: let me try | 10:45 |
Superpelican | "I prefer to have clean code, even if it is less efficient" :O | 10:45 |
Sfiet_Konstantin | IIRC, in release mode, compiler is able to detect that | 10:45 |
Sfiet_Konstantin | Superpelican: yes | 10:45 |
Superpelican | Sfiet_Konstantin:Just kidding ;) | 10:46 |
Superpelican | I know you should try to balance those 2 things | 10:46 |
Sfiet_Konstantin | well, of cause | 10:46 |
Sfiet_Konstantin | but clean cod efirst | 10:46 |
Yaniel | clean code tends to be sufficiently efficient anyways | 10:47 |
Superpelican | :nod: | 10:49 |
*** Pat_o has joined #sailfishos | 10:49 | |
Sfiet_Konstantin | Nicd-: aah, you are right | 10:51 |
Sfiet_Konstantin | it first calls a default constructor then calls the overloaded one | 10:51 |
Sfiet_Konstantin | maybe it is because I'm using pointers | 10:51 |
Sfiet_Konstantin | well anyway | 10:51 |
Sfiet_Konstantin | it is good to initialize them | 10:51 |
*** maninc has joined #sailfishos | 10:52 | |
*** Pat_o has quit IRC | 10:55 | |
Superpelican | Sfiet_Konstantin:What would you use for an "About" box/dialog in an Sailfish app? | 10:55 |
Superpelican | a Dialog{}? | 10:55 |
Superpelican | a custom made Rectangle{} derived object? | 10:55 |
Sfiet_Konstantin | Superpelican: a page | 10:55 |
Superpelican | A whole page? | 10:56 |
Sfiet_Konstantin | yes | 10:56 |
Sfiet_Konstantin | accessed via a pulley menu | 10:56 |
Superpelican | :nod: | 10:56 |
Sfiet_Konstantin | inside you can put version nformation | 10:56 |
Sfiet_Konstantin | copyright | 10:56 |
Superpelican | :nod: | 10:56 |
Superpelican | and credits | 10:56 |
Sfiet_Konstantin | github link | 10:56 |
Sfiet_Konstantin | icon | 10:56 |
Sfiet_Konstantin | anything you want | 10:56 |
*** gabriel9 has joined #sailfishos | 10:56 | |
Sfiet_Konstantin | donation | 10:56 |
Sfiet_Konstantin | explaination about what a free sw is | 10:56 |
Superpelican | Which will of course include all the people who have helped me ;) | 10:56 |
Sfiet_Konstantin | usually it fills a page | 10:56 |
Sfiet_Konstantin | :P | 10:56 |
Superpelican | Including "Sfiet_Konstantin" | 10:56 |
Superpelican | :D | 10:56 |
Sfiet_Konstantin | LOL | 10:57 |
*** gabriel9|work has quit IRC | 10:57 | |
*** mikhas has quit IRC | 11:03 | |
*** Pat_o has joined #sailfishos | 11:08 | |
*** arcean has joined #sailfishos | 11:14 | |
*** Pat_o has quit IRC | 11:14 | |
*** simathur has quit IRC | 11:19 | |
*** triggerhappy has quit IRC | 11:22 | |
*** triggerhappy has joined #sailfishos | 11:24 | |
*** dhbiker has joined #sailfishos | 11:32 | |
*** b0bben has joined #sailfishos | 11:34 | |
*** jpetersen has quit IRC | 11:34 | |
*** jpetersen has joined #sailfishos | 11:43 | |
*** ericcc has joined #sailfishos | 11:44 | |
*** arcean has quit IRC | 11:46 | |
*** arcean has joined #sailfishos | 11:49 | |
*** Pat_o has joined #sailfishos | 11:49 | |
*** ericcc has quit IRC | 11:57 | |
*** ericcc has joined #sailfishos | 11:57 | |
*** simbrown has joined #sailfishos | 11:59 | |
*** martyone has quit IRC | 12:04 | |
*** Pat_o has quit IRC | 12:11 | |
*** f3an0r has quit IRC | 12:15 | |
*** niqt has quit IRC | 12:16 | |
*** f3an0r has joined #sailfishos | 12:21 | |
*** Superpelican has quit IRC | 12:22 | |
*** khertan has joined #sailfishos | 12:23 | |
*** Pat_o has joined #sailfishos | 12:24 | |
*** arcean has quit IRC | 12:24 | |
*** f3an0r has quit IRC | 12:26 | |
khertan | Morning | 12:28 |
*** f3an0r has joined #sailfishos | 12:29 | |
*** b0bben has quit IRC | 12:35 | |
*** M13 has joined #sailfishos | 12:36 | |
*** maninc has quit IRC | 12:50 | |
*** Pat_o has quit IRC | 12:52 | |
*** Superpelican has joined #sailfishos | 13:01 | |
*** rcg has joined #sailfishos | 13:03 | |
Superpelican | Sfiet_Konstantin:If I want to send a signal to QML which carries a string with it, | 13:03 |
Superpelican | Should I use a QVariant or a QString as parameter? | 13:03 |
Superpelican | I'm a bit confused | 13:03 |
Superpelican | about when a QVariant is necessary | 13:04 |
Superpelican | and when the type will automatically be converted for you | 13:04 |
Sfiet_Konstantin | QString | 13:04 |
Sfiet_Konstantin | signals are strongly typed | 13:05 |
*** Pat_o has joined #sailfishos | 13:05 | |
Superpelican | ok thanks :) | 13:06 |
*** arcean has joined #sailfishos | 13:07 | |
Superpelican | Sfiet_Konstantin:Signals always have a void return type, right? | 13:11 |
Sfiet_Konstantin | yep | 13:11 |
Superpelican | ok | 13:11 |
*** VitaBushido_ has joined #sailfishos | 13:12 | |
*** Pat_o has quit IRC | 13:12 | |
khertan | Superpelican: QString | 13:13 |
Superpelican | :) | 13:13 |
Superpelican | khertan:Sfiet_Konstantin had already replied ;) | 13:14 |
Superpelican | but thanks anyway :D | 13:14 |
khertan | use a QVariant<QString> only to carry different type of returned value | 13:14 |
khertan | lol :) | 13:14 |
khertan | didn't see it :) | 13:14 |
Superpelican | khertan:What do you mean with a different return type? | 13:14 |
Superpelican | Ints or booleans? | 13:14 |
khertan | a signal that can return int, bool, string, garbagedata | 13:15 |
khertan | :) | 13:15 |
khertan | oups ... can't update my sdk target | 13:15 |
khertan | can't resolve sailfishos.org same for you ? | 13:15 |
*** VitaBushido_ has quit IRC | 13:16 | |
khertan | same for http://merproject.org/ | 13:16 |
t7 | Qt has its own string class? | 13:16 |
*** Shaan7 has quit IRC | 13:16 | |
*** VitaBushido has joined #sailfishos | 13:16 | |
khertan | t7: at least since Qt3 | 13:16 |
t7 | why not std string? | 13:16 |
Yaniel | encodings I guess | 13:17 |
t7 | oh unicode stuff? | 13:17 |
Yaniel | IIRC QString does UTF-8 by default | 13:17 |
Nicd- | http://stackoverflow.com/questions/11028948/advantage-of-qstring-over-stdstring | 13:17 |
Yaniel | std::String does not | 13:17 |
*** Shaan7 has joined #sailfishos | 13:17 | |
aknight | yep, QStrings are stored as utf16 | 13:17 |
Superpelican | khertan:I can reach http://sailfishos.org in my browser | 13:17 |
Yaniel | Superpelican: works fine here | 13:17 |
Superpelican | Yaniel:I'm not the one having problems ;) | 13:18 |
Superpelican | khertan is | 13:18 |
Superpelican | t7:Plus no dependency on the STL | 13:19 |
Superpelican | or whatever it's correct name is | 13:19 |
Yaniel | STL | 13:19 |
Superpelican | std::string isn't exactly part of the STL iirc | 13:19 |
t7 | Qt is a pretty hefty dep | 13:19 |
Superpelican | t7:Yes | 13:19 |
Superpelican | but if you are already using it | 13:19 |
Yaniel | exacctly | 13:20 |
Superpelican | you can better use all of it | 13:20 |
Superpelican | instead of pulling in even more ;) | 13:20 |
khertan | oh ... can resolve http://sailfishos.org | 13:20 |
Yaniel | and std::string is part of the STL | 13:20 |
khertan | but not www.sailfishos.org | 13:20 |
khertan | nor https://releases.sailfishos.org/ | 13:20 |
Superpelican | lol :) | 13:20 |
Superpelican | :( | 13:20 |
khertan | arg | 13:21 |
khertan | can't install python-devel to finish ownNotes | 13:21 |
khertan | ... | 13:21 |
Sfiet_Konstantin | khertan: can resolve here | 13:21 |
Superpelican | khertan:I can reach it in my browser | 13:21 |
khertan | roh ... | 13:21 |
Superpelican | including https://releases.sailfishos.org/written_offer_for_source_code.txt | 13:21 |
Superpelican | :D | 13:21 |
*** f3an0r has quit IRC | 13:22 | |
Morpog_PC | khertan, try http instead of https | 13:23 |
ottulo | typo in that txt :< | 13:23 |
khertan | look like that s come from dns | 13:24 |
*** b0bben has joined #sailfishos | 13:33 | |
*** khertan has quit IRC | 13:34 | |
*** khertan has joined #sailfishos | 13:35 | |
Superpelican | Sfiet_Konstantin:The Qt-project docs page about the Connections{} says it can also be used with objects that are not available to QML | 13:57 |
Superpelican | So I could use it with my QObject derived class, right? | 13:57 |
Superpelican | without setContext*? | 13:58 |
Sfiet_Konstantin | Superpelican: do whatever you want honestly | 13:59 |
Superpelican | Sfiet_Konstantin:yes, but is it possible? | 13:59 |
Sfiet_Konstantin | well, you have to expose something to QML | 14:00 |
Superpelican | Sfiet_Konstantin:But: http://qt-project.org/doc/qt-5.0/qtqml/qml-qtquick2-connections.html | 14:00 |
Sfiet_Konstantin | basically the Connection component is often used to connect to global singletons | 14:00 |
Superpelican | However, it is not possible to connect to a signal in this way in some cases, such as when: | 14:00 |
Sfiet_Konstantin | like those that you are exposing | 14:00 |
Superpelican | Multiple connections to the same signal are required | 14:00 |
Superpelican | Creating connections outside the scope of the signal sender | 14:00 |
Superpelican | Connecting to targets not defined in QML | 14:00 |
Superpelican | sorry for the flood :( | 14:00 |
Sfiet_Konstantin | stop spamming | 14:00 |
Sfiet_Konstantin | you can use Connection to connect to whatever that is available in QML | 14:01 |
Sfiet_Konstantin | including global singletons passed via setContextProperty | 14:01 |
Sfiet_Konstantin | I know, I have tried | 14:01 |
Superpelican | Sfiet_Konstantin:But I don't instantiate my class in QML | 14:01 |
Superpelican | "When any of these are needed, the Connections type can be used instead." | 14:02 |
Superpelican | "Connecting to targets not defined in QML" | 14:02 |
Superpelican | Sfiet_Konstantin:So will I have to expose my object that is instantiated in C++ to QML with setContext*? | 14:02 |
Sfiet_Konstantin | yep | 14:05 |
Sfiet_Konstantin | IMO the easiest way | 14:05 |
*** VDVsx has quit IRC | 14:05 | |
Sfiet_Konstantin | then you create a Connection component and use target: NAME_GIVEN_IN_SET_CONTEXT | 14:06 |
Superpelican | Sfiet_Konstantin:Well I think that page is very unclear then | 14:06 |
Sfiet_Konstantin | :/ | 14:06 |
Superpelican | Sfiet_Konstantin:But I could use QObject::connect too? | 14:07 |
Superpelican | with of course .findChild() | 14:07 |
Superpelican | first | 14:07 |
*** kaxing has quit IRC | 14:09 | |
Sfiet_Konstantin | well | 14:11 |
Sfiet_Konstantin | if you want | 14:11 |
Sfiet_Konstantin | I don't like messing with QML from C++ | 14:11 |
Sfiet_Konstantin | but you can do that | 14:11 |
Superpelican | So Connections{} is prefered by the experts ;) | 14:12 |
Superpelican | And what about a QML signal -> Qt/C++ slot connection? | 14:12 |
Superpelican | Would Connections{} be preferred for that too? | 14:13 |
aknight | Superpelican: you can get a pointer to the qml object and use QObject::connect in that case | 14:13 |
Superpelican | ok | 14:13 |
*** Eismann has joined #sailfishos | 14:13 | |
aknight | but you could also do onMyQMLSignal: myCPPObject.slot() | 14:13 |
Superpelican | yeah | 14:13 |
Superpelican | but then I would have to do a setContextProperty() first | 14:13 |
aknight | yep (or use a singleton import) | 14:14 |
*** VDVsx has joined #sailfishos | 14:19 | |
*** liar has joined #sailfishos | 14:19 | |
*** fk_lx has joined #sailfishos | 14:21 | |
Superpelican | aknight:And every page would needs it's own Connections{} ? | 14:21 |
*** b0bben has quit IRC | 14:21 | |
aknight | Superpelican: if the qml "slot" (reaction to the signal) is different for each page | 14:22 |
Superpelican | oh | 14:22 |
aknight | Superpelican: or you can define a function in each page | 14:22 |
Superpelican | aknight:So I could also just put it in main.qml? | 14:22 |
aknight | and maybe make one Connections that fires currentPage.myFunction() | 14:22 |
Superpelican | well | 14:22 |
aknight | or loop through the pages and fire that function... | 14:23 |
Superpelican | I don't really have | 14:23 |
Superpelican | pages with the same signal | 14:23 |
Superpelican | but who need a different handler/slot | 14:23 |
Superpelican | all my pages | 14:23 |
Superpelican | are totally different | 14:23 |
aknight | ok | 14:23 |
Superpelican | and have a different purpose | 14:23 |
Superpelican | and therefore also totally different slots and signals ;) | 14:23 |
aknight | so you probably want a Connections object in each then | 14:23 |
Superpelican | So I can't put one in main.qml? | 14:23 |
Superpelican | I won't have signals/slots with the same name | 14:24 |
aknight | you can, if your page is available | 14:24 |
aknight | you can say myPage.mySlot() | 14:24 |
Superpelican | aknight:So they should be in the same scope? | 14:24 |
aknight | right | 14:24 |
Superpelican | hmm | 14:24 |
aknight | you just need to be able to access the page by id and you can call functions it has defined | 14:24 |
Superpelican | Then I'll just give each page it's own Connections{} | 14:25 |
Superpelican | aknight:Pulley menu entries can be dynamic too, right? | 14:26 |
Superpelican | So for example a variable number | 14:26 |
Sfiet_Konstantin | Superpelican: not sure | 14:26 |
Sfiet_Konstantin | don't think so | 14:26 |
Superpelican | hmm | 14:27 |
Superpelican | I'll take a look at Chris' project again then | 14:27 |
Superpelican | (from the ML) | 14:27 |
Superpelican | I thought it had dynamic menu entries | 14:27 |
Superpelican | but not sure | 14:27 |
Superpelican | It won't work in Qt5 | 14:27 |
Superpelican | though | 14:27 |
Superpelican | but I can read the code | 14:27 |
*** b0bben has joined #sailfishos | 14:28 | |
*** simbrown has quit IRC | 14:29 | |
Superpelican | Sfiet_Konstantin:Can't you just the menu item an id and put "menuitemid.text = number_str" in some other component's signal handler? | 14:30 |
Superpelican | s/just/just give | 14:30 |
khertan | rahhhhh i got some problem package isn't deployed to the emulator... but none error ! grrrr any advice | 14:30 |
Superpelican | khertan:So you chose the Deploy by RPM package option? | 14:31 |
*** simbrown has joined #sailfishos | 14:33 | |
Superpelican | huh | 14:34 |
*** stephg has joined #sailfishos | 14:34 | |
Superpelican | Qt Creator itself is still based on Qt 4.8.4 lol | 14:34 |
khertan | Superpelican: yep as python file aren't deploy else | 14:34 |
Superpelican | ah | 14:34 |
Superpelican | your using Python | 14:35 |
Superpelican | well I think that's an important detail | 14:35 |
Superpelican | And I haven't used Python + Qt | 14:35 |
Superpelican | let alone with the Sailfish SDK | 14:35 |
Superpelican | So I don't think | 14:35 |
Superpelican | I can help much | 14:35 |
khertan | Superpelican: i m alone with the sailfish sdk :) | 14:35 |
Superpelican | khertan:Try it on the ML | 14:35 |
*** jayrulez has joined #sailfishos | 14:36 | |
khertan | i ve found / not really ... restarted qt remove the .pro.user and restart the vm | 14:36 |
khertan | fix the thing | 14:36 |
Superpelican | IIRC there are more Python developers for Sailfish | 14:36 |
khertan | :) | 14:36 |
Superpelican | strange | 14:36 |
khertan | Superpelican: https://github.com/khertan/pyotherside | 14:36 |
khertan | Superpelican: yep | 14:36 |
khertan | Superpelican: like the 3 target kit x86 x862 and x863 | 14:37 |
Superpelican | khertan:Are you the developer of PyOtherSide? | 14:37 |
khertan | look like i mess something | 14:37 |
*** chriadam has quit IRC | 14:37 | |
khertan | Superpelican: now i m the one who made it s own fork :) | 14:37 |
khertan | thp is the devel of pyotherside | 14:37 |
Superpelican | Ah so you are a contributor | 14:37 |
Superpelican | khertan:So PyOtherSide is for QML UIs and PySide is for Qt4 Widget based UIs? | 14:37 |
Superpelican | I've heard of PyOtherSide on the ML | 14:38 |
khertan | pyside is binding for Qt | 14:38 |
khertan | actually only Qt4 | 14:38 |
fk_lx | khertan: I was good with developing with PyQt3, but later life caught me so I'm unfortunately not up-to-date with newest solutions regarding Qt and Python | 14:38 |
*** chriadam has joined #sailfishos | 14:38 | |
khertan | PyOtherSide is extending qml with a python interpreter | 14:38 |
Superpelican | So instead of JavaScript, you then use Python with QML? | 14:39 |
Superpelican | Ah it's also for Python 3 | 14:39 |
Superpelican | nice | 14:40 |
Superpelican | My first computer programming language was Python :) | 14:40 |
Superpelican | I read a book about it | 14:40 |
Superpelican | and wrote 2 small programs with it | 14:40 |
Superpelican | then I switched to C++ | 14:40 |
Superpelican | ah | 14:40 |
Superpelican | thp = Thomas Perl | 14:40 |
khertan | almost the same ... except that i switch to python at the end | 14:40 |
khertan | Superpelican: yep | 14:40 |
Superpelican | khertan:But Thomas is on the ML | 14:41 |
khertan | Superpelican: i know | 14:41 |
Superpelican | So you should ask him | 14:41 |
khertan | i've no problem with pyside :) the problem is the sdk right now :p | 14:41 |
khertan | ok ... i got it ... python file are now copied with the binary | 14:41 |
khertan | ... | 14:41 |
Superpelican | exactly | 14:41 |
Superpelican | But the SDK wasn't designed for use with Python | 14:42 |
Superpelican | So problems could occur | 14:42 |
Superpelican | which are Python specific | 14:42 |
Superpelican | even though they don't aren't Python related | 14:42 |
Superpelican | So you should contact other Sailfish + Python users for that problems/stuff | 14:42 |
Superpelican | s/aren't/are | 14:42 |
khertan | my problem was founding documentation about .pro and the qmake documentation | 14:46 |
khertan | :) | 14:46 |
khertan | s/founding/found | 14:46 |
Sfiet_Konstantin | khertan: qmake is ... | 14:47 |
Sfiet_Konstantin | :D | 14:47 |
*** toartist has quit IRC | 14:47 | |
khertan | yeah | 14:50 |
khertan | i would like to track when user reenter in my application ... | 14:50 |
khertan | after switching from elsewhere | 14:50 |
khertan | so i test it on onStatusChanged { if (status == PageStatus.Activating ) { ... }} | 14:51 |
khertan | but i this event is also called when page is being created and so all other components aren't yet ready | 14:52 |
khertan | and sometime didn't exist ... tracking a ready status with a boolean property and onCompleted look like a bit over kill | 14:52 |
khertan | any idea ? | 14:52 |
*** arcean has quit IRC | 14:57 | |
*** exec_s has joined #sailfishos | 15:00 | |
*** gabriel9 has quit IRC | 15:02 | |
*** b0bben has quit IRC | 15:04 | |
*** b0bben has joined #sailfishos | 15:06 | |
*** arcean has joined #sailfishos | 15:06 | |
*** Xruxa has quit IRC | 15:09 | |
*** rashm2k has joined #sailfishos | 15:17 | |
* Superpelican just checked out KhtCMS, looks nice :) | 15:18 | |
khertan | Superpelican: oh thanks | 15:19 |
Superpelican | It's funny | 15:20 |
khertan | i should push a bug fix for the rss.php :) | 15:20 |
Superpelican | A while ago | 15:20 |
khertan | Superpelican: it s horrible php | 15:20 |
khertan | :) | 15:20 |
Superpelican | well I didn't actually check the code ;) | 15:20 |
Superpelican | And I don't know php | 15:20 |
Superpelican | so | 15:20 |
Superpelican | I'll probably not notice | 15:20 |
Superpelican | anyway | 15:20 |
Superpelican | a while ago | 15:20 |
khertan | Superpelican: u should not ... it s a ugly aggregation of code ... nothing clear | 15:20 |
Superpelican | I had a thought about a simple CMS, that just uses Markdown | 15:21 |
Superpelican | and now there is actually one :D | 15:21 |
*** exec_s has quit IRC | 15:21 | |
Superpelican | I was introduced to Markdown | 15:21 |
khertan | but that funny to write note on my n9 with KhtNotes and push them as post to my site | 15:21 |
Superpelican | for the wiki of my project on Bitbucket | 15:22 |
khertan | :p | 15:22 |
khertan | Superpelican: ... ur name come from pelican ? the python markdown blog engine ? | 15:22 |
Superpelican | no ;) | 15:23 |
Superpelican | never heard of that | 15:23 |
*** rm_work_ has joined #sailfishos | 15:23 | |
khertan | Superpelican: http://docs.getpelican.com/en/3.2/ | 15:24 |
Superpelican | khertan:What was your reason to write KhtCMS then? | 15:24 |
Superpelican | if Pelican already existed? | 15:24 |
Superpelican | and you seem to like Python a lot | 15:25 |
Superpelican | (with almost all your project written in Python) | 15:25 |
khertan | Superpelican: pelican is a python tool ... which need to run on the host or locally | 15:25 |
khertan | but my host is php only | 15:25 |
*** TW1920_ has quit IRC | 15:25 | |
Superpelican | :( | 15:25 |
Superpelican | too bad | 15:25 |
khertan | and it use some libs complicated to compile on harmattan | 15:26 |
khertan | so can publish from my phone | 15:26 |
Superpelican | I'm still thinking of buying a Beaglebone Black and running Owncloud + some other stuff on it :D | 15:26 |
khertan | s/can/can't | 15:26 |
khertan | Superpelican: i'm waiting my raspberrypi for that | 15:26 |
Superpelican | khertan:You can also buy a BBB | 15:26 |
Superpelican | It has a faster CPU | 15:26 |
Superpelican | so it should be better for a web server | 15:26 |
Superpelican | RPi should be better for multimedia ;) | 15:27 |
Superpelican | But currently I'm saving up for my Jolla :) | 15:27 |
Superpelican | so the BBB will have to wait a while :( | 15:27 |
*** t7 has quit IRC | 15:31 | |
*** rcg has quit IRC | 15:36 | |
*** b0bben has quit IRC | 15:37 | |
*** Pali has quit IRC | 15:41 | |
Superpelican | Sfiet_Konstantin:the sizeof() an empty vector is 4 bytes, should I declare one if I'm not sure if I'll need it? | 15:46 |
Superpelican | Because I've read that you can't declare a variable in an if-statement | 15:47 |
Superpelican | otherwise you won't be able to use it out of the if-statement's scope | 15:47 |
Superpelican | Or do you have a better solution? | 15:47 |
Nicd- | why would you not be sure if you'll need it? | 15:47 |
Superpelican | Nicd-:Well it depends on user input | 15:47 |
*** TW1920 has joined #sailfishos | 15:48 | |
*** piee has joined #sailfishos | 15:48 | |
Superpelican | the user can choose a mode | 15:48 |
Superpelican | and one mode does need a specific vector | 15:48 |
Sfiet_Konstantin | Superpelican: well | 15:48 |
Superpelican | and the other doesn't | 15:48 |
Sfiet_Konstantin | 4 byts | 15:48 |
Sfiet_Konstantin | 4 bytes | 15:48 |
Superpelican | 4 bytes isn't really much | 15:48 |
Nicd- | Superpelican: then define it inside that mode? | 15:48 |
Sfiet_Konstantin | no | 15:48 |
Sfiet_Konstantin | it is ok | 15:48 |
Sfiet_Konstantin | 4 bytes is nothing | 15:48 |
Nicd- | yeah but if he only needs it in one section it is cleaner to have it there | 15:48 |
Superpelican | Nicd-:But how do you check which mode is selected? | 15:48 |
Superpelican | an if-statement | 15:48 |
Superpelican | and you can't declare stuff in if-statements | 15:49 |
Superpelican | that's the point | 15:49 |
Nicd- | so then you define it inside that if statement. if you need it outside the if statement, that means you always need it, doesn't it? | 15:49 |
Superpelican | eh | 15:49 |
Superpelican | no | 15:49 |
Superpelican | Because I have a seperate initialisation function | 15:50 |
Superpelican | my old command line non-Qt worked that way | 15:50 |
Nicd- | then you *have* to define it outside the if statement | 15:51 |
Nicd- | I don't see what the problem is | 15:51 |
*** Pali has joined #sailfishos | 15:51 | |
Superpelican | well I only want to declare the vector if a specific mode is chosen | 15:51 |
Superpelican | so you'll have to check for that | 15:51 |
Superpelican | which is done with an if-statement | 15:51 |
Sfiet_Konstantin | Superpelican: if your vector is an attribute, and if you don't declare it | 15:51 |
Sfiet_Konstantin | it will be defaulty constructed | 15:51 |
Sfiet_Konstantin | and you will waste these 4 bytes anyway | 15:52 |
Superpelican | Sfiet_Konstantin:What do you mean with an attribute? | 15:52 |
Superpelican | you mean an argument for a function? | 15:52 |
Sfiet_Konstantin | Superpelican: no | 15:53 |
Sfiet_Konstantin | if it is an attribute | 15:53 |
Sfiet_Konstantin | of an object | 15:53 |
Superpelican | Sfiet_Konstantin:So you think the sailors will be fine if I waste http://www.wolframalpha.com/input/?i=4%2F1024^4 of the memory of the Jolla (if it has 1GB of RAM) :P | 15:54 |
Superpelican | s/fine if I waste/fine with the fact I'll waste | 15:55 |
Superpelican | :D | 15:55 |
Sfiet_Konstantin | Superpelican: if they are not fine, they will kill your app | 15:55 |
Nicd- | Superpelican: you cannot not declare it if you use it inside multiple separate if scopes, you have to declare it in the outer scope | 15:56 |
Nicd- | so there really is no problem | 15:56 |
Sfiet_Konstantin | and I will make sure to add a hidden routine in the kernel to kill your app each time it is launched | 15:56 |
Superpelican | nooooo | 15:56 |
Superpelican | Sfiet_Konstantin: than I'll install Nemo on my Jolla muhahah | 15:57 |
Superpelican | :D | 15:57 |
Superpelican | and port my app to Nemo | 15:57 |
Superpelican | which I'll do anyway | 15:57 |
Sfiet_Konstantin | :P | 15:57 |
Superpelican | Nicd-:Could you please explain with you're trying to say with an example? | 15:58 |
Nicd- | Vector foo; if (something) { foo will be used here } .... if (something2) { foo will be used here too } | 15:59 |
Nicd- | if you have something like that you *have* to declare foo in the outer scope, you cannot not declare it | 15:59 |
Superpelican | ok | 16:00 |
*** jjanvier has quit IRC | 16:00 | |
Nicd- | so I don't know what your problem is since you have to do it anyway | 16:00 |
Superpelican | Nicd-:But what if one mode needs *2* vectors and the other only 1? | 16:00 |
Superpelican | (spoiler:which is my current case) | 16:00 |
Nicd- | define a variable in the smallest scope it is used in | 16:01 |
Nicd- | that would mean you define the second vector inside the if scope if it is only used there | 16:01 |
Superpelican | ... | 16:01 |
Superpelican | Nicd-:I have a seperate slot/function for initialisation | 16:01 |
Superpelican | And I can't change that | 16:02 |
Superpelican | unless I add some counter | 16:02 |
Superpelican | and let the other function check each time it is run, is the first time it's called | 16:02 |
Superpelican | nvm | 16:03 |
Superpelican | that'll cost just as much resources | 16:04 |
Superpelican | as that counter will be an int | 16:04 |
Superpelican | ...which uses 4 bytes too | 16:04 |
Nicd- | you should stop worrying about 4 bytes | 16:04 |
Superpelican | Nicd-:But what if I in the future write an app | 16:04 |
Superpelican | which uses more than 4 bytes | 16:04 |
Superpelican | and actually does use *a lot* of memory | 16:05 |
Superpelican | It's not that I really care all that much about the 4 bytes | 16:05 |
Superpelican | but it's more a matter of principles | 16:05 |
Superpelican | I'm learning programming | 16:05 |
Nicd- | you need to learn to optimize in the right places | 16:05 |
Superpelican | and I want to learn myself the right way | 16:05 |
Nicd- | ints and pointers aren't the things you want to avoid | 16:05 |
*** rainemak has quit IRC | 16:06 | |
Superpelican | Nicd-:So what should I want to avoid then? | 16:07 |
Sfiet_Konstantin | Superpelican: memory leak | 16:08 |
Sfiet_Konstantin | if you cannot trim down a variable allocation | 16:08 |
Sfiet_Konstantin | either it is because you are doing it right (most of the time) | 16:08 |
Sfiet_Konstantin | or it is because the algo is wrong | 16:08 |
Sfiet_Konstantin | and you might have to take some time to rethink it | 16:08 |
Nicd- | memory leaks, allocating large things and not releasing them, memory use when you have very large containers | 16:09 |
Superpelican | Nicd-:And what would be very large containers? | 16:09 |
Superpelican | >20 | 16:09 |
Superpelican | ? | 16:09 |
Sfiet_Konstantin | Nicd-: not large stuff, just allocating some small stuff and repeating is enough | 16:09 |
Superpelican | >50 | 16:09 |
Superpelican | ? | 16:09 |
Sfiet_Konstantin | Superpelican: > 10^4 | 16:09 |
Nicd- | Sfiet_Konstantin: that goes under very large containers :) | 16:09 |
Superpelican | so that's 10,000 | 16:10 |
Sfiet_Konstantin | worry about stuff when your reach 10^2-3 | 16:10 |
Sfiet_Konstantin | and be careful when you reach 10^4 | 16:10 |
Superpelican | ok | 16:10 |
Sfiet_Konstantin | because you won't fill RAM with a couple of ints | 16:10 |
Sfiet_Konstantin | you are not in 20th century | 16:10 |
Sfiet_Konstantin | RAM is cheap, even in mobile devices | 16:11 |
Sfiet_Konstantin | just don't abuse | 16:11 |
Superpelican | Sfiet_Konstantin, Nicd-:So I shouldn't worry about if I'm not using an int or point too much? | 16:11 |
Sfiet_Konstantin | yes | 16:11 |
Sfiet_Konstantin | just like you shouldn't care about allocating a buffer of size 128 if you are only gonna use a part of it | 16:11 |
Sfiet_Konstantin | (like for strings) | 16:11 |
Sfiet_Konstantin | because a buffer of 128 is so cheap | 16:12 |
*** nahka has quit IRC | 16:12 | |
Superpelican | ok | 16:12 |
Superpelican | I think I'll have to accustom a little bit to this | 16:13 |
Superpelican | but eventually... | 16:13 |
Nicd- | note we are not saying you should be careless. but as a programmer you should learn to recognize the things that are worth your time | 16:14 |
Sfiet_Konstantin | Nicd-: +1 | 16:14 |
Sfiet_Konstantin | be careful on stuff that can create really bad things: algorithm, when you have to process lot of data, memory allocation / desallocation | 16:14 |
Sfiet_Konstantin | algorithmic complexity | 16:15 |
*** nahka has joined #sailfishos | 16:16 | |
Superpelican | Sfiet_Konstantin:Where an algorithm should be as complex as possible or as simple as possible? | 16:16 |
Superpelican | I had to make a trade off when coding my original non-Qt app | 16:17 |
Sfiet_Konstantin | Superpelican: simple: an algorithm must be as simple as possible | 16:17 |
Superpelican | I could use a very simple algorithm | 16:17 |
Superpelican | but use 5 times the memory | 16:17 |
*** stephg has left #sailfishos | 16:17 | |
Superpelican | or use a slightly more complex algorithm | 16:17 |
Sfiet_Konstantin | simplicity is not about simplistic though | 16:17 |
Superpelican | and I ended up choosing the more complex option | 16:17 |
Sfiet_Konstantin | Superpelican: try to get an optimum between kloc and alpha in O(n^alpha) | 16:18 |
Superpelican | note: I saved 320 bytes by the more complex algorithm | 16:18 |
Sfiet_Konstantin | Superpelican: show me your code | 16:18 |
Nicd- | 320 bytes is nothing | 16:18 |
Sfiet_Konstantin | and compute the algo complexity | 16:18 |
Sfiet_Konstantin | Nicd-: it can be something, especially if you have a O(log(n)) instead of a O(n) | 16:18 |
Sfiet_Konstantin | it really depends on the number of kloc involved, the maintenance burden etc. | 16:18 |
Nicd- | Sfiet_Konstantin: if he saved 320 bytes _total_, it's nothing :P | 16:19 |
Sfiet_Konstantin | Superpelican: if your algo is slightly complex but well documented, written, and easily maintainable, it is ok | 16:19 |
Sfiet_Konstantin | Nicd-: well, his app is simple | 16:19 |
Superpelican | well TBH | 16:19 |
Sfiet_Konstantin | but if he want to do something more complex involving the algo, it migt worth it | 16:19 |
Superpelican | I think I should comment my apps a bit more | 16:19 |
Superpelican | but then | 16:20 |
Superpelican | the apps I've written | 16:20 |
Superpelican | all still derive from the time I really was a C++ n00b | 16:20 |
Superpelican | When I was still learning the very basics | 16:20 |
Sfiet_Konstantin | mind showing the two versions of the code ? | 16:20 |
Superpelican | Sfiet_Konstantin:Which 2 versions? | 16:21 |
Sfiet_Konstantin | the simple one and complex one | 16:21 |
Sfiet_Konstantin | saving 320 bytes | 16:21 |
Superpelican | eh | 16:21 |
Superpelican | I've never actually written the simple one | 16:21 |
Superpelican | it was just a thought | 16:21 |
Superpelican | TBH | 16:21 |
Superpelican | I've thought days and days | 16:21 |
Superpelican | how I could implement a not too difficult and not too memory wasting algo | 16:22 |
Superpelican | note: I haven't literally thought all day | 16:22 |
Sfiet_Konstantin | Superpelican: IMO, a good code is code that minimize algorithmic complexity | 16:23 |
Sfiet_Konstantin | but that if you left it uncommented | 16:23 |
Sfiet_Konstantin | and went to vacation for two weeks, you can understand how it works in < 10s | 16:23 |
Sfiet_Konstantin | when looking at it again | 16:23 |
Superpelican | eh | 16:26 |
Sfiet_Konstantin | Superpelican: that's IMO | 16:27 |
*** ericcc has quit IRC | 16:27 | |
Sfiet_Konstantin | (remember, I'm for clearness over efficiency) | 16:27 |
Superpelican | Sfiet_Konstantin:When I had to rewrite a part of my program yesterday, TBH I didn't understand my algo in < 10s | 16:27 |
Superpelican | but I'm n00b | 16:27 |
Superpelican | so I'll probably get better | 16:28 |
Superpelican | at understanding algos | 16:28 |
Sfiet_Konstantin | well, in <tau | 16:28 |
*** arcean has quit IRC | 16:28 | |
Sfiet_Konstantin | tau proportional to your leve | 16:29 |
Sfiet_Konstantin | l | 16:29 |
Superpelican | Sfiet_Konstantin:Well, I think it would be interesting to see how fast you understand my algo ;) | 16:47 |
Superpelican | Sfiet_Konstantin:https://bitbucket.org/Superpelican/clamshell_cli/src/1d99c3abb3db1d2f94588debaf2dbdc6bfbb0d10/clamshell.cpp?at=default | 16:47 |
Superpelican | well actually I've got 2 algos | 16:47 |
Superpelican | But I'll let you try to understand the most complex one | 16:48 |
Superpelican | time saving hint:Only check the newquestion_mixed and checkAnswer functions | 16:48 |
Superpelican | and the if-statement of the main while loop | 16:48 |
Superpelican | with "//initialize practise all multiplication tables mixed mode" in it | 16:49 |
Superpelican | those are the relevant parts | 16:49 |
Superpelican | the rest is for the other, simpler algo mode, the multilingual system and the score system | 16:50 |
Sfiet_Konstantin | complex | 16:51 |
Sfiet_Konstantin | :/ | 16:51 |
Superpelican | yeah | 16:51 |
Superpelican | but I wanted to save mem | 16:51 |
Superpelican | by not creating to much variables | 16:51 |
Sfiet_Konstantin | flemme | 16:52 |
Superpelican | so I took some shortcuts | 16:52 |
Superpelican | with the +1 and -1's | 16:52 |
Superpelican | so I could for example fill a vector with only one variable | 16:52 |
Superpelican | instead of 2 | 16:52 |
Superpelican | I used the counter for both the loop and the value | 16:52 |
Superpelican | it's cleverly designed IMHO, but not very easy to understand | 16:53 |
Superpelican | after you forgot how it worked | 16:53 |
*** nahka^ has joined #sailfishos | 16:53 | |
Superpelican | or if you see it for the first time ;) | 16:53 |
Superpelican | But maybe I should just write some additional docs about it | 16:53 |
*** nwoki has quit IRC | 16:54 | |
Superpelican | Sfiet_Konstantin:But did you understand it after all? | 16:54 |
*** nahka has quit IRC | 16:54 | |
Superpelican | ah http://translate.google.com/#fr/en/flemme | 16:54 |
Superpelican | Sfiet_Konstantin:Do you understand know why I wanted to avoid rewriting parts of the program? :) | 16:55 |
Superpelican | I wanted to the write it once | 16:55 |
Superpelican | and then just treat it as a black bo | 16:55 |
*** nwoki has joined #sailfishos | 16:55 | |
Superpelican | x | 16:55 |
Superpelican | by copy and pasting the existing logic into my app | 16:55 |
Superpelican | but that didn't work ;) | 16:55 |
Superpelican | s/know/now | 16:56 |
Superpelican | and it's probably a bad idea too | 16:56 |
Sfiet_Konstantin | yeah | 16:57 |
Sfiet_Konstantin | maybe not a good idea | 16:57 |
Superpelican | lol :) | 16:57 |
Superpelican | worst idea ever | 16:58 |
Superpelican | laziness comes with a cost :( | 16:58 |
*** spider-mario has joined #sailfishos | 17:00 | |
*** pixraider has quit IRC | 17:03 | |
*** pixraider has joined #sailfishos | 17:05 | |
*** triggerhappy has quit IRC | 17:09 | |
*** exec_s has joined #sailfishos | 17:11 | |
*** pixraider has joined #sailfishos | 17:16 | |
*** piee has quit IRC | 17:26 | |
Superpelican | Sfiet_Konstantin:I should #include QQmlContext to be able to use setContextProperty, right? | 17:26 |
Sfiet_Konstantin | Superpelican: maybe | 17:27 |
Sfiet_Konstantin | yes I guess | 17:27 |
Superpelican | I do get errors | 17:27 |
Superpelican | about forward declaration blahah | 17:27 |
Superpelican | and invalid use of struct QQmlContext etc | 17:27 |
Superpelican | Sfiet_Konstantin:Adding setContextProperty broke the QObject::connect | 17:29 |
Sfiet_Konstantin | Superpelican: just manage | 17:29 |
Superpelican | same error as when I do a QObject::connect before setView | 17:29 |
Sfiet_Konstantin | if there is an invalid use of QQMlContext it means that QQmlContext is not declared | 17:29 |
Sfiet_Konstantin | and then you shjould include it | 17:29 |
Superpelican | I have already #Included | 17:29 |
Superpelican | Sfiet_Konstantin:Should I use QObject::connect for C++ signal ->QML handler/slot instead of Connections{} then? | 17:30 |
Sfiet_Konstantin | I don't kno | 17:30 |
Sfiet_Konstantin | only you can tell | 17:30 |
Superpelican | but is it considered bad practice? | 17:31 |
Superpelican | I'm trying to teach myself good habits | 17:31 |
Superpelican | so I won't come up with hacky, dirty solutions | 17:31 |
*** piee has joined #sailfishos | 17:31 | |
Superpelican | Sfiet_Konstantin:That's why I'm asking you ;) | 17:32 |
Superpelican | you know what's good and bad | 17:32 |
Superpelican | out of experience | 17:32 |
Sfiet_Konstantin | no, I don't know | 17:32 |
Sfiet_Konstantin | I have my habits, using Connection | 17:32 |
Sfiet_Konstantin | but some have others | 17:32 |
Sfiet_Konstantin | here both should be ok | 17:32 |
Sfiet_Konstantin | but I think that using Connection is cleaner | 17:32 |
*** nahkaz has joined #sailfishos | 17:33 | |
Superpelican | hmm | 17:33 |
Superpelican | then I'll just use what works | 17:33 |
Superpelican | I don't really care if I'm forced to give a specific element a specific name if I create a new UI for my app | 17:33 |
Superpelican | when I would like to reuse my C++ logic class | 17:33 |
Superpelican | for for example a Nemo UI | 17:34 |
*** b0bben has joined #sailfishos | 17:34 | |
Superpelican | that doesn't matter to me | 17:34 |
*** lbt has quit IRC | 17:34 | |
*** lbt has joined #sailfishos | 17:34 | |
*** nahka^ has quit IRC | 17:36 | |
*** b0bben has quit IRC | 17:46 | |
*** fk_lx has left #sailfishos | 17:51 | |
*** rm_work_ has quit IRC | 18:11 | |
*** diegoyam has joined #sailfishos | 18:17 | |
*** Superpelican has quit IRC | 18:25 | |
*** Superpelican has joined #sailfishos | 18:25 | |
*** Superpelican has quit IRC | 18:29 | |
*** Culain has quit IRC | 18:31 | |
*** Culain has joined #sailfishos | 18:33 | |
*** Tomiol80 has joined #sailfishos | 18:36 | |
*** lpotter has joined #sailfishos | 18:38 | |
*** rm_work_ has joined #sailfishos | 18:41 | |
*** Sfiet_Konstantin has quit IRC | 18:48 | |
*** disharmonic has joined #sailfishos | 18:55 | |
*** b0bben has joined #sailfishos | 18:56 | |
*** exec_s has quit IRC | 18:56 | |
*** furikku has quit IRC | 18:59 | |
*** rashm2k has quit IRC | 19:07 | |
*** Sfiet_Konstantin has joined #sailfishos | 19:07 | |
*** rashm2k has joined #sailfishos | 19:17 | |
*** rashm2k1 has joined #sailfishos | 19:21 | |
*** rashm2k has quit IRC | 19:21 | |
*** piee has quit IRC | 19:31 | |
*** rashm2k1 has quit IRC | 19:36 | |
*** rashm2k1 has joined #sailfishos | 19:36 | |
*** piee has joined #sailfishos | 19:36 | |
*** b0bben has quit IRC | 19:49 | |
*** Zotan has joined #sailfishos | 19:50 | |
*** ajalkane has joined #sailfishos | 19:50 | |
*** jpetersen_ has joined #sailfishos | 19:55 | |
*** jpetersen has quit IRC | 19:59 | |
*** louisdk has joined #sailfishos | 20:01 | |
*** Pali has quit IRC | 20:05 | |
*** rashm2k1 has quit IRC | 20:15 | |
*** itbaron has quit IRC | 20:25 | |
*** ajalkane has quit IRC | 20:28 | |
*** M4rtinK has joined #sailfishos | 20:29 | |
*** arcean has joined #sailfishos | 20:45 | |
*** arcean has quit IRC | 20:50 | |
*** Eismann has quit IRC | 20:56 | |
*** M13 has quit IRC | 20:58 | |
*** dhbiker has quit IRC | 21:24 | |
*** liar has quit IRC | 21:27 | |
*** piee has quit IRC | 21:31 | |
*** Custodian has quit IRC | 21:32 | |
*** fk_lx has joined #sailfishos | 21:36 | |
*** piee has joined #sailfishos | 21:37 | |
*** spider-mario has quit IRC | 21:40 | |
*** Tomiol80 has quit IRC | 21:42 | |
*** zenvoid has quit IRC | 21:49 | |
*** jayrulez has quit IRC | 22:02 | |
*** Sfiet_Konstantin has quit IRC | 22:10 | |
*** rashm2k1 has joined #sailfishos | 22:17 | |
*** fk_lx has quit IRC | 22:20 | |
*** gabriel9 has joined #sailfishos | 22:26 | |
*** piee has quit IRC | 22:28 | |
*** disharmonic has quit IRC | 22:28 | |
*** piee has joined #sailfishos | 22:31 | |
*** gabriel9 has quit IRC | 22:32 | |
*** Morpog_PC has quit IRC | 22:33 | |
*** nahkaz has quit IRC | 22:34 | |
*** gabriel9 has joined #sailfishos | 22:36 | |
*** rashm2k1 has quit IRC | 22:41 | |
*** piee has quit IRC | 22:51 | |
*** piee has joined #sailfishos | 23:03 | |
*** gabriel9 has quit IRC | 23:06 | |
*** piee has quit IRC | 23:11 | |
*** Zotan has quit IRC | 23:11 | |
*** triggerhappy has joined #sailfishos | 23:16 | |
*** datagutt has quit IRC | 23:17 | |
*** cxl000 has quit IRC | 23:32 | |
*** miksuh has joined #sailfishos | 23:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!