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
8971
Features: Posts & Topics / Likes
« on May 11th, 2011, 03:40 PM »
Area: Miscellaneous
Feature: Reactions (Likes)
Developer: Arantor & Nao
Target: users
Status: 95% (core functionality implemented for posts and thoughts)
Comment:
We never liked karma in SMF. We don't like the idea that people get thumbs down on the basis of a message, but they never get to know which posts got them that reputation. Plus -- it's a bit of an ego trip.
Implementing 'like' buttons on posts/topics is a better way of actually guiding people through a user's best posts. We're hoping to implement the feature in every possible feature, such as media items.
The structure already implemented allows for liking any structure in theory - even plugin-added ones, and there's already the foundation for even doing it through AJAX, just more UI work needs to be done; most of the core was added in enough time to get it on wedge.org with more to follow ;)
:edit: October 2014: added support for multiple like types; renamed to 'Reactions'.
Feature: Reactions (Likes)
Developer: Arantor & Nao
Target: users
Status: 95% (core functionality implemented for posts and thoughts)
Comment:
We never liked karma in SMF. We don't like the idea that people get thumbs down on the basis of a message, but they never get to know which posts got them that reputation. Plus -- it's a bit of an ego trip.
Implementing 'like' buttons on posts/topics is a better way of actually guiding people through a user's best posts. We're hoping to implement the feature in every possible feature, such as media items.
The structure already implemented allows for liking any structure in theory - even plugin-added ones, and there's already the foundation for even doing it through AJAX, just more UI work needs to be done; most of the core was added in enough time to get it on wedge.org with more to follow ;)
:edit: October 2014: added support for multiple like types; renamed to 'Reactions'.
8972
Features: Upcoming / Blogs!
« on May 11th, 2011, 03:39 PM »
Area: Miscellaneous
Feature: Blogs!
Developer: Nao (main), Arantor
Target: everyone
Status: 70% (still a lot left to do. And even after we're done, we'll add more features in subsequent releases.)
Comment:
Adds support for creating blogs that are internally considered as special boards. Based on the blog implementation at Noisen.com. Original code by Nao, re-implemented (rewritten?) by Arantor. Create a blog over at noisen.com if you want an idea of how it all works.
Feature: Blogs!
Developer: Nao (main), Arantor
Target: everyone
Status: 70% (still a lot left to do. And even after we're done, we'll add more features in subsequent releases.)
Comment:
Adds support for creating blogs that are internally considered as special boards. Based on the blog implementation at Noisen.com. Original code by Nao, re-implemented (rewritten?) by Arantor. Create a blog over at noisen.com if you want an idea of how it all works.
8973
Features: Theming / Re: New theme
« on May 11th, 2011, 03:37 PM »Ey up :)
I would want a blue based theme for my wedge site, I see from your FB screenshot Wedge is 'brownish'.
Is this customisable in some way or do I have to wait for a themer to do the job properly?
You just create a custom.css file, put it into your styling folder, and add a few lines to rebuild the main color scheme for all parent objects (i.e. everything that was used as a parent by inherited classes.)
This should automatically be applied to your style.css and override it.
Also, if you need IE6-specific hacks in your code, just create custom.ie6.css, and so on.
8974
Features: Posts & Topics / Re: Automatic Quote splitter
« on May 11th, 2011, 03:33 PM »
And it was fun to develop! Just took a couple of days to implement and debug...
8975
Features: Upcoming / Re: Private tag
« on May 11th, 2011, 12:18 PM »
You can specify a list of user IDs. Otherwise it'll be visible only to your friends list.
I should add that this feature is not actually in the trunk for now. But hopefully it should be, in time for the first public release.
I should add that this feature is not actually in the trunk for now. But hopefully it should be, in time for the first public release.
8976
Features: Theming / Re: WeCSS: the Wedge CSS parser
« on May 11th, 2011, 12:11 PM »But who'd want to destroy their life on duplicating common CSS rules when you can use this new syntax with extend and all the neat stuff?
It'd be nice, er no, awesome if CSS4 implemented at least some of those features.
8977
Features: Theming / Re: WeCSS: the Wedge CSS parser
« on May 11th, 2011, 12:10 PM »While such a tool would be great to sort things out, i do wonder if its the way people use CSS that tends to make files big and cluttered. Too often they dress something with a unique style that could be just as well made into a common class. If they took the time to strip it down to bare bones, and THEN start looking at where things would be different, it would be better.Curve theme is a prime example of just adding template specific style after style..when theres clearly so much common items between pages. Evey little tweak gets a new style...
There are those who think that each page should have its own ids, and style generic blocks accordingly for each page (I will call them "the school of semantics"), and those who think that templates should sort it out and generate many different generic blocks and use them directly in the templates (I will call them, "the school of objects"). Objects and semantics are both 'big' in general web development, but they can hardly be used together in CSS.
CSS frameworks started from objects (see OOCSS) -- they defined many, many minor blocks, like Lego cubes, and allowed designers to simply specify what they wanted in their templates, like "<div class="window1 cols2 lines3 line-height5">, things like that. Now that's the second school. It's obviously an interesting concept, but is better served with pre-parsing and a more specific div. So, if you inherit "<div class="this_place">" from window1, cols2, lines3 and line-height5, you get both the object abstraction, and the semantics of a proper name. It's the best of both worlds really. Of course, in order to use it at its best, you need to be very strict about your code.
It was pretty much impossible to rewrite the templates entirely, and it would have made it harder to target specific pages anyway, so I did my best to keep the old structure, and still build upon it with my pre-parser.
I think I've achieved my goals, but I can only tell when I see themers release CSS files using these techniques.
Personally I doubt I will be using it that much - having it the old cluttered way force me to be more efficient(and i haven't up to now, really, but with my latest I do try to do exactly that).
Just as long as you don't write CSS that should be mixed with WeCSS stylesheets, you can use the old style all you want. (Heck, you can even use nested selectors and a few others in the old-style format.)
Another thing is also that making a design - at least when everything isn't already drafted out - tends to be a nonlinear thing. You think of a certain look, and don't bother looking at existing styles, just throw in a new to get that *look* and move on in the creative process. When the time comes to clean up, its often too easy to just let it be."it works" lol.Been victim to that too.
Thats why i think this will appeal more to coders doing design - but not necessarily designers doing code. ;)
8978
Features / Re: New revs
« on May 11th, 2011, 11:59 AM »
rev 766
(13 files, 12kb)
! base64-encoding bypass technique failed when base64 encoding wasn't supported. (Class-CSS.php, Subs-Cache.php)
! The More tag could cause errors when parsed outside of a topic. (Subs-BBC.php)
! Some headers still had an icon next to the header text without any whitespace. (TEMPLATES: Login, Memberlist, Notify, PersonalMessage, Recent, Themes)
* Don't need strong tags in a header... Chances are it's already in bold. (Aeva-Foxy.php, ManagePermissions.template.php)
* $()[0].checked is faster than $().is(':checked'), so use that in loops. (ManagePermissions.template.php)
* Minor typos and such. (BoardIndex.php, Packages.template.php)
(13 files, 12kb)
! base64-encoding bypass technique failed when base64 encoding wasn't supported. (Class-CSS.php, Subs-Cache.php)
! The More tag could cause errors when parsed outside of a topic. (Subs-BBC.php)
! Some headers still had an icon next to the header text without any whitespace. (TEMPLATES: Login, Memberlist, Notify, PersonalMessage, Recent, Themes)
* Don't need strong tags in a header... Chances are it's already in bold. (Aeva-Foxy.php, ManagePermissions.template.php)
* $()[0].checked is faster than $().is(':checked'), so use that in loops. (ManagePermissions.template.php)
* Minor typos and such. (BoardIndex.php, Packages.template.php)
8979
Features: Posts & Topics / Re: Automatic Quote splitter
« on May 11th, 2011, 11:16 AM »
I think we're basically giving weapons to power flamers users in two ways:
- less work done to reply point by point,
- their antagonists can no longer answer a two-liner and say it's because multi-quoting is complicated to do. They can STILL do it, but they won't be able to argue that it's because quoting is hard.
Safe debates for all!
- less work done to reply point by point,
- their antagonists can no longer answer a two-liner and say it's because multi-quoting is complicated to do. They can STILL do it, but they won't be able to argue that it's because quoting is hard.
Safe debates for all!
8980
Features: Theming / Re: WeCSS: the Wedge CSS parser
« on May 11th, 2011, 09:07 AM »Wow, I just learn to theme a little bit... And now I have to learn this? :P
8981
Features: Posts & Topics / Automatic Quote splitter
« on May 11th, 2011, 08:24 AM »
Feature: Automatic Quote splitter
Developer: Nao
Target: users
Status: 100% (complete.)
Comment:
Another simple feature, but it took me ages to fine-tune, mostly because as far as I know, Wedge is the first ever forum system to do this.
When you're replying a post by someone and you want to break up their quoted text into several parts for convenience, you usually have to do some convoluted copying and pasting. Not so with Wedge.
Just put your cursor wherever you want to split the quote, and... press the Shift + Enter key combination (or Ctrl + Enter, your preference.)
That's it, you're done. The quote gets split automatically. Nested tags are taken into account, so you can even split a quoted quote, or right in the middle of a code tag, anything like that which used to be a nightmare before for power users...
It's so easy now, I may have to add a setting to disable this, just in case you miss being upset with all of the manual quote splitting. :eheh:
Let's take this example here, with nested tags:
Quote from Nao on March 3rd, 2011, 03:56 PM
[quote author=Nao link=msg=19 date=1299164218]
Seriously!
[code]Hello Click here and press Shift+Enter world[/code][/quote]
After pressing Shift+Enter, this becomes:
Quote from Nao on March 3rd, 2011, 03:56 PM Quote from Nao on March 3rd, 2011, 03:56 PM
[quote author=Nao link=msg=19 date=1299164218]
Seriously!
[code]Hello [/code][/quote]
Cursor is here now.
[quote author=Nao link=msg=19 date=1299164218][code] world[/code][/quote]
Developer: Nao
Target: users
Status: 100% (complete.)
Comment:
Another simple feature, but it took me ages to fine-tune, mostly because as far as I know, Wedge is the first ever forum system to do this.
When you're replying a post by someone and you want to break up their quoted text into several parts for convenience, you usually have to do some convoluted copying and pasting. Not so with Wedge.
Just put your cursor wherever you want to split the quote, and... press the Shift + Enter key combination (or Ctrl + Enter, your preference.)
That's it, you're done. The quote gets split automatically. Nested tags are taken into account, so you can even split a quoted quote, or right in the middle of a code tag, anything like that which used to be a nightmare before for power users...
It's so easy now, I may have to add a setting to disable this, just in case you miss being upset with all of the manual quote splitting. :eheh:
Let's take this example here, with nested tags:
Seriously!Code: [Select] Hello world
[quote author=Nao link=msg=19 date=1299164218]
Seriously!
[code]Hello Click here and press Shift+Enter world[/code][/quote]
After pressing Shift+Enter, this becomes:
Seriously!Code: [Select] Hello
Code: [Select] world
[quote author=Nao link=msg=19 date=1299164218]
Seriously!
[code]Hello [/code][/quote]
Cursor is here now.
[quote author=Nao link=msg=19 date=1299164218][code] world[/code][/quote]
8982
Features: Miscellaneous / Re: Improvements to Hooks
« on May 11th, 2011, 08:23 AM »
:edit: Expanded added/deleted hook paragraphs.
8983
Features: Upcoming / Private tag
« on May 11th, 2011, 08:07 AM »
Area: BBCode
Feature: Private tag
Developer: Nao
Target: users
Status: 30% (working but not committed; some features need to be added.)
Comment:
Use the 'private' tag inside a post to make sure only some people can read a portion of your message. This is different from the spoiler tag, as the portion will not be hidden, but completely removed from the message for those who can't read it.
Feature: Private tag
Developer: Nao
Target: users
Status: 30% (working but not committed; some features need to be added.)
Comment:
Use the 'private' tag inside a post to make sure only some people can read a portion of your message. This is different from the spoiler tag, as the portion will not be hidden, but completely removed from the message for those who can't read it.
8984
Features: Theming / Wess: the Wedge preprocessor for CSS
« on May 10th, 2011, 07:01 PM »
Feature: Wess (or WESS, or WeCSS, as you like...)
Developer: Nao
Target: themers, modders
Status: 100% (believed to be complete; given its nature, however, new features are being added regularly as needed.)
Comment:
This is one of the features that make me glad I made them, even though it took me many months of work. For the record, back in January 2011, I read an article about Sass, a CSS pre-parser written in Ruby. I already had plans to write something in that style, but they were nowhere near as advanced as their implementation, so I took inspiration and wrote my own PHP version. As a result, it's about 20 times smaller than Sass, and much faster. It's also a bit less elegant (in that it doesn't optimize resulting rules), and stricter in its structure, but I consider this to be a good thing. Finally, Wess also deals with JavaScript and CSS compression, although the line between Class-CSS[1] and Subs-Cache[2] is becoming increasingly blurrier. (Is that proper English?)
Given that Wess is an extremely complete (and sometimes overwhelming) implementation, it deserves, and will eventually get, its own documentation in the near future.
In the meantime, here's an incomplete list of features:
- selector inheritance ('extends' keyword),
- multiple inheritance (both from and to),
- prevent single rules from being inherited by children ('final' keyword),
- cancel inheritance ('unextends' keyword, useful for inherited skins),
- delete a property entirely ('@remove' command),
- reset a selector's earlier styles ('@reset' command, also useful for inherited skins),
- declare virtual selectors that will disappear once they're mixed or inherited.
- nested selectors,
- normal or simplified syntax (no {}; etc.),
- color manipulation functions,
- math functions,
- mixins (supporting parameters),
- variables,
- @if/@else/@endif (test for a browser or environment, and execute CSS accordinly),
- @is (basically an inline @if),
- & shortcut (current selector),
- cross-browser gradients,
- prefix-free CSS3 styles (just the common ones),
- grouping of properties with identical values (e.g. height, line-height: 20px),
- RGBA emulation in IE,
- and inline graphics where supported (can be disabled on a per-file basis.)
The example below is taken straight from our current index.css, and it uses many of the aforementioned features... Try to figure out what does what!
Developer: Nao
Target: themers, modders
Status: 100% (believed to be complete; given its nature, however, new features are being added regularly as needed.)
Comment:
This is one of the features that make me glad I made them, even though it took me many months of work. For the record, back in January 2011, I read an article about Sass, a CSS pre-parser written in Ruby. I already had plans to write something in that style, but they were nowhere near as advanced as their implementation, so I took inspiration and wrote my own PHP version. As a result, it's about 20 times smaller than Sass, and much faster. It's also a bit less elegant (in that it doesn't optimize resulting rules), and stricter in its structure, but I consider this to be a good thing. Finally, Wess also deals with JavaScript and CSS compression, although the line between Class-CSS[1] and Subs-Cache[2] is becoming increasingly blurrier. (Is that proper English?)
Given that Wess is an extremely complete (and sometimes overwhelming) implementation, it deserves, and will eventually get, its own documentation in the near future.
In the meantime, here's an incomplete list of features:
- selector inheritance ('extends' keyword),
- multiple inheritance (both from and to),
- prevent single rules from being inherited by children ('final' keyword),
- cancel inheritance ('unextends' keyword, useful for inherited skins),
- delete a property entirely ('@remove' command),
- reset a selector's earlier styles ('@reset' command, also useful for inherited skins),
- declare virtual selectors that will disappear once they're mixed or inherited.
- nested selectors,
- normal or simplified syntax (no {}; etc.),
- color manipulation functions,
- math functions,
- mixins (supporting parameters),
- variables,
- @if/@else/@endif (test for a browser or environment, and execute CSS accordinly),
- @is (basically an inline @if),
- & shortcut (current selector),
- cross-browser gradients,
- prefix-free CSS3 styles (just the common ones),
- grouping of properties with identical values (e.g. height, line-height: 20px),
- RGBA emulation in IE,
- and inline graphics where supported (can be disabled on a per-file basis.)
The example below is taken straight from our current index.css, and it uses many of the aforementioned features... Try to figure out what does what!
| .catbase virtual overflow: hidden border-radius: 5px padding: 5px 10px 5px margin-bottom: 4px border: 1px solid rgba(0,0,0, .15) font: 700 1.4em/20px $big_font img vertical-align: -3px .cat extends .catbase background-color: #b3afa9 color: white a color: white text-decoration: underline font-size: .92em text-shadow: none :hover color: #fc9 | .cat final background-color: #c3b9c3 border-color: #fd9604 border-width: 2px 0 0 0 text-shadow: black 0 1px 2px .table_list & margin: -5px .title extends .cat padding: 4px 8px border, margin: 0 #sidebar & margin-top: 6px a color: #faf8f8 |
| 1. | The main Wess core... |
| 2. | The list of functions that create the actual CSS and JS files and pass them through Wess or other functions. |
8985
Features: Theming / CSS caching
« on May 10th, 2011, 06:43 PM »
Feature: CSS caching
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
This is pretty much the same as for JavaScript caching, except that there's only one code path for CSS, since there aren't 50 ways to minify stylesheets.
Now, I'd just like to point out that thanks to the preparser, Wedge's cached CSS files will also embed all of the icon data, saving you yet another number of additional hits that servers and browsers usually don't like too much. IE6 and IE7 don't support data embedding, so they'll simply keep using external links. Who uses these stupid browsers anyway?
Developer: Nao
Target: everyone
Status: 100% (believed to be complete.)
Comment:
This is pretty much the same as for JavaScript caching, except that there's only one code path for CSS, since there aren't 50 ways to minify stylesheets.
Now, I'd just like to point out that thanks to the preparser, Wedge's cached CSS files will also embed all of the icon data, saving you yet another number of additional hits that servers and browsers usually don't like too much. IE6 and IE7 don't support data embedding, so they'll simply keep using external links. Who uses these stupid browsers anyway?