No idea. I doubt they’d announce features before they’re ready – that’s a fairly stupid strategy for software. Check out trac if you want to see what’s being worked on and download the latest SVN releases if you want it early (and potentially buggy).
I hope development team had a look on this thread:
and on this:
I know that you are frustrated cool2sv because WP and bbPress both use different AJAX, but it really only matters when you are doing what you are trying to do with running them both at the same time. Most users won’t be affected by this same problem you are having.
I am not saying what the developers of bbPress has done is 100% the right direction with AJAX in the core, but it was designed to be standalone and work that way. The WP integration was with logins and not developed to have them sharing libs. I have passed this on to mdawaffe, but the redesign of bbPress and its use of AJAX in the core most likely won’t be the #1 priority. WP uses AJAX in the core and so does bbPress. So which one should be blame? Automattic developers like AJAX in the core!
**Edit** As well, you could sent your request into the bbDevList as well. Just head over to the about page for the address!
I also think people should realize that bbPress isn’t dsigned to be a plugin for WP in any way and the developers should keep in mind to not develop too much towards this too.
It’s a standalone forum, fast and light and should stay this way
Of, thank you guys for reply…
I’m sorry, maybe I did not explained myself clearly:
I appreciate the thing that developers like the accessibility given by ajax, and are using this in their application, but the point was to leave the core functions that are for displaying content (like wp_list_pages(); for example in wordpress) outside of ajax.
You’re right wordpress uses ajax in the core but the templating part and the content is not affected at all (only the admin CP). This way we have ajax but only where it is really necessary.
Sorry for bugging, I do understand that my problem is not the #1 priority of the project team but I was thinking maybe there is any solution, thats why I reported that. Sorry …
Maybe the problem was in the marketing. bbPress was from the start advertised as perfectly compatible and easy to be integrated with WordPress. That is a great advantage, because WordPress is already one of the most usable publishing platform on the web, and people like everything that comes with it – as a result they took bbPress as an another plugin for giant. =]
It’d be better as a plugin for WordPress, with the obvious option not to activate it, and the opportunity to deactivate it without affecting the function of WordPress.
It’d share all the benefits of WP too.
Although bbpress does not want to become a bloated forum software, it would always evolve to enable capabilities to be added via plugins. As and when requests come in for features, it would be evaluated on the basis of whether it needs to be in a core or as a plugin – and if it needs to be a plugin, hooks will be provided for plugin developers to built *any* feature.
As this issue is a concern for the users of bbPress here and forward, I created the ticket.
- You must be logged in to reply to this topic.