On Fri, Dec 21, 2018 at 4:56 AM Joe Orr <joe....@gmail.com> wrote: > 1. When you say that you want LeoWapp to be restful, what do you mean? > > I'm thinking of a standalone HTML5 client written in Javascript. When it > needs to modify the file or otherwise save state off of the browser, it > calls a stateless http service with some data and one of PUT, PATCH or > DELETE. Reads are with http GET. The service has no code dealing with the > UI, just with the file. >
That kinda sounds like flask. It would be a big architectural change from flexx. Might need an additional refresh service running on websocket to deal with > updates to the file outside of the client. > > 2. What about flexx doesn't seem restful to you? > > If I understand it right, flexx builds the UI. So the UI is baked into > flexx, not separate. > > The client I'm thinking of will be able to talk to a local or remote > server written in any language. One server could be a wrapper on Leo. > Another could be a node service talking to mongo. > > Still finishing up a couple of LeoVue features and then will create a POC > which should make this clear. > Thanks for this heads up. It will be interesting to compare your approach with leoflexx.py. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
