Closed GoogleCodeExporter closed 9 years ago
class ViewComponent :public Composite < Component >
{
public:
ViewComponent() {
};
virtual ~ViewComponent()throw() {
}
static ting::Ref<ViewComponent> New() {
return ting::Ref<ViewComponent>(new ViewComponent());
}
};
Original comment by Davidgui...@gmail.com
on 29 Apr 2014 at 1:24
One of the usage of course could be to show a game ready api as it is already
the case....
Original comment by Davidgui...@gmail.com
on 29 Apr 2014 at 3:17
Sorry, I'm not sure I understand what you mean. What is this Composite that you
propose? What is its use case (example)? Could you describe in more details?
Original comment by igagis@gmail.com
on 30 Apr 2014 at 3:24
ok i sent you an email :) it was late the nite
Original comment by Davidgui...@gmail.com
on 30 Apr 2014 at 5:01
Hi, I'm afraid I still did not catch your idea completely...
From your description in the email:
"I was thinking that the next level could be the stack that enable you to build
games more quickly like :
Component
Event Queue (already there but add the ability to send message to registrated
component a bit like topic in messaging system )
Service Locator
and common desing pattern ."
I see that you propose something similar to IPC lib (like D-Bus) but within the
single process?
Please describe more precisely with example, snippets of code, usage examples,
sample design patter that you have in mind and so on. It is possible that your
idea is out of ting scope and can be formed as a standalone library...
Original comment by igagis@gmail.com
on 1 May 2014 at 5:42
[deleted comment]
[deleted comment]
i think it's out of scope of the usage of ting , sure it very similar to D-Bus
, but out of scope, should be implemented by ting client.
let s close it
Original comment by Davidgui...@gmail.com
on 19 May 2014 at 12:45
out of library scope
Original comment by igagis@gmail.com
on 29 May 2014 at 8:35
Original issue reported on code.google.com by
Davidgui...@gmail.com
on 29 Apr 2014 at 1:22