Wedge
Public area => Bug reports => The Pub => Archived fixes => Topic started by: Nao on November 26th, 2010, 03:16 PM
-
Because Wedge is a work in progress, and the website shouldn't be.
So instead, it's based off the customized SMF that I've been using on the Noisen.com website, with all of its features.
One of our goals is to integrate most of these features into Wedge, so when we're ready to release, we'll start building the converter, and will use it to get wedge.org to use Wedge instead.
Just be patient!
:edit: Current plans are to move the website to the Wedge platform in the coming weeks (hopefully in June 2011.)
:edit: Obviously not June 2011... More like March 2012, only a much better Wedge than originally envisioned ;)
:edit: Well, looks like this question is outdated :) Of course Wedge.org has been running Wedge since March 2012.
-
Just be patient!
:edit: Current plans are to move the website to the Wedge platform in the coming weeks.
well
Now I will not sleep :yahoo: :lol: :whistle:
-
Well you'll have to wait for the import tool to be ready ;)
We're not writing it actually, so it's not up to us. And I won't put any pressure on our courageous volunteer! :angel:
-
As a long time SMF user (especially in the last 3 years), I have learnt to be patient :angel:
Bob
-
Current plans are to move the website to the Wedge platform in the coming weeks.
Thanks for the update guys :) Really looking forward to it and kudos for the Wedge team. :) It's really nice to see Wedge is still in development, because many softwares are discontinued. :P
-
Because they're not made by lunatics who maintain blogs about innovation or spend years working on a silly puzzle game until it's perfect :niark:
Although from time to time it's hard... Right now I'm pulling my hair trying to fix some Aeva Media bugs that I don't ever remember meeting in the SMF version of it... (OTOH, today I added proper transparent PNG support for IE6 in the gallery as well.)
(Oh, and I also fixed the smg (now 'media') BBC tag to all for multiple IDs to be used in a regular tag without the use of the 'box' type.)
-
Is it my FF 4.0 or are the post wrappers missing?
nope IE8 also.
edit - ah! I see..... its a blog not forum - sorry
-
yeah it's intentional
-
And something similar will be added into the core of Wedge, though not quite the same way as it's done here. It might look similar though, haven't exactly decided how it should look yet.
-
The only thing I'm sure will be in Wedge is the reduced first line on each post...
Although I myself am wondering whether or not to remove the systematic title on every post... I think it's redundant because it's already in the page header, but OTOH sometimes it could be useful...
-
Well... what we could do is at post-save, determine whether the subject is 'original topic subject with Re: prefix' and if so, ditch it so that there isn't a subject per post - only when it's a per-post title.
-
...Which is exactly what is done at Noisen (just have a look at the patch I sent you months ago... :p)
-
Yes, I knew it was :P I actually knew even before seeing the Noisen patches that's how you'd done it because merged topics, the later thread's first post has a title.
I'm just reaffirming that we can do that unless anyone has any better ideas?
-
I did that years ago and never had a complain about it -- and I love it myself.
However, during that time, I had the opportunity to feel one major drawback to this system. (Well, it's the only one really.)
If you're switching to a tab that's right in the middle of a conversation, you really have to go look at the browser title bar to know what topic this is. Or go to the very bottom or very top of the topic. It's not... practical. Even after years of use, I still can't bring myself to look at the title bar... :^^;:
-
I'd say that since other systems don't worry about it too much (vBulletin for example does much as Noisen does), it's not really an issue in the long run. Though I don't know how you'd fix it other than an all or nothing scenario.
-
Yeah.
Plus, it's a waste of bandwidth to show the same title every single time... And it encourages users not to change the title because people just won't notice -- whereas when it's shown only when changed, it just becomes obvious.
Here's me wondering what should be the behavior for Re: posts where the Re: contents is the changed title. If we assume that all Re: posts should have their title hidden, it gives more real estate, but also fails to convey the fact that an entire derivative conversation is taking place. I think I'd rather hide Re: titles only when they're the same as the first post's. It might encourage moderators to split topics when they see that suddenly all of the posts are using a visible title...
Not sure yet.
-
What, like:
OP: Some Topic
Reply 1: Re: Some Topic
Reply 2: Re: Another Topic Entirely
?
-
Yes...
OP: Some Topic
Reply 1: Re: Some Topic
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Solution 1:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3:
Solution 2:
OP: Some Topic
Reply 1:
Reply 2: Another Topic Entirely
Reply 3: Re: Another Topic Entirely
Which would be best...?
-
:hmm: I'd go with solution 1. The other option is confusing IMO. People are going to suspect that its an bug when you go with solution 2...
-
Solution 1 is what Noisen already does and I'm inclined to think that's what Wedge should do.
Or you can store it but only display it as per solution 1 - which means that if there's a split, the split still retains the information to make semantic use of it.
-
Noisen always stores the title, whether it's repeated or not. It's pretty much mandatory if you want to make it work elsewhere (message search, etc.)
BTW... At some point we should also determine whether we record parent messages IDs for posts. (Even if we don't use them, of course.)
-
Oh, I thought it only stored it if necessary :/ But yes, it is.
Parent id would be interesting but I don't see any practical application other than threading of posts which I'm really not sure about.
-
I don't know... Apart from threading, we could simply add a small icon next to the post, redirecting to the parent post. Which could be useful if one replied to a post and then deleted all of the quotes...
Then again, you'd usually do that through Quick Reply. And of course it's not possible to get a parent ID for those... (Except, of course, if there's only one post in the topic so far.)
-
Hmm, the only problem there is when people multiple-quote across posts.
-
Could do something like the following.
« #23(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259146/#msg259146) Today at 3:56:52 PM » In reply to #22(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259144/#msg259144).
In the case of multiple quotes from multiple posts it could look like this.
« #23(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259146/#msg259146) Today at 3:56:52 PM » In reply to #20(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259138/#msg259138), #21(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259141/#msg259141), and #22(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259144/#msg259144).
Where the numbers are listed in the order the quotes are added or just numerical order. You could also add the poster name so instead of just saying "In reply to #22(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259144/#msg259144)." it could say "In reply to Nao #22(http://wedge.org/pub/faq/6388/faq-why-isn-t-wedge-org-running-wedge/msg259144/#msg259144)."
-
Why don't you add 3 options? No title, second option and first option.
-
Too many options = confusion and illusion of bloat...
-
Too many options = confusion and illusion of bloat...
Provide choice
let the admin to decide whether it will look like forum
it will not look like freaks
p.s. I always tidy up the prefix re
p.p.s. here I am missing the names topic in each message (especially when viewing a page with a mobile phone)
-
We're providing choices where we feel it can be helpful.
For instance, the caching system in Wedge can use 9 different settings (no compression, compress with JSMin, compress with a customized Packer / local jQuery, jQuery at jQuery CDN, jQuery at Google CDN, maybe at Microsoft not sure, and 3² = 9). Things like that can be useful (even to me for debugging purposes)... But modifying a post layout is more of a styling's or a plugin's job to me. I'm trying to move as much as possible into these really.
-
I know, I know. When you are ready, when it is ready. :ph34r:
Damnation :) 8-)
-
You can always participate a lot, get noticed, be made a Friend, then participate again a lot, be technical about everything, and then request for SVN access and you may get it... :P
Of course, by then we may already have gone public... :whistle:
-
I'd love to participate more, but I am more about breaking stuff than coding stuff :niark: Besides there's just too much stuff going on in the regiment - I really don't have the luxury of excess spare time at the moment. I just wish I'll have some when you go public with this :lol: