Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • release/202005
  • release/202001
  • release/201912
  • release/201911
  • release/releaseWindowsTestOne
  • release/releaseTest
  • release/releaseWindowsTest
  • release/windowsReleaseTest
  • release/201910
  • release/qt/201910
  • release/windows-test/201910
  • release/201908
  • release/201906
  • release/201905
  • release/201904
  • release/201903
  • release/201902
  • release/201901
  • release/201812
  • 1.0.0
  • 0.3.0
  • 0.2.1
  • 0.2.0
  • 0.1.0
25 results

web-chatview

  • Clone with SSH
  • Clone with HTTPS
  • Sébastien Blin's avatar
    Sébastien Blin authored
    - use configurable color for incoming messages and send file container
    - use dark-blue for action-buttons (windows)
    
    Change-Id: Ib6fe82c44b37aa60bf62032bcf26206f1bdb4eee
    032f1dba
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    # README - chatview
    
    The chatview runs under a WebKit GTK view. It is written using web technologies
    (HTML5/CSS3/JS) and is responsible for displaying everything that deals with the
    navbar, the messages, and the message bar.
    
    ## Contributing - syntax
    
    We have a set of ESLint rules that define clear syntax rules (web/.eslintrc.json).
    
    You will need the following tools:
    
    - ESLint (The pluggable linting utility for JavaScript and JSX)
      https://eslint.org/
    - ESLint HTML plugin (eslint-plugin-html)
      https://www.npmjs.com/package/eslint-plugin-html
    
    Before pushing a patch, make sure that it passes ESLint:
    $ eslint chatview.html
    
    Most trivial issues can be fixed using
    $ eslint chatview.js --fix
    
    We will not accept patches introducing non-ESLint-compliant code.
    
    ## WebKit GTK
    
    Everything runs under WebKit GTK, that is if you need to write browser specific
    code, you will only need to support WebKit (CSS -webkit- prefix).
    
    Do not use querySelector if getElementById or getElementByClassName can be used
    instead. querySelector doesn't always make the code easier and has very bad
    performances.