当前位置:首页>PPT>PPT消亡史:AI智能体如何让HTML交互式演示成为主流

PPT消亡史:AI智能体如何让HTML交互式演示成为主流

  • 2026-06-30 10:12:40
PPT消亡史:AI智能体如何让HTML交互式演示成为主流
 
PPT消亡史:AI智能体如何让HTML交互式演示成为主流
 
从静态幻灯片到AI生成的交互式网页
 
导读:你有多久没用过PPT了?不是HTML替代了PPT,也不是AI对话取代了HTML,而是AI智能体让HTML交互式演示的创作门槛降到了零。架构图、流程图、数据图表,一句话就能生成。这才是演示技术的真正变革。
先说个我自己的观察。2020年之前,许多人每周至少要打开PowerPoint两三次。产品汇报、项目提案、培训分享,哪个离得开PPT?但到了2026年,这个数字逐渐变成了零。
取而代之的是什么?HTML交互式页面。能嵌入实时数据、交互式图表、动态流程图的网页。过去这东西技术门槛高,需要懂HTML、CSS、JavaScript。现在呢?AI智能体帮你生成,你只需要说一句话。
这不是HTML被取代,而是HTML的创作方式被彻底改变了。
PPT的问题:静态、线性、单向传递
PPT诞生于1987年。那时候的办公场景是什么样?线下会议、单向汇报、固定流程。演讲者站在投影幕布前,一页页翻着幻灯片,观众坐在下面听,偶尔记笔记。
这种场景下,PPT的"线性播放+静态内容"模式是够用的。但今天呢?
 
数据要实时更新。市场分析报告要显示最新的销售数据,项目提案要根据实时指标动态调整,培训材料要随业务变化自动刷新。PPT能做这些吗?做不到。它只能放静态截图,数据一变就得重做。
 
架构图、流程图要能交互。系统架构需要点击展开细节,业务流程需要高亮关键路径,组织结构需要动态筛选层级。PPT的静态图片做不到,但HTML的SVG+JavaScript可以。
 
团队协作成为刚需。远程办公、混合办公常态化之后,演示稿需要多人实时协作、持续迭代。PPT文件传来传去,版本混乱,v1、v2、final、final_final版,谁也搞不清哪个是最新的。
所以不是PPT做得不好,而是它所服务的场景,已经不存在了。
HTML5:正当红的演示技术
HTML5不是"过去时",它是目前最当红的演示技术。reveal.js、impress.js这些框架,让演示稿变成了网页。跨平台兼容,任何设备只要有浏览器就能打开。非线性导航,观众可以自由跳转。可编程性,能嵌入实时数据、交互组件。版本控制,用Git管理修改历史。
更重要的是,HTML能做PPT做不到的事情。
 
   
交互式架构图
   
点击展开
动态高亮
 
 
   
动态流程图
   
实时数据
动画演示
 
 
   
可筛选图表
   
多维度钻取
即时响应
 
以前的问题是什么?创作门槛高。要写HTML、CSS、JavaScript,不是每个职场人都能胜任。我见过不少同事,想学reveal.js,最后被代码劝退。
现在这个问题被AI智能体解决了。
AI智能体:让HTML创作零门槛
这才是真正的变革。不是HTML被取代,而是AI智能体让HTML的创作门槛降到了零。
举个例子。上周我要给客户做一个系统架构演示。以前的做法是什么?先在PPT里画静态架构图,然后用箭头和标注说明各模块的关系,最后在会议上指着屏幕讲解。客户想看某个模块的细节?抱歉,得另做一页。
现在呢?我对AI说:"生成一个微服务架构图,包含API网关、用户服务、订单服务、支付服务,支持点击展开每个服务的详细接口列表。"
几秒钟后,AI生成了一段HTML代码。我在浏览器里打开,看到一个交互式的架构图。点击"用户服务",右侧展开该服务的所有API接口。点击"订单服务",显示订单处理的完整流程。客户想看哪个模块,自己点开就行。
 
不只是架构图。流程图、时序图、状态机图、组织结构图、数据关系图,统统可以一句话生成。AI理解你的需求,自动选择合适的可视化方式,生成可交互的HTML/SVG代码。你不需要懂技术,只需要知道"我要什么"。
这才是AI智能体的核心价值:不是替代HTML,而是让HTML的创作变得像说话一样简单。
对内 vs 对外:两种演示场景的分化
AI智能体普及之后,演示场景出现了明显的分化。
 
对内协作:AI对话输出就够了
 
飞书、钉钉、企业微信里的AI对话输出,适合团队内部快速同步。我在群里@AI助手,说"帮我分析H1市场表现",AI输出一个结构化的消息,包含数据卡片、趋势图表、核心洞察。团队成员看到后,可以直接评论、提问、迭代。这是高效的内部协作工具。
 
对外演示:HTML交互式页面是首选
 
但对外演示呢?客户会议、公开演讲、产品发布会,这些场景需要的是独立的、专业的、可控的演示页面。你不能让客户打开飞书群聊看你的汇报,也不能让投资人扫码进钉钉会议看你的提案。你需要一个独立的URL,一个专业的界面,一个可以定制的交互体验。
 
关键区别:对内协作要的是"快",对外演示要的是"美"和"专"。AI对话输出满足前者,HTML交互式页面满足后者。两者不是替代关系,而是互补关系。
AI + HTML:演示技术的最佳拍档
回过头看,这个演进路径背后的逻辑很清晰。
PPT的局限在于静态、线性、单向传递。它服务于一个已经消失的场景。
HTML交互式页面的局限在于创作门槛高。但它本身的技术能力是完全没问题的——跨平台、可编程、易协作、易分发。
AI智能体解决的,正是HTML的"门槛"问题。
 
   零门槛创作。自然语言描述需求,AI生成HTML/SVG代码。
   即时迭代。说一句"把架构图改成三层结构",AI自动修改。
   智能优化。AI根据内容自动选择最佳可视化方式。
   多格式输出。HTML交互式页面、PDF静态版本、PNG截图,一键生成。
   跨场景复用。同一份内容,对内用AI对话输出,对外用HTML页面。  
未来的演示工作流会是这样:你用AI生成HTML交互式页面,然后根据场景选择不同的输出方式。团队内部同步?发到飞书群,AI输出对话消息。客户演示?发送独立URL,对方在浏览器里打开。存档备查?一键导出PDF。
PPT的时代结束了,HTML + AI的时代刚开始
我不认为PPT会彻底消失。就像今天依然有人在用纸质笔记本、白板和便签纸一样,工具的选择永远取决于具体场景。但在主流办公场景中,PPT正在被更高效、更智能的形态取代。
演示技术的演进焦点,已经从"工具效率"(如何做得更快更好),转移到"创作智能"(AI辅助甚至主导创作),再到"场景适配"(对内对外,不同场景不同输出)。
这不是HTML被AI取代,而是AI让HTML变得人人可用。架构图、流程图、数据图表,一句话就能生成。这才是演示技术的真正变革。
 
PPT的时代结束了。不是因为它做得不好,而是因为时代已经不需要它了。HTML + AI的时代,才刚刚开始。
The Death of PowerPoint: How AI Agents Made HTML Interactive Presentations Mainstream
 
From Static Slides to AI-Generated Interactive Web Pages
 
Introduction: How long has it been since you last used PowerPoint? It's not that HTML replaced PPT, nor that AI conversations replaced HTML. It's that AI agents have reduced the barrier to creating HTML interactive presentations to zero. Architecture diagrams, flowcharts, data charts—generate them with a single sentence. This is the real transformation in presentation technology.
Let me share a personal observation. Before 2020, I opened PowerPoint at least two or three times a week. Product reports, project proposals, training sessions—none could do without PPT. But by 2026, that number dropped to zero.
What replaced it? HTML interactive pages. Web pages that can embed real-time data, interactive charts, dynamic flowcharts. In the past, this had a high technical barrier—you needed to understand HTML, CSS, JavaScript. Now? AI agents generate it for you. You just need to say one sentence.
This isn't HTML being replaced—this is how HTML is created being completely transformed.
PowerPoint's Problem: Static, Linear, One-Way Transmission
PowerPoint was born in 1987. What did the work environment look like back then? Offline meetings, one-way reporting, fixed processes. A presenter stood in front of a projection screen, flipping through slides one by one, while the audience sat and listened, occasionally taking notes.
In that context, PowerPoint's "linear playback + static content" model was sufficient. But today?
 
Data needs real-time updates. Market analysis reports need to display the latest sales data. Project proposals need to dynamically adjust based on real-time metrics. Training materials need to refresh automatically as business changes. Can PowerPoint do this? No. It can only display static screenshots—when data changes, you have to redo it.
 
Architecture diagrams and flowcharts need to be interactive. System architecture needs click-to-expand details. Business processes need highlighted critical paths. Organizational structures need dynamic level filtering. PowerPoint's static images can't do this, but HTML's SVG+JavaScript can.
 
Team collaboration has become essential. With remote and hybrid work normalized, presentation decks require real-time multi-person collaboration and continuous iteration. PPT files get passed around with version chaos—v1, v2, final, final_final versions where no one knows which is latest.
So it's not that PowerPoint is poorly made—it's that the scenario it served no longer exists.
HTML5: The Presentation Technology That's Currently Thriving
HTML5 isn't a "past tense"—it's currently the hottest presentation technology. Frameworks like reveal.js and impress.js have turned presentation decks into web pages. Cross-platform compatibility—any device with a browser can open them. Non-linear navigation—audiences can jump freely. Programmability—embed real-time data, interactive components. Version control—manage revision history with Git.
More importantly, HTML can do things PowerPoint cannot.
 
   
Interactive Architecture
   
Click to expand
Dynamic highlights
 
 
   
Dynamic Flowcharts
   
Real-time data
Animated demos
 
 
   
Filterable Charts
   
Multi-dimensional drill-down
Instant response
 
What was the problem before? High creation barrier. Writing HTML, CSS, JavaScript—not every professional could handle it. I saw many colleagues excited to learn reveal.js, only to be discouraged by the code.
Now AI agents have solved this problem.
AI Agents: Making HTML Creation Zero-Barrier
This is the real transformation. Not HTML being replaced, but AI agents reducing the barrier to HTML creation to zero.
For example, last week I needed to present a system architecture to a client. The old approach? Draw a static architecture diagram in PowerPoint, use arrows and annotations to explain module relationships, point at the screen during meetings to explain. Client wants to see details of a specific module? Sorry, need to make another slide.
Now? I tell the AI: "Generate a microservices architecture diagram including API Gateway, User Service, Order Service, Payment Service, with click-to-expand detailed interface lists for each service."
Seconds later, AI generates HTML code. I open it in a browser and see an interactive architecture diagram. Click "User Service" and all API interfaces for that service expand on the right. Click "Order Service" to display the complete order processing flow. Clients can explore whichever module interests them.
 
Not just architecture diagrams. Flowcharts, sequence diagrams, state machines, organizational charts, data relationship diagrams—all can be generated with a single sentence. AI understands your needs, automatically selects the appropriate visualization method, and generates interactive HTML/SVG code. You don't need to understand technology—you just need to know "what I want."
This is the core value of AI agents: not replacing HTML, but making HTML creation as simple as speaking.
Internal vs. External: Differentiation of Presentation Scenarios
After AI agents became widespread, presentation scenarios showed clear differentiation.
 
Internal Collaboration: AI Conversational Output Is Enough
 
AI conversational outputs in Feishu, DingTalk, and WeCom are suitable for rapid internal team synchronization. I @ the AI assistant in a group chat and say "Help me analyze H1 market performance"—AI outputs a structured message with data cards, trend charts, and key insights. Team members can comment, ask questions, and iterate directly. This is an efficient internal collaboration tool.
 
External Presentations: HTML Interactive Pages Are Preferred
 
But for external presentations? Client meetings, investor roadshows, public speeches, product launches—these scenarios require independent, professional, controllable presentation pages. You can't have clients open a Feishu group chat to see your report, or have investors scan a QR code to join a DingTalk meeting to see your proposal. You need an independent URL, a professional interface, a customizable interactive experience.
 
Key distinction: Internal collaboration needs "speed"; external presentations need "beauty" and "professionalism." AI conversational output satisfies the former; HTML interactive pages satisfy the latter. They're not replacements—they're complements.
AI + HTML: The Best Partnership in Presentation Technology
Looking back, the logic behind this evolution path is clear.
PowerPoint's limitations lie in being static, linear, and one-way. It served a scenario that has disappeared.
HTML interactive pages' limitation was the high creation barrier. But its technical capabilities are completely fine—cross-platform, programmable, easy to collaborate, easy to distribute.
AI agents solve exactly HTML's "barrier" problem.
 
   Zero-barrier creation. Describe needs in natural language, AI generates HTML/SVG code.
   Instant iteration. Say "change the architecture diagram to three-tier structure" and AI automatically modifies.
   Intelligent optimization. AI automatically selects the best visualization method based on content.
   Multi-format output. HTML interactive pages, PDF static versions, PNG screenshots—one-click generation.
   Cross-scenario reuse. Same content—AI conversational output for internal use, HTML pages for external use.  
The future presentation workflow will be: you use AI to generate HTML interactive pages, then choose different output methods based on scenarios. Internal team sync? Post to Feishu group, AI outputs conversational messages. Client presentation? Send independent URL, they open in browser. Archive for reference? One-click PDF export.
PowerPoint's Era Has Ended; HTML + AI's Era Has Just Begun
I don't think PowerPoint will completely disappear. Just like people still use paper notebooks, whiteboards, and sticky notes today, tool choice always depends on specific scenarios. But in mainstream work scenarios, PowerPoint is being replaced by more efficient, more intelligent forms.
The focus of presentation technology evolution has shifted from "tool efficiency" (how to make things faster and better) to "creation intelligence" (AI-assisted or even AI-led creation) to "scenario adaptation" (internal vs. external, different outputs for different scenarios).
This isn't HTML being replaced by AI—it's AI making HTML accessible to everyone. Architecture diagrams, flowcharts, data charts—generate with a single sentence. This is the real transformation in presentation technology.
 
The era of PowerPoint has ended. Not because it was poorly made, but because the era no longer needs it. The HTML + AI era has just begun.

最新文章

随机文章

基本 文件 流程 错误 SQL 调试
  1. 请求信息 : 2026-07-07 18:36:49 HTTP/2.0 GET : https://h.sjds.net/a/527080.html
  2. 运行时间 : 0.092952s [ 吞吐率:10.76req/s ] 内存消耗:4,328.42kb 文件加载:140
  3. 缓存信息 : 0 reads,0 writes
  4. 会话信息 : SESSION_ID=16620cbfaab93092b6cf6bf388e96a22
  1. /yingpanguazai/ssd/ssd1/www/h.sjds.net/public/index.php ( 0.79 KB )
  2. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/autoload.php ( 0.17 KB )
  3. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/composer/autoload_real.php ( 2.49 KB )
  4. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/composer/platform_check.php ( 0.90 KB )
  5. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/composer/ClassLoader.php ( 14.03 KB )
  6. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/composer/autoload_static.php ( 4.90 KB )
  7. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/helper.php ( 8.34 KB )
  8. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-validate/src/helper.php ( 2.19 KB )
  9. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/helper.php ( 1.47 KB )
  10. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/stubs/load_stubs.php ( 0.16 KB )
  11. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Exception.php ( 1.69 KB )
  12. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-container/src/Facade.php ( 2.71 KB )
  13. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/symfony/deprecation-contracts/function.php ( 0.99 KB )
  14. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/symfony/polyfill-mbstring/bootstrap.php ( 8.26 KB )
  15. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/symfony/polyfill-mbstring/bootstrap80.php ( 9.78 KB )
  16. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/symfony/var-dumper/Resources/functions/dump.php ( 1.49 KB )
  17. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-dumper/src/helper.php ( 0.18 KB )
  18. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/symfony/var-dumper/VarDumper.php ( 4.30 KB )
  19. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/App.php ( 15.30 KB )
  20. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-container/src/Container.php ( 15.76 KB )
  21. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/psr/container/src/ContainerInterface.php ( 1.02 KB )
  22. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/provider.php ( 0.19 KB )
  23. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Http.php ( 6.04 KB )
  24. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/helper/Str.php ( 7.29 KB )
  25. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Env.php ( 4.68 KB )
  26. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/common.php ( 0.03 KB )
  27. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/helper.php ( 18.78 KB )
  28. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Config.php ( 5.54 KB )
  29. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/app.php ( 0.95 KB )
  30. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/cache.php ( 0.78 KB )
  31. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/console.php ( 0.23 KB )
  32. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/cookie.php ( 0.56 KB )
  33. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/database.php ( 2.48 KB )
  34. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/facade/Env.php ( 1.67 KB )
  35. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/filesystem.php ( 0.61 KB )
  36. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/lang.php ( 0.91 KB )
  37. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/log.php ( 1.35 KB )
  38. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/middleware.php ( 0.19 KB )
  39. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/route.php ( 1.89 KB )
  40. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/session.php ( 0.57 KB )
  41. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/trace.php ( 0.34 KB )
  42. /yingpanguazai/ssd/ssd1/www/h.sjds.net/config/view.php ( 0.82 KB )
  43. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/event.php ( 0.25 KB )
  44. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Event.php ( 7.67 KB )
  45. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/service.php ( 0.13 KB )
  46. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/AppService.php ( 0.26 KB )
  47. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Service.php ( 1.64 KB )
  48. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Lang.php ( 7.35 KB )
  49. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/lang/zh-cn.php ( 13.70 KB )
  50. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/initializer/Error.php ( 3.31 KB )
  51. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/initializer/RegisterService.php ( 1.33 KB )
  52. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/services.php ( 0.14 KB )
  53. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/service/PaginatorService.php ( 1.52 KB )
  54. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/service/ValidateService.php ( 0.99 KB )
  55. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/service/ModelService.php ( 2.04 KB )
  56. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-trace/src/Service.php ( 0.77 KB )
  57. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Middleware.php ( 6.72 KB )
  58. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/initializer/BootService.php ( 0.77 KB )
  59. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/Paginator.php ( 11.86 KB )
  60. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-validate/src/Validate.php ( 63.20 KB )
  61. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/Model.php ( 23.55 KB )
  62. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/Attribute.php ( 21.05 KB )
  63. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/AutoWriteData.php ( 4.21 KB )
  64. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/Conversion.php ( 6.44 KB )
  65. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/DbConnect.php ( 5.16 KB )
  66. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/ModelEvent.php ( 2.33 KB )
  67. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/concern/RelationShip.php ( 28.29 KB )
  68. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/contract/Arrayable.php ( 0.09 KB )
  69. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/contract/Jsonable.php ( 0.13 KB )
  70. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/model/contract/Modelable.php ( 0.09 KB )
  71. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Db.php ( 2.88 KB )
  72. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/DbManager.php ( 8.52 KB )
  73. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Log.php ( 6.28 KB )
  74. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Manager.php ( 3.92 KB )
  75. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/psr/log/src/LoggerTrait.php ( 2.69 KB )
  76. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/psr/log/src/LoggerInterface.php ( 2.71 KB )
  77. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Cache.php ( 4.92 KB )
  78. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/psr/simple-cache/src/CacheInterface.php ( 4.71 KB )
  79. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/helper/Arr.php ( 16.63 KB )
  80. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/cache/driver/File.php ( 7.84 KB )
  81. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/cache/Driver.php ( 9.03 KB )
  82. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/contract/CacheHandlerInterface.php ( 1.99 KB )
  83. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/Request.php ( 0.09 KB )
  84. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Request.php ( 55.78 KB )
  85. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/middleware.php ( 0.25 KB )
  86. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Pipeline.php ( 2.61 KB )
  87. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-trace/src/TraceDebug.php ( 3.40 KB )
  88. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/middleware/SessionInit.php ( 1.94 KB )
  89. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Session.php ( 1.80 KB )
  90. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/session/driver/File.php ( 6.27 KB )
  91. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/contract/SessionHandlerInterface.php ( 0.87 KB )
  92. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/session/Store.php ( 7.12 KB )
  93. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Route.php ( 23.73 KB )
  94. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/RuleName.php ( 5.75 KB )
  95. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/Domain.php ( 2.53 KB )
  96. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/RuleGroup.php ( 22.43 KB )
  97. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/Rule.php ( 26.95 KB )
  98. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/RuleItem.php ( 9.78 KB )
  99. /yingpanguazai/ssd/ssd1/www/h.sjds.net/route/app.php ( 1.72 KB )
  100. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/facade/Route.php ( 4.70 KB )
  101. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/dispatch/Controller.php ( 4.74 KB )
  102. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/route/Dispatch.php ( 10.44 KB )
  103. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/controller/Index.php ( 4.81 KB )
  104. /yingpanguazai/ssd/ssd1/www/h.sjds.net/app/BaseController.php ( 2.05 KB )
  105. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/facade/Db.php ( 0.93 KB )
  106. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/connector/Mysql.php ( 5.44 KB )
  107. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/PDOConnection.php ( 52.47 KB )
  108. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/Connection.php ( 8.39 KB )
  109. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/ConnectionInterface.php ( 4.57 KB )
  110. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/builder/Mysql.php ( 16.58 KB )
  111. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/Builder.php ( 24.06 KB )
  112. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/BaseBuilder.php ( 27.50 KB )
  113. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/Query.php ( 15.71 KB )
  114. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/BaseQuery.php ( 45.13 KB )
  115. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/TimeFieldQuery.php ( 7.43 KB )
  116. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/AggregateQuery.php ( 3.26 KB )
  117. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/ModelRelationQuery.php ( 20.07 KB )
  118. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/ParamsBind.php ( 3.66 KB )
  119. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/ResultOperation.php ( 7.01 KB )
  120. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/WhereQuery.php ( 19.37 KB )
  121. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/JoinAndViewQuery.php ( 7.11 KB )
  122. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/TableFieldInfo.php ( 2.63 KB )
  123. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-orm/src/db/concern/Transaction.php ( 2.77 KB )
  124. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/log/driver/File.php ( 5.96 KB )
  125. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/contract/LogHandlerInterface.php ( 0.86 KB )
  126. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/log/Channel.php ( 3.89 KB )
  127. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/event/LogRecord.php ( 1.02 KB )
  128. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-helper/src/Collection.php ( 16.47 KB )
  129. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/facade/View.php ( 1.70 KB )
  130. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/View.php ( 4.39 KB )
  131. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Response.php ( 8.81 KB )
  132. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/response/View.php ( 3.29 KB )
  133. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/Cookie.php ( 6.06 KB )
  134. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-view/src/Think.php ( 8.38 KB )
  135. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/framework/src/think/contract/TemplateHandlerInterface.php ( 1.60 KB )
  136. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-template/src/Template.php ( 46.61 KB )
  137. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-template/src/template/driver/File.php ( 2.41 KB )
  138. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-template/src/template/contract/DriverInterface.php ( 0.86 KB )
  139. /yingpanguazai/ssd/ssd1/www/h.sjds.net/runtime/temp/ad153693ed39fba6d1bda2fe72512cde.php ( 12.06 KB )
  140. /yingpanguazai/ssd/ssd1/www/h.sjds.net/vendor/topthink/think-trace/src/Html.php ( 4.42 KB )
  1. CONNECT:[ UseTime:0.000686s ] mysql:host=127.0.0.1;port=3306;dbname=h_sjds;charset=utf8mb4
  2. SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.000768s ]
  3. SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000331s ]
  4. SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000292s ]
  5. SHOW FULL COLUMNS FROM `set` [ RunTime:0.000478s ]
  6. SELECT * FROM `set` [ RunTime:0.000206s ]
  7. SHOW FULL COLUMNS FROM `article` [ RunTime:0.000658s ]
  8. SELECT * FROM `article` WHERE `id` = 527080 LIMIT 1 [ RunTime:0.000506s ]
  9. UPDATE `article` SET `lasttime` = 1783420609 WHERE `id` = 527080 [ RunTime:0.011809s ]
  10. SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000415s ]
  11. SELECT * FROM `article` WHERE `id` < 527080 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.000559s ]
  12. SELECT * FROM `article` WHERE `id` > 527080 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.002097s ]
  13. SELECT * FROM `article` WHERE `id` < 527080 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.000919s ]
  14. SELECT * FROM `article` WHERE `id` < 527080 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.002386s ]
  15. SELECT * FROM `article` WHERE `id` < 527080 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.002822s ]
0.094578s