Right now my thought is to run this on my web server and connect to it through ssh with local port forwarding.
Being able to create new files through the web UI would be cool, especially if you can have it start with a template of some kind. Other than that there aren’t many file operations *really* needed. Another kind of nice-to-have would be to open files by typing their names in an autocomplete box. Useful when you have a folder with more than a screenful of Pollen source files. On Tuesday, January 29, 2019 at 11:45:45 PM UTC-6, Junsong Li wrote: > > > On Tuesday, January 29, 2019 at 1:46:39 PM UTC-8, Joel Dueck wrote: >> >> Very nice! I plan to incorporate this into the workflow for my next >> Pollen project. I’ll be sure and let you know how it goes. >> > > Awesome! I use the tool mostly for editing pollen/html/css because they > are so easy to access, and the compile feedback is quick. Another super > useful feature is showing nested tags, especially when the cursor is deep > down in the tree. > > Editing racket code can be a bit challenging because the editor doesn't > watch the parens as other editors do. > > I also got good plans on file operations this time, so stay tuned :p > -- You received this message because you are subscribed to the Google Groups "Pollen" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
