[01:57] <akiva-thinkpad> ajalkane, ah nice !
[01:57] <akiva-thinkpad> I just saw your merge
[01:58] <akiva-thinkpad> I'm going to work on getting it merged immediatel.
[02:08] <akiva-thinkpad> ajalkane, what does cancel do?
[02:08] <akiva-thinkpad> it just turned my screen blank o_o
[02:36] <ajalkane> akiva-thinkpad: howdy... I have bad news
[02:36] <akiva-thinkpad> ajalkane, ?
[02:37] <ajalkane> The designers have been too busy, there's just have not been time to take a look at the different propositions
[02:37] <akiva-thinkpad> ajalkane, yah I know that ~
[02:37] <ajalkane> But I really want to get this top header merged
[02:37] <akiva-thinkpad> I'm not expecting this to make rtm
[02:37] <akiva-thinkpad> ajalkane, all in due course
[02:37] <akiva-thinkpad> btw I merged your branch
[02:38] <ajalkane> So I hope you don't mind me taking the conservative approach, and with future branches more experimental stuff can be tried?
[02:38] <akiva-thinkpad> ajalkane, Doesnt bother me.
[02:39] <ajalkane> akiva-thinkpad: that's great to hear. How about I make a new merge request to your branch, that has many fixes and a simplified approach that I can sign off on. And then in future you can make new propositions if you feel necessary?
[02:40] <akiva-thinkpad> ajalkane, sounds good.
[02:41] <ajalkane> akiva-thinkpad: good... do you have time to work on the autopilot tests once I have made the merge request to your branch? I think I can try to do some autopilot tests tomorrow also to help it make through
[02:41] <akiva-thinkpad> ajalkane, I have been a bit preoccupied by the recent stuff in Canada, but yes; I have all the time in the world otherwise.
[02:42] <ajalkane> heh okay... it'd be great if you can do some autopilot tests tonight and push them in the branch after you've checked the merge request I'm about to do
[02:42] <akiva-thinkpad> ajalkane feel free to delete the unused code; we can go back to it in a previous branch.
[02:42] <ajalkane> I will try to continue with it tomorrow and make new merge requests
[02:43] <akiva-thinkpad> ajalkane, Well I need to know what exactly is sticking first.
[02:43] <ajalkane> Yeah I have done such clean-up, the old code is available anway as its been pushed
[02:43] <akiva-thinkpad> ajalkane, exactly
[02:43] <akiva-thinkpad> so feel free to delete unused code; we can grab it later if need be.
[02:43] <ajalkane> ok good!
[02:45] <akiva-thinkpad> ajalkane, As it stands; the only thing I have any semblence of emotional investement in is the contentx behaviour of the flickable, and the flickable itself. Anything else is free for the chopping block without debate.
[02:46] <akiva-thinkpad> ajalkane, have the branch uploaded within the next hour and a half, and I'll branch it and start working on getting it ready for a merge.
[02:46] <akiva-thinkpad> ajalkane, does this work?
[02:50] <ajalkane> That sounds good, I will try to do it
[02:50] <ajalkane> Yeah I see you have done much work on that and I think I preserved the essence of it
[02:51] <akiva-thinkpad> Cool beans
[02:51] <ajalkane> Like, most of it. I just changed where it positions it when changing folders
[02:51] <ajalkane> It's, by the way, very cool work - so thanks for it
[02:52] <akiva-thinkpad> ajalkane, Np ~
[03:03] <ajalkane> akiva-thinkpad: I've done the merge request, check it out
[03:04] <akiva-thinkpad> ajalkane,
[03:04] <akiva-thinkpad> sure
[03:04] <ajalkane> And once we've done the autopilot tests it's good to go for merging in my opinion
[03:04] <ajalkane> After that there's good time to look if it needs some improving and wait for design decisions
[03:05] <ajalkane> Thanks already for the great work you've been doing on the top header merge! It's really important improvement
[03:06] <ajalkane> I'll be checking again in about an hour... and if you get any autopilot tests done, please commit them to your branch so that I don't duplicate your work tomorrow :)
[03:07] <akiva-thinkpad> ajalkane, I'll doubt that I will get around to it today. As said, with the events happening in Canada, I am a bit preoccupied. I am merging though right now and checking out the branch.
[03:10] <akiva-thinkpad> ajalkane, May I offer a bit of disagreement on the contentx?
[03:10] <ajalkane> Of course you can, and please do offer disagreement
[03:10] <akiva-thinkpad> okay
[03:11] <akiva-thinkpad>  /disagreement time; brace yourself! -- or rather, why I chose the model the way I did.
[03:11] <ajalkane> I just hope we can agree the current one is better than the trunk, because this is what I can sign-off on right now - and I really would like to get it merged :)
[03:12] <akiva-thinkpad> The reason why I did not have the content x adjust to any new folder, and only home and its immediate subfolders
[03:12] <akiva-thinkpad> was because you are unlikely to go into many child directories after that.
[03:14] <akiva-thinkpad> and so it made more sense in my opinion to have to let it extend on, and help keep your baring as to where you were in the current path.
[03:14] <akiva-thinkpad> Not sure if that makes sense.
[03:14] <ajalkane> I can understand that. I did the change just because now it's for new users also clear that clicking on the folder next to "back" gets them upwards.
[03:14] <ajalkane> Your reasoning makes perfect sense
[03:15] <ajalkane> I was just looking at it from the going upwards in consistent way kind of eyes - you always click on the shown folder item to go up
[03:16] <ajalkane> And I think any tweaking to this branch will be easy in future - this doesn't have to be the final say. Just the one to get the top header in meaningful way in reasonable time
[03:17] <ajalkane> I'm gone for a while, and no problem if you don't have time for autopilot tests today. I'll look at them tomorrow morning if I can make any sense of them :)
[03:18] <akiva-thinkpad> ajalkane, fine I'll leave it as is. If I want; I'll branch my version in the app store :P Opensource for the win
[03:18] <akiva-thinkpad> your version is good for the phone anyways, as there is not much space for displaying full paths.
[04:19] <ajalkane> akiva-thinkpad: the limited space was another worry of mine. Initially I thought why not show "> upperDir / currentDir". But then currentDir could be such a long name that you can't see the upperDir and moving up wouldn't be consistent
[09:58] <vitimiti> Hi
[12:42] <popey> morning all!
[12:42]  * popey is in stadler A
[12:43] <ahayzen> o/
[12:43] <ajalkane> morning popey
[12:44] <ahayzen> popey, should any of us be in there as well?
[12:44] <ajalkane> balloons: I'm unsurprisingly having troubles with autopilot, it just crashes now. Do you know what this is about: http://pastebin.com/qF3aGECU
[12:44] <ahayzen> popey, seems like a design thing?
[12:44] <popey> yeah
[12:44] <popey> i am not sure even I need to be here, let alone you guys ☻
[12:44]  * ahayzen has autopilot things to fix
[12:44] <balloons> ajalkane, looking
[12:45] <balloons> ajalkane, so the application doesn't even startup?
[12:48] <ajalkane> balloons: seems like that
[12:48] <ajalkane> I can run it from QtCreator
[12:49] <balloons> ajalkane, mmm. so in theory it's been built
[12:50] <balloons> ajalkane, you should run with autopilot3
[12:50] <balloons> ajalkane, autopilot3 run -v filemanager and show that log would be more useful
[12:52] <ajalkane> sorry, Ubuntu crashed. I'll try again
[12:54] <ajalkane> ah, it's trying to run the click package
[12:58] <rpadovani> mzanetti, lp:~rpadovani/reminders-app/uriHandler when you have time
[13:01] <dpm> rpadovani, http://pad.ubuntu.com/reminders-app-meeting
[13:01] <rpadovani> thanks!
[13:03] <ajalkane2> Sorry again, I'm having multiple problems here
[13:06] <ajalkane2> balloons: so here is an example of the output: http://pastebin.com/D9uppdiW
[13:07] <ajalkane2> this line looks suspicious: Path: /opt/click.ubuntu.com/.click/users/arto/com.ubuntu.filemanager
[13:08] <balloons> ajalkane2, are you running on the desktop or device?
[13:08] <ajalkane2> on the desktop
[13:08] <balloons> right, so it's not finding the binary
[13:09] <ajalkane2> does it understand branches? Or does it expect to run from trunk?
[13:09] <balloons> ajalkane2, try building inside the source tree manually, that should solve it. That said, I thought support for out of tree binaries existed in file manager
[13:10] <balloons> ajalkane2, qtcreator by default builds in a special seperate folder the test doesn't know about
[13:10] <ajalkane2> it worked a couple of days ago and I was happy
[13:12] <balloons> ajalkane2, right, so it's rather odd that changed. I don't have the source in front of me, but I'm pretty sure it's supposed to have support for these out of tree builds
[13:17] <balloons> ajalkane2, can you leave the branch you are working on and I can try?
[13:24] <ajalkane2> balloons: yeah thanks... just a sec
[13:25] <ajalkane2> balloons: https://code.launchpad.net/~ajalkane/ubuntu-filemanager-app/toolbar-to-header-modifications
[13:27] <ajalkane2> I ran "cmake . && make" and still have the same problem
[13:28] <ajalkane2> I do have the click package installed on my desktop, might that be the cause of the problem?
[13:28] <ajalkane2> though that should have been a problem a couple of days too then
[13:35] <ajalkane2> balloons: I took a fresh checkout, and built it with only desktop target. And now it works!
[13:42] <ajalkane2> can I run with autopilot just one test out of a suite?
[13:43] <veebers> ajalkane2: you sure can, just provide the test id (i.e. application.tests.test_som_feature) on the command line
[13:44] <ahayzen> Hi, How can i tell when an object created using Qt.createComponent and createObject has been destroyed?
[13:47] <mzanetti> ahayzen: http://qt-project.org/doc/qt-5/qml-qtqml-component.html#destruction-signal
[13:50] <ahayzen> mzanetti, hmmm how do I use that from outside of the object.... i basically have a created page being pushed and then popped from the stack and i need to refilter the list after it has been popped
[13:51] <ahayzen> mzanetti, the issue at the moment is when it refilters the model the delegate gets removed that holds the created object causing an error and then freezing the UI
[13:51] <ahayzen> mzanetti, so i need to know after the created object has been destroyed ?
[13:52] <mzanetti> var page = component.createObject()
[13:52] <mzanetti> page.destroyed.connect(function() { print("destroyed"); } )
[13:52] <ahayzen> mzanetti, ok thanks i'll try that :)
[13:53] <mzanetti> also, you might want to use pageStage.onDepthChanged in this case?
[13:53] <mzanetti> ahayzen: ^
[13:54] <ahayzen> mzanetti, ooo yeah i'll try that as well :)
[13:56] <ahayzen> mzanetti, for the first one i get... TypeError: Cannot call method 'connect' of undefined
[13:56] <mzanetti> page.destruction.connect(function() { print("destroyed"); } )
[13:56] <mzanetti> I messed up the name
[13:57] <mzanetti> basically you use object.signalName.connect()
[13:57] <ahayzen> ah yeah i tried onDestruction earlier but it is a signal not a property
[13:59] <kunal> popey, this branch lp:~pkunal-parmar/ubuntu-calendar-app/NewDayView
[14:02] <ahayzen> mzanetti, songsPage.destruction.connect was undefined as well... and onDepthChanged is too early and causes the error that we were having :/
[14:07] <vthompson> davmor2, do you want to try using this click to fix your playing an album from the scope issue? https://www.dropbox.com/s/3xlphjg2wx01j51/com.ubuntu.music_1.3.700_all.click?dl=0
[14:07] <vitimiti> I have this problem when I open a dialog menu in my app: the text is way wider than the white portion where it's meant to be, until I click a button that changes text and click it (changing it back to the text that was overflowing), and then it's inside the white portion. Is this a known issue? Can I fix it for it to look good before touching the text changer button?
[14:13] <popey> kunal: kk
[14:28] <ajalkane2> veebers: thanks!
[14:28] <veebers> ajalkane2: nw :-)
[14:41] <kalikiana> t1mp: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/pushToTemp/+merge/239568
[14:44] <balloons> kunal, file:///home/nskaggs/workspace/Collection-Change/NewEvent.qml:566: TypeError: Cannot read property 'contactSelected' of undefined
[14:47] <mihir> popey: one of them is http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-013
[14:50] <mhall119> DanChapman: would Dekko be able to use http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Connectivity.NetworkingStatus/ to switch the trojita-core bits into "bandwidth saving mode" when on cellular data?
[14:50] <mhall119> and does that mode actually do anything at the moment?
[15:05] <kalikiana> elopio: please have a look at this one https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1385324
[15:22] <kalikiana> elopio: nevermind in fact, I saw the other bug and reviewed the branch
[15:36] <mzanetti> rpadovani: manifest.json.in:10
[15:37] <mzanetti> comma missing
[15:41] <gventuri> mihir: kunal: I've sent you guys an email. Let me know if it makes sense. The height of the sub-header should be 1GU less then the standard header, Text should be on one line
[15:42] <kunal> gventuri, thanks, let me check
[15:44] <gventuri> kunal: I can catch up today if you want
[15:44] <kunal> yes, that would be great
[15:44] <kunal> so you said its just icon, no feedback required ?
[15:44] <kunal> to notify its pressed or not ?
[15:44] <kunal> and I am not sure, but do we have icons for < and > ?
[15:46] <kunal> gventuri, and I also made some change for month view alignment issue
[15:46] <gventuri> kunal: coming
[15:46] <kunal> thanks
[15:47] <rpadovani> mzanetti, thanks, added
[15:50] <mzanetti> rpadovani: doesn't work...
[15:50] <mzanetti> Unable to dispatch url 'evernote://newnote':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'evernote://newnote' is not handleable by the URL Dispatcher
[15:50] <mzanetti> not yet sure why
[16:02] <elopio> kalikiana: ok.
[16:07] <Elleo> gventuri: I'm free of meetings today, so if you want to discuss the keyboard thing you started mentioning yesterday just grab me when it's convenient :)
[16:08] <gventuri> Elleo: Thanks
[16:09] <gventuri> Elleo: after lunch 1:30ish?
[16:10] <Elleo> gventuri: sure, sounds good; shall I come to you?
[16:11] <gventuri> Elleo: Thanks
[16:11] <Elleo> gventuri: San Fransisco, right?
[16:12] <gventuri> Elleo: Yep
[16:13] <Elleo> gventuri: okay, cool
[16:34] <boiko> mihir: http://paste.ubuntu.com/8658167/
[16:57] <DanChapman> mhall119: it's already setup to use it in a naive fashion that on limitedbandwidth it will automatically just set bandwidth saving mode http://bazaar.launchpad.net/~dpniel/dekko/trunk-1/view/head:/qml/main.qml#L340.
[16:57] <DanChapman> The issue is the statusChanged signal of the NetworkingStatus singleton never get's fired so it still doesn't change anything in dekko. I havn't had time to dig into it yet. And yes that mode does currently does drastically reduce network usage
[16:58] <mhall119> DanChapman: you can probably listed for the onLimitedBandwidthChanged signal instead
[16:59] <mhall119> s/listed/listen/
[17:00] <DanChapman> mhall119: nothing happens on that one either
[17:00] <DanChapman> http://bazaar.launchpad.net/~dpniel/dekko/trunk-1/view/head:/qml/main.qml#L355
[17:04] <mhall119> DanChapman: why the isRunningOnMir check?
[17:05] <DanChapman> mhall119: so the NetworkWatcher still works on unity 7
[17:05] <mhall119> is the API not available in 14.10 on Unity 7?
[17:08] <mhall119> Wellark: ^^ can you help DanChapman get NetworkStatus working for Dekko?
[17:09] <DanChapman> mhall119: tbh i'm not entirely sure it doesn't seem to work on 14.10 unity 7 using the Qt c++ bindings whcich i tried here. http://bazaar.launchpad.net/~dpniel/dekko/UnityNetwrkWatcher/view/head:/src/Imap/Model/UnityNetworkWatcher.cpp
[17:55] <rpadovani> mzanetti, is that the modify I have to do in uriHandler to CmakeLists.txt? http://paste.ubuntu.com/8659216/
[17:56] <mzanetti> rpadovani: no... configure_file() is used to generate files out of .in files
[17:56] <mzanetti> rpadovani: like, reminders.desktop.in will be reminders.desktop after the configure
[17:56] <mzanetti> and it'll replace stuff marked with % in the file
[17:57] <mzanetti> but we don't need that for the url-dispatcher file
[17:57] <rpadovani> mzanetti, ah, gotcha. So what we need to do?
[17:57] <mzanetti> we just need to install it without change
[17:57] <ahayzen> mihir, this bug https://bugs.launchpad.net/mir/+bug/1383745
[17:58] <mzanetti> rpadovani: line 71
[17:58] <rpadovani> mzanetti, danke
[18:04] <ahayzen> mihir_, do you mind marking that ^^ bug as also affects you so it is confirmed?
[18:04] <mihir> ahayzen: sure
[18:11] <ahayzen> mihir, thanks :)
[18:19] <kunal> gventuri, sorry this one http://imgur.com/hVGW0Ob
[18:23] <gventuri> kunal: nice
[18:24] <gventuri> kunal: how high is the subheader?
[18:27] <rpadovani> mzanetti, I updated the uriHandler branch, I dunno if you like the solution I thought, let me know!
[18:53] <kunal> gventuri, regarding EventBubble change from UbuntuShape to Rectangle
[18:53] <kunal> should we use some boarder ?
[18:53] <kunal> http://imgur.com/mlv86yG
[18:53] <kunal> if you look at image
[18:54] <kunal> there are two events at same time slot, it will be difficult to distinguish both if we use flat color
[18:55] <popey> JoeyChan: do you have a copy of the photo you took outside that I can use in a presentation?
[18:55] <JoeyChan> popey:  check my g+   (´・ω・｀)
[18:55] <popey> oh cool!
[19:00] <gventuri> kunal: yes please. which colour are you using?
[19:03] <gventuri> kunal: I guess Ubuntu colour Light Grey #888888
[19:09] <kunal> gventuri, I was think white color, same as text color
[19:10] <gventuri> kunal: try LightGrey or DarkGrey in Ubuntu Colours
[19:11] <gventuri> kunal: eventually we are not going to use the Theme Palette anymore, just UbuntuColours
[19:11] <gventuri> kunal: apps will be able to define their own theme and palette
[19:13] <kunal> gventuri, ok
[19:13] <kunal> gventuri, will try both and post some pics, let me know which you like
[19:17] <kunal> gventuri, light gray - > http://imgur.com/9jygEVI
[19:18] <kunal> gventuri, sorry , dark gray ->http://imgur.com/9jygEVI
[19:18] <kunal> light gray -> http://imgur.com/Fl26xuL
[19:20] <gventuri> kunal: you are right, make it white
[19:21] <kunal> gventuri, ok, thanks
[23:10] <akiva-thinkpad> ajalkane, pingers
[23:11] <akiva-thinkpad> I tried a merge of your branch into mine, and ran into 5 conflicts. I defferred to the bottom each time, presumably the changes you made, and it isnt running for me
[23:14] <akiva-thinkpad>     function openFileManager() {
[23:14] <akiva-thinkpad>         pageStack.push(fileManagerComponent, { fileSelectorMode: true} )
[23:14] <akiva-thinkpad>     }
[23:14] <akiva-thinkpad>     function openFile(filePath) {
[23:14] <akiva-thinkpad>         pageStack.push(Qt.resolvedUrl("content-hub/FileOpener.qml"), { fileUrl: "file://" + filePath} )
[23:14] <akiva-thinkpad>     }
[23:16] <ajalkane> akiva-thinkpad: hi
[23:16] <akiva-thinkpad> ajalkane, o/
[23:16] <akiva-thinkpad> hows it going?
[23:16] <ajalkane> I think I've made a mistake
[23:16] <akiva-thinkpad> sorry Ive been a bit preoccupied; I have a bit more time now to attack this.
[23:17] <ajalkane> I think my merge proposal was something that wasn't based on correct version
[23:17] <akiva-thinkpad> ajalkane, That would explain it :P~
[23:17] <ajalkane> akiva-thinkpad: no problem and great if we have time now to hash this out
[23:18] <ajalkane> Let me just start working on a good merge proposal so that there wouldn't be extra conflicts
[23:18] <akiva-thinkpad> ajalkane, well how do you want to move forward with this? I am basically just merging your changes as long as it runs,
[23:18] <akiva-thinkpad> okay
[23:18] <akiva-thinkpad> sounds good
[23:19] <ajalkane> akiva-thinkpad: basically I'd like that we get this top header thing merged with tests running. If we can get that done, then if you have further improvements in mind they can be made in future merge proposals and we can try and let the designers have time to make a decision what to do
[23:19] <akiva-thinkpad> ajalkane, oh don't worry about that. I forked the project
[23:19] <akiva-thinkpad> so i'll be tossing it in the store for like 20 cents or something :P
[23:20] <akiva-thinkpad> if it wants to get merged later; then that is cool
[23:20] <ajalkane> akiva-thinkpad: unfortunately it's a bit more difficult than that :(
[23:20] <akiva-thinkpad> ajalkane, hmmm?
[23:20] <ajalkane> The problem is that Ubuntu Touch applications has this permission model
[23:21] <akiva-thinkpad> ajalkane, meaning?
[23:21] <akiva-thinkpad> I'm not close sourcing it
[23:21] <ajalkane> Basically each application runs in confined mode - they can access only a little part of the filesystem that's assigned to them
[23:21] <akiva-thinkpad> ah interesting
[23:21] <ajalkane> Now FileManager has been granted an exception, and it's running "unconfined"
[23:22] <akiva-thinkpad> ah fascinating
[23:22] <ajalkane> But you can't upload "unconfined" applications to Ubuntu Store
[23:22] <ajalkane> So it's not as easy as one would like...
[23:22] <akiva-thinkpad> ah well
[23:22] <akiva-thinkpad> I'll call it desktop mode then
[23:22] <akiva-thinkpad> Toss it in the software center :P
[23:22] <ajalkane> Yeah that'll work
[23:23] <akiva-thinkpad> ajalkane, either way; as it stands, its so experimental with the design, its pretty reasonable to just fork it for the time being.
[23:23] <akiva-thinkpad> the branch now; lets just stick to what is orthodox and safe :)
[23:24] <ajalkane> akiva-thinkpad: that's my thinking also. Let's get the great improvements in, because they're really something needed, and let experimenting continue and give it good time to mature
[23:25] <akiva-thinkpad> exactly
[23:26] <ajalkane> I deleted the previous proposal to merge, and will try now again to make all the changes so that you don't get awful conflicts
[23:26] <akiva-thinkpad> ajalkane, cool; keep me posted; I'll merge it asap
[23:26] <ajalkane> akiva-thinkpad: thanks dude, really appreciated
[23:27]  * akiva-thinkpad knows how much I like it when merges go through quickly
[23:28] <ajalkane> this is kinda tricky as there are branches, where branches are merged into, and you have to merge the changes to trunk also :P
[23:28] <akiva-thinkpad> ajalkane, do you want me to merge from trunk first?
[23:28] <ajalkane> akiva-thinkpad: no you don't have to do that. I will try to do all that into my merge proposal
[23:28] <akiva-thinkpad> okay
[23:28] <akiva-thinkpad> any conflicts, I will just defer to your version.
[23:37] <ajalkane> alright, I'm running autopilot tests on my merge proposal to make sure its okay
[23:38] <akiva-thinkpad> cool beans
[23:40] <ajalkane> and you know, this branch only has back for history. But if we use / as separator, it might be workable to have like "< > /home/phablet" thingy so that "<" goes back and ">" forward. Just an idea to think about
[23:41] <akiva-thinkpad> ajalkane, I'm not so hot on the forward
[23:41] <akiva-thinkpad> ajalkane, I took it out of my branch even. Its iffy to program in qml
[23:41] <akiva-thinkpad> If someone wants to do it on the qt side of this app, then by all means.
[23:44] <ajalkane> I'm kind of in the same mindset that I'm not sure if forward is really useful. But I guess if there's bug reports and it seems people want it we can revisit it then - but you're most likely correct that it fits better if there's C++ backend support for it
[23:44] <akiva-thinkpad> ajalkane, yah its probably useful 1 percent of the time.
[23:45] <akiva-thinkpad> ajalkane, it only becomes enabled once you use the back button
[23:45] <akiva-thinkpad> and considering the limited space on a phone ~
[23:45] <ajalkane> yeah :(
[23:45] <ajalkane> Even on desktop I don't remember when I've last used it
[23:45] <akiva-thinkpad> ajalkane, heh. speaking of which
[23:45] <ajalkane> But on the other hand, I'm just one person and perhaps other people have used it
[23:46] <akiva-thinkpad> oh in this branch, did you keep the up history?
[23:46] <akiva-thinkpad> sorry the down history?
[23:46] <akiva-thinkpad> because i wanted to add a flickable to it
[23:46] <akiva-thinkpad> that when you flick left or right, that you can go up and down.
[23:46] <ajalkane> the down history is kept in code, and in visuals like you see in grayed where you were
[23:46] <ajalkane> yeah that's there
[23:47] <ajalkane> I think it's pretty cool, and shouldn't be confusing
[23:47] <akiva-thinkpad> ajalkane, I might not be explaining myself; this hasnt been programmed in yet :P
[23:47] <akiva-thinkpad> anyways I'll see.
[23:47] <ajalkane> ah flick on the files section to go up or down. That's not there
[23:48] <akiva-thinkpad> yah; as said; hasnt been programmed in yet
[23:48] <ajalkane> I just want to get these great top header changes merged and tackle any other things separately
[23:48] <akiva-thinkpad> though, we might want to save the gensture for something else
[23:48]  * akiva-thinkpad agrees
[23:48] <akiva-thinkpad> just thinking out loud :)
[23:48] <ajalkane> yeah gestures are a bit problematic, but going back/forward with those swipes seems kinda logical
[23:49] <ajalkane> But definitely requires some thinking about
[23:49] <akiva-thinkpad> erm up and down you mean :P
[23:49] <akiva-thinkpad> ajalkane, yah and we do have an advanced options feature
[23:49] <akiva-thinkpad> so we could have best of both worlds.
[23:49] <akiva-thinkpad> might as well put something in there
[23:49] <akiva-thinkpad> its empty atm
[23:49] <ajalkane> akiva-thinkpad: true that. The settings dialog is _quite_ empty right now
[23:49] <akiva-thinkpad> :D
[23:50]  * akiva-thinkpad has had a lot of fun working with the filemanager app
[23:50] <akiva-thinkpad> terminal app is fun too.
[23:50]  * akiva-thinkpad goes back to editting the reddit stylesheet
[23:50] <ajalkane> great to hear. Your contributions have been great. And I've seen you've contributed to a lot of core apps. Which is just awesome.
[23:51] <akiva-thinkpad> ajalkane, most of us here are volunteers, so the gratitude is sent back to you as well
[23:52] <ajalkane> it's good to work on common good :)
[23:52] <akiva-thinkpad> :D
[23:53] <ajalkane> I put in the merge request to your branch. There shouldn't be much or any conflicts now. Let me know if there's a problem
[23:53] <akiva-thinkpad> okay checking it now
[23:54] <akiva-thinkpad> ajalkane, btw; are you an ubuntu member yet?
[23:55] <ajalkane> akiva-thinkpad: I'm not sure what that means? I'm registered in launchpad
[23:55] <akiva-thinkpad> ajalkane, after you contribute long enough, you become a member
[23:55] <akiva-thinkpad> and get your own ubuntu email address
[23:56] <akiva-thinkpad> and a page on ubuntu
[23:56] <ajalkane> Oh, no I'm not a member then
[23:56] <akiva-thinkpad> ajalkane, neither :D
[23:56] <ajalkane> We'll see in some years :P
[23:56] <akiva-thinkpad> going for it though
[23:56] <ajalkane> do you know what the threshold in years is?
[23:56] <akiva-thinkpad> https://wiki.ubuntu.com/Membership ajalkane
[23:57] <akiva-thinkpad> I can imagine that its probably no more than a good several months of consistent work on it.
[23:57] <akiva-thinkpad> ah no conflicts
[23:57] <akiva-thinkpad> great
[23:58] <ajalkane> ah, so you have to apply for the membership. I might do that someday when I feel qualified.
[23:58] <akiva-thinkpad> ah this looks wonderful
[23:59] <akiva-thinkpad> ajalkane, yah I think the requirements for us may be a bit steeper given that were in application development
[23:59] <akiva-thinkpad> Ive known members though who all they do is act as a moderator on kubuntu forums or something
[23:59] <akiva-thinkpad> and they don't know too much about programming
[23:59] <akiva-thinkpad> lots of irc ops too I think
[23:59] <ajalkane> good that there's no conflicts. When you merge it to your branch, I can do one final test on device to make sure everything's okay and then I'll approve your merge proposal