1

(8 replies, posted in Programming)

http://svnbook.red-bean.com/nightly/en/index.html Probably in there somewhere tongue

2

(189 replies, posted in Announcements)

paulrobert_a wrote:

Probably a stupid suggestion, but why don't you just rename 1.3 to 2.0 alpha 0 or 1?

Because 2.0 will not be simply a continuation of the 1.3 development.

3

(93 replies, posted in Show off)

xable wrote:

First compression: Removing white space, comments ect.
Second compression: By server.

That doesn't mean it'll be a lot smaller by doing both, if your server compresses files it probably deals with whitespace quite well.

4

(7 replies, posted in FluxBB discussion)

Basically, you shouldn't be including index.php, it outputs full pages. What are you actually trying to do?

5

(8 replies, posted in FluxBB discussion)

Paul is on it, no need to continue with this.

6

(93 replies, posted in Show off)

Is it really worth it xable, css files are generally cached.

Its a new feature in 1.3, it may make 1.4 which will be a direct update from 1.2

8

(189 replies, posted in Announcements)

Fulltext isn't the best for everyone, and only works on mysql (and possibly postgresql).

9

(189 replies, posted in Announcements)

1.3 didn't have fulltext, and neither will 1.4, it may include some of the search indexing improvements in 1.3

10

(8 replies, posted in Test board)

test




test

11

(189 replies, posted in Announcements)

shedrock wrote:

You cannot expect people to jump when you say jump

My point exactly.

12

(189 replies, posted in Announcements)

The exact feature list for 2.0 will be discussed later, we can't say right now simply because we haven't decided.

Smartys is not back, he has just been developing the code for 1.4 by himself and is contributing the code rather than releasing it separately.

Your post is completely out of line, in my opinion, shedrock, I fight for this project every day in this forum, if I am not committed then I don't know who is. Do you not see that the entire point of this decision is to make things run more smoothly in future? As for setting dates for release, it simply does not work, we can't guarantee our time, setting dates just causes disappointment when we miss them, which is what we have seen already. What we are opting for is a much more structured roadmap which makes our aims clear and achievable.

13

(189 replies, posted in Announcements)

We've had problems with the extension system for a long time, the problem is we had no easy way to fix it, and a release was always just about to happen, obviously when we forked to create FluxBB we didn't want to just start again, even though that may have been the best thing to do.

The problem is it was planned to allow admins to add a couple of features, and became a system to add any feature, which is very messy with the way we have markup and code mixed together.

14

(26 replies, posted in FluxBB discussion)

Also, just to note, we will let you know when the site is ready to translate, it currently isn't but we're working on it.

15

(26 replies, posted in FluxBB discussion)

I wasn't telling you what was best, I have no idea.

16

(26 replies, posted in FluxBB discussion)

zh and zh-tw? I'm not sure whats the correct ones to use.

17

(54 replies, posted in General discussion)

http://upload.wikimedia.org/wikipedia/c … ht_HDR.jpg slightly different version.

18

(189 replies, posted in Announcements)

dstroma, I realise it seems like this, but the truth is we haven't been happy with 1.3 for quite a long time, and it seemed ridiculous to keep waiting for the final CSS/Markup when this wasn't going to fix our underlying issues with the code.

Say we did get the final CSS and markup today, we'd probably be a month away from a final release, which we wouldn't be happy with, at that point we either choose to live with it for a few years (probably at the cost of losing some of our best people), or try to replace 1.3 almost straight away. We know as soon as we start developing the next version the previous one will be largely ignored by the community (look at mods for 1.2). So we think in a couple of years time this decision will have been for the best.

19

(2 replies, posted in FluxBB discussion)

We did plan to start accepting donations once we had made a major release, we haven't discussed this recently though.

20

(189 replies, posted in Announcements)

There aren't new developers for 1.4, Smartys is doing the majority of the work, and you can see the people who have joined the FluxBB Team here its up to them what they work on, some have expressed interest in 2.0 but I'm sure enough people will be contributing to 1.4 to keep it going.

21

(221 replies, posted in FluxBB discussion)

1.4 will be out very soon though, so you can go from 1.3 to that.

22

(9 replies, posted in FluxBB discussion)

Probably not, it would require every link in every file changing.

23

(189 replies, posted in Announcements)

Jérémie wrote:

Aside for the fact you're giving up on people who have been waiting for 3 years or so (most of them who didn't gave up on you, didn't attack you, and several of them trusting you with the fork), here's an idea: choose someone else on the core team as a spokesperson. Verbally assaulting users and contributors won't get the job done.

It wasn't meant to be a verbal assault. The fact is, people on this forum continually complain that PunBB is better, if they feel that is the case, they should use PunBB.

We have also not given up on anyone, we are continuing to develop this project in the way we think is best, this is NOT giving up. Giving up would be releasing 1.3 in a mess and spending the next few years attempting to patch it up badly.

I also want to point out, we are not dropping 1.3 because we don't have the CSS styling, please stop saying that.

---

To the people who have made supportive posts, thank you, it is much appreciated.

24

(189 replies, posted in Announcements)

Go use PunBB then, we can't please everyone, we're doing what we think is best, we gave opportunity for discussion, we took comments on board, if you don't like what we're doing, use different software.

25

(189 replies, posted in Announcements)

KeyDog, you miss the point completely, 1.3 is a bit of a mess, the extension system was taken much further than it was originally designed, and the markup needs to be in a template system. We no longer want to release 1.3, we don't think its the best idea for the future, its not a case of we need to iron out the bugs, we feel it is fundamentally flawed, and instead of trying to patch it up, we should fix it properly.

I hope that clarifies it a bit.