Feature Request #670

sort content from jcom.hub

Added by Renaud Rubiano about 8 years ago. Updated almost 6 years ago.

Status:RejectedStart date:2011-02-03
Priority:LowDue date:
Assignee:Renaud Rubiano% Done:


Category:-Spent time:-
Target version:MVC for 0.6


When I send the message ''content'' to the jcom.hub, I would like that the output is sorted by priority.

Related issues

Related to Modular - Feature Request #659: jcom.namespace output order Closed 2011-02-01
Copied to Max - Feature Request #1480: sort content from jcom.hub Closed 2011-02-03


#1 Updated by Renaud Rubiano about 8 years ago

  • Status changed from New to Assigned

#2 Updated by Tom Mays over 7 years ago


Cause for celebration... This is my FIRST feature request!

In working with jcom.hub, I would really like and extension to the "content" message which can separate "parameter", "message" and "return". Don't know if it should be an argument to "content" or after a slash or a colon, but I do know that I want to be able to separate the different types coming out of a jcom.hub.

more soon!


#3 Updated by Théo de la Hogue over 7 years ago

  • Status changed from Assigned to Resolved

Is the new jcom.namespace features cannot be used to do this ?

if you add a [jcom.namespace @relative 1 @criterias parameter] you would have all the parameter of your model

By this way the "content" attribute could be removed from the hub because it is not very user friendly
and a patcher component (a jcom.content ?) could be added in order to provide a simple way to do this.

any opinions ?

#4 Updated by Théo de la Hogue over 7 years ago

  • Assignee changed from Théo de la Hogue to Renaud Rubiano

#5 Updated by Pascal Baltazar over 6 years ago

I agree with Théo

Concerning Tom's feature, I guess that now this can be monitored with the activity attributes (using jcom.receive e.g.) (see below)
and then sorted with some patcher using jcom.namespace...

So I guess this issue could be closed... Renaud ? Tom ?


#6 Updated by Pascal Baltazar over 6 years ago

  • Priority changed from High to Low

#7 Updated by Trond Lossius almost 6 years ago

  • Status changed from Resolved to Rejected

Also available in: Atom PDF