Styling of axpen libraries should be confined into a single dependency #891
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced a new tailwind.css file to define custom styles. - Added styles for various badge types: primary, success, warning, danger, and info. - Created action button styles with hover effects and active states. - Implemented shadow glow effects for different color themes. - Configured dark theme support for border colors and animations.
Added the `AXOpen.Operon.Blazor` project to the solution files (`AXOpen.sln` and `AXOpen.solution.sln`) under the new `styling` folder. Updated build configurations and project dependencies accordingly. Refactored `axopen_core_blazor.csproj` and `axopen_data_blazor.csproj` by adding necessary project references and removing unused `<None>` item groups and redundant `<PropertyGroup>` entries. Performed general cleanup and restructuring of the solution, including the addition of `src` and `styling` folders, and removal of redundant project references to improve maintainability.
… AXOpen styling documentation
Reordered build steps to improve efficiency: - Added `DotNetBuildSettings.NoRestore` to skip redundant restores. - Introduced explicit `DotNetRestore` for `AXOpen.proj`. - Moved `BuildTailwindCss` to occur after dependency restoration. Enhanced maintainability: - Suppressed numerous compiler and system warnings to reduce build noise. - Added conditional logic to control apax traversal creation based on build parameters. Minor formatting improvements for readability.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Technical Summary
This Pull Request implements a major architectural shift in how styling is handled across the AXOpen framework, moving towards a centralized, dependency-based approach using Tailwind CSS.
Centralized Styling Architecture
New Styling Project: A new project styling has been introduced to serve as the single source of truth for styles.
Tailwind CSS Integration: The framework now utilizes Tailwind CSS. This is evidenced by the addition of tailwind.css files, tailwind.config.js (implied), and build scripts (tailwind-build.ps1, tailwind-watch.ps1) within the new styling project.
Component Updates: Multiple existing Blazor components (e.g., components.abb.robotics, components.drives, etc.) now include tailwind.ps1 scripts and tailwind.css assets, indicating they consume this new centralized styling configuration.
Build System Enhancements
Node.js Provisioning: The BuildContext.cs (Cake build script) has been updated with a ProvisionNodeJs method.
It automatically detects if Node.js is installed.
If missing, it attempts to install it via winget or Chocolatey on Windows, and apt on Linux.
This ensures the build environment can execute the new Tailwind CSS build processes without manual setup.
New Component: AXOpen.Operon.Blazor
A new Blazor library AXOpen.Operon.Blazor has been added to the solution. This likely encapsulates the new "Operon" design system or specific UI components that leverage the new Tailwind styling.
Cleanup
Configuration Removal: Obsolete apax.yml configurations have been removed, streamlining the package definitions to align with the new dependency structure.
.gitignore Update: The .gitignore file was updated to properly exclude node_modules, preventing the committed
bloat from the new Node.js-based tooling.
closes #890