slupjs / slup Goto Github PK

We should provide CI builds, both to test our components and to build the demo on every commit.
The demo should be compiled, optimized, minimized and then uploaded to services like zeit/now or GitHub Pages.

It's a very important step torward a better and more open demo, for everyone to access and admire.

@Gejsi should polish the buttons demo and then i'll work on a more modular implementation for all the other pages.

As in HTML, you can provide a <label> for an input component, in the @slup/controls package should enable the users to provide a label/description prop. This prop should generate a Label alongside the control component that should fire linked input as a normal click would.

Example:

<Checkbox label='Whatever' />

The user should be able to define the direction of this element by supplying the labeld(which stands for direction) prop.

We should follow material design guidelines and provide support for the stepped slider as shown in this picture:

This feature triggered by the discrete prop will enable an additional prop called steps that should indicate the number of fixed points that should be present on the slider track.
The background of these dots should be the same as the text color

Tapping on buttons on mobile shows an ugly blue background(only on WebKit)

At the moment we haven't added this property to the buttons package yet.
We have already written it in the documentation because it will be added as soon as the branch #21 is merged.

The current ripple effect works fine, however, there are some issues that should be fixed.

• The wave doesn't need to end before fading out: the fade-out should start immediately instead of happening when the wave finished its growth.

• If the container is pressed for a certain amount of time ( I think 300 ms ), the wave should fade out before being removed from the dom.

Related to #8 #4

This will lower and speed up the build process. And luckily fix the errors that we're getting in the CI builds. Plus rollup provides and amazing es6 configuration and a really tiny footprint, with blazing-fast performance. We'd also replace it in the demo if it supports chunk splitting! 🎉

This implementation would actually lower the size BY A LOT, especially when using polished:

What is "tree-shaking?"

Tree-shaking, also known as "live code inclusion," is the process of eliminating code that is not actually used in a given project. It is similar to dead code elimination but can be much more efficient.

The major reason for this is shrinking the size even further

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: separateMajorReleases

This NPM release channel can be used to ship critical versions of the framework right from the master branch of GitHub via Travis CI builds. This would help us find bugs before complete versions roll out and would be great for those who wants to use this library with the new bleeding edge features that we'll ship.

Better performance and more lightweight

This prevents bugs from ripples that gets triggered in the container but receives the mouseUp event outside of it and so it gets ignored. Resulting in an ever-lasting ripple.

Related to #25

After #51

The 404 page is currently not displaying.

We should use rofrischmann/fela which has native support for inferno.

We should use tools such as hammerjs to improve usability and overall feedback on mobile platforms, introducing swipes and tap-enabled components like tabContainer(swipable) and ripples(touchable)

Related to #16

We should implement these props in the ripple element:

• startX and startY
• primary and secondary

We should implement hammerjs to enable swipes from sides on the sidenav component.

Related to #17

Set webpack/rollup'output to umd for better browser support without compliation.

We should follow this repo's mockup to make the demo work on github pages.

The theming package misses some key features that can be very useful.

• css (helper function that generates styles from a template literal with interpolation)

• Properties attached to a component shouldn't be rendered as attributes in HTML

I would also propose to change the name of this package from theming to styling or something like that, because it offers a lot more than theming.

We have created a bunch of packages but they still don't have a README which should be available for all of them.
It's important for the user but even for us since it will help us remember every feature.
We will have to create a new PR for current packages to add the README.

Tapping on buttons on mobile shows an ugly blue background(only on WebKit)