So, yeah, we're about 5 days in after finally moving wedge.org to actually running Wedge, and I'd like to take a bit of time to just go over how I (at least) see it.

First of all, thank you to everyone who's stopped by, especially if you've stopped by and really loved what Nao's done with the default theme. I had the joy of seeing it ahead of time, so the surprise wasn't quite as big on me, but it was really great seeing it, especially being able to watch it grow.[1]

Also, a big thanks to everyone that's put up with the bugs we've had. As you can probably imagine, Wedge is still a living breathing work, it's still growing, still changing, as you can see from the New Revs thread every time we commit.

Because of that, and because we'd never deployed it in a public way beforehand, there was a lot of stuff that had never been thoroughly tested. So it was a matter of a little disappointment for us that things were buggy - and the list has seemed to be pretty huge in some respects - but overall, I think it's turned out pretty well. The bulk of the bugs are more annoying than serious, and I don't believe any of them are privacy or security related, either, so that's something to be quite happy about, really.

The funny thing is that there's a lot of things that I doubt people have really noticed yet. The theme's the most obvious change, and the way there are icons and animations and things, but I would encourage people to dig a little deeper. There are all sorts of less obvious changes afoot. You might just be surprised at what you find ;)

As ever, if there's anything you like or don't like, tell us! We can't fix things if we don't know they're broken, and if there's a better way of doing something than we're currently doing, tell us that too - the end of it, we want to turn out something truly awesome, and while Wedge is a long way down that road, there's still plenty more to do yet.

Sadly, we have not yet turned the corner that marks the end of 'new features' which would otherwise put us on the road to public releases. Things are still a bit too raw for that, still too many things not yet polished, or finished or tested to destruction. But we've certainly passed the biggest milestone: we've finally moved our own site to our own platform. With that, the single greatest hurdle has been passed; we get to test things in a real environment, we got to thoroughly test the importer, and we get to properly share with you what we've been doing all this time.

So, really, thank you all for bearing with us while we got here, and while we deal with the immediate things we've seen from it - and you'll be able to see the rough edges get polished, things get tweaked, things get added or removed. It's been a long road thus far, and it's not nearly over yet - but you're certainly welcome to join us for the ride :)

The only sad part for me was that we'd decided to keep it under wraps so even when there were screenshots of stuff I was working on, they were all using the existing 'Wine' skin, which you can use here if you want, just head to Profile > Skin Selector.

Well, the only thing I really, really want to finish implementing before we go alpha is proper privacy, which means doing custom membergroups and trying to find the ideal performance solution for table joining or set searching.

It's not that... Wedge generates a URL like [url=real_url]shortened_url[/url]... It should be showing that exact same structure, because at that point, the shortened url is just like any proper 'string' between url tags (i.e. not a URL per se.)

Posted: March 21st, 2012, 11:33 PM

Also, I'm really, really getting sent to the previous post whenever I send a new one... If I reload, then I get to the last post.IIRC you made the "first post is sticky" blog hack, and I don't think you've been using the same technique as I did..?Do you remember what you did?

It's not that... Wedge generates a URL like shortened_url... It should be showing that exact same structure, because at that point, the shortened url is just like any proper 'string' between url tags (i.e. not a URL per se.)

That's the thing, it shouldn't even be doing that, the bare URL is supposed to remain a bare URL unless the author explicitly put it inside url tags, cf. the Dr Who thread in the private board where Aaron quoted a link of mine.

Quote

IIRC you made the "first post is sticky" blog hack, and I don't think you've been using the same technique as I did..?Do you remember what you did?

No, I messed around big-time with the way pagination was set up, but I think that's related to how 'new' is calculated. I'll add it to the to-investigate pile.

I will take a look at it but right now (given 'T minus 2 days') I don't really feel I can give it my full attention, if that makes sense.

Also, I'm slightly surprised no-one's said anything about the page-index navigation having 'prev/next' arrows by the pages. I actually thought that was more of a usability improvement than a lot of things we did >_>

So, really, thank you all for bearing with us while we got here, and while we deal with the immediate things we've seen from it - and you'll be able to see the rough edges get polished, things get tweaked, things get added or removed. It's been a long road thus far, and it's not nearly over yet - but you're certainly welcome to join us for the ride :)

You are thanking us? I personally have to thank you guys for all the work and the patience. I am and will remain a noob with these kind of stuff you guys are doing. But I am a noob who appreciates the commitments and the sacrifices of others. Thank you guys. Keep wedging into the future.

Also, I'm slightly surprised no-one's said anything about the page-index navigation having 'prev/next' arrows by the pages. I actually thought that was more of a usability improvement than a lot of things we did >_>

Definitely!

Oh, and I didn't notice that enablePreviousNext was disabled here... Re-enabled it. I'm sure someone will suddenly notice how cool that rewritten feature is :)

Also, I'm slightly surprised no-one's said anything about the page-index navigation having 'prev/next' arrows by the pages. I actually thought that was more of a usability improvement than a lot of things we did >_>

Definitely!

Oh, and I didn't notice that enablePreviousNext was disabled here... Re-enabled it. I'm sure someone will suddenly notice how cool that rewritten feature is :)

I noticed the prev/next the other day?? - really frikkin useful on an iPad, I can tell you!

Was in the demo, but here...? I'm not sure.Heck, it's enabled by default in Wedge (from install.sql), I have no idea why it was disabled... Perhaps I disabled it in the SMF-based Wedge.org...?

Posted: March 22nd, 2012, 03:35 PM

BTW, the links are hidden when there's not enough width on your device to accomodate for three titles at the same time.Since I have an Opera sidebar (list of tabs) that takes a lot of space, I never see the list. Maybe I should rework that, because it's really a bit too strict.

Oh, and the setting really wasn't set in the admin area... So it's not related to that.

Yes, I know what you were referring to, but come to think of it, that post from billy2 about the iPad was probably in reply to you, not me ;)(Heck, yeah it's definitely so much more usable on a touch screen..!)