Hey Kartik -
> Gentle reminder regarding previous email. > I read through it and didn't see anything that needed a response from me - let me know if there is something there you would like for me to weigh-in on? > > Also, I have implemented a Plotly based frontend and Bokeh server as > backend. Please see [1 <http://github.com/kartikp1995/gr-htmlgui/>]. > Awesome! I really appreciate your effort to prove things out with prototypes. > > For demo: Go to [2 > <http://terminal.kartikpatel.in/?bokeh-session-id=h4NyPINXVEniemWudNItOhpEwM1U9NvoC3WaHu1Dmfyr>] > for Bokeh based output and [3 <http://terminal.kartikpatel.in/plotly/>] > for Plotly based output. In both cases, backend is handled by Bokeh. > Unfortunately, neither of those links worked for me - the pages don't seem to render anything. > Now, I think this example solves the query of independent frontend and > backend. As shown in the example, using the socket provided by Bokeh > server, one can use any frontend library for plotting. > > Also, any change in connected client will be pushed by Bokeh server. So, > the person changing the frontend library (in future) will have to handle > such changes using Javascript. > While this does prove the feasibility of independent front-end and back-ends, it is still "all-in" on Bokeh in the sense that the server and integration with GR is built with Bokeh. Again, I'm not saying that's the wrong decision, but I want to be sure that where the delineations lie are clearly called out in the proposal & docs. > > So, I think, now we can easily use Bokeh backend for the task. Instead of > writing server application on our own, Bokeh will be more structured and > efficient. What is your suggestion on this? > I think this is suitable for this effort, and creating it in the OOTM mitigates the risk of dependency lock-in. I'm on-board with the use of Bokeh. Cheers, Ben
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
