Sheratan
Well-known member
And a widget framework.An official portal addon is enough for me. No need to use cms. A simple, easy costumized, lightweight.
And a widget framework.An official portal addon is enough for me. No need to use cms. A simple, easy costumized, lightweight.
But then, i don't know any company that's into business that doesn't want to expand...
All i'm saying is that right now, when somebody want to create a website with forums and maybe some gallery and blogs in the future, to make his business/website feature richer he will say
Xenforo:
✔ Has decent forum system
✘ No Gallery
✘ No CMS for front page and other pages,
✘ No Blogs
Competitor:
✔ Good forum system, not better than xenforo
✔ Gallery
✔ CMS that can help me customize my website with front pages and other pages
✔ Blogs
Though, IF XenForo had more addons, things would have been way more different...
I have to agree with this - a suite is vital now to XF and the CMS should be top of the list under forum development; adding a CMS to XF would open up so many doors to expand sites and make them more interesting, diverse and immersive. Forums on their own are fighting an uphill battle against the more usual places that people visit for Social Interactivity, so forums need something 'extra' to help combat this decline and exodus. It's not an easy task and it's not something I would suggest lightly, but there is a need for diversity. Whilst 3rd party developers are capable of delivering these 'extras' there is no guarantee that they will continue to do so - and no guarantee that they will implement upgrades in a timely manner when XF moves to v.2 which could leave site owners in a predicament.
Fully supported first level apps are a must as they instil confidence in the overall product and they would, essentially, be an investment that could leverage sales for XF and more activity on owners sites.
Yes of course it would be separate...If a CMS happens, I think it should be separate like the RM. That way the core forum software is still flexible.
Would love to see integrated blogs and gallery, too. XF 1.4 does a great job of pushing Profiles into active social media pages, but users still do not have photos or videos to associate with their profile.
I agree with thatThere are a couple different galleries already available, each integrated into XF near perfectly (I only add "near" for staying safe purposes). Why wouldn't you install one of those two?
Because an official app from XF would be safer than an addon where the addon developer can disappear.There are a couple different galleries already available, each integrated into XF near perfectly (I only add "near" for staying safe purposes). Why wouldn't you install one of those two?
Products like a CMS and Gallery would be able to piggy back off of already existing functionality (e.g. text editor, likes, content, comments, etc). It really shouldn't be that difficult to release updates in a timely manner. Especially if the XenForo architecture is as good as we all bragged about in the beginning.And an official app from XF takes away from the development of the software itself. Exactly how stretched do you want updates to XF, ES and RM... add in another product or two, and 2 people are doing quite a bit.
Products like a CMS and Gallery would be able to piggy back off of already existing functionality (e.g. text editor, likes, content, comments, etc). It really shouldn't be that difficult to release updates in a timely manner. Especially if the XenForo architecture is as good as we all bragged about in the beginning.
I'm not saying that up front it wouldn't be a lot of work, I'm saying once it's already established it shouldn't be difficult to update.Just because a lot of the functionality already exists doesn't mean it's not still a lot of work. Just talk to @Chris D .
That, to me, says it could have been architected a lot better. In one of the enterprise applications I work on, we have a comments system that can be plugged into anything. All I have to do is add a new content type and it uses the same CommentService class. They share the same table, because why would you want a bunch of xenforo_xxxx_comment tables, for example?Plus comments aren't actually an existing functionality, they don't have their own handlers and stuff; to make comments for another thing (for a lack of a better word), you have to make a new table and make the datawriters and everything just like they don't already exist in other places.
I'm not sure exactly what they're doing for 2.0 - I think I remember at one point in the beginning them talking about the use of Zend Framework was just to get the product out more quickly. It would be interesting to see how far from the current architecture that move away from.The architecture is as good as we all said, however v2 is a recode and we don't know anything about it. In theory, it should be just as good but in theory it could also be horrible (I obviously doubt it but the point is we don't know).
Yeah this issue is the time up front. Maintaining isn't the problem. It's all the man hours that have to go into it first.I'm not saying that up front it wouldn't be a lot of work, I'm saying once it's already established it shouldn't be difficult to update.
I agree. I've mentioned before in a few posts that this is a design flaw which really erks me. In the grand scheme, it's a relatively small issue though so all in all I still call it a solid architechure.That, to me, says it could have been architected a lot better. In one of the enterprise applications I work on, we have a comments system that can be plugged into anything. All I have to do is add a new content type and it uses the same CommentService class. They share the same table, because why would you want a bunch of xenforo_xxxx_comment tables, for example?
We all just have to wait and see. :|I'm not sure exactly what they're doing for 2.0 - I think I remember at one point in the beginning them talking about the use of Zend Framework was just to get the product out more quickly. It would be interesting to see how far from the current architecture that move away from.
We use essential cookies to make this site work, and optional cookies to enhance your experience.