Git Product home page Git Product logo

datdot-ui's People

Contributors

ninabreznik avatar serapath avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

datdot-ui's Issues

plan - dashboard - map

@todo

  • design phase
    • datdot-ui#144 wireframe-plan-dashboard-map
    • show numbers
    • region active
    • change map section
      • remove "operating system" and "Host" title
      • remove "host: swarmkey" (it is a detail visible when selecting chunks in grid)
      • remove "availability icon" and move that as marker to "plan card" instead
      • replace "location: western europe" with a little "world map" to highlight regions.
  • implementation phase

[UI] Help wizard box

@todo

  • create repository
    • @outputrepository
  • implement first iteration of component and tag with v0.0.1-alpha
    • @inputrepository
    • update package.json (new path for the dependencies and version v0.0.1-alpha)
    • install budo and browserify as dev dependency
    • add terminal to dev dependencies
    • set up github page using demo maker component dev dependency
    • implement first version and add communication protocol and use latest message standard
      • design notifications overlay box
      • design help overlay box
      • implement notifcations/help overlay box component
    • build new bundle.js to include changes in demo page
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
      • @outputrepo#readme.md
    • install latest specific version of dependencies
      • #10
      • make datdot-ui-card-header component
      • make datdot-ui-card-body component
      • make datdot-ui-duration-map component
    • @outputrepo_url#v0.0.1-alpha

@info

Help mode in PLANS

v18-4
plan list

image

map

image

performance chart

image

actions example

image
image

Previous design

Plan summary list

image

Map

image

Map

image

actions

image

[UI] Actions bar

@todo

  • create repository
    • @outputrepository
  • implement first iteration of component and tag with v0.0.1-alpha
    • @inputrepository
    • update package.json (new path for the dependencies and version v0.0.1-alpha)
    • install budo and browserify as dev dependency
    • add terminal to dev dependencies
    • set up github page using demo maker component dev dependency
    • implement first version and add communication protocol and use latest message standard
    • build new bundle.js to include changes in demo page
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
      • @outputrepo#readme.md
    • install latest specific version of dependencies
    • @outputrepo_url#v0.0.1-alpha

@info

...

[UI] Sort

@todo

  • create repository
    • @outputrepository
  • implement first iteration of component and tag with v0.0.1-alpha
    • @inputrepository
    • update package.json (new path for the dependencies and version v0.0.1-alpha)
    • install budo and browserify as dev dependency
    • add terminal to dev dependencies
    • set up github page using demo maker component dev dependency
    • implement first version and add communication protocol and use latest message standard
    • build new bundle.js to include changes in demo page
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
      • @outputrepo#readme.md
    • install latest specific version of dependencies
      • ...
    • @outputrepo_url#v0.0.1-alpha

@info

for PLANS

image
Sort by

  1. Name
  2. Feeds
  3. Chunks
  4. Price
  5. Start date
  6. End date
  7. Data size
  8. Location

for USER

image
Sort by

  1. Id
  2. Earned
  3. Spent
  4. Price
  5. Newest timestamp
  6. Oldest timestamp

for JOBS

image
Sort by

  1. Id
  2. Earned
  3. Size
  4. Newest timestamp
  5. Oldest timestamp

[UI] Account action

No account

image

  1. create new account
  2. import account

Account created/imported

image

  1. create new account
  2. import account
  3. transfer
  4. edit account
  5. remove account
  6. switch accounts

plan - dashboard - performance chart

@todo

  • design phase
    • datdot-ui#143 wireframe-plan-dashboard-performance-chart
    • real timeline chart
    • options (hourly, daily, weekly, monthly, yearly)
    • chart legend
      • CPU
      • RAM
      • HDD
      • remove Legend
      • Price
      • Download
      • Upload
      • Latency
    • make a timeline graph (like the one for "bandwidth") with full screen width
      • the timeline start and end date is representing the "duration" already
      • it should have one curve line for each value we decide to add (it can be many), for the start it is: RAM, CPU, HDD, download, upload, price
      • the time lines can have gaps or holes when a plan has time slots where it is not hosted
      • when many plans are selected each line for (e.g. RAM, CPU, ...) is combined value for all selected plans
      • remove all "progress circles charts" (e.g. RAM, CPU, HDD, ...) and instead:
      • add icons for each performance item

[UI] Icon

@todo

  • implement first iteration of component
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • create repository
    • @output 📦 repository
  • refactor component and its dependencies and tag with v0.0.0-prealpha
    • @input 📦 repository
    • refactor very old commit with domlog and old button/icon to use versions
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-prealpha
  • refactor component for last Fiona's commit and tag it with v0.0.0-alpha
    • @input 📦 v0.0.0-prealpha
    • refactor commit with latest terminal/log to use versions
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 v0.0.0-alpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 📦 v0.0.1-alpha
  • implement next component version v0.0.2-alpha
    • @input 📦 v0.0.1-alpha
    • fix bugs & add features for v0.0.2
      • Use shadowDOM
      • Icon demo
      • Support SVG
      • Add style
      • Support custom style
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
    • document component api in readme
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
      • note: icon has no states and no protocol
      • @output 📦 README.md
    • install latest dev dependencies
      • budo
      • browserify
      • datdot-terminal (add in v0.0.3)
    • update github page links
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.2-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • document component api in readme or whatever needs to show in the readme
  • Implement next component version v0.0.4-alpha
    • @input 📦 v0.0.3-alpha
    • update theming (use stylesheets + allow to send a new stylesheet that overwrites the default one)
    • update readme
    • add help logic
    • add update (theme + opts)
    • add default opts and theme
    • @output 📦 repository#v0.0.4-alpha

@info

Repo 📂

https://github.com/datdot-ui/icon

[UI] Datepicker-range

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 📦 repository
  • refactor component latest commit with new comm protocol and tag with v0.0.1.-alpha
    • @input 📦 repository
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 📦 v0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @input 📦 v0.0.3-alpha
    • fix bugs & add features for v0.0.3
    • use calendar-month and calendar-days as subcomponents
    • update sending/receiving messages
    • document component api in readme or whatever needs to show in the readme
      • list all opts
      • list all incoming message types
      • list all outgoing message types
    • [x document component api in readme
    • install latest dev dependencies
      • budo
      • browserify
    • use latest internal dependencies
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.4-alpha

@info

Repo 📂

[UI] Plan - map

map

image

  1. Dark color - display how many data hosting nearby regions on map
  2. White color - currently host region
  3. Zoom in +
  4. Zoom out -

[UI] Button

@todo

  • implement first iteration of component
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • create repository
    • @output 📦 repository
  • refactor component and its dependencies and tag with v0.0.0-prealpha
    • @input 📦 repository
    • refactor very old commit with domlog and old button/icon to use versions
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-prealpha
  • refactor component for last Fiona's commit and tag it with v0.0.0-alpha
    • @input 📦 v0.0.0-prealpha
    • refactor commit with latest terminal/log to use versions
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 v0.0.0-alpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @outputv0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • @outputrepository#v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @inputv0.0.3-alpha
    • Button demo (example: text, icon, link, disabled, toggle, switch, navigation)
    • update theming (use stylesheets + allow to send a new stylesheet that overwrites the default one)
    • slim down button component
      • remove cover (image button => should consider making an image component)
      • state only disabled and current
    • document component api in readme
    • install latest dev dependencies
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.4-alpha

@info

Repo 📂

https://github.com/datdotorg/datdot-ui-button
https://github.com/datdot-ui/link

[UI] Filter

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 📦 repository
  • refactor component for filter and its dependencies and tag with v0.0.0-prealpha
    • @output 📦 repository
    • refactor very old commit with domlog and old button/icon to use versions
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-prealpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 v0.0.0-prealpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 📦 v0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • set up github page using demo maker component dev dependency
    • @outputrepository#v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @input 📦 v0.0.3-alpha
    • fix bugs & add features for v0.0.4
      • Data: Option list(Available, Not available, Hypercore, Hyperdrive, Cabal)
      • Add CSS style
      • Import #3 datdot-ui-button
      • Import ui-domlog
      • Toggle check function
      • Get result from filter option
      • Testing string compare on Safari (with @serapath)
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
    • set up github page using demo maker component dev dependency
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
    • document component api in readme
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
    • install latest dev dependencies
      • budo
      • browserify
      • datdot-terminal
    • install latest specific version of dependencies
    • update github page links
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @outputv0.0.4-alpha

@info

THIS ELEMENT has been merged with the dropdown #71

// datdot-ui-filter
require('datdot-ui-button')

Repo 📂

https://github.com/datdot-ui/filter

for PLANS

image
Filter by

  1. Name
  2. Swarm
  3. Feeds
  4. Chunks
  5. Price
  6. Start date
  7. End date
  8. Data size
  9. Location

Filter option

imageimageimage

Repo

https://github.com/datdotorg/datdot-ui-filter-option

Important issue

  1. string compare failed in Safari
    From data entry
let optionList = { unchecked: [], checked: ['Available', 'Not available', 'Hypercore', 'Hyperdrive', 'Cabal']}

Option button

const option = filterOption({page, flow, name: 'filter-option', data: optionList.checked}, optionProtocol('filter-option'))
function optionProtocol (name) {
....
....
// get type 'unchecked' or 'checked' to check from and currentValue are equality.
if (type === 'unchecked') {
      // handle chekced status
      const result = optionList.checked.reduce( (acc, currentValue) => {
      if (from === currentValue) {
            const index = optionList.checked.indexOf(from)
            optionList.unchecked.push(from)
            optionList.checked.splice(index, 1)
      }
      acc = optionList.checked
      return acc
}, [])

if (type === 'checked') {
      // handle unchecked status
      const result = optionList.unchecked.reduce( (acc, currentValue) => {
      if (from === currentValue) {
            const index = optionList.unchecked.indexOf(from)
            optionList.checked.push(from)
            optionList.unchecked.splice(index, 1)
      }
      acc = optionList.checked
      return acc
}, [])

This code line is an issue to cause compare failed on Safari

from === currentValue

even change === to == is failed too

option == from

Chrome
image

Safari
image

Chrome result

image

Safari result

image image

Even I do console.log(typeof from, typeof currentValue)
This is what've I got
image

I've tried many ways with different pattern in JavaScript

let optionList = { unchecked: [], checked: ['Available', 'Not available', 'Hypercore', 'Hyperdrive', 'Cabal']}
optionList.checked.findIndex( option => option === from ) // -1
optionList.splice( optionList.checked.indexOf(from), 1) // it is worked fine in Codepen.io 

Solution

  1. Refactor entry data structure
const data = [
        {id: 1, status: "Available", active: true}, 
        {id: 2, status: "Not available", active: false}, 
        {id: 3, status: "Hypercore", active: true},
        {id: 4, status: "Hyperdrive", active: false},
        {id: 5, status: "Cabal", active: true}
    ]
  1. Use id to compare with button's index
src/index.js
// get lits
    optionListRender(data).then( buttons => {
        buttons.map( (item, i) => { 
            const li = bel`<li>${item}</li>`
            // need to set an id to button for toggle using, because Safari cannot compare body or from (string issue)
            item.setAttribute('id', i+1)
            optionList.append(li) 
        })
        return buttons
    })
  1. make new function to toggle check
    image
demo/demo.js
function actionToggleCheck (message) {
...
...
      data.map( item => { 
            // * better to use return item for add more conditions
            if (item.id === body ) item.active = !item.active 
            return item
        })

It is still failed when I refactored the data structure and test again via item.status and body
image
typeof item.status and typeof body are all string, somehow it is failed to compare string in Safari.
item.status.localeCompare(body) is also return -1, only 0 is matched


Conclusion

Use regex.test(string) to compare from existed array instead of comparing string by from to fix issue on Safari

let options = optionList.map( item => { 
    // * better to use return item for add more conditions
    if (item.id === body ) item.active = !item.active
    if (/^Available/.test(item.status) && item.active ) on = online(data)
    if (/^Not available/.test(item.status) && item.active ) off = offline(data)
    return item
}).map( item => {
    if (/core/i.test(item.status) && item.active) {
            let arr = data.filter( obj => /core/i.test(obj.type))
            return result.push(...arr)
    }
    if (/drive/i.test(item.status) && item.active) {
            let arr = data.filter( obj => /drive/i.test(obj.type)) 
            return result.push(...arr)
    }
    if (/cabal/i.test(item.status) && item.active) {
            let arr = data.filter( obj => /cabal/i.test(obj.type))
            return result.push(...arr)
    }
    return item
})

[UI] Plan - plan list

Plan list

image

Plan card information

image

  1. swarm identicon
  2. plan status & plan name
  3. account
  4. payment total price
  5. feeds
  6. chunks & data size
  7. start datetime
  8. selected location
  9. end datetime

Selected plan card

image
Plan action
image

  1. play
  2. pause
  3. edit
  4. remove

[UI] Month selector

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 🏭 repository
  • refactor component for last Fiona's commit and tag it with v0.0.0-alpha
    • @input 🏭 repository
    • refactor commit with latest terminal/log to use versions
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 🏭 v0.0.0-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 🏭 v0.0.0-alpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 🏭 v0.0.1-alpha
  • implement next component version v0.0.4-alpha
    • @input 🏭 v0.0.1-alpha
    • fix bugs & add features for v0.0.2
      • Add CSS style(Support two styles)
      • Make previous and next month selector
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
    • document component api in readme or whatever needs to show in the readme
    • document component api in readme
      • list all opts
      • list all incoming message types
      • list all outgoing message types
    • install latest dev dependencies
      • budo
      • browserify
    • install latest specific version of dependencies
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @output 🏭 v0.0.4-alpha
  • Next
    • @input 🏭 v0.0.4-alpha
    • Year Selector(Current not support yet, maybe later should add on too)
    • set up github page using demo maker component dev dependency
    • document apis for each screen and return available actions
      • @inputwireframes action bars

@info

Repo

datdot-webapp-components

@todo


@info

  • BOTTOM MENU
    Screenshot_2022-08-26_00-12-03

    • menu buttons
      Screenshot_2022-08-26_00-09-24
    • action tab
      Screenshot_2022-08-26_00-10-39
      Screenshot_2022-08-26_00-16-31
    • subaction tab
      Screenshot_2022-08-26_00-19-04
    • steps
      Screenshot_2022-08-26_00-20-39
      Screenshot_2022-08-26_00-22-08
    • substeps
      Screenshot_2022-08-26_00-14-16

  • USER
    • create account form
      Screenshot_2022-08-26_01-43-46
    • seed phrase
      Screenshot_2022-08-26_01-44-48
      Screenshot_2022-08-26_01-45-36
    • dashboard
      Screenshot_2022-08-26_01-46-13
      • transactions list
        Screenshot_2022-08-26_01-46-39
      • balance stats
        Screenshot_2022-08-26_01-49-06
        • @todo segments of the stats

  • PLANS
    • new plan overview card
      Screenshot_2022-08-26_02-31-15
      Screenshot_2022-08-26_02-36-43
    • new plan title
      Screenshot_2022-08-26_01-53-03
    • new plan duration
      Screenshot_2022-08-26_01-54-03
      • datepicker
        Screenshot_2022-08-26_01-55-50
      • schedule
        Screenshot_2022-08-26_02-29-33
      • start end
        Screenshot_2022-08-26_01-56-15
    • new plan swarm
      Screenshot_2022-08-26_01-58-00
      • list
        Screenshot_2022-08-26_01-59-46
      • search input
        Screenshot_2022-08-26_02-00-21
        Screenshot_2022-08-26_02-01-25
      • filter
        Screenshot_2022-08-26_02-00-21
    • new plan data config
      Screenshot_2022-08-26_02-15-19
      • data card
        Screenshot_2022-08-26_02-25-02
        Screenshot_2022-08-26_02-36-33
      • multi selection list
        Screenshot_2022-08-26_02-25-47
      • chunk selector
        Screenshot_2022-08-26_02-26-01
      • scheduler
        Screenshot_2022-08-26_02-34-46
      • location
        Screenshot_2022-08-26_02-35-13
      • performance
        Screenshot_2022-08-26_02-35-52
      • budget estimation
        Screenshot_2022-08-26_02-37-47
    • new plan summary
      Screenshot_2022-08-26_02-38-45
    • all plans dashboard
      Screenshot_2022-08-26_02-40-58

  • WORK
    • register resources
      resources
    • register location
      Screenshot_2022-08-26_23-06-44
    • register schedule
      Screenshot_2022-08-26_23-07-05
  • dashboard
    Screenshot_2022-08-26_23-07-31

[UI] Tab

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 📦 repository
  • refactor component for last Fiona's commit and tag it with v0.0.0-alpha
    • @input 📦 repository
    • refactor commit with latest terminal/log to use versions
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 🏭 v0.0.0-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 🏭 v0.0.0-alpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 🏭 v0.0.1-alpha
  • implement next component version v0.0.2-alpha
    • @input 🏭 v0.0.1-alpha
    • fix bugs & add features for v0.0.2
      • Tab demo
      • Add CSS style
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
      • maybe we should split button in more sub components
    • set up github page using demo maker component dev dependency
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
    • document component api in readme
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
    • install latest dev dependencies
      • budo
      • browserify
      • datdot-terminal
    • install latest specific version of dependencies
    • update github page links
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @output 🏭 v0.0.2-alpha

@info

Repo 📂

https://github.com/datdotorg/datdot-ui-tab

[UI] Range slider

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 📦 repository
  • refactor component for filter and its dependencies and tag with v0.0.0-prealpha
    • @output 📦 repository
    • refactor very old commit with domlog and old button/icon to use versions
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-prealpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 v0.0.0-prealpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 📦 v0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • set up github page using demo maker component dev dependency
    • @outputrepository#v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @input 📦 v0.0.3-alpha
    • fix bugs & add features for v0.0.4- [ ] support single select (Support a filter for search swarm key and terminal messages using)
      • make it based on #243
      • Add CSS style
      • Import ui-domlog
      • Refactor code(protocol, receive, recipients)
      • On keyup changes value
      • Support onmousewheel(Safari, Chrome, Opera), onwheel(Firefox)
      • Support increase number by ArrowRight, ArrowUp and decrease number by ArrowLeft, ArrowDown
      • Support increase multiple times by shiftKey + ArrowRight or ArrowUp
      • Support decrease multiple times by shiftKey + ArrowLeft or ArrowDown
      • Support set start value
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
    • set up github page using demo maker component dev dependency
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
    • document component api in readme
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
      • @output 🏭 README.md
    • install latest dev dependencies
      • budo
      • browserify
      • datdot-terminal
    • install latest specific version of dependencies
    • update github page links
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @outputv0.0.4-alpha

@info

Repo 📂

https://github.com/datdotorg/datdot-ui-range-slider

Notes

(by @fionataeyang)

  • Slide range is part of performance form when the user needs to use slide range to select what the numbers they would be like to share via their computer. And slide range would be combined with number input together that it has a decimal.

[UI] Day selector - single

@todo

  • implement first iteration of component
    • create repository
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • @output 📦 repository
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 repository
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @output 📦 v0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • set up github page using demo maker component dev dependency
    • @outputrepository#v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @input 📦 v0.0.3-alpha
    • fix bugs & add features for v0.0.4
      • Display days
      • Select day(Only support pick one day for Timeline)
      • Before today displays disabled and not clickable
      • Add CSS style
      • Year Selector(Current not support yet, maybe later should add on too)
      • Refactor codes(protocol, receive, recipients)
      • refactor all messages and status and update documentation
    • set up github page using demo maker component dev dependency
    • document component api in readme or whatever needs to show in the readme
      • document apis for each screen and return available actions
        • @inputwireframes action bars
    • document component api in readme
      • list all opts
      • list all roles
      • list all incoming message types
      • list all outgoing message types
      • list all possible status the component instance can be in
    • install latest dev dependencies
      • budo
      • browserify
      • datdot-terminal
    • install latest specific version of dependencies
      • ...
    • update github page links
    • build new bundle.js to include changes in demo page
    • update package.json (new path for the dependencies)
    • @output 🏭 v0.0.4-alpha

@info

Repo

https://github.com/datdotorg/datdot-ui-timeline-days

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.