[14:44] <sakrecoer_> hm... loging in to twitter... it is asking me to verify my identity... so i should guess this email and i have no idea...
[14:46] <sakrecoer_> never mind, it was just to find a tutorial someone tagged @ubuntustudio in.
[17:46] <sakrecoer_> found that emailadress :) it is in the encrypted password file.
[19:28] <sakrecoer_> https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1540759/comments/5 have i got ARandR because i've added some PPA? 
[19:33] <zequence_> sakrecoer_: ARandR used to be screen tool when the stock XFCE was not good enough
[19:33] <zequence_> If you've updated your system from an older install, it might still be there
[19:33] <sakrecoer_> fairly certain both my machines are fresh 14.04 installs...
[19:36] <sakrecoer_> zequence_: how can i check? i've seen it displayed in bugrepports "installation media"
[22:19] <zequence_> sakrecoer_: 14.04 still includes it
[22:19] <zequence_> So, that is normal
[22:20] <zequence_> It's in the seeds for 14.04
[22:20] <knome> hey zequence_ 
[22:20] <zequence_> knome: Hi
[22:20] <knome> landed a few fixes/improvements for the theme today
[22:20] <zequence_> Ok, thanks. I will check it out.
[22:24] <OvenWerk1> sakrecoer_: I have been trying to get rid of ARandR for a while now, but keep on putting the change in too late. I think it is gone now.
[22:25] <sakrecoer_> thanks zequence_ and OvenWerk1 :)
[22:28] <zequence_> knome: So, what are your thoughts about making the theme mobile friendly?
[22:28] <zequence_> Aside from a hamburger menu, autoresizing of images would be nice
[22:28] <knome> zequence_, my thoughts are that it's fairly friendly to fairly modern devices
[22:28] <knome> autoresizing in what sense?
[22:28] <knome> providing a smaller image, or just making sure it fits the screen?
[22:29] <zequence_> Not sure how it is done technically on some sites I have seen, but the image will automatically become smaller if you make the web browser window smaller
[22:30] <knome> ok, so is the theme not doing that now?
[22:30] <zequence_> No
[22:30] <zequence_> Check our staging site
[22:30] <knome> ok, then i'll take care of that
[22:30] <knome> anyway, re: the hamburger menu, a simple one at that is relatively easy, but i'm not sure if a simple menu is good enough
[22:31] <zequence_> Just the fact that it is a popup menu would be good enough for me
[22:32] <knome> for you, but would it be enough for the ones using the site with their mobile devices?
[22:32] <knome> :)
[22:32] <zequence_> How do you mean? Wouldn't it be made specifically for small screens anyway?
[22:33] <knome> there are good/correct and bad/incorrect ways to work on mobile support
[22:33] <knome> and everything in between
[22:33] <zequence> Ok
[22:33] <knome> now just doing that in a simple way isn't really incorrect, but it's not the best way either
[22:34] <knome> for example, check the xubuntu site and how the navigation collapses in a nice way
[22:34] <knome> with all the bits for the submenus etc.
[22:34] <knome> that's not a trivial menu
[22:34] <knome> or at least it takes some time to get it right
[22:35] <knome> just doing a menu that opens with a button and shows for example only the root level items is much easier
[22:35] <zequence> Ah, right. Submenus
[22:35] <knome> but then question remains how submenus are handled for example
[22:36] <knome> would they only be visible when you were on a page within that menu structure?
[22:36] <zequence> So, copy and paste is not on the table? :P
[22:36] <knome> no, unfortunately it isn't that simple
[22:36] <knome> or at least it would still require attention and love
[22:37] <knome> and the fact that the community theme is made to work with both a specified menu and a fallback menu...
[22:37] <knome> (yes, they do have different markup...)
[22:37] <knome> (for reasons unknown to me)
[22:38] <zequence> Other than the hamburger menu, and the image sizes, I find that the minimal width is a bit too large. It's about twice or more the width compared to the Xubuntu site theme
[22:38] <knome> yes, it is
[22:38] <knome> that's another aspect of doing the mobile stuff "right"
[22:38] <knome> currently, i don't want to make the minimum width smaller because then it would mean the menu would break
[22:38] <knome> eg. items overlap the logo or each other, and wrapping to two lines
[22:39] <zequence> Ok. Well, I would consider doing some work on this myself, since I have some basic knowledge of all the coding involved, but haven't every even attempted making a WP theme before. Still, if there is some code I could work on, to adapt or whatever, I could give it a try
[22:40] <knome> we don't need code
[22:40] <knome> we need CSS
[22:40] <zequence> It's all CSS?
[22:41] <zequence> no javascript?
[22:41] <knome> apart from some js event binds, yes
[22:41] <knome> but the binds are the smallest problem; they are trivial
[22:41] <knome> how i (would) do it is just apply a css class to the menu element from the event
[22:42] <knome> then with/in the changed css class, make sure the menu is shown/hidden appropriately
[22:42] <zequence> If I have some spare hours (I'm going to work on -controls some days anyway), I could check how you are doing it for the Xubuntu web theme.
[22:42] <zequence> It's all here, right? https://code.launchpad.net/xubuntu-website
[22:42] <knome> yeah, i can even give you exact pointers...
[22:43] <knome> http://bazaar.launchpad.net/~xubuntu-website/xubuntu-website/theme/view/head:/xubuntu-fifteen/menu.js
[22:43] <knome> that's the JS part
[22:44] <knome> the responsive design for the menu (and more) is in style-resp-*.css
[22:44] <knome> HTML markup is pretty generic for both the xubuntu site and the community theme
[22:45] <zequence> Ok, cool. I'll poke in it.
[22:45] <knome> appreciated
[22:46] <knome> oh, one thing you probably should be aware of
[22:46] <knome> the responsive design is incremental
[22:46] <knome> eg. stuff that is in -800 affects all resolutions smaller than that
[22:46] <knome> the -450 file is relatively small, because it's inheriting a lot of stuff from the other files
[22:47] <knome> somebody might argue that you should go "mobile first" eg. start adding stuff for the larger resolutions incrementally, and i could even agree with them
[22:47] <knome> but what's done is done
[22:47] <knome> re: images
[22:48] <knome> the theme *does* limit them to 100% width already
[22:48] <knome> the minimum size is just too big and that's why the image (and the content) is wider than the viewport
[22:48] <knome> i just tested this on my own sandbox installation
[22:49] <zequence> I would have no opinion on that, since I have no experience in that - yet. I've taught php, html and css, but on a very basic level. CSS I still haven't figured out well enough to fully understand positioning of elements. But, now I can learn some more :)
[22:49] <knome> actually, the different subsets of work in the mobile menu are all trivial
[22:49] <zequence> That's good to hear :)
[22:49] <knome> it's their combination that makes it interesting
[22:50] <knome> for example, the positioning is actually "static"
[22:50] <knome> eg. the normal behavior
[22:51] <knome> just make sure the menu items are stacked on top of each other (which is natural for the markup too)
[22:51] <knome> the positioning in the dropdown menu we have on the larger screens is different
[22:52] <knome> i could do one really simple thing for now to at least somehow support the small sizes
[22:52] <knome> and take care of the main content area tweaks needed
[22:56] <zequence> knome: Ok, thanks. I'm going to say nighty nighty for now. Don't think I will do anything for at least one week, and I might wait until after FF. But, I'll be sure to ask your help when that CSS starts making my life sour :)
[22:56] <knome> ;)
[22:56] <knome> sure
[22:56] <knome> good night
[23:22] <sakrecoer_> thanks for the insights knome ! got a few "aha" moments reading up.
[23:22] <sakrecoer_> i'm off as well! read y'all later!