You are not logged in.
- Topics: Active | Unanswered
#1 Re: Core development » spam » 2010-05-06 08:35:10
- Rich Pedley
good to see 
#2 Re: Feature requests » Anti Spam in core » 2010-05-06 08:34:13
- Rich Pedley
note on CAPTCHA - besides being difficult for some users to understand - the majority have already been broken.
#3 Re: Core development » Spam blocking idea » 2009-09-15 07:39:35
- Rich Pedley
hmmm similar to something already in one of my extensions - user settable as to how many reports there is before the content of the post is hidden for review.
#4 Re: Announcements » FluxBB 1.3-legacy released » 2009-04-24 20:55:38
- Rich Pedley
Changes in the code? Its not really needed for 1.3 as you can overwrite the core files (not config obviously) without a problem.
#5 Re: Core development » 2.0 - Plans and suggestions » 2009-04-04 15:29:22
- Rich Pedley
Ahh - but I can see how what you posted could be changed to make it more flexible, but probably not as easy to template... erm.
#6 Re: Core development » 2.0 - Plans and suggestions » 2009-04-04 08:46:33
- Rich Pedley
Well using the example, as given, how would extensions add anything in? It would require template changes each and every time - which isn't good. Though I can see where/how that could be changed.
#7 Re: Core development » 2.0 - Plans and suggestions » 2009-04-03 18:16:32
- Rich Pedley
erm, design by committee?
If correctly done then go for just the one style/layout. By correctly I mean make it possible for someone to extend it to allow multiples. therefore both are then covered. It also helps keep the forum mean and lean 
I still haven't grasped what the template system will be, so I won't be saying that much on that side of things.
#8 Re: Core development » 2.0 - Plans and suggestions » 2009-04-03 15:07:48
- Rich Pedley
agree with SQLite -twas a PITA to manage even on a good server.
agree with dropping IE6 as by the time 2 is released it'll be quite old. - however that is just a style issue and fixes can probably be done to make it work anyway.
agree with dropping php4 support, by the time 2 is released I think there will be a better percentage of people using php5.
#9 Re: FluxBB discussion » fluxbb should make layouts change,maybe? » 2009-03-10 21:57:24
- Rich Pedley
Hum, do you have statistical inputs?
Statistics mean diddly squat. I speak from experience, 10 + years of it. Plus take a look at the majority of the forums out there and by default they have a left/right hand column for user data.
As I said before:
Qie - feel free to write a theme/style that does what you want. When its finished I know a few people that would be interested in seeing it.
I already state that I know of people that would like to see it.
#10 Re: FluxBB discussion » user experience: " write --> Tab --> Enter" » 2009-03-10 11:43:28
- Rich Pedley
No. For many reasons.
1. users expect a submit button to follow all form entry fields
2. accessibility - (eg. not everyone uses a mouse)
3. some people still use text only browsers (it may not be many but there are some)
So for the core it shouldn't be in - as I have said before it is best left to an extension.
#11 Re: FluxBB discussion » user experience: " write --> Tab --> Enter" » 2009-03-10 10:55:30
- Rich Pedley
Can be - but shouldn't. But then again I personally don't think tabindex should be used at all - ever.
#12 Re: FluxBB discussion » fluxbb should make layouts change,maybe? » 2009-03-10 09:22:04
- Rich Pedley
Qie - feel free to write a theme/style that does what you want. When its finished I know a few people that would be interested in seeing it.
But I personally prefer what we have atm, and so do a lot of users - especially those that add things into the profile area.
#13 Re: FluxBB discussion » user experience: " write --> Tab --> Enter" » 2009-03-10 09:19:54
- Rich Pedley
Write an extension that changes it. The tab order through a form should be logical and therefore in order. So I don't think you'll find it changed in the core.
But also the quick reply form does have write - tab - enter...
Your comment about the Submit and Preview are interesting - in theory the Preview should come before the Submit as that would be more logical - but that would mean an extra tab to submit a post.
#14 Core development » 1.3 Legacy » 2009-03-02 12:06:36
- Rich Pedley
- Replies: 0
Is this now all done? or are there things that haven't been added to trac?
I'm thinking of tidying up and releasing all my extensions for 1.3 now that the majority of work has been completed. The few I have released will be updated as some of the features will no longer be needed.
#15 Re: Core development » Any plans? » 2009-02-24 20:10:47
- Rich Pedley
1. agreed that it needs updating
2. for 1.3? what is left to do?
I've been quiet because I've been working on 2 big projects my eShop plugin for WordPress and a membership system for a convention. Hopefully both should be cleared within a week or so. (well eShop is never - ever - finished). So I haven't been able to donate the time as much as I'd like.
#16 Re: Announcements » The future of FluxBB » 2009-02-24 16:38:26
- Rich Pedley
I think this thread should be closed *sigh*
#17 Re: General discussion » hows everyone? » 2009-02-17 22:17:39
- Rich Pedley
I've got busy with my wordpress plugin. Plus urgent convention membership system needed doing yesterday - which is of course when I got the information... Will probably take 2 weeks - hopefully less.
#18 Re: Feature requests » Including faster options in Fluxbb 2.0 » 2009-02-08 19:11:52
- Rich Pedley
For Example Quick Quote. i see no reason for it to not be in core. i mean wouldn't it be (FASTER) if you did a quick quote using javascript or something else rather then clicking on quote and reopening another page.
I hate quick quote, so it had better be implemented correctly. Which as has been proved elsewhere is unlikely. It would also mean that the quick reply box would need to be resizeable - to cope with replying to larger posts.
1- May be it slows pages because it loads extra javascript code. (loading another page must be faster i guess
)
2- You people might think that some browsers don't allow javascript. it must be 1% of browsers. (you want to work with every thing. then what about if a person use I.E5, even if it doesn't support javascript, you can make an alternate option by making him to open page the original way. )
3- does this some how increase server load.
accessibility - but if it defaults to the standard quote/reply then it isn't a problem. However javascript only links should really be added via the DOM.
Personally I think it should stay where it belongs, as an extension.
#19 Re: Feature requests » More topic possibilities » 2009-02-07 14:11:38
- Rich Pedley
hmm, in that case I'd suggest it isn't in the core and is more practical for an extension.
#20 Re: Feature requests » More topic possibilities » 2009-02-07 10:19:20
- Rich Pedley
how does a print this page link help with that?
#21 Re: Programming » Looking for a text editor » 2009-02-07 10:18:20
- Rich Pedley
I use Textpad
#22 Re: Feature requests » More topic possibilities » 2009-02-06 16:04:22
- Rich Pedley
No, but doesn't the browser use it automatically for printing if it is specified?
99 times out of a hundred - yes
I see no need for a 'print this page' link at all, on any page.
#23 Re: Feature requests » More topic possibilities » 2009-02-06 15:31:39
- Rich Pedley
I'm pretty sure print topic was intended to be in the code since there's a print.css file in the style folder. I doubt it would be in the 1.3 legacy though.
As for PDF, doesn't it require a PHP plugin?
erm having a print.css doesn't mean anything of the sort.
#24 Re: General discussion » PHPBB website has been hacked » 2009-02-06 11:30:10
- Rich Pedley
'Wonderful functionality' is dependant upon your viewpoint. I think S.E.F URL's are a bastardisation, personally.
There is no need for them, especially on a forum!
#25 Re: General discussion » PHPBB website has been hacked » 2009-02-05 19:32:14
- Rich Pedley
Maybe, but I wouldn't use it again, ever - not even after hell has frozen over and the devil has been skating.