On Mon, Aug 5, 2013 at 6:55 PM, John D. Hume <duelin.mark...@gmail.com>wrote:
> On Mon, Aug 5, 2013 at 8:37 PM, kovas boguta <kovas.bog...@gmail.com>wrote: > >> https://github.com/kovasb/paredit-widget >> > > >> The bigger idea is that code editing should be available a la carte. >> >> Tying something as fundamental as code editing together with IDE concerns >> (file & project management, artifact generation, debugging, etc) is a >> mistake with profound consequences. >> > > That's an interesting idea. How would you envision interactions like "jump > to definition" or even auto-completion working in an editor decoupled from > IDE concerns? > The IDE keeps track of what the global set of definitions is and where they are. It can easily issue a command to the editor to scroll to a place, or feed the editor a list of possible completions. What is part of the editor API is an open question, but I think supporting the basics for tooltips, syntax highlighting, autocompletion is good as long as it is data-driven. It would also make sense to have good integration between the editor and the model (eg the parsley parse tree) so that one could easily direct the editor to highlight a piece of the tree in a certain way, but I think the model should sit outside the editor per se. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
