StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2922542
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-27T15:38:18.283
FavoriteCount
0
LastActivityDate
2010-05-27T15:38:18.283
LastEditDate
LastEditorUserId
0
OwnerUserId
247533
ParentId
2916057
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I couldn't claim that this is a canonical property change framework in Scala, but I've used a class like this before: <pre><code>abstract class Notifier[T,U](t0: T) { import java.util.concurrent.atomic.AtomicReference import scala.actors.OutputChannel type OCUT = OutputChannel[(U,AtomicReference[T])] val data = new AtomicReference[T](t0) def id: U protected var callbacks = Nil:List[T => Unit] protected var listeners = Nil:List[OCUT] def apply() = data.get def update(t: T) { val told = data.getAndSet(t) if (t != told) { callbacks.foreach(_(t)) listeners.foreach(_ ! (id,data)) } } def attend(f: T=>Unit) { callbacks ::= f } def attend(oc: OCUT) { listeners ::= oc } def ignore(f: T=>Unit) { callbacks = callbacks.filter(_ != f) } def ignore(oc: OCUT) { listeners = listeners.filter(_ != oc) } } </code></pre> The motivation for creating this class was that I wanted a flexible thread-safe way to react to changes, which this provides (as it delivers both callbacks and can push messages to actors). It seems to me--unless I'm misunderstanding exactly what you want because I haven't had occasion to learn the WPF/Silverlight stuff--that this can implement everything you want and more. For example, <pre><code>class IDrawable extends SomethingWithOnPropertyChanged { val drawOrder = new Notifier[Int,Symbol](0) { def id = 'DrawOrder } val visible = new Notifier[Boolean,Symbol](false) { def id = 'Visible } drawOrder.attend((i:Int) => OnPropertyChanged(drawOrder.id)) def mutate { if (visible()) drawOrder() += 1 } } </code></pre> should be roughly equivalent to what you want. (Again, I'm not sure how flexible you want this to be; you could create a set of symbol -> notifier mappings that you would look up with an apply method so the target would have an easier time of doing something when it gets the DrawOrder symbol.) The only significant difference from your usage is that the Notifier uses its apply/update methods to save boilerplate; you don't have to write def x and def x_= methods every time, but you do have to use () for access.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POidiomatic property changed notification in scala?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRex Kerr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POidiomatic property changed notification in scala?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.