cdub
Well-known member
I guess I meant to reply to someone else.I don't mind you quoting my post but hopefully your response would relate to the full context of my point.
I guess I meant to reply to someone else.I don't mind you quoting my post but hopefully your response would relate to the full context of my point.
I can see why the api wasn't part of the plan for 2.0 because they said they are aiming for feature parity with 1.5. It makes sense that they would lay the groundwork now and add it in a future release. I am sure they will add an api, else they would not have laid the groundwork. It's just a matter of when.
The screenshots look nice so far. I did think the line behind the button was a bug – but it doesn't matter since I wouldn't use the default theme no matter what it looks like. I still look forward to seeing the new theme on this site and the others that will use it.
I'm relieved that the option to add a default icon image was restored. We just held a contest to design our default avatar, and it would be disappointing to switch to letters after that.
Overall I'm excited to see the new direction, and I look forward to more details and screenshots leading up to the public beta.
I agree with this sentence. if you are planning to add API in XF2, then it should be added in XF2.0.0 not after to avoid the double work for the developers.An API must be released with a major version , not minor version upgrade.
Frankly, this is just incorrect.All websites/developers will invest crazy amount of money/time on upgrading to XF 2 just to find out that XF 2.2 may feature an API which will basically require you to do most of the work again.
Frankly, this is just incorrect.
The API people are referring to would be a REST (or similar) API. This primarily benefits 2 groups:
It doesn't explicitly benefit anyone writing a XenForo add-on. An API doesn't deal with templates, routes, new entities and all the other work that you need to do. Even if you did choose to use the REST API internally for an add-on, you're likely going to have various work outside the API to add those bits you need. Nevermind that you actually lose access to a lot of the dynamic support you have by working with the entities directly. There are certainly areas where having the API may make more work for add-on developers (mostly as it potentially becomes something they "should" support/integrate with).
- Integration into other parts of your site (such as WordPress or other custom work)
- Alternative views of the forum (often brought up in the context of mobile apps)
Clearly it does benefit the external usage (otherwise we wouldn't be considering it for a future release), but it doesn't mean that any group suddenly needs to redo their entire system when it becomes available. If you wanted to convert to it, then that would take effort, but you may even find that the particular thing you're trying to do isn't exposed by the API by default (because if we're talking about an API that works for semi-public usage, there will certainly be constraints on what is exposed and how it's exposed).
Just because X feature you require/need/want to see isn't added there shouldn't be other, minor improvements?An API is 1000 times more critical than that Avatar function that didn't exist in XF 1 series.
Your assertions are basically wrong. There are benefits to an API but it isn't going to fundamentally hinder people from extending XF 2.0 nor would a later introduction of an API affect that.I am sorry Mike but this is an excuse nothing more.
This is a major release , with this major release we are going to invest a lot of time , money and work on the upgrade. Therefor we all deserve the right to correctly plan , develop correctly from day 1. If you do release the API with a sub release , none of us can do this correctly.
This is simple thing , you first make your base perfect and let rest build on it.
I am sorry Mike but this is an excuse nothing more.
This is a major release , with this major release we are going to invest a lot of time , money and work on the upgrade. Therefor we all deserve the right to correctly plan , develop correctly from day 1. If you do release the API with a sub release , none of us can do this correctly.
This is simple thing , you first make your base perfect and let rest build on it.
I think there's two pretty good addons for that. Depending on the XF2 release date, I'd probably wait it out to make sure they work on XF2.What about groups? Like where members can create and join etc ..
Yeah, but I think it should be part of it. As a community forum software it should have that type of functionality already. But, it's not a crisis, I'm just looking forward to 2.0I think there's two pretty good addons for that. Depending on the XF2 release date, I'd probably wait it out to make sure they work on XF2.
What I said about it perhaps being laid out in a minor version was speculation. Maybe the whole XF2 API idea circulated the same way, and everyone believed that to be coming when the developers themselves didn't say anything about it being on the table to begin with.All websites/developers will invest crazy amount of money/time on upgrading to XF 2 just to find out that XF 2.2 may feature an API which will basically require you to do most of the work again.
We use essential cookies to make this site work, and optional cookies to enhance your experience.