Apache Linkis builds a computation middleware layer to facilitate connection, governance and orchestration between the upper applications and the underlying data engines.
element ui我个人觉得好看的,目前用的iview感觉美观度一般,element ui官方有现成的表单组件
陆小龙
建议UI组件iview换一下哈哈 上ts
The current main optimization direction
The file directory is too messy (irregular names/redundant folders), which increases the threshold for open source user participation
The interface style is not uniform, there are many native usages, and there are inconsistencies in the styles of different pages. Consider using an open source framework to unify all styles
For pages that use iframe, whether to consider replacing them with micro-apps
Front-end code specification and some guidelines such as annotations of key logic
The abstraction of public tools/components such as encryption and decryption, unit conversion, etc. need to supplement the corresponding documents
Added function points
Frame selection
Based on the selection of the existing framework, it is necessary to give a comparison reference
Many data tables will have many entries, and the page will only display some key information, such as the historical task page, it is necessary to consider how to conveniently display other unimportant information fields
Is the design style consistent with other modules in the industry? Still give priority to open source components
functionally
Added menu support to be controlled by configuration, and the list of menus returned by the backend interface
Support simple configuration of the relationship between roles and menus
There is a panel indicator page planned to display the graphic panel of task resources
Phase
Main Tasks
Participants
Time
Collection of Refactoring Requirements
Collect some ideas and suggestions from the community and front-end/back-end developers in the industry
Confirmation of selection plan
Output comparison plan
Consider open source situation, mainstream technology
Main work content of workload
Community students can Is it better to get started
Is there any problem with the current compatibility with dss
UI Design
Based on the existing management platform, design a new UI mainly layout and style confirmation of icon gallery
Demo version
Provide a demo version of several pages, preferably covering the main component functions, initial code base and specification documents, departure of public tools/components
Full Refactoring
Full refactoring of the front-end code
Comment collection
Zhou Xin
vue version, whether to switch to vue3
Menu bar permission problem, display and hide the control of the menu returned by the background interface.
At the same time, the structure of the front-end project does not feel necessary to be divided into several parts. unified into one module.
Some components can use existing ui components: such as the left menu bar, etc. There's no need to reimplement it yourself.
Permissions, administrators and commonly used dictionaries and other data need to be returned through a separate interface, and the front end uses vuex for unified management
Is the design style consistent with other modules in the line
Can the page using iframe be replaced by micro-app
Beacon Town
The flexibility of form-create is very poor. There is a bug that I don’t know how to deal with. When I click Add, the named data is passed as empty but there is still data to fill in.
I personally think that element ui is good-looking. The current iview is not as good-looking. Element ui officially has ready-made form components
Lu Xiaolong
It is recommended to change the UI component iview haha on ts
当前主要优化方向
文件目录太乱(名字不规范/冗余文件夹),增加了开源用户参与的门槛
界面风格不统一,有不少比较原生的用法,存在不同页面风格不一致问题,考虑使用开源框架统一全部风格
使用iframe的页面,是否考虑使用微应用替换
国际化适配问题
规范相关
文件目录划分以及命名规范
国际化规范
图标license问题: 确定能使用的图标库,后续优先使用,如google 的icon库 https://marella.me/material-icons/demo/
无关代码的移除
前端代码规范和一些准则 如关键逻辑的注解
公共工具/组件的抽象 如加解密 单位换算等 需要补充对应的文档
新增的功能点
框架选型
功能上
icon图库的确认
初始代码库以及规范文档,
公共工具/组件的筹抽离
意见收集
周鑫
BeaconTown
陆小龙
The current main optimization direction
The file directory is too messy (irregular names/redundant folders), which increases the threshold for open source user participation
The interface style is not uniform, there are many native usages, and there are inconsistencies in the styles of different pages. Consider using an open source framework to unify all styles
For pages that use iframe, whether to consider replacing them with micro-apps
Internationalization adaptation issues
specification related
File directory division and naming convention
Internationalization specification
Icon license problem: Determine the icon library that can be used, and use it first, such as Google's icon library [https://marella.me/material-icons/demo/](https://marella.me/material-icons/ demo/)
Removal of extraneous code
Front-end code specification and some guidelines such as annotations of key logic
The abstraction of public tools/components such as encryption and decryption, unit conversion, etc. need to supplement the corresponding documents
Added function points
Frame selection
functionally
confirmation of icon gallery
initial code base and specification documents,
departure of public tools/components
Comment collection
Zhou Xin
Beacon Town
Lu Xiaolong