[Cosmo-dev] Dashboard Plumbing Stuff

[Matthew Eernisse]

Responses inline ...

Bobby Rullo wrote:
> Well, it depends on what you mean by intelligence. If you are talking 
> about a domain model in which the objects know how to save themselves, 
> and collections are really collections of items, then I think that is 
> out of the question. That's not a re-factoring, that's a complete 
> rewrite almost. I wrote a wiki page on that here: 
> http://wiki.osafoundation.org/Journal/AnemicVersusRich It might be hard 
> to understand though, since I really was just using it for debating with 
> myself.

I have a quick question -- who won the debate? :)

Sounds like we need to move that getChanges method out of 'legacy,' 
figure out a logical place for it, and finally get rid of the last 
little bits of legacy code living in there. I'll put that on my list of 
stuff to do.

> Why publish keypresses on a topic when they can already handled by the 
> native event stuff in the browser? In any case, it's irrelevant as I am 
> talking about high level events here, not key presses and whatnot.

As Alex has pointed out in various places, one of the advantages of the 
Dojo event system and systems like it is that it allows you to treat DOM 
events as just another event in your app.

So publishing keypresses on a topic means you don't have to set up 
individual, local listeners for something that's by definition global, 
like keypresses. It's another global, app-level event, and you can 
handle it the same way as any other event that many or most of the UI 
elements in your UI may need to know about.


Matthew