Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Where's the template file of 'composer' ?

K

K68 last edited by K68

Hello everyone ,

I want to modify the view of 'composer', where is the template file of 'composer' ?

Besides, what's the 'component' attribute mean here ?

Any help will be appreciated
Reply Quote 0
1 Reply Last reply
Bri Community Rep last edited by

It's a separate plugin: https://github.com/NodeBB/nodebb-plugin-composer-default
Reply Quote 0
1 Reply Last reply
K

K68 last edited by K68
@Bri
Great!! Thank you very much.

Besides, do you know the following html mean?
```
<div component="composer" class="...
```
Reply Quote 0
1 Reply Last reply
Bri Community Rep last edited by

That's probably where the composer begins to be rendered: https://github.com/NodeBB/nodebb-plugin-composer-default/blob/4a90f85801eb58a98bdd56f34decade07dc49e22/static/templates/composer.tpl#L1
Reply Quote 0
K
1 Reply Last reply
pichalite Plugin & Theme Dev last edited by @K68

@K68 it's just an attribute. NodeBB uses it to identify the composer element on the page.
Reply Quote 0
1 Reply Last reply
K

K68 last edited by @Bri

@Bri @pichalite
I got it now , thank you guys
Reply Quote 0
1 Reply Last reply

composer 21 template 16 component 1

6
Posts

2349
Views

Log in to reply

Suggested Topics

Composer preview auto size issue
Bug Reports • bug composer preview • • JaredBusch

3

0
Votes

3
Posts

1768
Views

@baris said in Composer preview auto size issue: This is already reported here https://github.com/NodeBB/NodeBB/issues/5208 Cool
M

NodeBB's Usage of Realtime Communication
NodeBB Development • • miksago

1

1
Votes

1
Posts

919
Views

M

Something that interested me when I first started hacking on NodeBB was how the platform uses realtime communication through socket.io (and websockets). This interest stems from work I did whilst working as a realtime engineer at Pusher several years ago. One of my research projects whilst there was to look into how websockets get used in production, and other use cases for websockets besides the standard "subscribe to a channel and receive events". In 2011, I gave a talk at Keeping It Realtime conference in portland about some of my findings, you can watch it here: http://2011.krtconf.com/videos/micheil_smith (long hair and all) or check out the slides here: https://speakerdeck.com/miksago/krtconf-websockets-sub-protocols How NodeBB currently seems to use realtime communication: RPC: Request data from the server, get a response back, present that data to the user (or send data to a server like you would POST to a HTTP server) Channels: Used for user to user chat messages Events: Used for online/offline states of users. I may have missed something here, so, let me know if I have. Most of the websocket usage appears to be in RPC style messages: Get this piece of data do something with it. At present, all realtime communication for NodeBB is built on top of Socket.io, which uses a protocol more tailored for event type packets, rather than for RPC style packets. For this, something like JSON RPC may be more appropriate. Refactoring this deep internal of NodeBB would make the platform more resource efficient on the wire, and also allow for better logging and handling of data. You'd know exactly what has failed on the client-side or server-side and be able to give an appropriate response. In the code, refactoring this level of things would make the code far cleaner, and give option to provide all HTTP Verbs over WebSocket or vica-verse (meaning if you wanted to, you could make 90% of NodeBB standard HTTP. You'd end up with an "api" module internally that is everything that can be exposed, which simple returns back standard javascript objects. For user-to-user chat messaging you could still multiplex that onto the same actual websocket / socket.io connection (although it's arguable if this is actually beneficial). Why do any of this writing or work? Interest more than anything else, but it may make the code to NodeBB cleaner, and improve maintainability.
"BEGIN categories" not working in menu.tpl
Bug Reports • template categories • • Tanner

3

0
Votes

3
Posts

1308
Views

Category data is not avaiable in the header, if you want to use it you will have to use the hook filter:middleware.renderHeader and add the data.
A

Changing template file with a plugin...
General Discussion • plugin template topic-footer • • a_5mith

16

0
Votes

16
Posts

5497
Views

@a_5mith said: @psychobunny .username { font-size: 80%; } Well that works for me ... updated
O

Composer - List Icon change: fa-list > fa-list-ul
Feature Requests • composer css icon • • omega

3

0
Votes

3
Posts

36
Views

O

@baris Oh my! Awesome!

| |

Copyright © 2018 NodeBB | Contributors

1 / 1