OK, so I've been very quiet on the coding front lately, one of those projects has materialised in Game Memorial - http://gamememorial.com/
It's a sort of blog/forum hybrid and it's built on SMF 2.0. The reason it's not Wedge is because 1) I couldn't be arsed porting newBalance to Wedge at this point and 2) I don't want to keep patching it once it's stable, something that can't be guaranteed for an indefinite period with Wedge.
There are some other aspects to this that I'm exploring for how they'll fit into Wedge in future:
* future posting - there is the ability to future-post topics and replies. I have a crude but workable UI for this, which isn't really suitable for Wedge at the present time[1] but I want to explore its applications beyond blogging; I'm a biggish fan of WP having the ability to post blog posts in the future, and it's something Wedge deserves, but I'm fairly certain there are benefits to this for regular forum content too, and that's something I will be exploring. The thing is, I don't want to take a risk with this in mainline Wedge, I want to explore it on my own terms and see how it works in practice for me before I figure out a nice way to integrate it into Wedge (core or otherwise)
* tagging - I know we talked about topic tags for Wedge in the past. I'm not entirely sure how useful it would be so I want to explore that too, though in GM's case it's only on the 'game a day' board.
There's all sorts of nuances related to navigation and so on for these things that I need to try out on a real site and see how I interact with it as well as trying to judge how users interact with it - and again, I think the potential is drastic enough that I don't want to drop that in the core just yet until I understand how it works in a real environment.
There is also the fact that it gives me a goal that isn't directly tied into writing code, and more about exercising other parts of my skills and abilities, which serves as a nice rest from the stresses of coding, and by the time demand implied on me it'll actually *force* me to take a break from being stressed by coding which will hopefully work out the last of the kinks related to burn-out and help reduce it happening in the future.
It's a sort of blog/forum hybrid and it's built on SMF 2.0. The reason it's not Wedge is because 1) I couldn't be arsed porting newBalance to Wedge at this point and 2) I don't want to keep patching it once it's stable, something that can't be guaranteed for an indefinite period with Wedge.
There are some other aspects to this that I'm exploring for how they'll fit into Wedge in future:
* future posting - there is the ability to future-post topics and replies. I have a crude but workable UI for this, which isn't really suitable for Wedge at the present time[1] but I want to explore its applications beyond blogging; I'm a biggish fan of WP having the ability to post blog posts in the future, and it's something Wedge deserves, but I'm fairly certain there are benefits to this for regular forum content too, and that's something I will be exploring. The thing is, I don't want to take a risk with this in mainline Wedge, I want to explore it on my own terms and see how it works in practice for me before I figure out a nice way to integrate it into Wedge (core or otherwise)
* tagging - I know we talked about topic tags for Wedge in the past. I'm not entirely sure how useful it would be so I want to explore that too, though in GM's case it's only on the 'game a day' board.
There's all sorts of nuances related to navigation and so on for these things that I need to try out on a real site and see how I interact with it as well as trying to judge how users interact with it - and again, I think the potential is drastic enough that I don't want to drop that in the core just yet until I understand how it works in a real environment.
There is also the fact that it gives me a goal that isn't directly tied into writing code, and more about exercising other parts of my skills and abilities, which serves as a nice rest from the stresses of coding, and by the time demand implied on me it'll actually *force* me to take a break from being stressed by coding which will hopefully work out the last of the kinks related to burn-out and help reduce it happening in the future.
| 1. | The date picker facility is jQuery UI's. It's 42KB minified before gzipping. I am not kidding. |






