
This section allows you to view all posts where this member received or gave a like to.
1
[Commit revision 058f163]
Author:
Date: Wed, 15 Jul 2015 15:21:14 +0200
Stats: 2 files changed; +6 (insertions), -3 (deletions)
[Commit revision 529c041]
Author:
Date: Wed, 15 Jul 2015 15:55:22 +0200
Stats: 1 file changed; +2 (insertions), -1 (deletion)
[Commit revision f278947]
Author:
Date: Tue, 28 Jul 2015 00:52:30 +0200
Stats: 3 files changed; +3 (insertions), -3 (deletions)
[Commit revision a274925]
Author:
Date: Sun, 16 Aug 2015 14:31:26 +0200
Stats: 1 file changed; +2 (insertions), -1 (deletion)
[Commit revision b60ebf0]
Author:
Date: Sun, 16 Aug 2015 14:33:45 +0200
Stats: 1 file changed; +0 (insertion), -1 (deletion)
[Commit revision 5875683]
Author: Nao
Date: Tue, 08 Sep 2015 09:31:11 +0200
Stats: 2 files changed; +7 (insertions), -3 (deletions)
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]
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
2
[Commit revision 3c844de]
Author: Nao
Date: Tue, 08 Sep 2015 09:33:58 +0200
Stats: 1 file changed; +2 (insertions), -6 (deletions)
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)
3
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 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.
4
[Commit revision df4d8fa]
Author: Nao
Date: Thu, 20 Aug 2015 15:06:25 +0200
Stats: 2 files changed; +5 (insertions), -5 (deletions)
Date: Thu, 20 Aug 2015 15:06:25 +0200
Stats: 2 files changed; +5 (insertions), -5 (deletions)
- Spacinazi. (index.css, sections.css)
5
Keep us updated on your progess :cool:
6
If you actually click on the notification or message it then marks it as read and does not show the number. :cool:
7
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:.
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:.
8
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.
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.
9
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.
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.
10
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
Problem is that Aeva isn't to well documented :D Debugging is also not really easy.
Perhaps @Nao has some tips for us :D