Dependency / relationship between two features?

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
9/22/2010 11:24:51 AM
Gravatar
Total Posts 2

Dependency / relationship between two features?

Hi,

Is there a best practice / advice on this topic for mojoPortal? My specific requirement is around a feature that supports maintaining a database of predefined events with search / browse / structured browse. This feature then supports selecting the predefined event putting a date / time on it and posting to an EventCalendar feature. To follow the principles, as I understand them, of mojoPortal I need for the predefined event feature to "know" the moduleID of the EventCalendar feature and I am wondering what is the best approach for this. Maybe a feature setting? Maybe this is not a good idea at all and the whole thing should be packaged as a single feature?

Thanks in anticipation for any advice,

John

P.S. The EventCalendar in my case extends the existing EventCalendar following the guidelines to separate from the main trunk as excellently described in the documentation and videos. Good job and very clear instructions.

9/23/2010 8:20:36 AM
Gravatar
Total Posts 18439

Re: Dependency / relationship between two features?

Hi John,

My advice is that CMS plugin features are self contained and don't depend on other features nor try to orchestrate other CMS features. A content feature should not know or care about what other features are on the page. 

If you build a custom event calendar then you should build into it the ability to do whatever you need as far as predefined events.

There are sub systems which can be re-used by different features such as content rating, content history, and in the future we will have sub systems for tagging and comments, but I differentiate sub systems which are intended to be re-used across features vs content features which should not have cross talk or dependencies with other content features. Any feature that plugs into the content plugin system is a content feature.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.