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.
7531
Features / Re: AeMe reusability of your album images
« on May 1st, 2011, 09:56 PM »
Ah, well in the posting area is an icon for adding new images while posting, there's no way to reload from existing through a click interface, especially when you could find it no less quickly from the main gallery itself, then get the direct bbcode for it from the item's page...
7533
Features / Re: AeMe reusability of your album images
« on May 1st, 2011, 08:09 PM »
Which means it's in Wedge too... :ph34r: :whistle:
7534
The Pub / Re: profiles on wedge.org
« on May 1st, 2011, 07:18 PM »
Ultimate Profile mod, plus the Google Member Map mod...
7535
Features / Re: Custom fieldsets in new topic
« on May 1st, 2011, 05:01 PM »
There's already a mod for that in SMF; it's called the Custom Form mod.
Can't see it being a core feature, nice enough mod though.
Can't see it being a core feature, nice enough mod though.
7536
Off-topic / Re: Least its not cranky here...
« on May 1st, 2011, 04:24 PM »
They get to see part of the truth, the part recorded there, and as we know history can be manipulated.
None of the new team members were privy to the full events that happened, they weren't in the chat rooms, they weren't in IM conversations... and none of that is documented.
None of the new team members were privy to the full events that happened, they weren't in the chat rooms, they weren't in IM conversations... and none of that is documented.
7537
Features / Re: Ditching themes? (+ CSS preparsing)
« on May 1st, 2011, 03:59 PM »I don't see what they can do that stylings could not do *eventually*.
Yeah... You're right in the sense that it's accessible. But from the moment I added more options (override JS, blocks...), it became less accessible. People have to rely on Warm/settings.xml as their documentation on stylings.
We can move the language folder to the root, and then potentially allow themers to specify more language files inside settings.xml...? (Which would then be stored in /data/ or something.)
The idea is just to avoid parallel theme folders when they could benefit from a nested structure. I know that themes in SMF *are* inheriting missing templates from the default folder, but it doesn't do it for CSS files afaik.
This is naturally less of an issue for us because that option was removed.
7538
Features / Re: Ditching themes? (+ CSS preparsing)
« on May 1st, 2011, 03:54 AM »
Yes, I meant the block system, though really, it IS a meta tag, since <we:*> is a tag that will become other tags.
Like an alien? SILENCE, DOCTOR, SILENCE WILL FALL.Quote Hrm. This is a complex issue. Let's see...
We have a top level Sources folder for all the fun sources stuff. We also have a top level Themes folder which contains a whole bunch of stuff, including languages.
Now, there is a wisdom to that top level Themes folder - you have the default theme and each theme that's added to it is added in parallel, making up anything it doesn't have in resources by substituting the default theme's.
If we remove that Themes folder, we essentially risk damaging that association. Thing is, true parallel themes can do things that styling cannot.
Yes, styling can change any CSS right now, and can change certain block elements in the HTML of templates. For stylings to replace themes, two things would have to happen.
Firstly, we'd need to give stylings the ability to modify any template's markup. To me, this seems the wrong way to go; a styling should be a *style*, rather than a complete layout specification. To me, then, I see stylings as making the theme variants system what it always wanted to be: a clear, easily accessible manner for a theme to provide multiple colour variations, or small style variations under a single 'theme' banner. This it can do, and do extremely well, and I see no reason to graft on the ability to hit up markup more generically when really if the markup is that far different, it should be a different physical theme with its own templates (and using the default templates where necessary)
Secondly, languages. If you have a theme that's doing really, really funky things the odds are it's going to bringing its own settings and with that its own language strings. Right now, SMF can deal with this (and even do it properly now, as far as I know!)
More importantly, languages already inherits the template loader subsystem, so it can load theme specific strings then load the default ones.
IOW, I'm not 100% sure we need to change anything, unless we replicate most of the functionality that's already present.
Like an alien? SILENCE, DOCTOR, SILENCE WILL FALL.
Does this mean it'll make more sense for us to ditch /Themes/*/ and just move everything to a root and then extend stylings with the ability to refine some templates?
We have a top level Sources folder for all the fun sources stuff. We also have a top level Themes folder which contains a whole bunch of stuff, including languages.
Now, there is a wisdom to that top level Themes folder - you have the default theme and each theme that's added to it is added in parallel, making up anything it doesn't have in resources by substituting the default theme's.
If we remove that Themes folder, we essentially risk damaging that association. Thing is, true parallel themes can do things that styling cannot.
Yes, styling can change any CSS right now, and can change certain block elements in the HTML of templates. For stylings to replace themes, two things would have to happen.
Firstly, we'd need to give stylings the ability to modify any template's markup. To me, this seems the wrong way to go; a styling should be a *style*, rather than a complete layout specification. To me, then, I see stylings as making the theme variants system what it always wanted to be: a clear, easily accessible manner for a theme to provide multiple colour variations, or small style variations under a single 'theme' banner. This it can do, and do extremely well, and I see no reason to graft on the ability to hit up markup more generically when really if the markup is that far different, it should be a different physical theme with its own templates (and using the default templates where necessary)
Secondly, languages. If you have a theme that's doing really, really funky things the odds are it's going to bringing its own settings and with that its own language strings. Right now, SMF can deal with this (and even do it properly now, as far as I know!)
More importantly, languages already inherits the template loader subsystem, so it can load theme specific strings then load the default ones.
IOW, I'm not 100% sure we need to change anything, unless we replicate most of the functionality that's already present.
7539
Features / Re: New revs
« on May 1st, 2011, 02:23 AM »
Not a very exciting r750, but still...
Revision: 750
Author: arantor
Date: 01:23:17, 01 May 2011
Message:
! Centralised the setlocale calls instead of making them on every call to formatting some time, as well as centralising the locale definition in the language files (Load.php, Subs.php, Subs-Media.php, index.french.php)
----
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/Subs.php
Modified : /trunk/Sources/media/Subs-Media.php
Modified : /trunk/Themes/default/languages/index.french.php
Revision: 750
Author: arantor
Date: 01:23:17, 01 May 2011
Message:
! Centralised the setlocale calls instead of making them on every call to formatting some time, as well as centralising the locale definition in the language files (Load.php, Subs.php, Subs-Media.php, index.french.php)
----
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/Subs.php
Modified : /trunk/Sources/media/Subs-Media.php
Modified : /trunk/Themes/default/languages/index.french.php
7540
Features / Re: Ditching themes? (+ CSS preparsing)
« on May 1st, 2011, 01:33 AM »
It's all relevant, actually.
The whole nature of the caching and processing means that theme editing from inside the box, as it were, is far less realistic, but making it vastly easier for admins to tweak the colour scheme of their forum. And since it's done as a styling rather than a theme, it really is ditching the bulk of what themes were conventionally used for.
This is not to say that we're ditching the theme capability, but to focus intent where it's needed: for themes that are simple recolouring/CSS tweaks derivatives of an existing theme, they shouldn't be made into new themes fully, but made into stylings that can inherit from the parent - which takes care of all the issues about mods on custom themes when the themes are basically the same.
The system does make it easier for themers to do slightly more interesting CSS too - but when custom templates are the only way to go, there's no barrier there at present that isn't in SMF in some fashion, but the barrier is lower: instead of having to craft some random mashup of tags that varies between RCs, there is a standard meta tag to use instead, that's under the theme's control, not mod control.
The whole nature of the caching and processing means that theme editing from inside the box, as it were, is far less realistic, but making it vastly easier for admins to tweak the colour scheme of their forum. And since it's done as a styling rather than a theme, it really is ditching the bulk of what themes were conventionally used for.
This is not to say that we're ditching the theme capability, but to focus intent where it's needed: for themes that are simple recolouring/CSS tweaks derivatives of an existing theme, they shouldn't be made into new themes fully, but made into stylings that can inherit from the parent - which takes care of all the issues about mods on custom themes when the themes are basically the same.
The system does make it easier for themers to do slightly more interesting CSS too - but when custom templates are the only way to go, there's no barrier there at present that isn't in SMF in some fashion, but the barrier is lower: instead of having to craft some random mashup of tags that varies between RCs, there is a standard meta tag to use instead, that's under the theme's control, not mod control.
7541
Off-topic / Re: Doctor Who
« on May 1st, 2011, 01:24 AM »
Confusing... I won't argue with that entirely; mostly because it doesn't answer enough questions. There's still a lot of stuff left unanswered, and it smacks of the one thing that irritated me a little in season 5: the crack in Amy's wall was there in Every Single Episode. Didn't matter what, it was there in some fashion, some shape or form, as though each episode wasn't just part of events, but it was all part of this mega huge scheme that it didn't need to be.
As for the problem with the Silence...
(click to show/hide)
The pirate episode...
(click to show/hide)
As for Gaiman's episode... This is a spoiler, rather than opinion. Click at your peril.
(click to show/hide)
There is one more thing that should be noted.
(click to show/hide)
As for the problem with the Silence...
They were the ones who drew the TARDIS to where it was at the end of Season 5, and as far as we know, the ones who caused it to blow up. The Pandorica trap was designed to snare the Doctor, but what none of the Alliance realised was that it wasn't the Doctor himself that caused the end of the Universe, but his TARDIS exploding, but it wasn't explained in the Big Bang why the TARDIS exploded.
The pirate episode...
We've already had a spoiler of that; it's the scene that happens right at the start of S6E1 where the Doctor is hiding, I think you'll find. But I think it'll be more back to being playful.
As for Gaiman's episode... This is a spoiler, rather than opinion. Click at your peril.
Gaiman's original draft called for very expensive effects, and even after 'shaking down and stealing the lunch money of other episodes', they decided they couldn't afford it. So they're using the Ood again, this time with green eyes. And a character called Idris, who by all speculation seems like it might be someone we already know. Moffat hasn't been against meta references to Old Who; since S5E1 we have seen the faces of the First Doctor three times, the Second Doctor twice, and all other Doctors at least once, plus the writing on the oldest cliff face in the Universe, where River writes 'Hello Sweetie', the first two characters on the second line were Theta Sigma, the Doctor's "nickname" when at school going way back. So, maybe there's more to this yet.
There is one more thing that should be noted.
There is a mid-season break. We're basically 1/3 the way through this half the season already, and the consequences of what's happened are still going to be felt. We haven't seen the last of any of it yet. Not the Silence, not the you-know-what at the end of the episode. Not of the FBI dude. Not of any of it. The Doctor is going to rise high, and then fall further than he has ever fallen. That's still to come. And who River Song is.
7542
Off-topic / Re: Doctor Who
« on May 1st, 2011, 12:44 AM »
Oh, completely bonkers, yes :D
I'm looking forward to next week...
(click to show/hide)
In other news I acquired some 'Lego compatible' stuff today which features the Doctor, Amy, the TARDIS, the Dalek Progenitor Machine and the white Supreme Dalek.
(click to show/hide)
I'm looking forward to next week...
...on board the pirate ship!
In other news I acquired some 'Lego compatible' stuff today which features the Doctor, Amy, the TARDIS, the Dalek Progenitor Machine and the white Supreme Dalek.
And since I already own a big-ass pirate ship of Lego... the TARDIS may just have to land on deck for a photo-op...
7544
Off-topic / Re: Wedge official shirt?
« on May 1st, 2011, 12:42 AM »It would be a great way to have some donations... ;)
I do not want it to be a profiteering exercise, so if we ever do anything other than a limited edition run for supporters or whatever, I really can't see us doing it for any serious profit - but that's just my opinion right now, sat in a darkened room, late at night, in between struggling to make a new feature work. (i.e. Not with my business-sense brain in gear.)
It's never been about the money with us, but I guess one day we could consider it for funding servers down the line if needed.
(Right now: I'm just trying to get an idea of interest, so I can go investigate pricing and so on. More that are interested, the cheaper it gets per item.)
7545
Off-topic / Re: Doctor Who
« on April 30th, 2011, 11:45 PM »I have the episode but can't watch it. Girlfriend too busy speaking with her friend. Ahhhhh >_<