Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
2281
Features / Re: One theme to rule them all?
« on November 15th, 2013, 11:13 AM »
It's a really, really good thing I decided to drop my ongoing work of changing folder structure, because I needed more work than I expected on the code side.
It's more than that, though. Just earlier, I had a look at the Noisen admin area (it's still running SMF 2.0), and was just 'thrilled'. It turns out that what I believed was true: there WAS a 'default member options' tab in SMF, it was just removed (quite certainly by Pete) in Wedge, and I don't know what the equivalent is.
As I told you, I never worked much on the admin area; I left it entirely in his hands while I was focusing on user experience. But now that I need to do this one admin experience thingy, I realize that the admin area went in a completely different direction that what I'd expected.
In fact, the real fun starts here: in the general settings area, Wedge has only a handful of options, while Noisen has tons of them. Pete actually moved them away, in the name of 'thematic grouping', while I consider that this area should hold everything that the admin might want to change as soon as they install the software. I guess it's a clash of concepts, but in my case, it's very bothersome.
I'm trying to think of what I could do about it all. But it's clear, by now, that neither the old SMF developers, nor Arantor, were thorough in their writes/rewrites. If anything, it's all very confusing, even for someone skilled in SMF/Wedge development like I am.
Perhaps I should remove the themes table entirely, and store user options in their members->data table. It would make it harder to force all member settings to something, but I'm not sure there's even a point in that. What would matter more, I think, is if I could enter someone's profile (on their behalf), and change some of their setting(s), if they requested it of me, the admin. Not ideal either, but what is?
It's more than that, though. Just earlier, I had a look at the Noisen admin area (it's still running SMF 2.0), and was just 'thrilled'. It turns out that what I believed was true: there WAS a 'default member options' tab in SMF, it was just removed (quite certainly by Pete) in Wedge, and I don't know what the equivalent is.
As I told you, I never worked much on the admin area; I left it entirely in his hands while I was focusing on user experience. But now that I need to do this one admin experience thingy, I realize that the admin area went in a completely different direction that what I'd expected.
In fact, the real fun starts here: in the general settings area, Wedge has only a handful of options, while Noisen has tons of them. Pete actually moved them away, in the name of 'thematic grouping', while I consider that this area should hold everything that the admin might want to change as soon as they install the software. I guess it's a clash of concepts, but in my case, it's very bothersome.
I'm trying to think of what I could do about it all. But it's clear, by now, that neither the old SMF developers, nor Arantor, were thorough in their writes/rewrites. If anything, it's all very confusing, even for someone skilled in SMF/Wedge development like I am.
Perhaps I should remove the themes table entirely, and store user options in their members->data table. It would make it harder to force all member settings to something, but I'm not sure there's even a point in that. What would matter more, I think, is if I could enter someone's profile (on their behalf), and change some of their setting(s), if they requested it of me, the admin. Not ideal either, but what is?
2282
Off-topic / Re: Doctor Who
« on November 15th, 2013, 12:23 AM »
When you mean it doesn't work; did you post that same URL, just with the https added? Did it try to show anything, or just the URL..?
It's fixable, of course.
As for the episode, it was fantastic indeed! I never saw the Dr Who TV movie from '96 or so, and I was very impressed with this guy's performance. In less than 7 minutes, and without as much of an 'emotional' scene, he managed to make me feel for him.
Oh, and the younger John Hurt... It does remind me a bit of his Caligula in I, Claudius -- just without the blond hair, of course! :P
It's fixable, of course.
As for the episode, it was fantastic indeed! I never saw the Dr Who TV movie from '96 or so, and I was very impressed with this guy's performance. In less than 7 minutes, and without as much of an 'emotional' scene, he managed to make me feel for him.
Oh, and the younger John Hurt... It does remind me a bit of his Caligula in I, Claudius -- just without the blond hair, of course! :P
2283
Features / Re: One theme to rule them all?
« on November 15th, 2013, 12:20 AM »
I'm 95% finished with moving theme options to settings.
It's just funny that I realized only today that I'd completely forgotten about the difference between member options, theme settings and things like that.
Basically:
- the settings table has site-wide features. That, I know.
- the themes table has both theme-wide settings, and member-specific options. That, I knew enough.
Only, id_member in the theme table can be one of three:
- "-1" seems to be "guest options",
- "0" seems to be "default member options". It's also "theme-wide settings", such as theme URLs. This is a confusing aspect.
- id > 0 is "current options for this member ID".
I'm going through the code, trying to analyze it... There are things that leave me puzzled (for instance, Register.php has $_POST['options'] and $_POST['default_options'] handling, but I've failed to find anything like that being shown at registration), and others where I feel completely out of touch.
Another example... 'view_newest_pm_first' is set to 1 for the theme settings, i.e. id_member = 0, so I'm guessing that it becomes the default setting both for guests (which don't have PMs...) and users. There is no interface to change that setting that I know of, as it's not in Settings.template.php -- but it IS in Admin > Member Options > Options (or Settings, or Preferences, can't remember the English word), which is a page that lists the member defaults. Did I say confusing...?
Then how am I supposed to change the default, short from modifying it in the database?
And my favorite has to be 'posts_apply_ignore_list', which is applied to id_member = -1, that is, 'default for guests'. Guests can't have an ignore list... So this doesn't serve any purpose. Even SMF 2.1 and ElkArte still have this one.
I'd be very, very grateful if someone 'in the know' could share their thoughts about this system, and clear up any confusion I might have. It's really a good thing that I'm eliminating the 'theme settings' page, but I don't want to eliminate any possibility of setting 'default options' for members and/or guests.
Of course, you find another layer of complexity when you start moving show_avatars to the general settings, and modify the code to basically mean, "if I allow show_avatars in settings, the user can determine whether they want to see them or not through their profile. If I disallow show_avatars, then the user won't even see that option in their profile." It's 'working', but it's not really a generic setting any more, to me.
I really, really need to go to bed I think...... -_-
It's just funny that I realized only today that I'd completely forgotten about the difference between member options, theme settings and things like that.
Basically:
- the settings table has site-wide features. That, I know.
- the themes table has both theme-wide settings, and member-specific options. That, I knew enough.
Only, id_member in the theme table can be one of three:
- "-1" seems to be "guest options",
- "0" seems to be "default member options". It's also "theme-wide settings", such as theme URLs. This is a confusing aspect.
- id > 0 is "current options for this member ID".
I'm going through the code, trying to analyze it... There are things that leave me puzzled (for instance, Register.php has $_POST['options'] and $_POST['default_options'] handling, but I've failed to find anything like that being shown at registration), and others where I feel completely out of touch.
Another example... 'view_newest_pm_first' is set to 1 for the theme settings, i.e. id_member = 0, so I'm guessing that it becomes the default setting both for guests (which don't have PMs...) and users. There is no interface to change that setting that I know of, as it's not in Settings.template.php -- but it IS in Admin > Member Options > Options (or Settings, or Preferences, can't remember the English word), which is a page that lists the member defaults. Did I say confusing...?
Then how am I supposed to change the default, short from modifying it in the database?
And my favorite has to be 'posts_apply_ignore_list', which is applied to id_member = -1, that is, 'default for guests'. Guests can't have an ignore list... So this doesn't serve any purpose. Even SMF 2.1 and ElkArte still have this one.
I'd be very, very grateful if someone 'in the know' could share their thoughts about this system, and clear up any confusion I might have. It's really a good thing that I'm eliminating the 'theme settings' page, but I don't want to eliminate any possibility of setting 'default options' for members and/or guests.
Of course, you find another layer of complexity when you start moving show_avatars to the general settings, and modify the code to basically mean, "if I allow show_avatars in settings, the user can determine whether they want to see them or not through their profile. If I disallow show_avatars, then the user won't even see that option in their profile." It's 'working', but it's not really a generic setting any more, to me.
I really, really need to go to bed I think...... -_-
2284
Features / Re: One theme to rule them all?
« on November 14th, 2013, 02:54 PM »Y'know, I started something similar for Protendo, renaming and changing that is..but it was too much work lol.
But it's just a matter of taking the time to do it, and try to do it portion by portion, even if it means breaking everything for a while.
My original restructuring helped me see what should be done, and in what order, for a better result. Not that I'm going to achieve it this time, but... I'll do my best.
But, I have actually made folders = name, same as you have done. Also, Protendo just reads all theme folders at startup, then check if its installed and show the thumbs so one can see what theme it is easily. Those that are not installed will have a install checkbox.
You are right - themes are a real confusing feature in SMF, even if I spent most of my time with them, I still have lots of things I want to change internally.
It just shows that the theme feature was a highpoint from Unknown - but less attention have been given to it since(internally that is).
On another note: I have installed and tried out Wedge latest. I have to be honest though, its quite another way to work for me.
I am not sure where the border between whats user-adjustable, whats auto-generated and whats left to a themer in the skins/themes code.
Auto-generated content, there's not much... A few callbacks in Subs-Cache (smileys, language flags, admin icons), and I think that's all. No more than 3 or 4 items.
Of course, the skins and its css..but the skeleton, if you change that in a theme, what are the chances it will not be changed by a plugin or the core..or the user?
That's the why I tried to satisfy both modders and themers, and believe me -- not easy. I can still add steps to these, but I'm limited by what I'm actually using in my own system -- there are usually several ways to do a single thing, it's up to the author's preference. I do things my own way, but sometimes, sometimes I probably don't see the bigger picture. I'm flawed, but at least I know it.
It seems, to me, and pardon me again for being forward :) that theres less "to do" for a themer other than provide the "look" of it.
Maybe shift things around - but thats as much the job for the admin as for a themer.
This is a bit difficult atm..but I will persevere in it, although it may take some time to then come up with good designs - without being too much alike each other. ;) Thats my drive in it anyhow, it may not be that for others of course.
Regarding core, Wedge will definitely ship with Weaving and Wilde. Wine will probably be distributed as a separate plugin 'for fun', as well as Warm. Wuthering will almost certainly be deleted entirely, because it was just a draft for Wilde, and originally a use case for 'nested skins', but Warm can do that as well. Regarding Weaving, I find it to be too complex, so I undertook a simplification of its CSS, got started a few days ago but stopped my work when I figured I should probably remove themes first. Weaving's goal is to remain 'usable', while refraining from using graphical additions to the DIVs around there. For instance, the linktree is very simple in Weaving, so I'm okay with that one, but the cat/title elements are already too 'busy'. This is actually the first thing I redid locally, lol... Removed a third of my cat/title CSS, just like that. I think Weaving can still look good as long as some care is given to the page header. It needs to be 'striking' in order to at least catch some attention. Maybe the Wine (or Warm) header is well suited for that. Or maybe Wilderless's. I don't know.
Anyway, just my 2 cents (and 2 years of work)... ;)
2285
Features / Re: New revs
« on November 14th, 2013, 02:30 PM »
rev 2321 -- changed my mind. I'll get rid of as much as possible, before I start moving folders around.
11 files changed, 13 insertions(+), 49 deletions(-), 4.32 KiB
* Moved Forum Width setting from themes to general settings. (ManageSettings.php, Settings.template.php, index.template.php, ManageSettings.language.php, Themes.language.php)
* Moved Random News setting from themes to News Settings. Renamed language string to 'enable_news'. (ManageNews.php, Settings.template.php, ManageSettings.language.php, Themes.language.php, install.sql)
- Removed Show Profile Buttons theme option. Seriously, I could understand that one wouldn't want to know their friends' online status, but... Nope, couldn't understand. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed Last Modification theme toggle. Again: no crazy reason for disabling that will work on me. If you really want to hide them, set 'ins' styling to display: none. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed deprecated language strings: enable_single_post, enable_multiple_posts (I have no idea what these are, but they're not used anywhere), inline_desc (this one was probably outdated 8 years ago) and member_list_bar. (Themes.language.php)
@ Yes, I know, I have no reason to keep updating upgrade.php. Don't mind me.
11 files changed, 13 insertions(+), 49 deletions(-), 4.32 KiB
* Moved Forum Width setting from themes to general settings. (ManageSettings.php, Settings.template.php, index.template.php, ManageSettings.language.php, Themes.language.php)
* Moved Random News setting from themes to News Settings. Renamed language string to 'enable_news'. (ManageNews.php, Settings.template.php, ManageSettings.language.php, Themes.language.php, install.sql)
- Removed Show Profile Buttons theme option. Seriously, I could understand that one wouldn't want to know their friends' online status, but... Nope, couldn't understand. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed Last Modification theme toggle. Again: no crazy reason for disabling that will work on me. If you really want to hide them, set 'ins' styling to display: none. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed deprecated language strings: enable_single_post, enable_multiple_posts (I have no idea what these are, but they're not used anywhere), inline_desc (this one was probably outdated 8 years ago) and member_list_bar. (Themes.language.php)
@ Yes, I know, I have no reason to keep updating upgrade.php. Don't mind me.
2286
Features / Re: New revs
« on November 14th, 2013, 01:09 PM »
rev 2320 -- hopefully, my last commit before I start pushing theme changes.
3 files changed, 6 insertions(+), 7 deletions(-), 1002 bytes
* Minor fixes on quote/code headers. Most notably, style was broken on quoted spoiler tags. (index.css)
- Don't remove overflow on an open sidebar. I know it will slightly break the skin selector or board selector on short pages, but it's better than mobile complications. (script.js)
* Trying an !important-free responsive admin area. Don't laugh, it's hard to get right. (sections.css)
3 files changed, 6 insertions(+), 7 deletions(-), 1002 bytes
* Minor fixes on quote/code headers. Most notably, style was broken on quoted spoiler tags. (index.css)
- Don't remove overflow on an open sidebar. I know it will slightly break the skin selector or board selector on short pages, but it's better than mobile complications. (script.js)
* Trying an !important-free responsive admin area. Don't laugh, it's hard to get right. (sections.css)
2287
Features / Re: One theme to rule them all?
« on November 14th, 2013, 12:49 PM »
Update.
Sadly, I've decided to throw away all my work (or close to), and start again from the original folder structure.
The main reason is that I was starting to turn crazy, with all of the code that needed to be removed.
So, I will instead:
- Do a slightly softer structure change (no renaming of Sources to sources, so that I can keep blaming these files without trouble; renaming of Themes/default/skins to Themes instead of skins),
- possibly give up on the term 'skins' to just use 'themes' instead (internally, I'll still have both), but the jury's still out on this one.
- And, still keeping, ONLY at the beginning, most theme code in. I need to be able to do incremental commits, otherwise I'll just turn crazy again. So, for instance, Wedge will simply consider default_theme_url and theme_url to be the same as skin_url, etc... Then, in the longer term, I'll just remove default_theme_url and theme_url, etc.
That's still a lot of work, but it'll be worth it. I'm sure it will. Seriously, theme code is incredibly confusing, it's nice that I'll be able to remove that.
Oh, and I've decided to drop <name> params in skins. The skin will now be named by its folder, so that people can easily rename their folders to rename their skins, and not risk name collisions when updating the site with a new zip.
Sadly, I've decided to throw away all my work (or close to), and start again from the original folder structure.
The main reason is that I was starting to turn crazy, with all of the code that needed to be removed.
So, I will instead:
- Do a slightly softer structure change (no renaming of Sources to sources, so that I can keep blaming these files without trouble; renaming of Themes/default/skins to Themes instead of skins),
- possibly give up on the term 'skins' to just use 'themes' instead (internally, I'll still have both), but the jury's still out on this one.
- And, still keeping, ONLY at the beginning, most theme code in. I need to be able to do incremental commits, otherwise I'll just turn crazy again. So, for instance, Wedge will simply consider default_theme_url and theme_url to be the same as skin_url, etc... Then, in the longer term, I'll just remove default_theme_url and theme_url, etc.
That's still a lot of work, but it'll be worth it. I'm sure it will. Seriously, theme code is incredibly confusing, it's nice that I'll be able to remove that.
Oh, and I've decided to drop <name> params in skins. The skin will now be named by its folder, so that people can easily rename their folders to rename their skins, and not risk name collisions when updating the site with a new zip.
2288
Features / Re: New revs
« on November 14th, 2013, 12:42 PM »
rev 2319
5 files changed, 10 insertions(+), 11 deletions(-), 1.37 KiB
! Fixed username positioning in topic pages on iOS browsers. Please -- don't ask. If you really must know, it was an old hack for iOS 4 (from rev 1584), that was fixed by Apple in iOS 5, without my knowledge. To hell with iOS 4, I'm removing the hack entirely. (extra.ios.css)
* Tweaked layout in userbox for mobile; should be properly aligned, now. (Wireless/extra.css)
- Duplicate code. (Wine/extra.css)
! Forgot some <ins> styling. (extra.rtl.css)
+ Some line needed clearing up. (contributors.txt)
5 files changed, 10 insertions(+), 11 deletions(-), 1.37 KiB
! Fixed username positioning in topic pages on iOS browsers. Please -- don't ask. If you really must know, it was an old hack for iOS 4 (from rev 1584), that was fixed by Apple in iOS 5, without my knowledge. To hell with iOS 4, I'm removing the hack entirely. (extra.ios.css)
* Tweaked layout in userbox for mobile; should be properly aligned, now. (Wireless/extra.css)
- Duplicate code. (Wine/extra.css)
! Forgot some <ins> styling. (extra.rtl.css)
+ Some line needed clearing up. (contributors.txt)
2289
Features / Re: On Mobile Theme...
« on November 14th, 2013, 12:20 PM »
Ahem.
Fixed.
Partially my fault.
Let's forget about it. I wasted enough time on that 'bug'.
Fixed.
Partially my fault.
Let's forget about it. I wasted enough time on that 'bug'.
2290
Features / Re: One theme to rule them all?
« on November 13th, 2013, 10:51 PM »
Update...
Everything is working, AFAIK. Skin selection probably fails; skin selector shows a flattened view.
There are probably tons of things to fix, but phase 1, "getting the HTML, CSS and JS to work", is pretty much done.
I had to add hacks to the skin parser, though, and I hate that. Hopefully, I won't keep that too long...
Everything is working, AFAIK. Skin selection probably fails; skin selector shows a flattened view.
There are probably tons of things to fix, but phase 1, "getting the HTML, CSS and JS to work", is pretty much done.
I had to add hacks to the skin parser, though, and I hate that. Hopefully, I won't keep that too long...
2291
Features / Re: One theme to rule them all?
« on November 13th, 2013, 08:23 PM »
An update...
- Continued removing theme-related elements.
- Enabled ability to override a template entirely within a skin. Just create a sub-folder called 'templates' in it. As easy as that... So, basically, the main feature in themes is back, really.
- Removed theme-related settings in index.template.php, because who cares. Most of them were already removed.
- Flattened the skin folder. Instead of something like...
/skins/
/skins/Wilde/
/skins/Wilde/Wilderless/
You'll now have:
/skins/
/skins/Wilde/
/skins/Wilderless/
This makes it easier to 'spot' updated files, and/or update all skins manually, etc. And of course, easier to add custom folders, eh. However, it's going to be only for templates right now. I'm planning to add support for languages later, but 'images' is more complicated. The current implementation in themes is very, very messy and confusing. I'd rather not touch that. Plus, the images that count (which skins might want to 'override') are already defined by CSS and can be replaced easily.
Wilderless is seen as a child of Wilde by adding a 'parent' option pointing to Wilde.
However, I'm having trouble getting it to work fine, ah ah...
Overall, I'm starting to get worried about the fact that Wedge will be very buggy for the days to come. Maybe even months to come... There is so much to remove! (And also, so much ugly theme code that I'm thrilled to remove!)
Meh...
- Continued removing theme-related elements.
- Enabled ability to override a template entirely within a skin. Just create a sub-folder called 'templates' in it. As easy as that... So, basically, the main feature in themes is back, really.
- Removed theme-related settings in index.template.php, because who cares. Most of them were already removed.
- Flattened the skin folder. Instead of something like...
/skins/
/skins/Wilde/
/skins/Wilde/Wilderless/
You'll now have:
/skins/
/skins/Wilde/
/skins/Wilderless/
This makes it easier to 'spot' updated files, and/or update all skins manually, etc. And of course, easier to add custom folders, eh. However, it's going to be only for templates right now. I'm planning to add support for languages later, but 'images' is more complicated. The current implementation in themes is very, very messy and confusing. I'd rather not touch that. Plus, the images that count (which skins might want to 'override') are already defined by CSS and can be replaced easily.
Wilderless is seen as a child of Wilde by adding a 'parent' option pointing to Wilde.
However, I'm having trouble getting it to work fine, ah ah...
Overall, I'm starting to get worried about the fact that Wedge will be very buggy for the days to come. Maybe even months to come... There is so much to remove! (And also, so much ugly theme code that I'm thrilled to remove!)
Meh...
2292
The Pub / Re: git problems for non-gits.
« on November 13th, 2013, 04:47 PM »
Issue apparently got acknowledged by a contributor, so it does mean it's not a wrong operation on my part; it's something that others managed to reproduce. Good!
Also opened another issue, more like a suggestion:
https://code.google.com/p/tortoisegit/issues/detail?id=1990
I don't like making too many suggestions for software I don't (or in this case, can't) contribute to, but these are the two items that directly affect the viability of the Wedge git repo. Former causes Blame to fail everywhere after my latest commits, and latter causes two extra 'steps' when blaming an old file, because in SVN, I once committed many files with the Windows whitespace (used the wrong search-replace software and didn't check!), and then I redid a commit to strip the extra \r bytes.
(I guess I could use a rebase to reduce this by at least one step, but... I'm not sure if it's even doable.)
Also opened another issue, more like a suggestion:
https://code.google.com/p/tortoisegit/issues/detail?id=1990
I don't like making too many suggestions for software I don't (or in this case, can't) contribute to, but these are the two items that directly affect the viability of the Wedge git repo. Former causes Blame to fail everywhere after my latest commits, and latter causes two extra 'steps' when blaming an old file, because in SVN, I once committed many files with the Windows whitespace (used the wrong search-replace software and didn't check!), and then I redid a commit to strip the extra \r bytes.
(I guess I could use a rebase to reduce this by at least one step, but... I'm not sure if it's even doable.)
2293
The Pub / Re: git problems for non-gits.
« on November 13th, 2013, 12:19 AM »
Note: since it might be a software bug, I submitted an issue to the authors:
https://code.google.com/p/tortoisegit/issues/detail?id=1985
https://code.google.com/p/tortoisegit/issues/detail?id=1985
2294
Features / Re: One theme to rule them all?
« on November 13th, 2013, 12:02 AM »
Update: finally got my skin to show up.. There are still plenty of problems (JavaScript not loaded, etc), but it's an important step for me.
I'm trying to document (internally) all of the steps required to make the conversion. This should help me here once I convert wedge.org, and maybe for Pandos, too, but other than that, it doesn't matter much. I think!
OTOH, if I can't get TortoiseGit Blame to work correctly for me, it may all have been for nothing, I don't know. I don't know if I can imagine working on a project where the history isn't available to me because of a software bug... :-/
I'm trying to document (internally) all of the steps required to make the conversion. This should help me here once I convert wedge.org, and maybe for Pandos, too, but other than that, it doesn't matter much. I think!
OTOH, if I can't get TortoiseGit Blame to work correctly for me, it may all have been for nothing, I don't know. I don't know if I can imagine working on a project where the history isn't available to me because of a software bug... :-/
2295
Features / Re: One theme to rule them all?
« on November 12th, 2013, 08:23 PM »lol, fun times it seems, for you removing that. :)
About series, I like some of them you mention, but most of them is too light for me , Agents of Shield was promising, but now I just see it of curiosity.
Still, if they have to rely on a Samuel Jackson cameo to make it exciting, well... ;)
Person of interest is kind of silly, true..but I love the characters in them, well, most of the time. Spader acting I am mostly unaware of, apart from the old Stargate movie, but then I rarely watch cop series anyway, so Boston legal I haven't seen.
Sherlock is great, look forward to new season, others I follow now are CSI and Supernatural, still exciting!
but I started and ended alot of series..lately i saw Broadchurch though, that was a keeper.
but did you know about another, similar but less bloody, called "Les revenants"? :D It was slow at first(well, first episode was quite fascinating), but it soon got me hooked all the way in. And yes, its indeed true what they say about french girls :) Look forward to second season of that too.
I'm sad that Les Revenants gets to become popular outside France when Kaamelott, which is such a stunning show (started off as a cheap, short comedy show and ended as a full-length comedy-drama show with a large budget), is barely ever heard of.
I guess I try to avoid most French shows because 90% of them are really bad. The last one I liked that isn't Kaamelott, was "Bref" ("In short..."), a very short one (90 seconds per episode), but it'd probably lose too much in translation. It's one of the most original shows ever, though. Not only in France. A bit like Fight Club, come to think of it. Well, you'd need to see the show to understand what I mean.
Okay, apart from that, not much that stands out. Oh, I did like a couple of thriller TV movies adapted from Fred Vargas. I doubt they're available in English, though. There's also "Fais pas ci, fais pas ça", it's a very funny comedy, but they sold the rights to the US a few years ago, and they made a remake called, ahem... "Modern Family". It's not widely known that it's adapted from a good French show, but it's the truth. They only added the gay couple, the rest is the same.
My bitbucket account is bloc67 - I think you mentioned it a bit back.
As for the fixed header..uhm, I haven't even checked on mobiles yet. I might get rid of it again, its a fad really, maybe not worth doing "hacks" for it. I'll make my mind up soon hah. :)