|
|
Show Posts
|
Pages: [1]
|
2
|
PureMVC Manifold / Standard Version / Using the obj-c port with X-Code 3.23
|
on: June 29, 2010, 09:55:09
|
I am having all kinds of problems compiling the current version to xCode, i get a boat load of errors like:
1. I've tried recompiling the puremvc project 2. I've tried to include all the classes with no success 3. Can't get this to work either way
Undefined symbols: "_OBJC_METACLASS_$_Proxy", referenced from: _OBJC_METACLASS_$_TimerProxy in TimerProxy.o _OBJC_METACLASS_$_DeviceProxy in DeviceProxy.o _OBJC_METACLASS_$_LoginProxy in LoginProxy.o _OBJC_METACLASS_$_PowerProxy in PowerProxy.o _OBJC_METACLASS_$_ServiceProxy in ServiceProxy.o _OBJC_METACLASS_$_StatusProxy in StatusProxy.o _OBJC_METACLASS_$_IpProxy in IpProxy.o _OBJC_METACLASS_$_UserProxy in UserProxy.o "_OBJC_METACLASS_$_Mediator", referenced from: _OBJC_METACLASS_$_DeviceListMediator in DeviceListMediator.o _OBJC_METACLASS_$_LoginViewMediator in LoginViewMediator.o _OBJC_METACLASS_$_VoxSTRUCTUREMediator in VoxSTRUCTUREMediator.o "_OBJC_IVAR_$_Notifier.facade", referenced from: _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in StartupCommand.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LogOutCommand.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in ValidateUserCommand.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LoginUserCommand.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in GetDevicesCommand.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in TimerProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in DeviceProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in LoginProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in PowerProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in StatusProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in IpProxy.o _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr in UserProxy.o (maybe you meant: _OBJC_IVAR_$_Notifier.facade$non_lazy_ptr) "_OBJC_CLASS_$_Mediator", referenced from: _OBJC_CLASS_$_DeviceListMediator in DeviceListMediator.o _OBJC_CLASS_$_LoginViewMediator in LoginViewMediator.o _OBJC_CLASS_$_VoxSTRUCTUREMediator in VoxSTRUCTUREMediator.o "_OBJC_CLASS_$_Proxy", referenced from: _OBJC_CLASS_$_TimerProxy in TimerProxy.o _OBJC_CLASS_$_DeviceProxy in DeviceProxy.o _OBJC_CLASS_$_LoginProxy in LoginProxy.o _OBJC_CLASS_$_PowerProxy in PowerProxy.o _OBJC_CLASS_$_ServiceProxy in ServiceProxy.o _OBJC_CLASS_$_StatusProxy in StatusProxy.o _OBJC_CLASS_$_IpProxy in IpProxy.o _OBJC_CLASS_$_UserProxy in UserProxy.o "_OBJC_CLASS_$_SimpleCommand", referenced from: _OBJC_CLASS_$_StartupCommand in StartupCommand.o _OBJC_CLASS_$_LogOutCommand in LogOutCommand.o _OBJC_CLASS_$_ValidateUserCommand in ValidateUserCommand.o _OBJC_CLASS_$_LoginUserCommand in LoginUserCommand.o _OBJC_CLASS_$_GetDevicesCommand in GetDevicesCommand.o "_OBJC_IVAR_$_Mediator.viewComponent", referenced from: _OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in DeviceListMediator.o _OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in LoginViewMediator.o _OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr in VoxSTRUCTUREMediator.o (maybe you meant: _OBJC_IVAR_$_Mediator.viewComponent$non_lazy_ptr) "_OBJC_METACLASS_$_Facade", referenced from: _OBJC_METACLASS_$_ApplicationFacade in ApplicationFacade.o "_OBJC_METACLASS_$_SimpleCommand", referenced from: _OBJC_METACLASS_$_StartupCommand in StartupCommand.o _OBJC_METACLASS_$_LogOutCommand in LogOutCommand.o _OBJC_METACLASS_$_ValidateUserCommand in ValidateUserCommand.o _OBJC_METACLASS_$_LoginUserCommand in LoginUserCommand.o _OBJC_METACLASS_$_GetDevicesCommand in GetDevicesCommand.o "_OBJC_IVAR_$_Proxy.data", referenced from: _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in TimerProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in DeviceProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in PowerProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in ServiceProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in StatusProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in IpProxy.o _OBJC_IVAR_$_Proxy.data$non_lazy_ptr in UserProxy.o (maybe you meant: _OBJC_IVAR_$_Proxy.data$non_lazy_ptr) "_OBJC_CLASS_$_Facade", referenced from: _OBJC_CLASS_$_ApplicationFacade in ApplicationFacade.o ld: symbol(s) not found collect2: ld returned 1 exit status
|
|
|
3
|
PureMVC Manifold / MultiCore Version / Re: A New Approach to Inter-Core communication
|
on: March 17, 2010, 12:45:54
|
OK, I am curious, I have had issues with pipes, where I have to send a message to know when the junctions are created and input output pipes have been connected. I wish it could be handled in one method, when the module is ready and can interact with framework?
Does your solution provide an easy mechanism to know when your module is complete and hooked up to the framework?
Thanks, Patrick
|
|
|
6
|
PureMVC Manifold / MultiCore Version / Using FSM with muti-core,
|
on: November 10, 2009, 02:23:40
|
Is there an example of this, I am having issues getting my FSM injected..
multitonKey for this Notifier not yet initialized!
How do I register this mediator with the multicore framework in the FSM please.
Thanks, Patrick
|
|
|
8
|
Announcements and General Discussion / Getting Started / AS3 - null viewComponent Mediator
|
on: April 13, 2008, 11:59:29
|
I was trying to use flash cs3 to create a new PureMVC implementation, and I'm having issues with a null viewComponent in my applicationMediator.
Here's a snapshot of my problem. i'm going off of how my flex works with passing a reference to my app as "this", from my main MovieClass in flash cs3...
from my main class
var app:ApplicationFacade = new ApplicationFacade(); app.startup(this);
How come when I pass my instance of my app to my ApplicationFacade it is not null. However, when i try to access it in my app mediator it is?
when I try to access app like below...
facade.registerMediator ( new InitialViewMediator("InitialViewMediator",app.initialView) );
it's always null... Are there some difference to view startups from cs3 to flex?
Thanks, reduxdj
|
|
|
10
|
Announcements and General Discussion / Getting Started / CrossPopulating Proxies
|
on: March 19, 2008, 04:49:10
|
Another newbie question, I have a proxy and it gets back a dataset. How do I keep this dataset around so I can make another command do some business logic on my data, so my other view can use it? What's the best practice for this? See, what a beginner question, I am so embarrassed. Thanks, patrick
|
|
|
11
|
Announcements and General Discussion / Getting Started / Binding a value object into a proxy
|
on: March 19, 2008, 04:21:31
|
HI,
I am having a difficult time of passing the data parameter of an object in my proxy at creation time. I am new at this so I am trying to work from the documentation.
public function LoginProxy ( data:Object = null) {
how do I create a loginVO object on my main application and then make sure that when I create my loginProxy - I have my loginVO created in the constructor as "data", data is always null for me.
Inside my LoginMediator, i am getting the result and I am working it like this...
// User clicked Login Button; try to log in private function onTryLogin ( event:Event ) : void { sendNotification( ApplicationFacade.LOGIN, UrLogin.loginVO ); //trace (UrLogin.loginVO.username); loginProxy.login(UrLogin.loginVO); }
Is the preceding best practice? or am i missing a step.
Thanks, Patrick
|
|
|
|
|