mirror of
				https://github.com/vector-im/element-web.git
				synced 2025-10-31 08:11:16 +01:00 
			
		
		
		
	Merge remote-tracking branch 'origin/develop' into develop
This commit is contained in:
		
						commit
						839d4ba41b
					
				
							
								
								
									
										23
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										23
									
								
								README.md
									
									
									
									
									
								
							| @ -11,16 +11,8 @@ a 'skin'. A skin provides: | |||||||
|  * The containing application |  * The containing application | ||||||
|  * Zero or more 'modules' containing non-UI functionality |  * Zero or more 'modules' containing non-UI functionality | ||||||
| 
 | 
 | ||||||
| **WARNING: As of July 2016, the skinning abstraction is broken due to rapid | As of Aug 2018, the only skin that exists is `vector-im/riot-web`; it and | ||||||
| development of `matrix-react-sdk` to meet the needs of Riot (codenamed Vector), the first app | `matrix-org/matrix-react-sdk` should effectively | ||||||
| to be built on top of the SDK** (https://github.com/vector-im/riot-web). |  | ||||||
| Right now `matrix-react-sdk` depends on some functionality from `riot-web` |  | ||||||
| (e.g. CSS), and `matrix-react-sdk` contains some Riot specific behaviour |  | ||||||
| (grep for 'vector').  This layering will be fixed asap once Riot development |  | ||||||
| has stabilised, but for now we do not advise trying to create new skins for |  | ||||||
| matrix-react-sdk until the layers are clearly separated again. |  | ||||||
| 
 |  | ||||||
| In the interim, `vector-im/riot-web` and `matrix-org/matrix-react-sdk` should |  | ||||||
| be considered as a single project (for instance, matrix-react-sdk bugs | be considered as a single project (for instance, matrix-react-sdk bugs | ||||||
| are currently filed against vector-im/riot-web rather than this project). | are currently filed against vector-im/riot-web rather than this project). | ||||||
| 
 | 
 | ||||||
| @ -48,15 +40,14 @@ https://github.com/matrix-org/synapse/tree/master/CONTRIBUTING.rst | |||||||
| Please follow the Matrix JS/React code style as per: | Please follow the Matrix JS/React code style as per: | ||||||
| https://github.com/matrix-org/matrix-react-sdk/blob/master/code_style.md | https://github.com/matrix-org/matrix-react-sdk/blob/master/code_style.md | ||||||
| 
 | 
 | ||||||
| Whilst the layering separation between matrix-react-sdk and Riot is broken | Code should be committed as follows: | ||||||
| (as of July 2016), code should be committed as follows: |  | ||||||
|  * All new components: https://github.com/matrix-org/matrix-react-sdk/tree/master/src/components |  * All new components: https://github.com/matrix-org/matrix-react-sdk/tree/master/src/components | ||||||
|  * Riot-specific components: https://github.com/vector-im/riot-web/tree/master/src/components |  * Riot-specific components: https://github.com/vector-im/riot-web/tree/master/src/components | ||||||
|    * In practice, `matrix-react-sdk` is still evolving so fast that the maintenance |    * In practice, `matrix-react-sdk` is still evolving so fast that the maintenance | ||||||
|      burden of customising and overriding these components for Riot can seriously |      burden of customising and overriding these components for Riot can seriously | ||||||
|      impede development.  So right now, there should be very few (if any) customisations for Riot. |      impede development.  So right now, there should be very few (if any) customisations for Riot. | ||||||
|  * CSS for Matrix SDK components: https://github.com/vector-im/riot-web/tree/master/src/skins/vector/css/matrix-react-sdk |  * CSS: https://github.com/vector-im/riot-web/tree/master/src/skins/vector/css/matrix-react-sdk | ||||||
|  * CSS for Riot-specific overrides and components: https://github.com/vector-im/riot-web/tree/master/src/skins/vector/css/riot-web |  * Theme specific CSS & resources: https://github.com/matrix-org/matrix-react-sdk/tree/master/res/themes | ||||||
| 
 | 
 | ||||||
| React components in matrix-react-sdk are come in two different flavours: | React components in matrix-react-sdk are come in two different flavours: | ||||||
| 'structures' and 'views'.  Structures are stateful components which handle the | 'structures' and 'views'.  Structures are stateful components which handle the | ||||||
| @ -84,6 +75,7 @@ practices that anyone working with the SDK needs to be be aware of and uphold: | |||||||
| 
 | 
 | ||||||
|   * Per-view CSS is optional - it could choose to inherit all its styling from |   * Per-view CSS is optional - it could choose to inherit all its styling from | ||||||
|     the context of the rest of the app, although this is unusual for any but |     the context of the rest of the app, although this is unusual for any but | ||||||
|  |  * Theme specific CSS & resources: https://github.com/matrix-org/matrix-react-sdk/tree/master/res/themes | ||||||
|     structural components (lacking presentation logic) and the simplest view |     structural components (lacking presentation logic) and the simplest view | ||||||
|     components. |     components. | ||||||
| 
 | 
 | ||||||
| @ -139,8 +131,7 @@ for now. | |||||||
| OUTDATED: To Create Your Own Skin | OUTDATED: To Create Your Own Skin | ||||||
| ================================= | ================================= | ||||||
| 
 | 
 | ||||||
| **This is ALL LIES currently, as skinning is currently broken - see the WARNING | **This is ALL LIES currently, and needs to be updated** | ||||||
| section at the top of this readme.** |  | ||||||
| 
 | 
 | ||||||
| Skins are modules are exported from such a package in the `lib` directory. | Skins are modules are exported from such a package in the `lib` directory. | ||||||
| `lib/skins` contains one directory per-skin, named after the skin, and the | `lib/skins` contains one directory per-skin, named after the skin, and the | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user