[00:00] <MyExHatesMeButMy> the clock marker (the text in the circle) are a Great addition
[00:07] <nik90> MyExHatesMeButMy: as of now, no plans. But that is primarily because I need to first finish some high priority features like the digital mode, performance optimizations etc.
[00:07] <nik90> MyExHatesMeButMy: also I got to keep it consistent with other core apps.
[00:09]  * nik90 is off to sleep .zZ
[00:18] <MyExHatesMeButMy> cool nik90  happy sheep counting
[04:18] <goga> hello
[04:19] <goga> i need to use tray icons depending on current unity theme, is possible to check which current theme used by user?
[07:55] <dholbach> good morning
[08:52] <WebbyIT> ehy popey, if you have some time, could you please review https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/1267820/+merge/201313
[08:52] <WebbyIT> >
[08:52] <WebbyIT> ?
[08:52] <WebbyIT> thanks :-)
[09:37] <JamesTait> Good morning all; happy Poetry At Work Day! :-D
[09:38] <fr33r1d3> Hello. Best place to learn making Ubuntu touch apps?  read developer.ubuntu.com already.
[09:52] <dpm> mzanetti, I'm looking at the reminders-app branch to switch to cmake now. Is there any integration with Qt Creator? E.g. to build the project from within the IDE as it used to be with qmake. I don't see any .pro file
[09:53] <mzanetti> dpm: 'cause the .pro file is qmake
[09:53] <mzanetti> dpm: it's the CMakeLists.txt
[09:55] <dpm> mzanetti, oh, I see. It seems that Qt Creator can open the CMakeLists.txt file as a project
[09:55] <mzanetti> dpm: yeah, it can
[09:55] <dpm> nice, building from Qt Creator now
[09:55] <mzanetti> dpm: altough its not as good as with qmake. for example you can't add new files with the ui any more
[09:56] <mzanetti> dpm: or the whole cross compiling support from qtcreator does not work with cmake etc
[09:56] <mzanetti> well, all it can do is open the project and build it... everything else is not really supported
[09:57] <dpm> mzanetti, ah, gotcha. But then again, the Qt Creator cross-compiling support doesn't work with our projects either.
[09:58] <mzanetti> dpm: true... but that's another problem, not qtcreator's
[10:43] <WebbyIT> ehy popey :-)
[10:44] <popey> hey WebbyIT
[10:44] <popey> just notcied I get a strange message when I press enter
[10:44] <popey> but I cant reproduce it now
[10:45] <WebbyIT> popey, about MR, I added support for * / =, but for tab I think is better to open another bug, because at the moment I have no idea on how implement it
[10:45] <popey> ok, no worries.
[11:14] <popey> dpm: do you want to get a click package submitted by sergio to the store and I'll approve it, then we can seed it in the image after the plugin lands
[11:15] <popey> I wouldn't seed the app in the image until we have tested the click and the plugin together
[11:18] <dpm> popey, it sounds like a plan, yes
[11:18] <dpm> popey, you might have seen it in #ubuntu-touch, already - didrocks confirmed the plugin would be in the next image
[11:18] <dpm> \o/
[11:18] <popey> ya, i was on the call earlier ☻
[11:19] <dpm> popey, awesome, thanks for making this happen
[11:19] <popey> i did very little ☻
[11:19] <popey> add a line to a spreadsheet, mention on a hangout
[11:19] <dpm> without that "little" it wouldn't have happened :)
[11:19] <popey> anyway, so he will seed it, we need to make sure it works on device, then we can manually install the click to test, yes?
[11:19] <dpm> yes
[11:19] <popey> cool
[11:20] <dpm> popey, calling the run_on_ubuntu_touch.sh script with the -c argument creates a click package that can be used for local testing
[11:21] <popey> super.
[11:21] <popey> I'll test from a clean phone
[11:22] <dpm> popey, yeah, I hear you like using the --bootstrap argument :P
[11:22] <popey> hah
[12:32] <ahayzen> timp, ping
[12:32] <timp> ahayzen: hello
[12:32] <ahayzen> timp, wht do i need to do to https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/199906
[12:32] <ahayzen> timp, i passed one time... then failed the next?!
[12:33] <timp> some random fails have been fixed recently
[12:33] <timp> ahayzen: go to your branch and type "bzr merge lp:ubuntu-ui-toolkit"
[12:33] <timp> to get the latest changes from trunk
[12:33] <ahayzen> timp, does it just need reapproving after i repull?
[12:33] <ahayzen> timp, i'll update now
[12:34] <timp> ahayzen: then you push the changes to your branch, and we'll see what jenkins says
[12:34] <ahayzen> timp, ah yes it'll auto CI
[12:35] <timp> It is weird that it passed CI once and then failed autolanding
[12:35] <timp> let's see if the jenkins issues are fixed after merging trunk
[12:35] <ahayzen> timp, guess those really were random errors ;)
[12:36] <ahayzen> timp, right i've pushed
[12:37] <timp> ok. let's wait now. when jenkins approves I will happrove again, and then hopefull it will merge
[12:37] <ahayzen> timp, thanks
[12:46] <timp> ahayzen: don't hesitate to remind me to happrove if jenkins tests pass and I don't do anything :)
[12:47] <ahayzen> timp, cool...i'm on my lunch break so i'll check when i get back
[12:47] <timp> ok
[12:47] <ahayzen> timp, as in back from work ;) not end of lunch break...i'm in my lunch break :) lol confusing
[12:48] <timp> I thought I understood what you said, but now this second sentence confuses me ;)
[12:48] <ahayzen> timp, hehe
[12:48] <ahayzen> timp, i'll check later ~1800UTC
[12:48] <timp> okay I get it now :)
[15:58] <MyExHatesMeButMy> mzanetti,  what I do with my project (which is cmake) is to build it in a chroot envo for cross-compile, as far as adding new files and what not. What I do which is not that great... is left click file open terminal there and touch  the file then add it to the CMakeLists.txt and build it
[15:58] <MyExHatesMeButMy> also making things visible to qtcreator helps also
[15:59] <MyExHatesMeButMy> using the add_custom_target()
[15:59] <mzanetti> ?
[16:00] <mzanetti> I guess I miss some context here
[16:01] <MyExHatesMeButMy> mzanetti,  it was in response to you and dpm conversation
[16:01] <mzanetti> ah
[16:02] <MyExHatesMeButMy> example:   "Qt Creator cross-compiling support doesn't work with our projects either."   << cmake does
[16:02] <mzanetti> not really
[16:02] <MyExHatesMeButMy> using a chroot and also sbuilder
[16:02] <mzanetti> yeah.
[16:02] <mzanetti> which sucks imo
[16:02] <mzanetti> but anyways
[16:02] <MyExHatesMeButMy> you can run this from te run command
[16:02] <mzanetti> I know how to get around those issues
[16:03] <mzanetti> I'm just not happy that we have to
[16:03] <MyExHatesMeButMy> what dont you like ?
[16:03] <MyExHatesMeButMy> OptPng ?
[16:03] <MyExHatesMeButMy> OptiPNG *
[16:03] <MyExHatesMeButMy> takes forever lol
[16:04] <mzanetti> no... that's not the thing
[16:04] <MyExHatesMeButMy> mzanetti,  I did not know that qmake was cross-compile  for c++ projects and armhf
[16:04] <MyExHatesMeButMy> can it be ?
[16:05] <mzanetti> sure...
[16:06] <mzanetti> qmake doesn't care about the architecture. if you give it a arm compiler it'll compile stuff for arm
[16:06] <MyExHatesMeButMy> mzanetti,  can you tell me what you do not like about cmake and the whole sbuilder and what not suit
[16:06] <MyExHatesMeButMy> qmake cares that is what depolyment.pri files are for I thought
[16:06] <mzanetti> that it doesn't work with qtcreator
[16:07] <MyExHatesMeButMy> mzanetti,  works for me
[16:07] <mzanetti> no it doesn't
[16:07] <MyExHatesMeButMy> at any rate I am very interested in what you do not like about the build system of CMAKE
[16:07] <mzanetti> I do like cmake
[16:08] <MyExHatesMeButMy> mzanetti,  maybe I should be more clear .....
[16:09] <MyExHatesMeButMy> mzanetti,  what I do is one hack hack hack . go to projects ->run-> add the sbuilder commands and cp commands and Click commands(though I am writing in click into the build now) this builds a debian package for all archs and a click .
[16:10] <mzanetti> [17:09] <MyExHatesMeButMy> mzanetti,  what I do is one hack hack hack .
[16:10] <mzanetti> this is what I dislike ^^
[16:10] <MyExHatesMeButMy> what do you mean that is also what I do with qmake
[16:11] <MyExHatesMeButMy> hack hack hack means fix some thing add new code and test.
[16:11] <mzanetti> ah
[16:11] <MyExHatesMeButMy> I should have been more clear sorry about that
[16:12] <MyExHatesMeButMy> mzanetti,  you have your chroot all set up and what not to build the debian package so you can make click ?
[16:26] <dpm> hi oSoMoN, renato_, boiko, who's developing the address-book app? We'd need to add i18n support to it in the same way as you guys already did for the rest of the apps
[16:27] <renato_> dpm, is me
[16:27] <renato_> what do you need?
[16:27] <dpm> thanks, let me have a look at the code in LP
[16:42] <nik90> mhall119: regarding our discussion yesterday about the app lifecyle QML API docs, were you able to decide where to place it in documentation?
[16:46] <mhall119> nik90: I don't even know where (if) it exists as an API
[16:46] <MyExHatesMeButMy> dpm,  I have a po dir how do I use it ?
[16:47] <nik90> mhall119: oh
[16:47] <mhall119> bfiller: do we have a platform API for notifying an app when it's going to be suspended?
[16:47] <mhall119> or any other app lifecycle event?
[16:47] <MyExHatesMeButMy> dpm,  why not use qsTr compaired to i16n.tr I am so lost on that
[16:48] <MyExHatesMeButMy> Is there just some command that I need to run to run the translations ?
[16:51] <bfiller> mhall119: there is on property that apps listen for, active I believe. It's true on when app is in foreground and false when app moves to background
[16:52] <bfiller> mhall119: apps should use the StateSaver in sdk to save restore/stuff
[16:52] <bfiller> mhall119: no specific signal for suspend or kill, that happens in the StateSaver
[16:52] <coder> Can anyone help me, I'm trying  to make a unity scope and following the tutorial, I get to qmake and it says mrss package not found
[16:53] <mhall119> bfiller: where is StateSaver in the SDK?
[16:53] <bfiller> mhall119: one sec
[16:53] <nik90> mhall119: it is in the SDK docs in qtcreator
[16:53] <mhall119> and the active property too
[16:53] <nik90> mhall119: I have used it before
[16:53] <mhall119> is it in QML?
[16:53] <MyExHatesMeButMy> mhall119,  yeah
[16:53] <nik90> mhall119, bfiller: Although I am not sure if I can statesaver for my use case
[16:53] <MyExHatesMeButMy> it is at the bottom of the sdk api
[16:53] <MyExHatesMeButMy> mhall119,  ^
[16:53] <timp> bfiller, mhall119 Qt.application.active is the property you want
[16:54] <mhall119> http://developer.ubuntu.com/api/qml/sdk-1.0/Qt/#application-prop ?
[16:54] <MyExHatesMeButMy> mhall119,  it is a Ubuntu component
[16:54] <nik90> bfiller: a bit of a background, I need the platform API for the clock apps timer where when the clock app goes to the background when the timer is running, it should send a notification to the system asking it to wake it up or create a snap decision when the timer is done
[16:55]  * mhall119 see no StateSaver component in my docs
[16:55] <mhall119> is it new?
[16:55] <nik90> mhall119: 13.10 or 14.04?
[16:55] <mhall119> sdk-1.0
[16:55] <mhall119> http://developer.ubuntu.com/api/qml/sdk-1.0/
[16:55] <nik90> mhall119: definitely there in the SDK PPA version
[16:56] <nik90> mhall119: the online docs at developer.ubuntu.com are unfortunately out of date for certain components
[16:56] <nik90> I remember WebbyIT also noticing it for the Tabs component
[16:56] <nik90> where the count property is missing in the online docs
[16:57] <timp> from checking the bzr logs, it seems statesaver was added in september
[16:57] <mhall119> yeah, it's what was there when 13.10 was released
[16:57] <MyExHatesMeButMy> anyone know how to use translations here ? I made a cmake file http://paste.ubuntu.com/6751401/    Now how do I use it ?
[16:58] <bfiller> nik90: one sec, just finishing a call
[16:58] <nik90> bfiller: sure
[16:58] <mhall119> bzoltan: bfiller: we *really* need to know how we're going to be versioning the SDK
[16:59] <Carbogen> Hi mhall119
[17:00] <mhall119> hi Carbogen
[17:00] <Carbogen> Hey guys, I'm trying to install a Qt-Project to my Ubuntu Touch running Nexus 4...
[17:00] <timp> mhall119: yeah that's a good point. perhaps we need report a bug for that
[17:01] <Carbogen> I can't seem to get it to work
[17:02] <Carbogen> I built it to my device, and installed it. It seemed to work, or so said the console... But the app isn't on the device's Applications menu
[17:03] <Carbogen> Anyone know how I should procede?
[17:04] <MyExHatesMeButMy> Carbogen,  c++ ?  or pure qml ?
[17:04] <Carbogen> It's both.
[17:05] <MyExHatesMeButMy> ok
[17:05] <MyExHatesMeButMy> Carbogen,  this is a qmake project or cmake ?
[17:05] <bfiller> nik90: when the clock app is moved to the background it will be suspended by the system and killed if memory is needed
[17:05] <Carbogen> We worked on it together, I think. Do you know a Brendan Wilson?
[17:05] <MyExHatesMeButMy> Carbogen,  what ?
[17:05] <MyExHatesMeButMy> not sure
[17:05] <bfiller> nik90: so the right approach here is not for the app to fire a timer, but a service needs to do this on behalf of the app
[17:05] <Carbogen> I think I know you from Google+, not sure though...
[17:06] <bfiller> nik90: the service would always be running, I think there are plans for an alarm service in the system
[17:06] <bfiller> nik90: but not sure about this, tedg or tvoss would know about this
[17:06] <Carbogen> Anyways, I think it's a qmake project.
[17:06] <MyExHatesMeButMy> at any rate Carbogen   you need to make you app into cmake then build a debian package for it then make a chroot envo  then build the package in the chroot envo  then you need to exstract the deban package and make a click out of it
[17:06] <nik90> bfiller: so the service would run the code (timer) on behalf of the clock app when it is suspended?
[17:07] <Carbogen> k...
[17:07] <Carbogen> I'll look into that...
[17:07] <MyExHatesMeButMy> Carbogen,  c++ apps are newer to Ubuntu Touch  and cross-compikle even more
[17:07] <bfiller> nik90: more like the app tells the service to start a timer, the service fires the timer when it's done and the app is out of the picture
[17:07] <MyExHatesMeButMy> Carbogen,  I wrote about it on google plus somewhere
[17:08] <MyExHatesMeButMy> THere should be docs on it though
[17:08] <bfiller> nik90: the service would always fire the timer, not the app
[17:08] <MyExHatesMeButMy> I am willing to explain but not willing to write the docs :P
[17:08] <Carbogen> lol ok
[17:08] <nik90> bfiller: oh okay, so the clock app in itself is not responsible for the timer except for showing it to the user?
[17:08] <Carbogen> I'm looking at the Qt-Docs right now to see how to make a CMake project
[17:08] <bfiller> nik90: right
[17:08] <MyExHatesMeButMy> Carbogen,  we could do a trade off if you like. I explain and show you and you write a wiki ?
[17:08] <MyExHatesMeButMy> or mhall119  ^^
[17:09] <nik90> bfiller: That would definitely free up the memory usage of the clock app.
[17:09] <bfiller> nik90: the user would create the timer/alarm using the app and then the app just tells the service about this and lets it do the work
[17:09] <MyExHatesMeButMy> mhall119,  is that something that you would be interested in ?
[17:09] <nik90> bfiller: what about the notification when the timer is complete? Would the service do that or the clock app?
[17:10] <nik90> bfiller: at the moment, I have an MP where the clock app triggers a audio notification when the timer is complete.
[17:10] <bfiller> nik90: the service would fire the notification
[17:10] <bfiller> nik90: lets ask tedg on #ubuntu-touch
[17:11] <nik90> bfiller: ok
[17:11] <Carbogen> Wait, how do I make a CMake project? I need to set an executable field in the Tools >> Options >> Build&Run>> Cmake
[17:11] <MyExHatesMeButMy> Carbogen,  that is the thing you need to know how to make cmakelist.txt files
[17:12] <Carbogen> ok, I'll look it up.
[17:12] <MyExHatesMeButMy> Carbogen,  you need to replace all your qmake stuff with cmakelists.txt files
[17:12] <Carbogen> hmm
[17:13] <MyExHatesMeButMy> Carbogen,  I know it is a bit silly "to make a click package for c++ app one needs to make a debian package"
[17:13] <Carbogen> I think I have one already
[17:13] <Carbogen> A .deb package
[17:14] <MyExHatesMeButMy> Carbogen,  where is your code.  No offence but I think that you would know if you had the files
[17:14] <Carbogen> My code is opened up right now, the deb package is on my phone...
[17:14] <Carbogen> Want me to push it to github?
[17:17] <MyExHatesMeButMy> Carbogen,  well yeah all of it so I can look at it
[17:17] <Carbogen> MyExHatesMeButMy, https://github.com/EnderLance/ubuntubooks is it
[17:18] <MyExHatesMeButMy> Carbogen,  there is no debian packaging in that branch and it is not cmake
[17:18] <Carbogen> Sorry about the directory structure and the random files, I indend to clean it up when I get this problem solved.
[17:18] <Carbogen> Should I include the deb?
[17:19] <MyExHatesMeButMy> Carbogen,  how did you make a deb with out the debian files to make a debian package ?
[17:19] <Carbogen> not sure... I built and installed to the phone via QtCreator... Then I found a deb in my /home/phablet/dev_tmp folder
[17:20] <MyExHatesMeButMy> wow cool
[17:21] <Carbogen> yeah, had to install like a bazillion packages to the phone though, via apt-get install
[17:21] <MyExHatesMeButMy> Carbogen,  that is not good
[17:22] <Carbogen> Oh
[17:23] <Carbogen> Anyways, I pushed the deb to github
[17:23] <Carbogen> I gtg for about 10 minutes.
[17:23] <Carbogen> I'll be back
[17:26] <Carbogen> Alright I'm back, took less time than I expected...
[17:26] <Carbogen> Much less time XD
[17:27] <MyExHatesMeButMy> Carbogen,  can you launch that app from ssh ?
[17:27] <Carbogen> I'll try
[17:28] <MyExHatesMeButMy> Carbogen,  like      /path/to/binary --desktop_file_hint=/path/to/desktop/file.desktop
[17:28] <Carbogen> ah
[17:28] <Carbogen> I'm trying to run the executable from the folder
[17:28] <Carbogen> like, ./ubuntubooks
[17:29] <Carbogen> It was saying could not connect to display.
[17:29] <Carbogen> wait, the binary is a .bin file, correct?
[17:29] <Carbogen> btw I don't see one
[17:31] <MyExHatesMeButMy> Carbogen,  <MyExHatesMeButMy> Carbogen,  like      /path/to/binary --desktop_file_hint=/path/to/desktop/file.desktop
[17:31] <bzoltan> mhall119: whatever you like to version
[17:33] <MyExHatesMeButMy> Carbogen,  your app will not show up in the dash because unity=scope-click does not know about it
[17:33] <MyExHatesMeButMy> so you have to launch it and save to your launcher. Or make a click package out of the debian package that you have
[17:35] <nik90> mhall119, dpm, dpm_: Ted and I need your help with https://code.launchpad.net/~ted/ubuntu-clock-app/url-dispatcher/+merge/201536
[17:35] <nik90> regarding the qmlproject file
[17:38] <Carbogen> Very sorry, my internet connection dropped
[17:40] <dpm> nik90, just finishing a call and I'll have a look
[17:40] <MyExHatesMeButMy> Carbogen,  that is cool no worries I am DL you deb and will try it out
[17:40] <Carbogen> k
[17:41] <Carbogen> It's not finished though, so there are a lot of bugs and glitches...
[17:41] <Carbogen> Graphical ones, nothing dangerous.
[17:43] <MyExHatesMeButMy> Carbogen,  you need to make your click json files
[17:43] <MyExHatesMeButMy> also a desktopfile
[17:43] <Carbogen> I thought I had a desktop file...
[17:43] <MyExHatesMeButMy> Carbogen,  where is it ?
[17:43] <Carbogen> in ./qml/OAuthPlayground/ubuntubooks.desktop?
[17:44] <mhall119> bzoltan: it's not my place to decide on release strategy for the SDK
[17:44] <Carbogen> ooh it's uBooks.desktop...
[17:44] <mhall119> I just need to know what the release strategy is to label the online API docs correctly
[17:44] <MyExHatesMeButMy> Carbogen,  ahh yeah you need to change this up I will paste a example
[17:45] <Carbogen> Yeah, I changed my project's directory so many times because so many things kept being messed up then fixed... It's hard to keep track of everything
[17:45] <bzoltan> mhall119:  Our strategy is to release continuously ... we regularly push changes to the actual development release and do backports for P, Q, R, S series... there is nothing what we would release at a magic date
[17:45] <MyExHatesMeButMy> Carbogen,  why dont you work on the click JSON files and I will work on your debian package
[17:46] <mhall119> nik90: I don't think we need that in the debian packages, since the desktop doesn't provide the alarm service anyway and debian packaging doesn't provide the click hooks that appear to be used to register with url-dispatcher
[17:46] <bzoltan> mhall119:  but we can stamp up a specific release when we reach a significant milestone. That could be called 1.1
[17:47] <mhall119> bzoltan: my concern is that if I have a device running the last saucy image of Ubuntu, it won't have all of the APIs currently available in the Trusty images
[17:47] <ahayzen> timp, ping
[17:47] <Carbogen> Ok.... what do I need to do though? I apologize for being so un-educated in this field, I'm a beginner
[17:47] <dpm> nik90, replied to the MP
[17:47] <mhall119> bzoltan: and an app using the new APIs shouldn't think it can safely install on a device running a version of the OS that doesn't provide them
[17:48] <bzoltan> mhall119: The APIs provided by the Qt framework and the SDK we develop are identical between P and T
[17:49] <bzoltan> mhall119:  but the API versioning you talk about is going to be a valid problem at some point. I do not know the solution for that right now.
[17:49] <dpm> renato_, nerochiaro, I've changed my review to Approved on https://code.launchpad.net/~amanzi-team/address-book-app/address-book-app-pot/+merge/188549 - could one of you guys top-approve?
[17:50] <MyExHatesMeButMy> Carbogen,  no worries I will make it so that you have a example
[17:50] <mhall119> bzoltan: I don't think the Saucy device images have the same APIs as the Trusty device images
[17:50] <Carbogen> hmm k
[17:51] <nik90> mhall119: true. I will note that in the MP for ted to consider
[17:53] <MyExHatesMeButMy> Carbogen,  can you fill in the blanks here please http://paste.ubuntu.com/6751682/
[17:53] <ahayzen> anyone know why jenkins hasn't run on the latest revision https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/199906 ?
[17:53] <nik90> dpm: thnx
[17:53] <MyExHatesMeButMy> Carbogen,  like YOUR Name and the email part
[17:53] <Carbogen> k
[17:53] <bzoltan> mhall119:  On the Qt and on the UITK and QML APIs they are identical.
[17:54] <bzoltan> mhall119:  on the platform APIs they could be different.. but that is not the scope of the SDK ... we can not call SDK all the APIs available from the archives
[17:56] <timp> ahayzen: hi. I see jenkins still didn't run the tests for your branch? :s I don't know what to do about it. perhaps in #ubuntu-ci-eng someone knows?
[17:56] <timp> ahayzen: I gotta go now. dinner time.
[17:56] <Carbogen> pushed it to https://github.com/EnderLance/ubuntubooks, MyExHatesMeButMy
[17:56] <ahayzen> timp, ok thanks
[17:58] <MyExHatesMeButMy> ok Carbogen  you are ready to make a click !  open a terminal  and cd  to where your app is
[17:59] <mhall119> bzoltan: they won't be identical because we aren't building new Saucy images
[17:59] <Carbogen> k
[18:00] <bzoltan> mhall119:  the APIs has little to do with the images
[18:00] <Carbogen> then..?
[18:00] <mhall119> ogra_: is that correct that we're not making new Saucy images?
[18:00] <MyExHatesMeButMy> Carbogen,   dpkg-deb -R ubuntubooks_0.1-1_armhf.deb Install
[18:00] <mhall119> bzoltan: but the images have everything to do with the ability of apps to run
[18:00] <MyExHatesMeButMy> Carbogen,  cd install
[18:00] <bzoltan> mhall119:  The Qt is the same in Saucy as it is in Trusty
[18:01] <Carbogen> yup
[18:01] <ogra_> mhall119, well, we could at any time, not sure it is desired ... the last one we built hasnt even been tested by anyone (102)
[18:01] <MyExHatesMeButMy> Carbogen,  rm -r DEBIAN;  rm -r usr/
[18:01] <Carbogen> done
[18:01] <MyExHatesMeButMy> Carbogen,  cd ../ ;  cp manifest.json install/
[18:02] <bzoltan> mhall119:  the very last  Saucy image has the same Qt API as in the Trusty ... even after we migrate to 5.2 Qt it will be API compliant with 5.0.1 in Saucy
[18:02] <Carbogen> done
[18:02] <MyExHatesMeButMy> Carbogen,  cd install/
[18:02] <bzoltan> mhall119:  same in the SDK ... we do not break public APIs between S and T
[18:02] <Carbogen> yup
[18:02] <MyExHatesMeButMy> Carbogen,  touch ubuntubooks.desktop ; touch ubuntubooks.json
[18:03] <Carbogen> ok
[18:03] <bzoltan> mhall119:  but all in all... we can bind the SDK release number to the series ... 13.10, 14.04 ..
[18:03] <mhall119> bzoltan: so SavedState is in the Saucy builds?
[18:03] <mhall119> or StateSaver whatever it ws
[18:03] <MyExHatesMeButMy> Carbogen,  now open the desktop file and make it look like this ....http://paste.ubuntu.com/6751712/
[18:04] <Carbogen> ok done
[18:04] <MyExHatesMeButMy> Carbogen,  once that is done open up the ubuntubooks.json and make it look like this .... http://paste.ubuntu.com/6751717/
[18:05] <Carbogen> yup
[18:05] <MyExHatesMeButMy> Carbogen,  now back to the terminal  and     cd ../
[18:05] <Carbogen> mhm
[18:06] <MyExHatesMeButMy> Carbogen,  you should now be at your top source dir now copy your icon to the install folder and call it ubuntubooks.png
[18:07] <MyExHatesMeButMy> Carbogen,  cp ubuntubooks64.png install/ubuntubooks.png
[18:07] <bzoltan> mhall119: it is in the SDK PPA backported ... so on a legacy device one should upgrade to the SDK PPA content...
[18:08] <mhall119> bzoltan: devices don't use apt at all, let alone PPAs
[18:08] <Carbogen> my icon disapeared... XD
[18:09] <MyExHatesMeButMy> Carbogen,  what  ?
[18:09] <bzoltan> mhall119: they can use ... just enable it
[18:10] <bzoltan> mhall119: are we going to support Saucy?
[18:10] <Carbogen> k I found it
[18:10] <Carbogen> I placed it into the Install directory
[18:11] <Carbogen> so iow done.
[18:12] <MyExHatesMeButMy> ok
[18:12] <MyExHatesMeButMy> Carbogen,  what is you pwd  ?
[18:12] <Carbogen> pwd?
[18:13] <MyExHatesMeButMy> in the terminal tyoe that in
[18:13] <Carbogen> the project's parent dir
[18:13] <MyExHatesMeButMy> type *
[18:14] <Carbogen> it's /home/<myuser>/UTouch-Apps/ubuntubooks
[18:14] <MyExHatesMeButMy> cool
[18:14] <MyExHatesMeButMy> Carbogen,   click build install
[18:14] <MyExHatesMeButMy> Carbogen,  did it build ?
[18:14] <Carbogen> Successfully built package in './ubuntubooks_0.1_armhf.click'.
[18:15] <MyExHatesMeButMy> good
[18:15] <MyExHatesMeButMy> Carbogen,  phone is pluged into computer ?
[18:15] <Carbogen> yes, I'm transfering the package
[18:15] <MyExHatesMeButMy> wait !
[18:15] <Carbogen> ooh k
[18:15] <MyExHatesMeButMy> where are you transfering it to ?
[18:16] <Carbogen> I didn't do anything else, just copy the .click
[18:16] <MyExHatesMeButMy> just so I know what commands to give you lol
[18:16] <Carbogen> to /home/phablet/Documents/
[18:16] <MyExHatesMeButMy> cool
[18:16] <Carbogen> Ik
[18:16] <MyExHatesMeButMy> adb shell
[18:16] <MyExHatesMeButMy> su -
[18:16] <Carbogen> it's either click install the_package.click
[18:16] <MyExHatesMeButMy> woops
[18:16] <MyExHatesMeButMy> su - phablet
[18:16] <Carbogen> or pkcon install-local the_package.click
[18:16] <MyExHatesMeButMy> sudo -u phablet -i
[18:17] <MyExHatesMeButMy> Carbogen,  you want help ?  sop jumping the gun
[18:17] <Carbogen> k sry
[18:18] <MyExHatesMeButMy> So did you enter in the commands above and you are the user phablet now right ?
[18:18] <Carbogen> yes
[18:18] <Carbogen> sudo -u phablet -i
[18:18] <Carbogen> after adb shell.
[18:19] <MyExHatesMeButMy> nope
[18:19] <MyExHatesMeButMy> Carbogen,  exit
[18:19] <Carbogen> ?
[18:19] <MyExHatesMeButMy> what does the user say you are ?
[18:19] <Carbogen> k I'm root in my phone, exit again?
[18:19] <MyExHatesMeButMy> root ?
[18:19] <Carbogen> yes
[18:19] <MyExHatesMeButMy> good
[18:19] <MyExHatesMeButMy> su - phablet
[18:19] <Carbogen> k
[18:19] <MyExHatesMeButMy> sudo -u phablet -i
[18:20] <Carbogen> done
[18:20] <MyExHatesMeButMy> now cd /where/my/click/is
[18:20] <timp> ahayzen: I'll happrove your branch and see what happens
[18:20] <Carbogen> ok
[18:20] <Carbogen> done
[18:20] <MyExHatesMeButMy> pkcon install local my_awesome_new_click.click
[18:20] <MyExHatesMeButMy> make sure that you use the right names
[18:20] <ahayzen> timp, thanks no one answered in #ubuntu-ci-eng
[18:20] <Carbogen> isn't it pkcon install-local?
[18:20] <Carbogen> and not pkcon install local
[18:21] <MyExHatesMeButMy> yes it is good catch Carbogen
[18:21] <Carbogen> thanks :)
[18:21] <Carbogen> working just like it was for my previous apps :D
[18:21] <Carbogen> k it's done
[18:22] <MyExHatesMeButMy> once it installs reboot the phone,  and it should now be installed and you should be able to open from dash
[18:22] <Carbogen> k...
[18:22] <MyExHatesMeButMy> Carbogen,  but I am wondering what you have your Viewer source set to though might need to change it and run all this over again
[18:23] <Carbogen> well the app runs on the computer in qmlscene so I expect it should work on the device
[18:24] <Carbogen> SOURCES += $$PWD/qtquick2applicationviewer.cpp
[18:24] <MyExHatesMeButMy> Carbogen,  what there is no qmlscence with qmake projects you create your own viewer
[18:25] <Carbogen> then my colaborator must've taken care of that. He did all the C++ I did the QML.
[18:29] <Carbogen> Thankyou MyExHatesMeButMy
[18:30] <Carbogen> It works now.
[18:30] <MyExHatesMeButMy> Good !
[18:30] <MyExHatesMeButMy> Carbogen,  screen shot
[18:32] <Carbogen> Ok
[18:33] <MyExHatesMeButMy> Carbogen,  you know how to use phablet-screenshot ?
[18:36] <MyExHatesMeButMy> Carbogen,  the thing is I think that this can also be done in a chroot envo  making Cmake not having to freaking happen.  If this is the case then I spent a lot of un-nessary time porting my apps to cmake :(
[18:36]  * MyExHatesMeButMy goes to the punching bag ! 
[18:37] <Carbogen> https://plus.google.com/+BrendanWilson/posts/fuybAgt5n77 MyExHatesMeButMy
[19:37] <mhall119> bzoltan: it's not about supporting Saucy, it's about supporting app devs
[19:39] <bzoltan> mhall119:  if we talk about Saucy then we talk about supporting Saucy. Who is going to develop app for what device what has Saucy? Who is using Ubunt Touch on Saucy? I mean is it a real use case?
[19:40] <bzoltan> mhall119: and when we talk about supportoing app devs I think we mean supporting them to develop for a spcific platform. Are we committed to support app devs in creating apps for Saucy?
[19:41] <beuno> bzoltan, I have no context at all here, but sanity tells me it means allowing devs on Desktop Saucy to create apps for 13.10 and 14.04 touch
[19:42] <bzoltan> beuno:  that one we cover with the SDK PPA where we have all the APIs for Precise, Quantal, Raring and Saucy ...
[19:43] <bzoltan> beuno:  no developer is blocked because of using "wrong" serie ... we support all since 12.04
[19:43] <beuno> right
[19:43] <beuno> so that shuts me up
[19:43] <beuno> :)
[19:45] <bzoltan> beuno:  As I understand mhall119 talks about the case when somebody is developing for an Saucy Ubuntu  ... I wonder if there is any Saucy based touch device out there what could be a target.
[19:46] <beuno> bzoltan, I don't think any OEM will ship 13.10, n
[19:46] <beuno> no
[19:47] <bzoltan> beuno:  I certainly do hope the same.
[19:47] <bzoltan> Why would anybody ship a device with a platform what will EOL in June this year.
[19:48] <beuno> bzoltan, you know OEMs :)
[19:49] <bzoltan> beuno:  Hehh :) yes
[19:50] <MyExHatesMeButMy> how in the world do I make translations for my app ?  I have wrote cmake file but how does it work.  Do I still need someone to translate all of it if so what is the point ? I am sorry I just dont understand this at all.  http://paste.ubuntu.com/6752202/
[19:50] <MyExHatesMeButMy> why move away from things that are in the kit already like NOOP or qstr ?
[19:51] <MyExHatesMeButMy> seems like it just makes more work for devs like making there app Touch and blackberry or android. I am so lost on this
[19:52] <MyExHatesMeButMy> or do we just say that "this is the way that it is tough stuff" Or am I wrong all together ?  I am sure that it is me.  but this is confusing
[19:55] <ahayzen> timp, it failed again :/ https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/199906
[23:47] <popey> nik90: shall i file a bug for this ☻   http://popey.com/~alan/phablet/device-2014-01-14-234616.png