Show Likes

This section allows you to view all posts where this member received or gave a like to.

1
Plugins / [Plugin] CountLikes
CerealGuy « on December 27th, 2014, 06:43 PM »
This Plugin basically shows in profile summary how many likes this user gave/receieved. You can also view those posts.

https://github.com/C3realGuy/CountLikes
2
Archived fixes / Re: Twice in online list?
Pandos « on November 13th, 2014, 09:04 AM »
Never happend again. Please move it.
3
Archived fixes / Re: Some thoughts on notifications
havok « on February 8th, 2014, 09:14 AM »
i would prefer a notification that changes colour (orange to gray) when you click on it but still show the number of unread posts, if a new notification comes in it would then revert to the other colour.(orange) with option to mark all as read
the colour changes would definitely catch your eye.
4
Quote from Wanchope on February 4th, 2014, 12:23 PM
Bump cough, just an innocent reminder...
Well, it's an actual feature to implement, not just a quick tweak, so it's not going to get done overnight...! Unless someone else steps up to do it, of course, but I doubt it..!

This week (and the next?), I'm trying to fix as many bugs as possible, so that I can release a proper public alpha package. A bunch of new features will hopefully come next, then I'll feature-freeze, go beta, fix bugs and do minor tweaks, go RC, fix bugs, and go stable.
That's my schedule...
This feature will probably get into Wedge before I feature-freeze, no worries, but I still have a lot of features I want to do before beta, so it's... kinda complicated.
5
Features / Re: Plugin revs
Nao « on January 23rd, 2014, 04:24 PM »
[Commit revision 45b22d9]
Author: Nao (Signed-off)
Date: Thu, 23 Jan 2014 15:45:31 +0100
Stats: 2 files changed; +141 (insertions), -0 (deletion)


  • Added a README for the plugin folder. It was screaming for one, really. (README.md)
  • And a license file, too, just to be clear, and everythin'. (license.txt)
  • Yeah, well, if all goes well, this commit should post itself automatically on the wedge.org website. We'll see.
  • And it should be using some nifty little icons, instead of obnoxious +-*@! signs.
  • This one means 'Deleted.'
  • This one is 'Added.'
  • This one is 'Modified.'
  • This one is 'Fixed.'
  • And, this one is a 'Comment'.
6
Development blog / That'll do.
Nao « on January 21st, 2014, 04:08 PM »
And here it is. I wanted to postpone it even more... But you don't deserve it. If anything goes wrong, I'll deserve it. In the meantime, please enjoy this; some of you have been waiting over three years for this moment.

https://github.com/Wedge/wedge

Read the README for instructions.
I will attempt to release a public alpha once I get some feedback confirming that everything's working all right.

https://github.com/Wedge/plugins

This is the official plugin repository. Most of these were written by Pete, John and Shitiz. The current license for them is the Wedge license; eventually, though, my goal is to make it clear which plugins are under more permissive licenses. Perhaps I'll even be able to make them all MIT, or something. If you write a plugin and don't want to share it under the MIT license, you can always push it elsewhere.

https://github.com/Wedge/languages

This one isn't a new repo, I introduced it recently on this blog, but what's new is that all of its files are now governed by the MIT license.

Lastly, if you're planning to make the switch to Wedge from an active SMF forum, please remember this:
  • There is currently no 'proper' importer available. Pandos confirmed to me that the official importer is broken, so I'll look into it ASAP.
  • Said official importer will be pushed to the Wedge/tools repo (or its own repo) when available. I'm planning to have it around by next weekend at the latest.
  • If Thorsten looks into it before I do (I know he loves this kind of thing), then he may fix the importer before I do. See? A programmer's logic is no more complex than yours.
  • It's still an alpha, even three years in. Meaning nothing is set in stone, and if a change I make breaks your forum, you can't complain to me. And if it makes it better, then you can't complain either. That was the whole point, after all.
Now, please allow me for a short break, before I jump into new adventures with you all.

7
Features / Re: New revs
Nao « on December 15th, 2013, 11:12 PM »
rev 2345 -- this huge commit is NOT pushed to master yet; I'm pushing it to the byebye-themes branch, mainly to test branching. I may rebase my stuff, although I'll try to avoid that.
 185 files changed, 1939 insertions(+), 2828 deletions(-), 169.14 KiB (record beaten! And unlikely to be beaten again :P The actual diff patch size is 717KB, and I'm going to go through it again, yay.)

 delete mode 100644 Themes/default/languages/Settings.english-uk.php
 delete mode 100644 Themes/default/languages/Settings.english.php
 delete mode 100644 Themes/default/languages/Settings.french.php
 delete mode 100644 Themes/default/languages/Settings.german.php

@ The previous commit, despite its size, was a joke compared to this one. Removing theme support (while keeping support for 99% of its features with intelligent skinning) saves a surprising amount of code. Most files get a few kilobytes shaved off their size. Everything done by hand (and triple-checked!), but I'm still expecting many things to be broken for a few days/weeks. I'll fix as bug reports come.

* Renamed all $theme variables to $settings equivalents. $theme, the equivalent of SMF's $settings, is gone. Forever. (There are 120 files or something in this commit, I'm not going to list them all.)

* Replaced $scripturl with SCRIPT and 'theme_url/theme_dir' with TEMPLATES/TEMPLATES_DIR everywhere. Lots of fun. Same with images_url/dir and ASSETS/ASSETS_DIR.

* And more importantly, renamed we::$id to MID most everywhere. This is about twice faster, and, I guess, easier to type and remember.

- Removed theme support from a lot of places. Again-- not listing these all. Basically, many areas will now consider there's only one theme, and that's all there is to say. They'll usually accept multiple skins, of course.

- Removed a suspicious $theme['smileys_url'] I couldn't find used anywhere. (Class-Editor.php)

- Removed theme settings page entirely, phew. (Admin.php Themes.php and Themes.template.php, ManageSettings.php, ManageSettings.language.php, and a few others.)

- Removed unused globals as found by the new version of my fix-globals script. (Class-Skeleton.php, Class-String.php, Notifications.php, and maybe a couple others.)

- This $theme['smileys_url'] alias hadn't been used for years. (Class-Editor.php)

- THEMEURL and DEFAULT_THEMEURL have never been used as variables in email templates. Time to go. (Subs-Post.php)

* Replaced $settings['images_aeva'] with just a hardlink to the /aeva assets folder.

* Renamed show_avatars and show_signatures user options to hide_* equivalents, as it used to be in SMF; this was partly motivated by the fact that most user options have a more sensible 'off' default (except for return to post and quick reply, where it makes more sense to enable these), but mostly because it was buggy and I had to fix it.

* Renamed reloadSettings() to loadSettings(). It's never called more than once... (index.php, Load.php)

* Renamed a few variables to use $context instead of a setting. For instance, if you want to play with templates to be loaded, you should now do it with $context['theme_templates']. Although this one will probably go at some point, too. Or be renamed. Or whatever. Also, $theme['output_buffers'] is now in $context. (Load.php, Subs-Template.php)

* Moved path settings from Server to basic settings. Seriously, this never had anything to do with 'database settings', why mix them up together..? (Admin.php, ManageServer.php, ManageSettings.php)

* Rewrote the $boardurl hack for url_parts(). Thus making $boardurl non-changing across the page lifetime. (Subs-Auth.php)

! News sender was incorrectly interpreting {$board_url} as the script URL, i.e. with 'index.php' in default situations. (ManageNews.php)

! Fixed query viewer not redirecting to the correct URL. (ViewQuery.php)

! Fixed thoughts being refreshed (after an Ajax post) in non-mobile mode even when posting from a mobile skin. (Ajax.php, Load.php, Subs-Cache.php)

! Fixed main menu showing error when the login process failed. (Subs.php)

! Fixed a Pete bug in loadEssentialThemeData stuff. Then removed all code related to the bug, including the fix. Because if you've been reading this changelog, I'm sure you won't mind reading an extra useless line. (ScheduledTasks.php)

* Harmonized member table column lists in loadMemberData; this saves something like 3KB, which is that less data the PHP parser has to load every page load. (Load.php)

* Slightly faster JS/CSS cache purging. (Subs-Cache.php)

Now, go ahead, Like like you've never liked a commit before!! Because that means I'm getting closer to a public release :P
8
OK, so I was talking to Asgard yesterday and he commented about how the search redundancy in SMF always annoyed him, hence the haiku-esque thought yesterday.

His complaint is that we have a search form every page, and we have a search button, why do we need both? Either drop the quick search, or drop the menu item, and be done with it.

And I thought about this, and I thought some more. Then I had some tea and all other arguments are invalid :D

OK, here's what I want to do.
1. Drop the search menu entirely, there's no need for it including all its fun markup.

2. Add a link to the full search page from just under the search form. This isn't duplication. This means when you want to do things the quick search can't do, you can still get to it.

3. Drop the distinction between simple and advanced searching and just have it push to the 'advanced' page and be done with it.

The result is simpler, cleaner functionality without multiple places on the page being duplicated.
9
The Pub / Re: Looking for volunteers to test the Wedge private alpha!
Nao « on November 1st, 2012, 01:38 AM »
Okay... I'll be honest with you guys.

- It's 1:30am here in Paris. I'm exhausted. I wake up every morning at 6:30am so it's not going to be easy tomorrow...
- I'm done with the alpha. I think it's pretty much ready for release.
- But I don't want to release something that I've completed while very tired, then go to bed, then wake up in the morning to discover a disaster.
- I really, REALLY wanted to release today. I mean it's October 31st and tomorrow is November and I hate November. The name sucks and it makes me think of really cold days. I'm a bit superstitious.
- Still, I did finish it on October 31st...[1]
- So, let's just say the changelog will start with "Private alpha 0.1 - October 31st", all right guys? :P

To sum it up:
- I've got a version I'm relatively happy with (relatively isn't great, but to me it's good enough for a release considering I spent the last few weeks hiding behind my keyboard.)
- I'll release it tomorrow morning.
- That way, I'll be able to assist with any issues while I'm at it.

Everyone fine with that? Click the Like button if you're ready to test tomorrow :P
 1. I'm on the American timezone today. Got too many annoying kids knocking at my door asking for friggin' sweets. Without any costumes. Yeah, the French imported that silly US/Irish tradition, and yet the kids only see the 'sweets' part and don't want to waste time on costumes. I hate Halloween. The only good thing to come out of it was the Nightmare before Christmas.
10
The Pub / Re: Logo Madness
Nao « on September 9th, 2012, 05:03 PM »
What about this? Getting closer...