Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Nao
9121
Other software / Re: Looking for Portal Suggestions
« on May 3rd, 2011, 05:25 PM »
Same as Pete.
Working on portal features could be fun in the feature. But everything could happen. e.g. we have in our team live627 who works on Envision Portal so maybe we'll end up forking it into Wedge, things like that. (I doubt it, but never say never.)
Working on portal features could be fun in the feature. But everything could happen. e.g. we have in our team live627 who works on Envision Portal so maybe we'll end up forking it into Wedge, things like that. (I doubt it, but never say never.)
9122
The Pub / Re: Wedge.org FAQ board
« on May 3rd, 2011, 04:04 PM »
Easy implementation, but complex hacking needed to apply to any site really. At least with the quality level that you would expect.
It'll be in Wedge for sure. It's one of the reasons I made Wedge to begin with... SMF? Nope.
It'll be in Wedge for sure. It's one of the reasons I made Wedge to begin with... SMF? Nope.
9123
Plugins / Re: Mods - no not *that* question!
« on May 3rd, 2011, 03:50 PM »
Really -- it'll be both.
1/ Mods will be uploadable through the Wedge download system. (Which, basically, is Aeva Media.)
2/ People will be able to vote on them, so they can praise the best mods.
3/ We will have a 'seal of approval' of some sorts -- basically, if we take some time and look into a mod, if we like it we'll give it our seal. Given that we're very demanding creators, though, I doubt we'll give that seal to many mods. Heck, to me a deal-breaker would be simply have unneeded tabs and spaces everywhere in the source code. (So, basically, you won't see me give that seal often, if ever...)
There is a Wedge team. Just not a 'customizer' team yet (or ever, I don't know.)
1/ Mods will be uploadable through the Wedge download system. (Which, basically, is Aeva Media.)
2/ People will be able to vote on them, so they can praise the best mods.
3/ We will have a 'seal of approval' of some sorts -- basically, if we take some time and look into a mod, if we like it we'll give it our seal. Given that we're very demanding creators, though, I doubt we'll give that seal to many mods. Heck, to me a deal-breaker would be simply have unneeded tabs and spaces everywhere in the source code. (So, basically, you won't see me give that seal often, if ever...)
There is a Wedge team. Just not a 'customizer' team yet (or ever, I don't know.)
9124
Features / Re: New revs
« on May 3rd, 2011, 03:36 PM »
I'd say Unknown committed these. It's so Unknown! :niark:
Soooo... One commit per minor bug fix, eh? Even with that trick, they still have barely done 430 commits since we started work on Wedge... And we certainly don't settle on a single change per commit :whistle:
rev 757
(12 files, 18kb)
* Reworked poll layout. Moved it below the topic title (to keep a sense of unity when switching between topics with the prev/next links), moved moderation buttons to the top, turned the box into a we:block, etc. (Display.template.php)
! Skip sidebar/top templating in Wireless. It's already done in a few areas to save CPU time, but should be systematic. (Load.php)
! Fixed wrong text string index. (Subs-Media.php)
! If a block specifies an empty parameter, it should be ignored entirely. (Subs.php)
+ Added an 'id' parameter to we:blocks. (index.template.php)
! Because of the sidebar, poll question inputs could overflow easily. (Poll.template.php)
* Reworked profile warning level system's layout. (Profile.template.php)
- ajax_indicator() is always defined. Don't bother testing for it. (topic.js)
! document.body isn't set up on all browsers, or so I've heard. (topic.js)
! User menus were closing unexpectedly in some situations. (topic.js, index.css, sections.css)
* Spacinazi. (Display.php, ManageSettings.php)
Soooo... One commit per minor bug fix, eh? Even with that trick, they still have barely done 430 commits since we started work on Wedge... And we certainly don't settle on a single change per commit :whistle:
rev 757
(12 files, 18kb)
* Reworked poll layout. Moved it below the topic title (to keep a sense of unity when switching between topics with the prev/next links), moved moderation buttons to the top, turned the box into a we:block, etc. (Display.template.php)
! Skip sidebar/top templating in Wireless. It's already done in a few areas to save CPU time, but should be systematic. (Load.php)
! Fixed wrong text string index. (Subs-Media.php)
! If a block specifies an empty parameter, it should be ignored entirely. (Subs.php)
+ Added an 'id' parameter to we:blocks. (index.template.php)
! Because of the sidebar, poll question inputs could overflow easily. (Poll.template.php)
* Reworked profile warning level system's layout. (Profile.template.php)
- ajax_indicator() is always defined. Don't bother testing for it. (topic.js)
! document.body isn't set up on all browsers, or so I've heard. (topic.js)
! User menus were closing unexpectedly in some situations. (topic.js, index.css, sections.css)
* Spacinazi. (Display.php, ManageSettings.php)
9125
Features / Re: New revs
« on May 2nd, 2011, 07:51 PM »
rev 755
(1 file, 7kb)
+ Added ability to inherit CSS elements from multiple parents. Specify a comma-separated list of items in base: for this, or if you prefer the extends syntax like me, use double quotes around the list (.class extends ".class2, .class3"), otherwise Wedge will consider anything after the first comma to be outside the extend declaration (".class extends .class2", .class3). Not used in Wedge yet, but this can be very interesting in the long run for themers and us. (Class-CSS.php)
! If extending with the use of an ampersand alias, Wedge will now make sure there's only one parent. If there are more, it will only extend based on the first listed parent, to avoid any complications. (Class-CSS.php)
@ That last line -- I could have fixed it to apply to all elements in the list, but honestly at this point it's probably a logic error in the themer's file, and I don't want to waste CPU cycles applying verbatim a request that comes from someone who didn't get what "&" does exactly...
(1 file, 7kb)
+ Added ability to inherit CSS elements from multiple parents. Specify a comma-separated list of items in base: for this, or if you prefer the extends syntax like me, use double quotes around the list (.class extends ".class2, .class3"), otherwise Wedge will consider anything after the first comma to be outside the extend declaration (".class extends .class2", .class3). Not used in Wedge yet, but this can be very interesting in the long run for themers and us. (Class-CSS.php)
! If extending with the use of an ampersand alias, Wedge will now make sure there's only one parent. If there are more, it will only extend based on the first listed parent, to avoid any complications. (Class-CSS.php)
@ That last line -- I could have fixed it to apply to all elements in the list, but honestly at this point it's probably a logic error in the themer's file, and I don't want to waste CPU cycles applying verbatim a request that comes from someone who didn't get what "&" does exactly...
9126
Features / Re: New revs
« on May 2nd, 2011, 03:27 PM »
rev 754
(7 files, 10kb)
! Fixed CSS/JS caching on Mobile Safari. (It appears the extension issue only occurs in the desktop version.) (Subs-Cache.php)
! Fixed Mobile Safari crash (why only this?) caused by incorrectly moved variable declaration. (topic.js)
! Webkit keyword wasn't removed from CSS URLs in the main file caching function. (Subs-Cache.php)
! Added missing device icons to stable_icons(). (Subs.php)
* IE always defined createTextRange, doesn't it? (Class-Editor.php)
* Added a meta tag for iPhone devices to increase image and text size. It doesn't look very good, but it's way more usable. (index.iphone.css, index.template.php)
* Overflow problems in polls. (sections.css)
@ Not too happy with the new iPhone look, but honestly... It can serve as a starting point, and usability is more important on a handheld device than looks.
(7 files, 10kb)
! Fixed CSS/JS caching on Mobile Safari. (It appears the extension issue only occurs in the desktop version.) (Subs-Cache.php)
! Fixed Mobile Safari crash (why only this?) caused by incorrectly moved variable declaration. (topic.js)
! Webkit keyword wasn't removed from CSS URLs in the main file caching function. (Subs-Cache.php)
! Added missing device icons to stable_icons(). (Subs.php)
* IE always defined createTextRange, doesn't it? (Class-Editor.php)
* Added a meta tag for iPhone devices to increase image and text size. It doesn't look very good, but it's way more usable. (index.iphone.css, index.template.php)
* Overflow problems in polls. (sections.css)
@ Not too happy with the new iPhone look, but honestly... It can serve as a starting point, and usability is more important on a handheld device than looks.
9127
The Pub / Re: profiles on wedge.org
« on May 2nd, 2011, 12:23 PM »
Nope. Don't assume anything at wedge.org is going to be in Wedge. Actually, assume the opposite. Until we're done publishing our feature list, assume that Wedge is going to be a stock SMF2 with a built-in Aeva Media.
9128
Features / Re: New revs
« on May 2nd, 2011, 11:58 AM »
rev 753
(4 files, 7kb)
! In the case where multiple selectors were extended at the same time, Wedge didn't always apply inheritance to all of them. (Class-CSS.php)
! Fixed stray dash in CSS cache files when using the default styling (oops.) (Subs-Cache.php)
! Hopefully fixed post overflow issues by, ahem... Setting it to visible. Eh, what? (index.css, index.ie8.css)
+ Added $big_font and $post_font CSS variables. Trying to be more... Semantic, see? Something like that. (index.css)
(4 files, 7kb)
! In the case where multiple selectors were extended at the same time, Wedge didn't always apply inheritance to all of them. (Class-CSS.php)
! Fixed stray dash in CSS cache files when using the default styling (oops.) (Subs-Cache.php)
! Hopefully fixed post overflow issues by, ahem... Setting it to visible. Eh, what? (index.css, index.ie8.css)
+ Added $big_font and $post_font CSS variables. Trying to be more... Semantic, see? Something like that. (index.css)
9129
The Pub / Re: profiles on wedge.org
« on May 2nd, 2011, 09:45 AM »
......
<SIGH>
...............
No, they will NOT work on Wedge. Where exactly is it so hard to understand?
*NOT A SINGLE MOD* from SMF will work on Wedge, except for Aeva Media, Footnotes, Merge Double Posts, Pretty URLs (because I have partial or complete ownership of those), and a few mods from Pete. Anything we didn't write isn't going to work. We rewrote some mods we liked our own way (URL trimmer for instance), but overall, *we don't own SMF mods*, we don't have the legal right to convert them without authorization and certainly can't include them into the Wedge core. That doesn't mean it won't happen in the future -- just that no mod authors have shared their desire to see this happen, and we're not going to ask anyone because basically, if we want something badly, we'll just write our own version.
Can you take half an hour and go read the FAQ page? If you're going to stick around, I'd rather not waste my time reasserting things that are already in the FAQs.
And again: just because there's a cool feature on Wedge.org, doesn't mean that feature is in Wedge (far from it actually. Most of the mods or hacks used on Wedge.org are so dirty, I wouldn't put them into Wedge without weeks of reworking/rewriting.)
And just the same, there are plenty of Wedge features that I'd love to be able to use on Wedge.org, but since the converter isn't done yet, I can't.
<SIGH>
...............
No, they will NOT work on Wedge. Where exactly is it so hard to understand?
*NOT A SINGLE MOD* from SMF will work on Wedge, except for Aeva Media, Footnotes, Merge Double Posts, Pretty URLs (because I have partial or complete ownership of those), and a few mods from Pete. Anything we didn't write isn't going to work. We rewrote some mods we liked our own way (URL trimmer for instance), but overall, *we don't own SMF mods*, we don't have the legal right to convert them without authorization and certainly can't include them into the Wedge core. That doesn't mean it won't happen in the future -- just that no mod authors have shared their desire to see this happen, and we're not going to ask anyone because basically, if we want something badly, we'll just write our own version.
Can you take half an hour and go read the FAQ page? If you're going to stick around, I'd rather not waste my time reasserting things that are already in the FAQs.
And again: just because there's a cool feature on Wedge.org, doesn't mean that feature is in Wedge (far from it actually. Most of the mods or hacks used on Wedge.org are so dirty, I wouldn't put them into Wedge without weeks of reworking/rewriting.)
And just the same, there are plenty of Wedge features that I'd love to be able to use on Wedge.org, but since the converter isn't done yet, I can't.
9130
Features / Re: AeMe reusability of your album images
« on May 2nd, 2011, 08:15 AM »
But my hands are already full ;)
9131
Features / Re: AeMe reusability of your album images
« on May 1st, 2011, 11:00 PM »
Everything is possible.
9132
Features / Re: AeMe reusability of your album images
« on May 1st, 2011, 10:36 PM »
I suppose I could list your x latest uploads in a popup.