Show Likes

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

Features / Re: New revs
Nao « on September 8th, 2015, 09:31 AM »
[Commit revision 058f163]
Date: Wed, 15 Jul 2015 15:21:14 +0200
Stats: 2 files changed; +6 (insertions), -3 (deletions)

  • Umm how about adding another magic string like <URL> for choosing http:// or https://?
  • Named it <PROT>

[Commit revision 529c041]
Date: Wed, 15 Jul 2015 15:55:22 +0200
Stats: 1 file changed; +2 (insertions), -1 (deletion)

  • typo...

[Commit revision f278947]
Date: Tue, 28 Jul 2015 00:52:30 +0200
Stats: 3 files changed; +3 (insertions), -3 (deletions)

  • Merge branch 'master' into dev_ssl

[Commit revision a274925]
Date: Sun, 16 Aug 2015 14:31:26 +0200
Stats: 1 file changed; +2 (insertions), -1 (deletion)

  • We already have all the information we need stored in PROTOCOL

[Commit revision b60ebf0]
Date: Sun, 16 Aug 2015 14:33:45 +0200
Stats: 1 file changed; +0 (insertion), -1 (deletion)

  • no need for  anymore and we don't even need it as a global when it's already a super global... thx @Nao

[Commit revision 5875683]
Author: Nao
Date: Tue, 08 Sep 2015 09:31:11 +0200
Stats: 2 files changed; +7 (insertions), -3 (deletions)

  • Merge pull request #31 from C3realGuy/dev_ssl
  • Fixing SSL for Aeva Media
Features / Re: New revs
Nao « on September 8th, 2015, 09:34 AM »
[Commit revision 3c844de]
Author: Nao
Date: Tue, 08 Sep 2015 09:33:58 +0200
Stats: 1 file changed; +2 (insertions), -6 (deletions)

  • Inserting the <PROT> replacement into the <URL> replacement line. One full-page replace is faster than two, if anything. (Subs-Template.php)
Importing into Wedge / Re: Import large WBB to Wedge
GOD « on August 23rd, 2015, 04:35 AM »
Quote from Nao on August 20th, 2015, 03:00 PM
Have no idea whether importing would work.
Good news, though, is that it's risk-free for you: it's not an upgrade tool, it's an importer, so you can run both versions side to side.

Wedge is pretty final these days, only thing left to do is to change the license to something less restrictive.
There are still bugs around, but if they get in the way I'll fix them eventually; also, some features are missing or unfinished, such as the friend & list system which I never got around to write an extensive UI for. Anyway, it's still working, just not as fantastic as I imagined it.
Wedge, itself, is fantastic enough to overlook that. ;)
I have been following the development for a while now.   The site in question is a site that I had going strong for about 1/2 a decade, but then discontinued for various reasons.  I would like to try to bring it back (was only closed for a month), but given the circumstance the idea of a free development such as Wedge is more appealing to me.

I am fully aware that it is still a work in progress.  But I like trying new things and I like where it has been going so far.
Features / Re: New revs
Nao « on August 21st, 2015, 01:07 PM »
[Commit revision df4d8fa]
Author: Nao
Date: Thu, 20 Aug 2015 15:06:25 +0200
Stats: 2 files changed; +5 (insertions), -5 (deletions)

  • Spacinazi. (index.css, sections.css)
Off-topic / Re: Skin edits
CerealGuy « on August 14th, 2015, 10:09 AM »
Keep us updated on your progess :cool:
Off-topic / Re: Notification counter
DC « on August 12th, 2015, 03:11 PM »
If you actually click on the notification or message it then marks it as read and does not show the number. :cool:
Off-topic / Re: Notification counter
CerealGuy « on August 12th, 2015, 01:09 PM »
Sure that's possible, but in my opinion it looks quite bad.
For example you could define this css rule: "span .notevoid{ display:none;}"
.notevoid is used when there are no "new" notifications (button color is grey).
However if you have highly customized skin, it maybe looks nice :eheheh:.
Off-topic / Re: Skin edits
CerealGuy « on August 12th, 2015, 01:14 PM »
The normal wedge way is not to copy every .css and create a new skin, it rather is to create a new skin. A skin uses all css rules from it's parent skin and you only edit or overwrite what you want to change. The benefits are that not every core change needs to be applied to every child skin and you don't have the general classes twice or more on your drive.

I never moved something around in a skin, but it should be possible with skeleton.xml. Have a look at wedge/core/skins/Warm/skeleton.xml.
The Pub / Re: Wedge templating for designers
« on February 3rd, 2013, 09:45 AM »
Stubborness? :)

Look, this is getting where I didn't want it to go. The focus here isn't my stuff, but Wedge. If you feel its working great in these areas I've brought up, then fine, I'll check it out.
Support / [Aeva] Re: Need help implementing Soundcloud
CerealGuy « on August 11th, 2015, 07:52 PM »
Nope didn't get it working...
Problem is that Aeva isn't to well documented :D Debugging is also not really easy.
Perhaps @Nao has some tips for us :D