Wedge

Well, it's one of the features in Wedge anyway. :niark:
So you'll get it once we switch wedge.org to use it!

I don't even remember installing it at all...

@Dr> I had a quick look at his vlog and at least he can be funny and say interesting things... (I agree with many of his hints from the March 21 one.) Still, too bad he seems to also stand for the big cliché of the self-made American entrepreneur who doesn't fear anyone... First victims: elephants. Next victims?Wedgens. Then you're a Wedgen forever unless you become a Wedger, eheh.

<tl:dr>

YES! :eheh:

Got fooled for a couple of seconds... Just enough time to think "Fuck, I haven't finished integrating AeMe yet!"... Then I realized it was too sci-fi to be true :niark:

Warning: this is a *very* technical post. It also spoils a lot of things about Wedge's internals, eheh.I don't see your point...

Let's take this example. Edit Load.php, loadSubTemplate().


Into this...


That basically allows us to load any kind of overriding template indicated by the styling (in settings.xml, let's say), and then we can completely override the existing function.
We could also have two other functions: $theme_function_before and $theme_function_after, which would be executed respectively before and after the target template function -- without preventing the original function from being run, allowing themers to insert data easily.
Of course, these functions could be added to each other (e.g. a mod adds a _before function to a template function, and the current function also overrides it -- let's just say themes always have priority over mods so their code is run first, then all mods in whatever order.)
Of course, it's not practical for very specific areas like adding buttons to a strip, but in these cases we always have proper hooks with the list of variables, so mods will use hooks for these, and for areas without a hook, they can use _before, _after and/or _override. Then our job is to simply split template functions into many smaller functions.

...Or we could just add template hooks here and there in important areas of the template, of course.
The solution I gave is just a quick one to allow themers to override any single function without us needing to add hooks everywhere.WeCSS also has the same features and limitations, somehow. Because it's preparsed, it gave me great freedom to develop it into an object-oriented version of CSS, and it made it so much simpler for me to manipulate objects with common parents, it's really impressive... However, it also puts an extra burden when it comes to inherited stylings -- if I want to restyle an object that is already parent to others, but I only want to restyle that particular object, I have to careful consider whether or not I'll specifically prevent inheritance for my rules. All in all, more power also means more complexity. Because most of the important objects in Wedge's CSS are linked to others through inheritance, themers will be required to learn how inheritance works, which is basically the whole point of having extra sample stylings that show how it works.

(And in that respect, I'm really glad I made Wine the main styling and pushed Warm to an inherited styling, because it shows how to... pretty much get rid of all the bells and whistles in Wine, so people don't have to worry about making designs that are too close to Wine. At this point, I could even rework Warm to make it even more removed from the Wine style. Something like WordPress's awful default themes.)Correct me if I'm wrong, but it's only hookable by splitting functions into many, right...? Or does it allow one to take the sub-template's HTML and manipulate it as a string before reinjecting it to Tox-G's parser? Which is the only way I can see for Tox-G to be superior to SMF/Wedge's current implementation...

We don't know what that is.Are they paid? If not, they're entitled to do whatever they want.
If you want something suited to your tastes, do it yourself or pay someone to do it for you. Otherwise, you'll have to pray that we have the same vision as you.

Go to simplemachines.org and ask them to implement whatever you want. You'll get the same answer and that'll be very logical. When I worked on Aeva Media, I received dozens of silly requests that I never implemented because they didn't match my vision. In the end, after two years of work, everyone was happy with AeMe. Guess why? Because I'd reached the point where my vision was fulfilled, and it turned out that many people finally got it and loved what they saw.

So, if you don't like Wedge when it's out, you're free to go to another platform. There will be people who will be appreciative of our work. It will make us very happy to see Wedge used on very small scale, and very large scale forums altogether. There is no "universal taste". Neither Pete and I like the WordPress platform, even though it's loved by most people. Wedge won't be loved by everyone. But it will be loved by its authors, and that alone will warrant its continued support from us. It's more than many software can boast about.

Just look at where it's at right now. We started the project on August 25, with diverging ideas about it but a common trust in each other's skills and beliefs. Seven months later, the project is still extremely active, we made 675 commits, added tens of thousands of lines of code... 95% of all web projects are dropped after a couple of months, because it's too complicated, or doesn't go in the direction the author wanted, or just lack of interest in general.

Wedge is here to stay. First of all, it will be out this year. People will be able to test it, give feedback and determine what they like best. So, until we're done with the implementation of our dream features, we won't implement anyone else's requests. We will, however, make tweaks based on community feedback. But we have to draw a line.

(Pete, maybe we should make a FAQ about feature requests...)

Just read through the pages of the topic -- all of the different elements were posted at some point in here.
I also argued against the line (although I do think it looks great. But please read my explanation.)