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
4096
The Pub / Re: Logo Madness
« on November 28th, 2012, 11:23 AM »It does.
I like the "wamer" feeling of lowercase here..if that makes sense. Could be that when I first saw the logo last year(?) it was using lower-case and it just felt right for wedge when i dabbled with it too. Uppercase seemed so bombastic and still does I guess.
Which reminds me, I had a logo under the hand which I liked, but felt it was too barebones... I had a quick look at it again, and thought, 'barebones? well that isn't a bad thing now is it..?'
So, you decide :) I'm not a huge fan, but I like it enough to think there might be potential once it's tweaked enough. If you're interested, I can also attach the original logo file for you to play with.
Watching it again also made me realize it looks a bit like the amazon logo, but it doesn't have the same history at all, so it's just a coincidence. :P
4097
Archived fixes / Re: Non-static method weMoDe::isMobile()
« on November 28th, 2012, 11:19 AM »
Thank you, fixed ;)
This class was basically taken from a web snippet, and I didn't bother to check the method type.
It only shows up on first load because the contents of the function is cached for the duration of the session.
Which reminds me that last week I had planned to rewrite detectBrowser() into a part of this object... To benefit from the session cache ;)
Then I stopped midway through it, because of cache filename considerations... Which have yet to be addressed. -_-
This class was basically taken from a web snippet, and I didn't bother to check the method type.
It only shows up on first load because the contents of the function is cached for the duration of the session.
Which reminds me that last week I had planned to rewrite detectBrowser() into a part of this object... To benefit from the session cache ;)
Then I stopped midway through it, because of cache filename considerations... Which have yet to be addressed. -_-
4098
Off-topic / Need help with my Interwebs connection
« on November 28th, 2012, 11:12 AM »
Okay, this isn't something I usually do... But I'm pretty much stuck these days.
Ever since I bought my new machine (running Windows 7) last year, or possibly more recently than that, I've been having Internet connection problems.
It all just adds up to this: if I'm sending too many HTTP REQUESTS, they're being DENIED.
An example: I'm loading a torrent file. Many requests, I guess. After a while, if I'm trying to browse the web, I'll get a generic error saying there's no connection available. Usually, doing a manual ping on wedge.org will work, doing a ping on a more obscure website will work so I guess the DNS is working...
Another example: forget about torrents, let's say I'm simply online with no download in progress. Launching Opera or Chrome or Firefox with hundreds of tabs in them. Chrome will still attempt to load its 500+ tabs immediately and miserably fails. Firefox is okay because it only loads tabs when you activate them. Opera is 'smarter' about it and load only a few tabs at a time, but it doesn't change the fact that after it's loaded a dozen tabs or so, the rest sends me network error messages.
One thing that's even sillier is that if I'm downloading a large file through HTTP (in my browser), and then I launch a series of requests that crashes my connection, the large file will STILL keep downloading. In fact, any ongoing requests are still being honored, it's only the new requests that fail and send a network error.
After months of pesting against this, and having to reboot my modem before I can resume my load, I discovered that I could simply unplug my Ethernet cable. After a few hours I tried deactivating the Ethernet connection from my network settings in Windows 7, and then immediately reactivating it. To my surprise, it actually worked.
So, so far so good... "My network card is faulty."
It just so happens that I have a second Ethernet port in my computer... Okay, so I'll just use it, right?
Wrong. I've got *exactly* the same problem on it. It works in the beginning, and then fails miserably until I do the deactivate/activate combo trick on it. Then I can 'reload' more tabs until it crashes again, I do the trick again, I manually reload more tabs, etc, etc...
Still, it's not 'normal'. Considering that both network cards do it, it's probably not a hardware failure -- rather a crappy setting in Windows 7 or something that does flood control.
But I have yet to find out who the culprit is. And it drives me crazy because, well, I realize it's one of the things that makes me spend less time loading websites and more time watching films. It's not good for Wedge.
If anyone out there is a network specialist, please help. :)
I feel I should also point out that browsing my local Apache install works even when the network is failing. So it tends to conflict with the idea that the problem happens *before* the request reaches the network card...
Annoying, no?
Ever since I bought my new machine (running Windows 7) last year, or possibly more recently than that, I've been having Internet connection problems.
It all just adds up to this: if I'm sending too many HTTP REQUESTS, they're being DENIED.
An example: I'm loading a torrent file. Many requests, I guess. After a while, if I'm trying to browse the web, I'll get a generic error saying there's no connection available. Usually, doing a manual ping on wedge.org will work, doing a ping on a more obscure website will work so I guess the DNS is working...
Another example: forget about torrents, let's say I'm simply online with no download in progress. Launching Opera or Chrome or Firefox with hundreds of tabs in them. Chrome will still attempt to load its 500+ tabs immediately and miserably fails. Firefox is okay because it only loads tabs when you activate them. Opera is 'smarter' about it and load only a few tabs at a time, but it doesn't change the fact that after it's loaded a dozen tabs or so, the rest sends me network error messages.
One thing that's even sillier is that if I'm downloading a large file through HTTP (in my browser), and then I launch a series of requests that crashes my connection, the large file will STILL keep downloading. In fact, any ongoing requests are still being honored, it's only the new requests that fail and send a network error.
After months of pesting against this, and having to reboot my modem before I can resume my load, I discovered that I could simply unplug my Ethernet cable. After a few hours I tried deactivating the Ethernet connection from my network settings in Windows 7, and then immediately reactivating it. To my surprise, it actually worked.
So, so far so good... "My network card is faulty."
It just so happens that I have a second Ethernet port in my computer... Okay, so I'll just use it, right?
Wrong. I've got *exactly* the same problem on it. It works in the beginning, and then fails miserably until I do the deactivate/activate combo trick on it. Then I can 'reload' more tabs until it crashes again, I do the trick again, I manually reload more tabs, etc, etc...
Still, it's not 'normal'. Considering that both network cards do it, it's probably not a hardware failure -- rather a crappy setting in Windows 7 or something that does flood control.
But I have yet to find out who the culprit is. And it drives me crazy because, well, I realize it's one of the things that makes me spend less time loading websites and more time watching films. It's not good for Wedge.
If anyone out there is a network specialist, please help. :)
Posted: November 28th, 2012, 10:58 AM
I feel I should also point out that browsing my local Apache install works even when the network is failing. So it tends to conflict with the idea that the problem happens *before* the request reaches the network card...
Annoying, no?
4099
Features / Re: Really petty, but I got to ask
« on November 28th, 2012, 11:03 AM »
I don't like the slider, but that's just me. The other day I switched my iPod to English and realized that sliders have "ON" and "OFF" text in them. In the French version, there is simply no text (probably because we French are too stupid to figure out what the words ON and OFF mean, even though we've been seeing them in real life for the last hundred years on anything with a switch!)
Anyway... I like the IPB version. What mattered to me in the AeMe rewrite, was to have a clear visual clue of whether it was Yes or No. As you can see, the dropdown (at least in the Wedge version) already shows a green Yes and a red No. I guess it makes sense to show them in a fashion similar to IPB's.
I would, however, tend to gray out the background of the disabled feature, i.e. only show Green on an enabled feature, and Red on a disabled feature.
I guess it's akin to using a slider... So don't mind me :lol:
Anyway... I like the IPB version. What mattered to me in the AeMe rewrite, was to have a clear visual clue of whether it was Yes or No. As you can see, the dropdown (at least in the Wedge version) already shows a green Yes and a red No. I guess it makes sense to show them in a fashion similar to IPB's.
I would, however, tend to gray out the background of the disabled feature, i.e. only show Green on an enabled feature, and Red on a disabled feature.
I guess it's akin to using a slider... So don't mind me :lol:
4100
Other software / Re: Discussing Wedge on simplemachines.org
« on November 28th, 2012, 10:34 AM »So this is kicking off again and the licence is being examined. Yay.
Just for the record, the exclusion against vbgamer was put in place after he excluded me from using goods for which I had paid for and revoked my licence; he was apparently willing to give me a partial refund if I apologised to him for the things I'd said (though he wasn't being asked to apologise for the comments he made about me, calling me - and I quote - 'a fucking liar' except would never state what it was I'd lied about when pushed) - but since that would be yet another compromise, I wouldn't back down. I bet he didn't mention the fact that he told me I couldn't build anything based on his work - not even converters to other systems of any kind.
http://www.simplemachines.org/community/index.php?topic=446866.msg3444825#msg3444825
As for the exclusion against Akyhne, that was after a mammoth argument where he violated Aeva's licence. You can - if you wish - go through the latter half of the crap at http://arantor.org/index.php?topic=168.0
(Also, what Motoko fails to realise, yet again, that by pushing things into Chit Chat, more people see Wedge than would have otherwise. Talk about backfiring.)
SMF has lost a lot of its momentum, which has shifted to other non-SMF-based solutions.
At this point, it would probably even make more sense for SM to push smCore aside (because I don't think it's ever going to be able to replace SMF in any capacity), and ask us to rename Wedge to 'SMF 3.0' and be done with it.
Why is it every time I find the time and motivation to contribute to Wedge, something comes along and leaves a nasty sour taste in my mouth?
It's been hard enough finding the time and motivation to work on it without having to deal with crap like this. As some people would remember, I'm not particularly happy writing this stuff any more, and I haven't been for months because all it's doing is making me greyer than before and leaving me feeling like I owe people.
A good decision we made was to feature-freeze it a few months ago, but it also makes it hard for us to find joy in developing when all we're doing is fixing bugs and trying to stop ourselves from implementing new features.
Actually, this is a common issue with developers: the best time is when you add a new feature. Having to actually FINISH said feature is often a PITA. Either because of language translations (for me), or documenting it, or simply leaving it be for a while and coming back and realizing you're not sure why you wrote this or that anymore... And then you rewrite it, and realize what it was for, and you have to go back, etc...
Really, it's not fun.
But once I've fulfilled what I see as my obligations to this project, I'll disappear into the sunset and enjoy a less unpleasant, if quieter, life with it. I don't need this crap, but I also don't want to let people down like the way XenForo is going at the moment.
I myself don't really see going into a different direction. I'm currently a bit unhappy with my work on Wedge (both current and future), but overall it's still a piece of software I'm proud of. I think that at the worst, I'll be creating custom websites based on the Wedge backbone, and have them go into different directions.
Somehow, I simply miss maintaining Noisen.com -- it was a simpler task, because I only had to account for French, and for MY tastes, and MY needs. I could easily write a feature with dirty code, when in Wedge I'm always rewriting stuff because it looks bad compared to some carefully written code like you, Shitiz, John etc. would usually write. I always push myself to doing things the 'right' way, and it leads me to considerably larger development times.
I'm proud of what we've done so far. I just miss being able to write shit for myself. ;)
My next project is probably going to be Deideo, my website about music thieves and homages turned wrong. But don't tell my girlfriend, she would kill me for even considering to build such a potentially lawsuit-inducing site. ;)
4101
Archived fixes / Re: Undefined: ex_string in Class-CSS
« on November 27th, 2012, 12:42 AM »
Yup...
Won't fix the file by adding .css.css, though. It'll just ignore the failed file. Normally.
Won't fix the file by adding .css.css, though. It'll just ignore the failed file. Normally.
4102
Archived fixes / Re: Thoughts usability on tablets
« on November 27th, 2012, 12:41 AM »
It's the Home template.
It's entirely up to the admin to determine how they show thoughts.
Technically, there's nothing saying that my particular implementation is what I think works best.
In fact, none of what I've been doing so far is what I would call "works best material".... It's just "works okay enough for me to switch to another task."
It's entirely up to the admin to determine how they show thoughts.
Technically, there's nothing saying that my particular implementation is what I think works best.
In fact, none of what I've been doing so far is what I would call "works best material".... It's just "works okay enough for me to switch to another task."
4103
Development blog / Re: It only took two guys two years...
« on November 25th, 2012, 11:29 PM »
I don't know, as I always say, it's going to save your server bandwidth, that I'm sure of.
Weird avatar.
eolith, yes it is, if you post more. But you didn't, even after that post. ;)
Weird avatar.
eolith, yes it is, if you post more. But you didn't, even after that post. ;)
4104
Features / Re: New revs
« on November 25th, 2012, 10:33 PM »
rev 1781 "Because I didn't want to have my first commit-less week..." :P
(5 files, 3kb)
! Worked around weird error that shows up when saving sessions in some specific setups. Seriously, I'm not 'fixing' what I'm sure is a PHP bug. (Load.php)
! Hopefully fixed bugs when trying to cache a non-existent CSS file. Needs some more work, I guess... (Subs-Cache.php)
* Grammar fix in French language JavaScript strings. (index, ManageMaintenance, ManageMembers)
(Pete, are you sure PHP 5.2 doesn't "always have json_decode"...? I mean, sure, people can disable it when recompiling PHP, but... Who does that? Who WOULD do that? Do you have any stats on this..?)
(5 files, 3kb)
! Worked around weird error that shows up when saving sessions in some specific setups. Seriously, I'm not 'fixing' what I'm sure is a PHP bug. (Load.php)
! Hopefully fixed bugs when trying to cache a non-existent CSS file. Needs some more work, I guess... (Subs-Cache.php)
* Grammar fix in French language JavaScript strings. (index, ManageMaintenance, ManageMembers)
(Pete, are you sure PHP 5.2 doesn't "always have json_decode"...? I mean, sure, people can disable it when recompiling PHP, but... Who does that? Who WOULD do that? Do you have any stats on this..?)
4105
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 09:19 PM »
It already deletes any files older than 2 months ;)
4106
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 06:01 PM »
Yeah, it's really always bothered me a bit...
Anyway... I'm pretty much stuck in the mess that I wrote for Wess before. It has variables for is_android and is_iphone (when really it should be is_ios only), and is_tablet -- what's the point in this...? is_tablet is only used PHP-wide in addition to is_iphone, and in JavaScript it can easily be replaced with is_touch and a screen dimension test. As for CSS, a media query is all it takes... (Plus is_touch tests.)
I'm looking at it, and I think I'll have to clean it further...
But I don't really see how I can justify storing this or that version number but not all of them. The only thing I can say is, look at Chrome... It has so many versions in my cache files, it's frightening.
Frak. I don't know where to go from there... -_-
Perhaps I should just forget about Windows version numbers for now. Only store version numbers for iOS because of the whole "browser engine is always Safari Mobile thanks to Apple" story that means new browser features are discovered with new iOS versions, rather than browser updates. Android, well... There are plenty of features added on each new version, but I guess it can be done by "@if (android && opera[7-], android && chrome[20-])", etc...
Maybe just store Windows version for Windows 7 and up -- and state it as "7" rather than "6.1", except of course if Microsoft decides to name Windows 9 differently, ah ah... You never know with them...
What do you think...?
Anyway... I'm pretty much stuck in the mess that I wrote for Wess before. It has variables for is_android and is_iphone (when really it should be is_ios only), and is_tablet -- what's the point in this...? is_tablet is only used PHP-wide in addition to is_iphone, and in JavaScript it can easily be replaced with is_touch and a screen dimension test. As for CSS, a media query is all it takes... (Plus is_touch tests.)
I'm looking at it, and I think I'll have to clean it further...
But I don't really see how I can justify storing this or that version number but not all of them. The only thing I can say is, look at Chrome... It has so many versions in my cache files, it's frightening.
Frak. I don't know where to go from there... -_-
Perhaps I should just forget about Windows version numbers for now. Only store version numbers for iOS because of the whole "browser engine is always Safari Mobile thanks to Apple" story that means new browser features are discovered with new iOS versions, rather than browser updates. Android, well... There are plenty of features added on each new version, but I guess it can be done by "@if (android && opera[7-], android && chrome[20-])", etc...
Maybe just store Windows version for Windows 7 and up -- and state it as "7" rather than "6.1", except of course if Microsoft decides to name Windows 9 differently, ah ah... You never know with them...
What do you think...?
4107
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 03:30 PM »
No, no... My example was the very reason I added OS numbers: Vista adds Segoe UI Light & co. Seven adds Calibri & co. For instance I'm a big fan of Calibri but it has a x-height that's not compatible with anything else (except for a few webfonts). So I can't use the usual stack system because I can't define different sizes for each font (the CSS standard is somewhat lacking in that respect.)
This is why I devised something like this...
@if win[6.1-]
font: 10pt Calibri, sans-serif
@else
font: 9pt Segoe UI Light, Arial, sans-serif
@endif
See what I mean..?
This is why I devised something like this...
@if win[6.1-]
font: 10pt Calibri, sans-serif
@else
font: 9pt Segoe UI Light, Arial, sans-serif
@endif
See what I mean..?
4108
The Pub / Re: Getting ready for an alpha release: WeCSS/Wess improvements
« on November 23rd, 2012, 11:06 AM »
So... Regarding @if statements.
Right now, if you didn't follow, there are two things you can do with them:
- Test for a variable's value.
@if $my_variable <= 7
do_this
@else
do that
@endif
- Test for a browser. (It's also more flexible, can be done anywhere.)
@if ie[7-8], opera
do this
@endif
Meaning "If browser is Opera or IE7 or IE8". The syntax is the same as in CSS file suffixes, e.g. "index.ie[7-8],opera.css" in the case above.
So... As usual when I'm a bit lost when resuming work on Wedge, I'm working on 'easy' stuff that I'm very familiar with, currently being the Wedge logo (yes, I've got something else in the works...) and this particular area of Wess.
These are the three additions I made to user agent tests, and I need some suggestions to help with them.
1/ Negative statements, i.e. @if (!ie[7-]) means "If browser is not IE 7 or above". (Parenthesis can be ommitted, of course.)
2/ OS, i.e. @if (win[6.1-]) meaning "if user is running Windows 7 or later".
3/ Logical AND, i.e. @if (opera, chrome && !android), meaning "if browser is Opera, or it's Chrome but not running in Android".
Pretty nice uh...?
Okay, the OS thing is due to two things.
- I've always been bugged by the fact that Wess stores some browsers per OS, like the fact that Safari Mobile's version number is actually the iOS version number because iOS doesn't allow for a different browser engine than Safari Mobile and thus any browser is locked to the OS version.
- There are some cases where a browser will behave differently in two different OSes, usually due to bugs. I like having the ability to specify browser and OS versions.
Okay, so here are my problems...
0/ First of all, with number zero... I know, 'semantics'... As if it's not 'right' to do browser sniffing. But until we're in a perfect universe where all browsers are perfectly compatible and follow standards etc etc, it's going to be a non-issue to me. People who are against browser sniffing and who say that to others have absolutely no idea how much time they're going to take away from them. IE6 being an obvious example... Wess makes it easy to add quick hacks to IE without hurting other browsers. Screw semantics here, they're just a twisted invention.
1/ I don't know what OS versions I should store... Windows is a given, iOS too (see above), Android as well. But what about the rest...? Are there any OSes, mobile or not, that are famous for requiring tweaks to one or more browsers running in them...? Because if I'm only storing Windows, iOS and Android, at least I don't have to create separate CSS files for each obscure OS like Bada or SunOS or whatever.
2/ Linux: should I store this..? If yes, a generic 'linux' entry? And what about the version number? Maybe no OS version at all, given the mess that it is? And I don't think Linux kernel versions have any influence over the browsers...
3/ Is it any actually necessary to store the OS version in the filename every time...? I was thinking of something a bit complex but that could save some space on the hard drive... Let's say we have a @if (win/windows) test in a file. Wess analyzes this, determines whether we're running Windows, and if yes, it tells the cache manager that we have a special behavior for 'windows'. Thus, the cache manager adds a 'windows-6.1' (or whatever version) keyword to the current file. Otherwise, no special keyword. At cache load time, Wess tries to load the 'windows-6.1' version. If it doesn't exist, it tries to load a version without the 'windows-6.1' keyword. Main problems is, I can already smell a really complex implementation (even if I'm up to it, it might be a failure in terms of performance or comprehensiveness in the end...)
4/ Or we could just store the 'main' version numbers, such as Windows shouldn't bother with anything below XP (5), then store only Vista versions (6) for anything above it because I'm not sure 7 or 8 have any significant differences in how they render stuff. Well, I'm mostly thinking of Vista adding things like Segoe UI Light and C fonts by default, or having support (IIRC) for Direct2D rendering in IE9, thus making it a no-brainer to use the ClearType-enabled fonts by default in a skin when instead it's probably wiser to just ommit them from the font stack in XP.
See what I mean...?
I'm just trying to make things 'right' and avoid having more cache files than necessary...
Re: negative statements, it was an annoying implementation, but it seems to be working. It adds quite a lot of lines though... AND statements were easier to add. And funnier, because I'm doing recursive calls for the AND lists. As I said -- fun. Not sure it's going to be liked widely, though... ;)
Right now, if you didn't follow, there are two things you can do with them:
- Test for a variable's value.
@if $my_variable <= 7
do_this
@else
do that
@endif
- Test for a browser. (It's also more flexible, can be done anywhere.)
@if ie[7-8], opera
do this
@endif
Meaning "If browser is Opera or IE7 or IE8". The syntax is the same as in CSS file suffixes, e.g. "index.ie[7-8],opera.css" in the case above.
So... As usual when I'm a bit lost when resuming work on Wedge, I'm working on 'easy' stuff that I'm very familiar with, currently being the Wedge logo (yes, I've got something else in the works...) and this particular area of Wess.
These are the three additions I made to user agent tests, and I need some suggestions to help with them.
1/ Negative statements, i.e. @if (!ie[7-]) means "If browser is not IE 7 or above". (Parenthesis can be ommitted, of course.)
2/ OS, i.e. @if (win[6.1-]) meaning "if user is running Windows 7 or later".
3/ Logical AND, i.e. @if (opera, chrome && !android), meaning "if browser is Opera, or it's Chrome but not running in Android".
Pretty nice uh...?
Okay, the OS thing is due to two things.
- I've always been bugged by the fact that Wess stores some browsers per OS, like the fact that Safari Mobile's version number is actually the iOS version number because iOS doesn't allow for a different browser engine than Safari Mobile and thus any browser is locked to the OS version.
- There are some cases where a browser will behave differently in two different OSes, usually due to bugs. I like having the ability to specify browser and OS versions.
Okay, so here are my problems...
0/ First of all, with number zero... I know, 'semantics'... As if it's not 'right' to do browser sniffing. But until we're in a perfect universe where all browsers are perfectly compatible and follow standards etc etc, it's going to be a non-issue to me. People who are against browser sniffing and who say that to others have absolutely no idea how much time they're going to take away from them. IE6 being an obvious example... Wess makes it easy to add quick hacks to IE without hurting other browsers. Screw semantics here, they're just a twisted invention.
1/ I don't know what OS versions I should store... Windows is a given, iOS too (see above), Android as well. But what about the rest...? Are there any OSes, mobile or not, that are famous for requiring tweaks to one or more browsers running in them...? Because if I'm only storing Windows, iOS and Android, at least I don't have to create separate CSS files for each obscure OS like Bada or SunOS or whatever.
2/ Linux: should I store this..? If yes, a generic 'linux' entry? And what about the version number? Maybe no OS version at all, given the mess that it is? And I don't think Linux kernel versions have any influence over the browsers...
3/ Is it any actually necessary to store the OS version in the filename every time...? I was thinking of something a bit complex but that could save some space on the hard drive... Let's say we have a @if (win/windows) test in a file. Wess analyzes this, determines whether we're running Windows, and if yes, it tells the cache manager that we have a special behavior for 'windows'. Thus, the cache manager adds a 'windows-6.1' (or whatever version) keyword to the current file. Otherwise, no special keyword. At cache load time, Wess tries to load the 'windows-6.1' version. If it doesn't exist, it tries to load a version without the 'windows-6.1' keyword. Main problems is, I can already smell a really complex implementation (even if I'm up to it, it might be a failure in terms of performance or comprehensiveness in the end...)
4/ Or we could just store the 'main' version numbers, such as Windows shouldn't bother with anything below XP (5), then store only Vista versions (6) for anything above it because I'm not sure 7 or 8 have any significant differences in how they render stuff. Well, I'm mostly thinking of Vista adding things like Segoe UI Light and C fonts by default, or having support (IIRC) for Direct2D rendering in IE9, thus making it a no-brainer to use the ClearType-enabled fonts by default in a skin when instead it's probably wiser to just ommit them from the font stack in XP.
See what I mean...?
I'm just trying to make things 'right' and avoid having more cache files than necessary...
Re: negative statements, it was an annoying implementation, but it seems to be working. It adds quite a lot of lines though... AND statements were easier to add. And funnier, because I'm doing recursive calls for the AND lists. As I said -- fun. Not sure it's going to be liked widely, though... ;)
4109
Archived fixes / Re: Media Gallery: Comment Preview not working
« on November 22nd, 2012, 07:39 PM »
Hmm maybe we are using a generic editor there?
4110
The Pub / Re: Looking for volunteers to test the Wedge private alpha!
« on November 21st, 2012, 07:44 PM »I understand exactly what you mean about ownership of certain areas, I've thought more than once about doing things with the media area in the admin panel, e.g. Harmonising everything to use the same style aesthetically and even the code in some places, but every time I think about it, it feels like overstepping my bounds.
I just don't feel like doing any admin work myself...
As far as translations go, I think the first step is for us to break the languages folder up as we discussed,
and if it helps any, I had an idea about having a language pack that I would be responsible for translating, that will be fun to do and will make sure I can keep on top of all the practical i18n issues that I've only really dealt with hypothetically from my perspective. People paying attention to my recent activity should have a clue as to what language pack that might be. If not, you fight like a dairy farmer.
Uh, no, that's not in Monkey Island.
Re: transifex, oh, the poetic irony... The French version of that website is no laughing matter. It sounds like it was translated through Google, or by someone who barely speaks French at the very least...