象这种需求如何搞二次开发 100分
商城源码shopnc本来挺好的,眉目清楚。但是各模块不能互相调用,这是此程序的一大致命缺陷。
比如,它分几个模块,有微商城、门户、圈子、画册这几个模块,每个模块中的mvc三个部分各自独立,当然它本意这么设计是为了便于快速开发,但发现这同时也是一大致使缺点。因为模块之间假如想互相调用数据就要报错。比如把微商城的搜索表单加在门户中就报错,提示说没有找到数组。
那么问题来了,怎样才能让模块间互相调用彼此的数据呢?
我有一个思路是再写一个 总控制文件,然后让其他的模块都继承它,这时又问题来了,怎么写这个文件呢?
还有就是,我的这个思路对不对
回复讨论(解决方案)
你开列的模块本来就是互不相干的
如果你确实需要一定程度上的数据共享,那么应该书写 API(本来就有吧?)
你开列的模块本来就是互不相干的
如果你确实需要一定程度上的数据共享,那么应该书写 API(本来就有吧?)
是的,shopnc中是有API的,它是做啥的,你的意思是不是说,它本来有这个数据共享功能,可是我试了一下,加了一个变量,打印不出来,比如在A模块中加了一下变量,在B模块中打印,显示不了,如果数据共享,应该能打印出来才对啊
我明白API是做啥用的,它的API搞的很怪,有些模块有,有些没有

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...

Article discusses late static binding (LSB) in PHP, introduced in PHP 5.3, allowing runtime resolution of static method calls for more flexible inheritance.Main issue: LSB vs. traditional polymorphism; LSB's practical applications and potential perfo

Sending JSON data using PHP's cURL library In PHP development, it is often necessary to interact with external APIs. One of the common ways is to use cURL library to send POST�...

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.
