Skip to content
This repository was archived by the owner on Dec 9, 2025. It is now read-only.

Bring smart banners into 2019#113

Open
tomascordero wants to merge 3 commits into
kudago:masterfrom
tomascordero:master
Open

Bring smart banners into 2019#113
tomascordero wants to merge 3 commits into
kudago:masterfrom
tomascordero:master

Conversation

@tomascordero

Copy link
Copy Markdown

I did somewhat of a bigger refactor of the styles.

For the CSS:

  1. I migrated the CSS to SCSS for easier maintenance.
    -- This means I created a "sass" folder containing all sass.
  2. I added gulp to the build process to compile the SCSS
  3. I added a test command npm run test to start a small test environment for dev
  4. I brought all the banners up to date with current design trends using google's material design.
  5. I added Flexbox

As for the Javascript:

Not much changed in this. I just added a few classes to the button for the material design. One of those classes is a color class that could be added to the options.

I hope these changes are welcome changes! I think the plugin is a great one and would love to see it brought up to current design trends.

Thanks,
Tomas

@dy

dy commented Jan 16, 2019

Copy link
Copy Markdown
Member

image 😬

@tomascordero

tomascordero commented Jan 16, 2019

Copy link
Copy Markdown
Author

image 😬

I know its a lot of changes but It adds a lot of future functionality (material design css library) and keeps this thing in line with the times!

@tomascordero

Copy link
Copy Markdown
Author

I guess we could remove some of those lines by removing some of the files that arent really needed. I just added the whole library. Im not pulling in all the modules when I compile I just have them in the repo

@dy

dy commented Jan 19, 2019

Copy link
Copy Markdown
Member

20 times more code... I'd expect ~10 lines of CSS changed to modernize it. This is a definitely a matter of a separate package.

@tomascordero

Copy link
Copy Markdown
Author

Let me revise it a bit. Ill remove the unused sass and make sure the included packages don't inject any unneeded CSS

@DaSchTour

DaSchTour commented Jan 21, 2019

Copy link
Copy Markdown

CSS library should not be added by copy but as a dependency. And it should be ensured, that only the needed SCSS is imported.

But I think this violates the idea of beeing standalone. So I'm not sure if it is really 2019 to add an external style library. It's definitly not 2019 to do it by copy.

@tomascordero

Copy link
Copy Markdown
Author

Im not sure what you mean by copy? I left the process the same exact way you had it to install the plugin to a website. As for the SCSS I only am importing the needed files however I believe there are some resets that are making their way over. I will clean those up.

Are you saying you want to change the way the CSS is included to a project?

@DaSchTour

DaSchTour commented Jan 23, 2019

Copy link
Copy Markdown

From what I understand the CSS is from an external library, so this external library is a dependency that needs to be included through package.json and imported from node_modules and they should not be commitet to git this repo.
And badges, cards, carousel, chips, datapicker, dropdown, grid and so on are not needed for this banner, so they should not be included anywhere in this project.
There are a lot of SCSS files pasted into this project that are not needed and that never had been pasted here as they should be included through importing from the place they were copied from.

@tomascordero

Copy link
Copy Markdown
Author

I understand what your saying! I will include them in the build process instead!

@tomascordero

Copy link
Copy Markdown
Author

Alright I went ahead and changed some stuff up with the sass. I also added a minified version of the css. Let me know what you think of it now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants