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.
Topics - Nao
211
FAQs / [FAQ] How can I become a friend?
« on March 29th, 2011, 03:08 PM »
The Friend group is not an "elite" group, it's just a private group of people who freely discuss the project and share sensible material about it. Because we can't (and don't really want to) release everything to the public right now, we're trying to keep our numbers low. Basically, the more committed you are to discussing Wedge, the more likely you are to catch our attention. If we already know you well, chances are we forgot to invite you. Just ask for it then.
Please note that if you are to become a 'Friend', you'll have to sacrifice your firstborn to us, and promise you won't discuss anything private outside of our private boards.
Our intention is to make as much as possible (90%+) of the currently private content, an actual part of the public area once we can safely release it. Among other things, we will publish discussions about features that ended up not being implemented, in case you want to make your opinion known.
Please note that if you are to become a 'Friend', you'll have to sacrifice your firstborn to us, and promise you won't discuss anything private outside of our private boards.
Our intention is to make as much as possible (90%+) of the currently private content, an actual part of the public area once we can safely release it. Among other things, we will publish discussions about features that ended up not being implemented, in case you want to make your opinion known.
212
The Pub / Read this first!
« on March 29th, 2011, 01:55 PM »
Welcome to the official Wedge forum. Please read this small introduction and guidelines for posting.
- Wedge is a fork of popular forum software SMF. Meaning we started building our software using a copy of SMF 2.0. It is legal to do it, just not legal to distribute it. The SMF team announced a year ago that once SMF 2.0 Final would be released, the license would be changed to one that would allow forks to be distributed.
- Wedge is not SMF. Even if it uses the same source originally, it has changed a lot, and it's going in a different direction. We have no official contact with the SMF team, we don't know their plans for future versions of SMF, just as they don't know our plans for Wedge. Please do not think that "it would be nice if Wedge could do this while SMF does that". We're not doing this with regards to what SMF is doing. We're just doing our thing.
- We're doing Wedge for ourselves first. After many years of frustration with the SMF software, we wanted to build something that would merge the best of SMF, with the best of our ideas for it. As long as Wedge is not officially out, it can evolve massively. We ask you not to post "feature suggestions" to the forum. We're okay with very small changes if they make sense to us, but we already have our hands full with the features we're already working on implementing. And believe us -- that's a lot of work.
- We're not trying to make everyone move to Wedge when it comes out. So, please don't try the usual "implement this, or I won't switch to Wedge" message. You will only be ignored. And even if we reply, our ready-made answer to anything like that will be "stay with SMF, then."
- You may post in the Pub area, but please make sure not to ask anything that isn't already mentioned in the FAQ section.
(This post will be updated if anything comes up that should be presented to new users immediately.)
- Wedge is a fork of popular forum software SMF. Meaning we started building our software using a copy of SMF 2.0. It is legal to do it, just not legal to distribute it. The SMF team announced a year ago that once SMF 2.0 Final would be released, the license would be changed to one that would allow forks to be distributed.
- Wedge is not SMF. Even if it uses the same source originally, it has changed a lot, and it's going in a different direction. We have no official contact with the SMF team, we don't know their plans for future versions of SMF, just as they don't know our plans for Wedge. Please do not think that "it would be nice if Wedge could do this while SMF does that". We're not doing this with regards to what SMF is doing. We're just doing our thing.
- We're doing Wedge for ourselves first. After many years of frustration with the SMF software, we wanted to build something that would merge the best of SMF, with the best of our ideas for it. As long as Wedge is not officially out, it can evolve massively. We ask you not to post "feature suggestions" to the forum. We're okay with very small changes if they make sense to us, but we already have our hands full with the features we're already working on implementing. And believe us -- that's a lot of work.
- We're not trying to make everyone move to Wedge when it comes out. So, please don't try the usual "implement this, or I won't switch to Wedge" message. You will only be ignored. And even if we reply, our ready-made answer to anything like that will be "stay with SMF, then."
- You may post in the Pub area, but please make sure not to ask anything that isn't already mentioned in the FAQ section.
(This post will be updated if anything comes up that should be presented to new users immediately.)
213
Archived fixes / [FAQ] Why isn't wedge.org running Wedge?
« on November 26th, 2010, 03:16 PM »
Because Wedge is a work in progress, and the website shouldn't be.
So instead, it's based off the customized SMF that I've been using on the Noisen.com website, with all of its features.
One of our goals is to integrate most of these features into Wedge, so when we're ready to release, we'll start building the converter, and will use it to get wedge.org to use Wedge instead.
Just be patient!
:edit: Current plans are to move the website to the Wedge platform in the coming weeks (hopefully in June 2011.)
:edit: Obviously not June 2011... More like March 2012, only a much better Wedge than originally envisioned ;)
:edit: Well, looks like this question is outdated :) Of course Wedge.org has been running Wedge since March 2012.
So instead, it's based off the customized SMF that I've been using on the Noisen.com website, with all of its features.
One of our goals is to integrate most of these features into Wedge, so when we're ready to release, we'll start building the converter, and will use it to get wedge.org to use Wedge instead.
Just be patient!
:edit: Current plans are to move the website to the Wedge platform in the coming weeks (hopefully in June 2011.)
:edit: Obviously not June 2011... More like March 2012, only a much better Wedge than originally envisioned ;)
:edit: Well, looks like this question is outdated :) Of course Wedge.org has been running Wedge since March 2012.
214
FAQs / [FAQ] Who's working on it?
« on November 9th, 2010, 02:10 PM »
Currently, Wedge is developed by its creators and project managers.
* Peter Spicer ("Arantor") is the creator and main developer of SimpleDesk. He's also one of the better known SMF community members, having posted more messages than anyone else in the boards, mainly as a project helper. He's so smart it's scary, he's nice, he's everywhere, he figures out solutions to problems before they even arise, he collects dragon toys, he's got a cool name and, more importantly, he's on fire.
* René-Gilles Deberdt ("Nao") is the main developer of Aeva Media, the most downloaded mod for SMF. He's doing his best to be a bigger drama queen than Arantor. He's got a weird name, he's so monomaniac he scares himself (90+ releases of Aeva Media in 2 years), and he's old and grumpy, and it's not getting any better. And, more importantly, he can move his ears and has mismatched pinkies.
Who does what?
Working on such a large codebase allows us to specialize in different areas, generally our areas of expertise or simply what we're interested on at the time. We both have a huge to-do list and they mostly don't overlap. Arantor is specialized in innovation, reworking the admin area and rewriting the add-on manager. Nao's main interests are in user experience, writing tools to make a designer's life easier, designing stuff in general, the media gallery which he built before working on Wedge, etc.
To simplify, one could say that Arantor is in charge of the backend while Nao is the frontend developer, but it wouldn't exactly be true, as we both do a little bit of each, and we also tend to look into each other's work and suggest improvements or fix tiny bugs here and there. What we learned after a year of development, though, is that right from day one, we got together pretty well and we've been very happy with our collaborative work.
We certainly hope it shows in the software itself!
Website credits
- The website itself is using Wedge as its platform, as logic would dictate.
- The forum logo is a community effort led by Nao, with help from Bloc and CJ Jackson.
- The forum badges are loosely inspired by earlier SMF badges created by Gazmanafc.
Wanna join the team?
Not for now, we're afraid. We will announce any team additions and changes here in the future. Please do not offer your help here or anywhere else. Right now we prefer to keep the team as small as possible. Of course, we always accept suggestions with pleasure, but we'll do the coding by ourselves. echo 'We like that.';
* Peter Spicer ("Arantor") is the creator and main developer of SimpleDesk. He's also one of the better known SMF community members, having posted more messages than anyone else in the boards, mainly as a project helper. He's so smart it's scary, he's nice, he's everywhere, he figures out solutions to problems before they even arise, he collects dragon toys, he's got a cool name and, more importantly, he's on fire.
* René-Gilles Deberdt ("Nao") is the main developer of Aeva Media, the most downloaded mod for SMF. He's doing his best to be a bigger drama queen than Arantor. He's got a weird name, he's so monomaniac he scares himself (90+ releases of Aeva Media in 2 years), and he's old and grumpy, and it's not getting any better. And, more importantly, he can move his ears and has mismatched pinkies.
Who does what?
Working on such a large codebase allows us to specialize in different areas, generally our areas of expertise or simply what we're interested on at the time. We both have a huge to-do list and they mostly don't overlap. Arantor is specialized in innovation, reworking the admin area and rewriting the add-on manager. Nao's main interests are in user experience, writing tools to make a designer's life easier, designing stuff in general, the media gallery which he built before working on Wedge, etc.
To simplify, one could say that Arantor is in charge of the backend while Nao is the frontend developer, but it wouldn't exactly be true, as we both do a little bit of each, and we also tend to look into each other's work and suggest improvements or fix tiny bugs here and there. What we learned after a year of development, though, is that right from day one, we got together pretty well and we've been very happy with our collaborative work.
We certainly hope it shows in the software itself!
Website credits
- The website itself is using Wedge as its platform, as logic would dictate.
- The forum logo is a community effort led by Nao, with help from Bloc and CJ Jackson.
- The forum badges are loosely inspired by earlier SMF badges created by Gazmanafc.
Wanna join the team?
Not for now, we're afraid. We will announce any team additions and changes here in the future. Please do not offer your help here or anywhere else. Right now we prefer to keep the team as small as possible. Of course, we always accept suggestions with pleasure, but we'll do the coding by ourselves. echo 'We like that.';
215
The Pub / [FAQ] Is it a friendly fork?
« on November 9th, 2010, 01:57 PM »
It is friendly -- to end users and anyone who happily embraces the software. It may be seen as a hostile fork of SMF, though, in the sense that currently the license we chose is set to prevent SMF from re-using our implementations. Our choice of license was dictated by a few events that, while regrettable in a sense, contributed to the birth of Wedge, and its subsequent good health.
In the first two months of the project lifetime, while we were building Wedge in private, we were in touch with the SMF team and were providing bug reports and fixes that we had done in Wedge. At the time, we thought of Wedge as a "laboratory" to allow experimenting outside of the SMF codebase. Our new code was supposed to be able to be merged back into the SMF codebase.
However, after more internal conflicts with the team, we decided that the SMF team didn't do anything to deserve our help. While we can understand that many people might have thought that our apparent leaving of the active SMF community might be reason enough to blame us for whatever conflict happened between the SMF team and us, fact is, we *were* active, and actually way more active than the SMF team itself, providing many, many bug fixes and helping speed up the releases of SMF 2.0 RC4 and RC5 among other things.
In the future, when Wedge is stable enough, then we will reconsider what our final license is. But as much as we'd like to license our code as BSD, it is unlikely to happen until we feel comfortable sharing more than a few fixes with the SMF team again. I guess we can say the ball is in their camp at this point. :)
In the first two months of the project lifetime, while we were building Wedge in private, we were in touch with the SMF team and were providing bug reports and fixes that we had done in Wedge. At the time, we thought of Wedge as a "laboratory" to allow experimenting outside of the SMF codebase. Our new code was supposed to be able to be merged back into the SMF codebase.
However, after more internal conflicts with the team, we decided that the SMF team didn't do anything to deserve our help. While we can understand that many people might have thought that our apparent leaving of the active SMF community might be reason enough to blame us for whatever conflict happened between the SMF team and us, fact is, we *were* active, and actually way more active than the SMF team itself, providing many, many bug fixes and helping speed up the releases of SMF 2.0 RC4 and RC5 among other things.
In the future, when Wedge is stable enough, then we will reconsider what our final license is. But as much as we'd like to license our code as BSD, it is unlikely to happen until we feel comfortable sharing more than a few fixes with the SMF team again. I guess we can say the ball is in their camp at this point. :)
216
Off-topic / Browser wars
« on October 14th, 2010, 05:20 PM »
http://my.opera.com/chooseopera/blog/2010/10/14/opera-11-will-have-extensions
Hopefully it'll be Firefox-like extensions, not Chrome-like crap!
I'm pretty confident, since they *already* made the whole Chrome-like extension crap earlier -- with their widgets concept.
Hopefully it'll be Firefox-like extensions, not Chrome-like crap!
I'm pretty confident, since they *already* made the whole Chrome-like extension crap earlier -- with their widgets concept.
217
Features / Naming Boards/blogs/sites etc.
« on October 13th, 2010, 10:23 AM »
I'm a bit at a loss here.
In Noisen.com, boards are called boards, blogs are called blogs, and sites are called sites. Yay.
A site, in my mind, is like a blog, but without the traditional blog homepage. It would be more like a portal of sorts, allowing you to sort articles manually, rather than chronologically. Internally, it represents few changes really.
However, what happens is that all of these site types are actually just boards.
In the French version of Noisen, I decided to rename "sections" (which is the unlikely French translation for "boards") into "sites". Made more sense to me, especially when offering people the ability to create their own sites. "Create your own section" is quite lackluster... And yes, that pretty much implies that all boards are "sites" by default, and only become "boards" (forums) when specifying so. It doesn't matter at all... I think it's okay. If you want to create a website, you know that forums and blogs have a special layout which you can select, but sites, OTOH, are yours to imagine.
So, should I rename 'board' to 'site' in the code, when it's generic enough, and leave it to board when it's specifically meant as a board? (Which doesn't happen a lot...)
In Noisen.com, boards are called boards, blogs are called blogs, and sites are called sites. Yay.
A site, in my mind, is like a blog, but without the traditional blog homepage. It would be more like a portal of sorts, allowing you to sort articles manually, rather than chronologically. Internally, it represents few changes really.
However, what happens is that all of these site types are actually just boards.
In the French version of Noisen, I decided to rename "sections" (which is the unlikely French translation for "boards") into "sites". Made more sense to me, especially when offering people the ability to create their own sites. "Create your own section" is quite lackluster... And yes, that pretty much implies that all boards are "sites" by default, and only become "boards" (forums) when specifying so. It doesn't matter at all... I think it's okay. If you want to create a website, you know that forums and blogs have a special layout which you can select, but sites, OTOH, are yours to imagine.
So, should I rename 'board' to 'site' in the code, when it's generic enough, and leave it to board when it's specifically meant as a board? (Which doesn't happen a lot...)
218
The Pub / Logo Madness
« on October 11th, 2010, 07:27 AM »
(I'm wondering if Adonis or Bloc would be willing to give a shot at doing a Yanone Kaffe-based Wedge logo...)
:edit: This is an old topic from the private area that I'm moving to the public area to show off the various and interesting logos that were built over time. It might give you an idea of how we're all working together. (Basically: people do their best -- then I bitch and complain -- then I do it my own way and I take all the credit. 8-))
:edit: This is an old topic from the private area that I'm moving to the public area to show off the various and interesting logos that were built over time. It might give you an idea of how we're all working together. (Basically: people do their best -- then I bitch and complain -- then I do it my own way and I take all the credit. 8-))
219
Off-topic / Two minutes of warmth in this cruel world
« on October 6th, 2010, 04:55 PM »220
FAQs / [FAQ] Should I switch to Wedge?
« on October 1st, 2010, 06:32 PM »
Should I be using Wedge instead of SMF?
- If you're an übergeek, yes. If you're Joe Yourmileage, your mileage may vary. You may enjoy the new features in Wedge, and some of the simplified processes, but may also fear our more frantic and chaotic release habits (although frantic is better than once a year innit?), or the different state of mind compared to SMF. We're just two people in here, and we're well known for saying the truth, rather than going through convoluted speeches to "keep it professional". We think that professionalism is delivering software that rocks. We'll leave the bullshitting to people on the payroll, thank you very much.
- You can still install Wedge and run it alongside SMF. Consider the two projects as totally separate. We will *not* provide an upgrade script, however later on we will release a perfect converter. You'll be able to test Wedge and see if it suits you, without deleting your current SMF install. (The SMF team will probably also write a Wedge to SMF converter at some point.)
- Maybe you should simply decide whether you want to follow the authors' vision rather than the main SMF line.
- If you're an übergeek, yes. If you're Joe Yourmileage, your mileage may vary. You may enjoy the new features in Wedge, and some of the simplified processes, but may also fear our more frantic and chaotic release habits (although frantic is better than once a year innit?), or the different state of mind compared to SMF. We're just two people in here, and we're well known for saying the truth, rather than going through convoluted speeches to "keep it professional". We think that professionalism is delivering software that rocks. We'll leave the bullshitting to people on the payroll, thank you very much.
- You can still install Wedge and run it alongside SMF. Consider the two projects as totally separate. We will *not* provide an upgrade script, however later on we will release a perfect converter. You'll be able to test Wedge and see if it suits you, without deleting your current SMF install. (The SMF team will probably also write a Wedge to SMF converter at some point.)
- Maybe you should simply decide whether you want to follow the authors' vision rather than the main SMF line.
221
FAQs / [FAQ] What's the point?
« on October 1st, 2010, 06:32 PM »
- To give new life to SMF. While it was ahead of its time when it first came out many years ago, SMF is now behind the competition, because of the long development time for version 2, including a "feature frozen" state that lasted for over 3 years (an eternity on the Internet), and the many team changes. So many ideas were lost in the process.
- Leaving aside the feature set, Wedge is here to try new things, apply new strategies, new systems of thoughts to the SMF world. The way SMF is built and released works for some, but not for everyone. Hence:
* The developers are the project leaders, who share a common vision for Wedge. No team democracy means that you're under our control (insert evil laugh). It also means, more interestingly, that there's no one to stop us from realizing our vision, and the only pressure is the one that we put onto ourselves. (Unfortunately, we happen to be very demanding of ourselves.)
* Release cycle: SMF 1.x was great. However, it is also very static. This is probably due to the complexity of releasing new minor updates in packages that can be installed in one click. We do not plan to follow the same system. Instead, we would like to release full packages, without regard to minor or major releases, and release them early and often, as soon as the backbone for Wedge is solid enough. The idea is to make it easier for mods and themes to coexist with SMF without having to edit Wedge files, meaning that you can simply overwrite the files without losing your mods and themes. If you don't like this way of releasing new versions, you should use SMF 2.x instead, where the development team intents to keep releasing packages for minor updates.
- Leaving aside the feature set, Wedge is here to try new things, apply new strategies, new systems of thoughts to the SMF world. The way SMF is built and released works for some, but not for everyone. Hence:
* The developers are the project leaders, who share a common vision for Wedge. No team democracy means that you're under our control (insert evil laugh). It also means, more interestingly, that there's no one to stop us from realizing our vision, and the only pressure is the one that we put onto ourselves. (Unfortunately, we happen to be very demanding of ourselves.)
* Release cycle: SMF 1.x was great. However, it is also very static. This is probably due to the complexity of releasing new minor updates in packages that can be installed in one click. We do not plan to follow the same system. Instead, we would like to release full packages, without regard to minor or major releases, and release them early and often, as soon as the backbone for Wedge is solid enough. The idea is to make it easier for mods and themes to coexist with SMF without having to edit Wedge files, meaning that you can simply overwrite the files without losing your mods and themes. If you don't like this way of releasing new versions, you should use SMF 2.x instead, where the development team intents to keep releasing packages for minor updates.
222
FAQs / [FAQ] Minimum requirements
« on October 1st, 2010, 06:32 PM »
Minimum requirements
Client side:
Opera 9 or higher, 12 or higher recommended.
Microsoft Internet Explorer 6 or higher, 10 or higher recommended.
Mozilla Firefox 2 or higher, 17 or higher recommended.
Apple Safari 3 or higher, 6 or higher recommended.
Google Chrome (any version), 27 or higher recommended.
JavaScript is strongly recommended
Cookies are strongly recommended
Flash is recommended for media embedding
Server side:
PHP 5.3 or higher
MySQL 5.0.3 or higher
GD2 graphic library for PHP
Client side:
Opera 9 or higher, 12 or higher recommended.
Microsoft Internet Explorer 6 or higher, 10 or higher recommended.
Mozilla Firefox 2 or higher, 17 or higher recommended.
Apple Safari 3 or higher, 6 or higher recommended.
Google Chrome (any version), 27 or higher recommended.
JavaScript is strongly recommended
Cookies are strongly recommended
Flash is recommended for media embedding
Server side:
PHP 5.3 or higher
MySQL 5.0.3 or higher
GD2 graphic library for PHP
223
FAQs / [FAQ] What is Wedge?
« on October 1st, 2010, 06:30 PM »
WHAT is Wedge?
- Wedge is a fork of SMF. To be clear, SMF is Simple Machines Forum, a forum (bulletin board) system that is free to use on your own web server. When it became apparent that SMF 2.0 would be released in an open source license, we used the opportunity to 'fork' it, that is, create a new software based on the same code, going in a different direction. Hopefully an interesting one!
- Our current target release dates: early 2012 for the demo, an alpha version one to three months later, a beta version one to three months after that, and summer/autumn 2012 for the stable release.
- Wedge is a fork of SMF. To be clear, SMF is Simple Machines Forum, a forum (bulletin board) system that is free to use on your own web server. When it became apparent that SMF 2.0 would be released in an open source license, we used the opportunity to 'fork' it, that is, create a new software based on the same code, going in a different direction. Hopefully an interesting one!
- Our current target release dates: early 2012 for the demo, an alpha version one to three months later, a beta version one to three months after that, and summer/autumn 2012 for the stable release.
224
Off-topic / iHate Apple
« on September 27th, 2010, 12:08 PM »
Sorry, I noticed Dismal's link so I couldn't help asking this here!
Ever since I saw the Epic Citadel demo for the iPhone4 and iPad, I've become a despicable Apple fanboy in the closet. (Yes, this is the closet here.) Don't get me wrong -- I still hate Apple, but I really, really like top tech 3D shite in small devices. I bought a DS at some point, but the 3D wasn't so good, and it's hardly hackable. Now, I got to manipulate several friends' iPhones over the years, and I loved the iPhone 4 because of the resolution, but hated the iPhone4 case, because it's rugged. I mean, its corners are edgy, rather than soft like on the iPhone 3 case.
Now, I'm considering buying an iPod Touch 4 because it's cheap (309¤ with 32GB), has high res, and seems to have the same case as earlier generations.
I don't know if it's the 'right' choice. Would 8GB be enough? Same hardware as the 32GB version or not?
I couldn't care less about a good camera, and I like my current phone (a very old cheap one, eh.)
I'd go for the iPhone4 if I had an actual reason to use the Interwebs outside of my place... But I really don't go outside a lot, and I think it's way too expensive for the use I'd make out of it -- I mean... I call people for something like, 15 minutes a month at the most?
Probably just posting this topic will give me some relief... I'm a sucker for gadgets. I've managed not to buy anything too 'gadgety' in the last couple of years. But right now, with Epic Citadel, it's become VERY hard. :P
Ever since I saw the Epic Citadel demo for the iPhone4 and iPad, I've become a despicable Apple fanboy in the closet. (Yes, this is the closet here.) Don't get me wrong -- I still hate Apple, but I really, really like top tech 3D shite in small devices. I bought a DS at some point, but the 3D wasn't so good, and it's hardly hackable. Now, I got to manipulate several friends' iPhones over the years, and I loved the iPhone 4 because of the resolution, but hated the iPhone4 case, because it's rugged. I mean, its corners are edgy, rather than soft like on the iPhone 3 case.
Now, I'm considering buying an iPod Touch 4 because it's cheap (309¤ with 32GB), has high res, and seems to have the same case as earlier generations.
I don't know if it's the 'right' choice. Would 8GB be enough? Same hardware as the 32GB version or not?
I couldn't care less about a good camera, and I like my current phone (a very old cheap one, eh.)
I'd go for the iPhone4 if I had an actual reason to use the Interwebs outside of my place... But I really don't go outside a lot, and I think it's way too expensive for the use I'd make out of it -- I mean... I call people for something like, 15 minutes a month at the most?
Probably just posting this topic will give me some relief... I'm a sucker for gadgets. I've managed not to buy anything too 'gadgety' in the last couple of years. But right now, with Epic Citadel, it's become VERY hard. :P
225
Features / Another life-changing fantastic idea for quotes! (Bit silly, too.)
« on September 12th, 2010, 04:47 PM »
Okay, you know what -- QUOTES ARE WAY UNDERUSED.
People don't multi-quote enough. People don't know the pleasure of replying everything line by line.
You know what? Because people use the Quote bbc button and it's so complicated.
Power-quoters like me, and perhaps Pete, do it manually. Quote message... Okay, focus on message, ctrl+end, ctrl+shift+left arrow until I select the entire [/quote], ctrl+c, ctrl+home (I use ctrl a lot, at this point...), go to end of the quote I want to reply to, ctrl+v, enter, enter, type answer... Enter, enter, ctrl+v, right arrow, del (this effectively turns it into an opening quote), go to end of the quote, keep doing it that way...
Now, you can try it if you never did. It works and, well, I don't see a better way of doing it quickly.
...
Until today.
I remembered these freaking' annoying e-mails.
Which were so easy to reply to, because they already were entirely quoted.
> Hello, world.
> Reply to this.
> Just below.
See? It's easy.
> More quotes.
---------------> Now what? Why can't we do that for Wedge?
That's the idea, really.
Quote message.
Show message. Instead of showing it inside a large quote tag, turn it into a post with limited width, add automatic carriage returns, and *add > signs in front of each line*.
Now, the user can reply like on any e-mail they may want to quote...
And then, when they hit the Send button, that's where the magic is supposed to be applied: we turn back this post into a properly quoted post. I don't know exactly how, but we can discuss it. Basically, it's simply about concatenating all lines with a starting ">" into a single quote. Special cases like code tags should be accounted for (we have to deal with them as a single block). We could keep a copy of the quoted post in memory, and compare it with the new post, and thus do some sort of diff on it -- you know, like Wikipedia. And then we quote everything that was inside the earlier post, and only that.
It could be exciting... Because it's something that actually talks to e-mail users. There are a few, I've heard. :whistle:
People don't multi-quote enough. People don't know the pleasure of replying everything line by line.
You know what? Because people use the Quote bbc button and it's so complicated.
Power-quoters like me, and perhaps Pete, do it manually. Quote message... Okay, focus on message, ctrl+end, ctrl+shift+left arrow until I select the entire [/quote], ctrl+c, ctrl+home (I use ctrl a lot, at this point...), go to end of the quote I want to reply to, ctrl+v, enter, enter, type answer... Enter, enter, ctrl+v, right arrow, del (this effectively turns it into an opening quote), go to end of the quote, keep doing it that way...
Now, you can try it if you never did. It works and, well, I don't see a better way of doing it quickly.
...
Until today.
I remembered these freaking' annoying e-mails.
Which were so easy to reply to, because they already were entirely quoted.
> Hello, world.
> Reply to this.
> Just below.
See? It's easy.
> More quotes.
---------------> Now what? Why can't we do that for Wedge?
That's the idea, really.
Quote message.
Show message. Instead of showing it inside a large quote tag, turn it into a post with limited width, add automatic carriage returns, and *add > signs in front of each line*.
Now, the user can reply like on any e-mail they may want to quote...
And then, when they hit the Send button, that's where the magic is supposed to be applied: we turn back this post into a properly quoted post. I don't know exactly how, but we can discuss it. Basically, it's simply about concatenating all lines with a starting ">" into a single quote. Special cases like code tags should be accounted for (we have to deal with them as a single block). We could keep a copy of the quoted post in memory, and compare it with the new post, and thus do some sort of diff on it -- you know, like Wikipedia. And then we quote everything that was inside the earlier post, and only that.
It could be exciting... Because it's something that actually talks to e-mail users. There are a few, I've heard. :whistle: