| 1. | Even if I just make it feature-comparable with Ad Management for SMF, it'll probably only take a couple of days, but settling for that is not in my to do list, because it isn't what I would call polished. It's functional, nothing more. |
| 2. | Note, in all the cases I'm talking about, I'm looking at no more than $10 for a *lifetime* subscription. It's not about making money. It is about limiting support and I know I'll be putting at least some of that back towards hosting in the end, too. It is no accident that Wedge supports lifetime subscriptions as a core feature. |
| 1. | And prettier, more rugged and generally better than that other pile of crap that a certain SOMEONE was selling. |
Note, in all the cases I'm talking about, I'm looking at no more than $10 for a *lifetime* subscription. It's not about making money. It is about limiting support and I know I'll be putting at least some of that back towards hosting in the end, too. It is no accident that Wedge supports lifetime subscriptions as a core feature.
I don't mind paying for important plugin :) about shoutbox, I think it will be similar to thoughts on wedge homepage? You can use it to chat or it is not the intended function?
A tournament system sounds very interesting.
I did write one (tournaments / raids) for SMF. Should be interesting to rewrite it for Wedge. Looking forward to it.
Also, I'm interested to note how the voting is currently split. Makes it hard to pick something to do!
I don't really care. I don't use ads on my pages. I feel they deteriorate the quality feeling of the site. Though I can understand why some people might want them.
AD management is a 'must have' :cool: I need it on all of my forums to cover hosting expenses..Quote from Norodo on April 1st, 2012, 01:19 PM I don't really care. I don't use ads on my pages. I feel they deteriorate the quality feeling of the site. Though I can understand why some people might want them.
the one which has been taken over by vblamer.. (but an older version).. initial developer was IIRC jerm?!?
My only problem would be that to earn back 10 dollars I'd have to go at least 6 months. For me it's better to just... Pay it all out of my pocket. :)
I'm still thinking $5 to $10, really depends how much complexity I give it. But at the same time, it's a one off fee and you can use it on as many sites as you want.Quote from Norodo on April 1st, 2012, 07:07 PM My only problem would be that to earn back 10 dollars I'd have to go at least 6 months. For me it's better to just... Pay it all out of my pocket. :)
Yup, I already figured anyone with a Friend or Consultant badge would be given a free pass anyway.
update new topic stats when splitting and merging a topic?
pm preview fails when replying to self
have a post unapproved. it links to the moderation center, which does NOT list unapproved posts anywhere...!
clicking the approve button doesn't work either.
merge posts: merge Likes as well!
add a nofollow bbcode!
Add a "IN THIS TOPIC" select box to the top search box... (see Noisen.com)
remove smiley -> JS popup has \n\n (VERY oddly, not all calls to JSE() generate a double-encoded \n, quick moderation items are fine... what's done differently?)
add smartphone/tablet icons next to user names in Who's Online and Info Center...?
write some UI for default_index (either an existing Source file, or a cat/board number)
add a 'force current GIF avatar transparency' setting for users?
unlink [topic prefixes], like on noisen.com (see noisen patch)
use reqWin for popups in media area, instead of zoomedia (which is not as practical here)
only accept A-Z keystrokes in select box if dropdown is open..?
add an actual action=thoughts page, with advanced filtering/sorting (i.e. either linear of threaded), and link that in the homepage.
img.resize JS (from theme.js) should only be printed (in the HTML) when a resized image is used...?
Of that list...
* nofollow bbcode - what exactly should it do? There's a lot more to it than simply adding the base bbcode, it is essentially duplicating the url bbcode including all the preparsing and calls to fixTags.
* merging likes - yeah, I forgot about that. I'll look at that shortly, should be relatively quick to implement.
* smartphone/tablet icons should be doable enough; the user agent is stored in the log_online table when the action is also logged, so it's not as if it's a huge ask to figure that out, really. Might be nice, actually.
* A-Z keystrokes, yeah, that's bitten me when I've set a different privacy and forgotten to click on the textbox again, heh.
But it needs to be 0-9 plus A-Z, since I can well imagine numeric entries as well as textual ones
* resize JS... that does depend on whether Zoomedia is used or not, really, since it may or may not be applicable then.
I was thinking of a tag that would turn all links *inside* its contents to nofollow... Should be rather easy to take the body, and do a regexp on it... (Although it would have to be done last. And I'm not sure whether Wedge converts tags as it finds them, or by nesting level, and even then, top-level or low-level first..?)
Yeah, sometimes I have nice little ideas like that... :eheh:
if you select a privacy and then type a thought, it'll reopen the select box. This is because Wedge doesn't remove focus from the select box when it's closed. It was actually a personal preference -- I thought that in terms of UI, it behaved more logically for people who used a keyboard.
Any key > 0x20, really...
As it finds them. It steps through the post, looking for each instance of a ], and parses as it finds, with the exception of code tags which are handled separately - first.
It's a good idea, but I think it should also be an option too.
There aren't that many keys you really need to worry about, 0-9 and A-Z are really it, rather than any printable character.
So, I guess it could be done only by parsing nofollow tags after all other tags, like for the footnote tag...
Of course. And you know how I hate manipulating UI stuff...
My main concern was that AeMe uses template_button_strip to basically show what is a contextual tab strip of related areas in the menu... Meh.
Any opinion?
Maybe "=", too... Things like that...
Anyway, I think I should just remove focus, like a regular sbox.
It depends how much inelegance you'd be prepared to put up with, and possible performance issues. It would be possible to add a flag in when the tag is detected to be 'nofollow' and reset it when closed, and use that flag in conjunction with the validate function for URL tags. But not the best way it could be handled.
I'd personally rather it be rewritten to be the same structure and style as other uses of the generic menus,
which also means it would be possible to cleanly extend it with hooks etc. if authors want to do so.
I can't see = ever being used properly in a selectbox
(outside the admin panel in which case people are almost certainly not using the keyboard). But yeah, I agree that removing focus would be better.
Scratch that.
Could be done through a post-group permission... (Easiest example.)
When showing a post, if they don't have permission to get rid of nofollow, go through the anchor tags in the post and add a nofollow.
I'm not sure it's the best option (especially, where do we determine the permission for the *author* rather than the current user...?), but it's better than a nofollow tag which itself is unlikely to be used by anyone... (If you don't want to give PR juice to someone, then just don't link to them. Or use a code tag around the link...)
Now, the question would be: is there a point in offering contextual tabs in the media area...? I think there is, but OTOH, perhaps it takes space in the upper area that would be better used by something else... (And if I start adding a 'description' for each entry, they'll take even more space I guess. But a description would be nice for some areas like Add Album...)
Well, I suppose it's all automated even in the current SVN version...?
No, but using it in an input box could lead Wedge to open a list of boards in a select box to a section that says "===> Board"... Although I don't think there should be any case of this happening.