Note!
Where we are it is now the weekend; so there might be a slight delay in our reply. Thanks for understanding!
JomSocial 2.6 compatibility?
-
Hey guys,
I see JS 2.6 is released as stable. Most other companies are saying they can support it within 30 days. Unfortunately JS is on a 6-month release cycle now so they are hard to keep up with. :-(
The most important feature of JS 2.6 that I am curious about integration with is the notifications system. Do you guys have any plans for EB & ED to somehow integrate? Ideally my users would have a single notifications system to worry about.
Additionally, JomSocial 2.6 combines e-mail and live notification settings in to a single page (nice). I don't know if they have an API to add items to this page but it would be wicked cool if EB + ED could incorporate the subscription features with JS so users had a single page for all of it. I am curious to know how well browsers will support this as most of them (and most web servers) limit the query/post strings length. With that in mind I would think adding a "global" option from JS would work. (EG: "Get notifications from EasyBlog" and "Get notifications from ED"). Then end-users would have a global option and could click a link to get details on EB/ED subscriptions and such.
Dean
Subscribed Products:
5 responses Add a reply
-
-
Hi Mark!
Great feedback. Perhaps the points/notifications integrations would be better as a plugin instead of as a main part of the component? It would slim the component code and the back-end control panel up a lot. Tho I must admit, I am a huge fan of having it all in the same place.
I am just trying to think outside the component so that as much work can be shared across products. It occurs to me that a single plugin could handle all integrations with others (EB + ED to JomSocial for example or EB+ED to AlphaUserPoints).
Dean
Subscribed Products: -
Hello Dean,
Unfortunately that code needs to be within the component itself unless we create unnecessary triggers that get's triggered when "certain xxx action" is performed. Yep, if you look at the long run, this would help minimize the code but this also means that the site admin would then need to manage / update many different types of extensions and plugin
Perhaps this could be much easier if you have some technical background like yourself but, in general I am not too sure if others would prefer it this way (Of course, without trying this, we wouldn't know)
-
Yeah I agree with all of your points. The idea would be that the component would check for plugins that add hooks or features to its classes. Then offer the control panels inside the component for that plugins features. Naturally the plugins would have to provide a control-panel to load... I see JoomAce did something like this using light-box pop-ups for extension options (gets around the query string length). But they also wrote their own plugin model.
Subscribed Products: -
I'll see what we can do in the future to centralize these 
Your Response
Please login to reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
