Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: [1]
1  PureMVC Manifold / Standard Version / Re: include swc to custom ant script on: September 19, 2008, 07:54:55
Yep, that worked.


Thanks, chr
2  PureMVC Manifold / Standard Version / include swc to custom ant script on: September 04, 2008, 06:35:12
I know, I am probably the only one using a custom ANT script to compile with Flex SDK. I'm trying to import the SWC, which is the only one for the project, and I use the syntax:

<arg line="-external-library-path='${swc.lib}'" />

where swc.lib is clearly a folder containing the swc file. Strange thing is that the file compiles but then I get the error:

VerifyError: Error #1014: Class org.puremvc.as3.patterns.facade::Facade could not be found.

I searched and on the entire google the only people getting that error they were trying to import puremvc, probably the as files, in CS3. I'm wondering first of all why this is a runtime error and not a compiling one. Does anyone know a solution, a part using the classes?

Cheers, chr
3  PureMVC Manifold / Standard Version / Separated View on: July 02, 2008, 03:15:10
The nice thing when using PureMVC in ActionScript is that because the presence of the EventDispatcher the view can be totally unaware of the mediator and the mediator registers to the events which it is interested. I saw the Java demo and because of the absence of a toolkit the view has a reference to the mediator. Isn't this a bit in contrast with PureMVC philosophy? Is there a lightweight toolkit which can be used, or created, to avoid it?

Cheers, chr
4  PureMVC Manifold / Bug Report / [ FIXED ] Unexpected behaviour when registering the same mediator twice on: April 07, 2008, 04:02:25
I noticed that if, maybe for mistake, I register the mediator twice, it will respond twice to the same event. I can agree that registering the same mediator twice shouldn't happen, but I was expecting eventually an error or ignoring the registration.

I'm using version 2.0.3.

Cheers, chr
5  PureMVC Manifold / Standard Version / new package structures in 2.0 on: March 11, 2008, 09:50:45
Maybe it's me, but why would you change the packages including the package "as3" ? Could it happen that you have different versions in the same project (library)? This definitely doesn't help the porting of applications to the new version.
I was going to try, for instance, to see if a bug was fixed in the last release but changing all the classes namespace is not that tempting :)

Thanks, chr
6  PureMVC Manifold / Bug Report / Re: Remove commands on: March 11, 2008, 09:40:57
I found the post and was:

http://forums.puremvc.org/index.php?topic=270.0

well, the problem seem similar, I had some problems with the vss so I wasn't sure if my swc 1.7.1 was the fixed one, so I downloaded the 1.7.1 source code from its tag in the svn and I still have the issue. I checked then the 2.0.1 source code and the controller still register a new observer everytime I set a command. I'm going now to try the 2.0.1 source with the fingers crossed :)


Cheers, chr
7  PureMVC Manifold / Bug Report / [ FIXED ] Remove commands on: March 11, 2008, 09:35:50
In a medium size application I was willing to register and unregister the commands when entering/leaving the section.
The second time I enter in the section the command (that has been removed on leaving) is fired twice. I think I posted already about it but with the new forum it has been lost. Anyway, if I remember well, the problem that time, that was fixed with a later revision, was that if I register two commands to the same event I had an unexpected behavior. Now I found out that if I register the same command twice after having unregistered it, it generates two observers and so gets fired twice. I personally see this as a bug because if I want to remove a command I don't want that any reference to it still exists, so I can register it again as brand new.

Thanks, chr
8  Announcements and General Discussion / General Discussion / Re: Server Interface on: March 09, 2008, 04:11:19
Quite interesting, in this case the reusable part would be the delegate. I'll give it some thoughts.

Thanks Cliff, chr
9  Announcements and General Discussion / General Discussion / Server Interface on: March 09, 2008, 05:52:57
In the application I'm doing I've a proxy (singleton) that does all the calls to the server (with weborb and different services). Then I register and unregister commands that observe its events based on the section where I'm. This class of course is growing and I'm wondering if and how I should split it, keeping in mind the reusability of the services.

Thanks, chr
10  PureMVC Manifold / Bug Report / Re: [ DEFUSED ] Register more Simple commands to same events on: February 28, 2008, 03:20:57
Hi Cliff, you are right, with the new version it seems to work as expected. It's strange just because I downloaded it less than a month ago.

Thanks a lot, chr
11  PureMVC Manifold / Bug Report / [ DEFUSED ] Register more Simple commands to same events on: February 25, 2008, 10:19:13
I encountered an expected behaviour while registering more simple commands to the same event. I found out, also watching the code, that registering another command to an event where another command was registered, SHOULD override and leave the latter registered. What is happening though is that correctly the first command is not registered anymore, but the second is registered twice  (it gets fired twice).
It sounds to big to be a bug, what am I missing?

Cheers, chr
Pages: [1]