**** BEGIN LOGGING AT Sun Jan 18 02:59:59 2015 Jan 18 18:24:09 Hello everyone! Jan 18 18:25:13 Just wanted to ask what is the best way to develop apps and services for LuneOS. Couldn't find the information anywhere. Jan 18 18:26:16 Do I need the full LuneOS dev environment or should I use the Palm webOS 3.x SDK? Jan 18 18:28:50 Also, I'd love to contribute to the development of LuneOS itself. I wrote a lot JavaScript in the past, but for the past two years I've been doing C/C++ Embedded and Linux userland work. Jan 18 18:31:19 I don't have much time to work on side projects with my studies and the work I have to do, but I'd love to contribute whenever I can. Where should I begin? Jan 18 18:31:45 isagar2004: Hello Jan 18 18:32:59 It can be pretty calm around here during the week-end, and I don't have all the answer, but a starting point could be to install LuneOS on a N4 or TouchPad, if you have one of those Jan 18 18:33:44 You can also give a try on the qemu emulator Jan 18 18:34:11 There are some guidelines on our website, let me see Jan 18 18:36:11 +Tofe: Thanks. I already installed it on my TouchPad and I love it. Jan 18 18:37:29 oh ok, well then it depends on what you'd like to work most; C/C++ is more going to be the OS itself, whereas Javascript/Enyo is going to be more on the app side Jan 18 18:37:45 We also have one or two pieces that are in Qt QML/JS Jan 18 18:38:53 But I don't have a very good overview of where help is needed the most; morphis could answer far better than me on this topic Jan 18 18:39:45 I haven't really touched JavaScript for the past 2 yrs, so I'd prefer C/C++ as this is what I do now (although I'd love to do small projects and fixes in JavaScript wherever needed). Jan 18 18:40:18 ok Jan 18 18:41:07 Then you'll need to be able to build the OS yourself Jan 18 18:41:27 Did you give it a try already? Jan 18 18:42:18 isagar2004: welcome! Jan 18 18:42:20 isagar2004: Tofe is right, that is the first step Jan 18 18:42:26 isagar2004: http://webos-ports.org/wiki/Build_for_Tenderloin is the starting point for this Jan 18 18:42:38 Yup. I have the environment set up and ready, and have built the qemux86 image for now. Jan 18 18:42:46 isagar2004: ah ok Jan 18 18:43:04 isagar2004: so you're experienced with C/C++? Jan 18 18:44:23 Yes, Mostly with user space Linux and with some esoteric Embedded hardware. Haven't done any kernel development apart from experimenting with char device drivers. Jan 18 18:44:53 isagar2004: oh yeah, sounds very good Jan 18 18:45:11 if you want I can give you some first small bits to work on Jan 18 18:45:35 morphis: I'd love that Jan 18 18:48:11 :) Jan 18 18:48:24 isagar2004: you're already registered on our bug tracker? Jan 18 18:48:37 isagar2004: http://issues.webos-ports.org/issues/815 Jan 18 18:49:05 Tofe, Herrie: please remind me that we have to create more those tiny feature tickets Jan 18 18:49:15 those are pretty good starting points for new people :) Jan 18 18:49:37 isagar2004: you have experience with webOS and it's architecture? Jan 18 18:49:46 especially the service bus luna-service2? Jan 18 18:49:51 morphis: Just signed up for the bug tracker. Jan 18 18:49:55 JaMa: ping Jan 18 18:50:21 isagar2004: under which name? Jan 18 18:50:29 ah found it Jan 18 18:50:34 morphis: yes, it's true that it is very handy to have some nice introduction point Jan 18 18:50:37 morphis: Not really. Other than developing patches and reading webos-internals apps' code, I haven't really done any webOS development. Jan 18 18:50:47 isagar2004: ok Jan 18 18:51:32 morphis: under isagar2004 Jan 18 18:52:02 JaMa: btw. do you thinks its possible we utilize the doxygen documentation from the various webOS library during the build somehow so that we can deploy the output somewhere where it can be reached by developers? Jan 18 18:52:30 isagar2004: what do you think about http://issues.webos-ports.org/issues/815? Jan 18 18:53:01 Herrie: btw. did you said there was a problem with the volume steps? Jan 18 18:53:07 Herrie: can you create a bug for that? Jan 18 18:54:14 morphis: Sound easy in theory. Though I'm not experienced with the webOS bus system. Jan 18 18:54:40 :) Jan 18 18:54:45 isagar2004: you know dbus? Jan 18 18:55:28 thrrgilag: thanks for the PR! Jan 18 18:55:41 morphis: A bit. I've only messed with it once or two. Jan 18 18:55:50 isagar2004: ok Jan 18 18:56:12 isagar2004: there is one other task you can work on while you're starting with this Jan 18 18:56:14 morphis: sorry it took me so long, it was sitting uncomitted on my system Jan 18 18:56:22 thrrgilag: np Jan 18 18:57:37 isagar2004: while you go foward can you document your steps for other people wanting to start to work on LuneOS in our wiki? Jan 18 18:57:37 morphis: I'm all ears Jan 18 18:57:47 so we can answer those questions Jan 18 18:58:02 like "What should I do first when I want to work on C/C++?" Jan 18 18:58:11 links to various documentation etc. Jan 18 18:58:21 morphis: I guess I can do that. Jan 18 18:58:53 isagar2004: great Jan 18 18:59:13 isagar2004: some information about luna-service2 are at https://developer.palm.com/content/api/index.html and in the webOS internals wiki Jan 18 18:59:49 also creating the doxygen documentation from https://github.com/openwebos/luna-service2 might give some good ideas about how it is working Jan 18 19:01:38 morphis: pong Jan 18 19:01:48 morphis: wrt doxygen, somewhere else then PN-doc, right? Jan 18 19:01:56 JaMa: yeah Jan 18 19:02:09 like on docs.webos-ports.org/ Jan 18 19:02:25 I don't know about anything in oe-core to do this, but we can probably write something Jan 18 19:02:32 isagar2004: when you have any questions feel free to ask here Jan 18 19:02:38 JaMa: that would be great Jan 18 19:02:56 morphis: thanks Jan 18 19:03:02 ok, I'll try to look into it Jan 18 19:03:26 for start I would copy PN-doc output somewhere during the build Jan 18 19:03:54 then we can fix doxygen support to generate more useful PN-doc and at the same time improve this output Jan 18 19:05:00 morphis: going to read now. Should I assign myself to #815 when I feel ready to take it? Jan 18 19:05:17 gtg, bye Jan 18 19:28:07 isagar2004: please Jan 18 19:28:57 morphis: thanks again Jan 18 19:30:37 isagar2004: Creating a bug for the volume Jan 18 19:30:50 http://issues.webos-ports.org/issues/819 Jan 18 19:30:54 Herrie: thanks Jan 18 19:31:04 Should be fairly straight forward for someone with c/c++ knowledge :P Jan 18 19:31:15 I could do it but I usually break more then fix when I touch c/c++ Jan 18 19:31:26 Once it's sorted I'll fix the QML/JS side of things for the UI Jan 18 19:40:53 Herrie: right on it Jan 18 19:41:52 Herrie: are there any coding guidelines? (don't want to write the way I used to do it when dealing with a 33Mhz processor :D) Jan 18 19:45:41 I think you should be OK in general, we're talking at least 1,2ghz dual core ;) Jan 18 19:48:04 hello isagar2004! guidelines: http://webos-ports.org/wiki/Submitting_Contributions. also had this question some time ago. Jan 18 19:53:24 Herrie: great. Jan 18 19:53:34 nizovn_: thanks Jan 18 20:39:34 So I had to fight git on msys2 because for an unfortunate reason I can't use my Linux machine. #819 is fixed now as far as I can tell. Jan 18 20:39:44 made a PR Jan 18 20:54:39 hi Jan 18 21:39:48 isagar2004: thanks for the PR, did you test it on the device or emulator? Jan 18 21:41:18 morphis: only tested it on the emulator Jan 18 21:49:58 morphis: Just noticed that there might be a problem using volumeDown after setVolume with new_volume < VOLUME_STEP, but this isn't related to my fix. Jan 18 21:50:18 morphis: should I open an issue about it? Jan 18 21:53:23 morphis: The problem is that becuase of the normalization in volume_down_cb() normalized_volume would be 0 if current volume < VOLUME_STEP, so it'll goto done without actually taking it down to 0. Jan 18 22:01:52 isagar2004: if you spotted the bug and analyzed it, I think that fixing it would take less time than opening an issue for it :) Jan 18 22:05:44 Tofe: should I create a new PR for it or attach it to the current one? Jan 18 22:07:11 Same PR should be ok, as it concerns same area of code Jan 18 22:08:17 We're not (yet !) in an industrial bugfix foilow-up :) Jan 18 22:09:06 going to be sleep a bit -- gn8 all ! Jan 18 22:09:52 Tofe: ok. Though I'm not sure if the right behavior is to treat every (value % VOLUME_STEP > 0) as the next VOLUME_STEP or create a special case for value < VOLUME_STEP... Jan 18 22:19:24 isagar2004: need to look tomorrow what the better solution is Jan 18 22:19:28 already too late here Jan 18 22:19:59 but generally just push out PRs even if there is now ticket for them if you find something which needs to be fixed or had fun to implement something new Jan 18 22:20:18 isagar2004: I will create some more tickets in the next days you can also work on Jan 18 22:20:54 isagar2004: and attaching to an existing PR is fine Jan 18 22:21:26 isagar2004: btw. we already have more work close to the hardware if that is something you prefer Jan 18 22:21:30 ok, enough for today Jan 18 22:21:32 bye Jan 18 22:21:44 morphis: decided to go with my first option as it makes more sense to me. Jan 18 22:21:57 morphis: thanks Jan 18 22:22:01 good night **** ENDING LOGGING AT Mon Jan 19 02:59:58 2015