It's about improving developer productivity generally.
Looking at the code snippets it looks like a lot of addons are going to require essentially a full rewrite to update to XF2; a mammoth task for the bigger addons I'm sure.
Just out of curiosity; is there any backward compatibility code that may allow an XF1.x structured/syntax addon to be ran on XF2 so that some, more basic, addons may remain operable (but using deprecated code) whilst a developer finds the time to rewrite? I imagine not but it's worth asking.
It doesn't have to be a negative thing. It's certainly going to be a considerable chunk of time to get things up to date. Of course we're in the same boat with RM 2.0 and MG 2.0. Also, in many ways, porting over big projects you've already written is the perfect way of learning the new framework.This was my initial thought as well. I have written some mammoth addons for a variety of sites. My payment addon is several thousand lines of code.
Having said that, I actually like the idea of doing a full rewrite. As a developer, and I think I am not the only, I always think of how I would do many things differently if I was starting over. I guess XF 2.0 is a chance for all of us to start over.
We don't know what form the alpha/beta process will take, yet. Certainly there will be some form of preview, just as there is with normal second point releases. We haven't yet decided how this process will differ with XF2.0.Are you going to grant access to an early alpha or kinda like that for add-on developpers ?
This debate has been had elsewhere. I think it would be unfair to only allow this to some people and not others. Just because some developers have released add-ons on here doesn't mean that's all the developers there are - there are those who develop only for their own communities and they would also need the same access for their add-ons. There may also be budding add-on developers too.Are you going to grant access to an early alpha or kinda like that for add-on developpers ?
And it will be so much fun too!Also, in many ways, porting over big projects you've already written is the perfect way of learning the new framework.
I can say on my part, if I were included I'd start converting add-ons to 2.0, but I most likely would not release them until 2.0 was out of beta. I've been burned by supporting beta versions before (not XF).We don't know what form the alpha/beta process will take, yet. Certainly there will be some form of preview, just as there is with normal second point releases. We haven't yet decided how this process will differ with XF2.0
Any 'Alpha' test is always closed to X number of people. It has to be that way to maintain control.This debate has been had elsewhere. I think it would be unfair to only allow this to some people and not others. Just because some developers have released add-ons on here doesn't mean that's all the developers there are - there are those who develop only for their own communities and they would also need the same access for their add-ons. There may also be budding add-on developers too.
Any 'Alpha' test is always closed to X number of people.
On a serious note, having been in the position myself of having to learn XF 2.0 from new when I joined the team, it actually was funAnd it will be so much fun too!
You're just weirdit actually was fun
I don't think he means the actual rewrite is fun but learning new ways of doing stuff is fun. For me, there are "fun" tasks and there are tasks that seem to drag on. Generally, anything that involves learning falls into the fun category. The process of porting my first add-on to XenForo 2 will likely be 'fun', the process of porting the other couple dozen will likely not be fun lol.When I think about how many tens of thousands of lines of code I may have to rewrite, fun isn't the word which springs to mind.
You really think it would be all that bad? I don't.When I think about how many tens of thousands of lines of code I may have to rewrite, fun isn't the word which springs to mind.
Oh, like my entire Essentials series (granted, they don't 'only' modify/expand but yeah...)... Yay me. lolThe add-ons that may have problems are the ones that don't do things on their own (totally add functionality) and only modify or expand existing functions. I have a few in that category myself.
The add-ons that may have problems are the ones that don't do things on their own (totally add functionality) and only modify or expand existing functions. I have a few in that category myself.
In case it wasn't really clear from Mike's code example, this is somewhat a thing of the past.Specifically what I worry about are all the addons which add joins and selectfields to existing queries, then rely on the data being available.
By design. Xenforo LTD hasn't informed customers about almost anything regarding the future.Nobody has any idea
Probably MCA...........K... on behalf of KAMC (CMAK? KMAC?)
Sure.but sometimes patience is a virtue.
edited.You've let the XF developers take you this far, you've seen their 2010 vision - just get on board and have a little blind, uninformed faith.
The perpetual problem of forums.We probably need to look at consolidating that information to somewhere so that it is easy to find.
I'm not sure getting a snippet of 1% of the plans enables people to plan for the future.They're posting about what they are doing.
I'm baffled Daniel had time to count my periods but not deliver the addon I helped crowdfund.I'm baffled
It is by almost every measure of a forum."XF1 is the best forum ever created"
We use essential cookies to make this site work, and optional cookies to enhance your experience.