Data in Motion

User Tools

Site Tools

Trace: • when_it_does_not_make_sense_for_an_editor_to_span_perspectives

Sidebar

Dave Orme muses about agile and functional programming.

My current work emphasizes SOA applications using Scala, Kubernetes, and AWS with a React-based SPA front-end. I'm also interested in progressive web applications and developer tools.

Blog

Scala, Clojure, and FP

Agile

The Cloud

Data-First Development

Older work

Coconut Palm Software home

Donate Bitcoin:

1Ecnr9vtkC8b9FvmQjQaJ9ZsHB127UzVD6

Keywords:

Kubernetes, Docker, Streaming Data, Spark, Scala, Clojure, OSGi, Karaf, GCP, AWS, SQL

Disclaimer:

Everything I say here is my own opinion and not necessarily that of my employer.

rcp:when_it_does_not_make_sense_for_an_editor_to_span_perspectives

When it does not make sense for an editor to span perspectives

Right now, this is a scratch pad to record the idea until I get a chance to write it up properly and blog it.

Editors belong to one ore more editing domains. When editing domains change, editors that are not in the current domain are hidden. Editors may also belong to no editing domain at all, indicating that they are potentially applicable to all editing domains. An example of this might be the text file editor.

~~LINKBACK~~ ~~DISCUSSION:off~~

rcp/when_it_does_not_make_sense_for_an_editor_to_span_perspectives.txt · Last modified: 2014/10/17 22:08 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
CC Attribution 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki