Bug #820

using relative address to binds on hub's attributes or messages

Added by Théo de la Hogue about 8 years ago. Updated about 7 years ago.

Status:ClosedStart date:2011-07-13
Priority:LowDue date:
Assignee:Pascal Baltazar% Done:

0%

Category:-Spent time:-
Target version:MVC for 0.6
Branch:0.6-alpha OS:

Description

For now if you put a [jcom.send :init] ina model the effective address is "/myModel/:init"
so it doesn't work... this to be a parsing problem.

History

#1 Updated by Théo de la Hogue about 8 years ago

  • Status changed from New to Resolved

this ok now : you can access hub's attribute using [jcom.receive :priority]

#2 Updated by Pascal Baltazar about 8 years ago

  • Status changed from Resolved to Assigned
  • Priority changed from Normal to Low

interestingly :
• jcom.receive has to be banged to output the value - this can be surprising on the first time, and maybe not so consistent with the usual jcom.receive behaviour (this happens both with a relative and absolute address)

• this only works with sends and receives (both in the model and a bound view), but not with a jcom.view object...

could be nice to have this working with a jcom.view also... but maybe this is not worth a lot of work ???

I'm reopening the FR in order to discuss this and take a decision

#3 Updated by Théo de la Hogue about 8 years ago

ok I get it : the Container class doesn't notify observers when his attributes changes (like the Data does)

about the view I don't know why but I'm pretty sure it's not a big deal... TODO

#4 Updated by Théo de la Hogue almost 8 years ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Théo de la Hogue to Pascal Baltazar
  • Branch set to 0.6-alpha

#5 Updated by Pascal Baltazar about 7 years ago

  • Status changed from Resolved to Closed

it works !

Also available in: Atom PDF