doubleedesign/comet-file-group
Composer 安装命令:
composer require doubleedesign/comet-file-group
包简介
Standalone package for FileGroup from the Comet Components library
README 文档
README
The standalone versions of FileGroup and File from the Comet Components library.
Installation
Install using Composer:
composer require doubleedesign/comet-file-group
[!INFO] Like many libraries, this isn't 100% standalone - it uses some other libraries. There is one dependency,
doubleedesign/comet-components-launchpad, which contains Comet Components Core's foundational classes and global CSS, and the dependencies for using Blade templates. This is so that if you use multiple standalone packages in your project, you don't end up with unnecessary duplication.
- Ensure your project loads dependencies using the autoloader:
require_once __DIR__ . '/vendor/autoload.php';
- Tell it where to find the Blade templates, as early as possible so the config is there when you attempt to render components:
use Doubleedesign\Comet\Core\Config; Config::set_blade_component_paths([ __DIR__ . '\\vendor\\doubleedesign\\comet-file-group\\src', ]);
- You can also add your own custom paths here to override the provided Blade templates.
- For a WordPress plugin, I place the above code in the root plugin file, right after the autoloader is included.
- If you are adding to a WordPress theme, the
BladeServiceis already configured to look in your active theme for files in acomponentsdirectory in your theme root.
- Load the CSS and JS assets for the component into your project, however you usually do so. You will need:
/vendor/doubleedesign/comet-components-launchpad/src/components/global.css/vendor/doubleedesign/comet-responsive-panels/src/components/file-group.css
An example of how you might set up the client-side assets in a WordPress plugin is:
<?php namespace YourNamespace\PluginName; class Frontend { public function __construct() { add_action('wp_enqueue_scripts', [$this, 'load_frontend_assets']); } public function load_frontend_assets(): void { $depDir = '/wp-content/plugins/simple-document-portal/vendor/doubleedesign/comet-components-launchpad/src'; $rootDir = '/wp-content/plugins/simple-document-portal/vendor/doubleedesign/comet-responsive-panels/src'; wp_enqueue_style('comet-global', $depDir . '/src/components/global.css', [], '0.0.2'); wp_enqueue_style('comet-file-group', $rootDir . '/components/FileGroup/file-group.css', [], '0.0.2'); } }
An example implementation can be seen in the Simple Document Portal plugin.
doubleedesign/comet-file-group 适用场景与选型建议
doubleedesign/comet-file-group 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 53 次下载、GitHub Stars 达 0, 最近一次更新时间为 2025 年 07 月 30 日, 在 PHP 生态内属于活跃度较高的组件。
我们在过去多个企业项目中使用过 doubleedesign/comet-file-group 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 doubleedesign/comet-file-group 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
统计信息
- 总下载量: 53
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 26
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: Unknown
- 更新时间: 2025-07-30