Take the first page slide as an example, the home slide is implemented in the plugin Nop.Plugin.Widgets.NivoSlider
- Home View Location
- This is actually the load plug-in inside the view content, specifically implemented in the plug-in implementation
- This is the extension method, that is, the execution of Nop.web under the Widgetcontroller controller inside the sub-action Widgetsbyzone
This widgetbyzone is to find the currently used @html.widget ("xxx") and return the corresponding controller name, method name and route value
- Widget Controller Location
Loadactivewidgetsbywidgetzone This method is to load the active @html.widget ("xxx") method, implementation can be found in the corresponding implementation class, note that its return object is the Iwidgetplugin interface
- This method according to the parameter name is known through the @html.widget ("XXX") inside the XXX as a parameter to find the implementation of @html.widget ("xxx") this plug-in, specifically implemented in the method has
This is the Iwidgetservice implementation class, here the 3 method followed by the fuzzy query, so will be based on the page has @html.widget ("xxx") xxx to find the specific implementation of the plugin
- Implementing the specific location of the class
- Load the active @html.widget ("xxx") Implementation method
- This method is defined in the plug-in, it is defined in the Iwidgetplugin interface, all the need to implement @html.widget ("XXX") must implement the interface
1. Location of the slide plug-in
2. Implementing the Iwidgetplugin Interface
3. Implement the Getwidgetzones method under the Iwidgetplugin interface and the implementation class under the Iwidgetservice interface is called implementation
--Fish head tail
This is my @html.widget in NOP ("xxx") understanding, personal humble opinion, also hope you crossing many forgive. Any other details can be asked in the group or private chat with me, I will help. (Group No.: 75272942)
Personal contact qq:875755898
Note:
I developed a scan code login, Sina Weibo login and other external licensing plug-ins, scan code (Mode II) payment, UnionPay online payment of payment plug-in, (can be online test preview)
Due to the need to sell plug-ins and provide plug-in follow-up service, update (dependent on NOP version) and technical guidance (buy plugin)
External authorization plug-in: As long as it is based on the Oauth2.0 licensing agreement can be developed, development needs to provide customers with relevant information (such as the merchant number, key, etc. for the authorization of the information needed to be used, and committed to the confidentiality of the customer's information).
Plug-in price: private chat details.
The plug-in version supports 3.1 and above 3.1 versions, followed by a NOP version update.
Follow up I will as far as possible out a set of plug-in video development tutorials, time conditions ample words.
The person who buys the plugin will respect my personal intellectual property rights.
Thank you!!!
Description of NOP @html.widget ("Home_page_top")