Thank you for the update. It is great that everything moved to git, then Pub package manager might be possible

Dart Editor
Version 0.1.0.201208201142, build 10994
Dart SDK version 10993

By the way using latest version of PureMVC_Dart 1.3 and Demo_Dart_ReverseText 1.3:
A___________________________
I think there's a typo:

Demo_Dart_ReverseText:
model/proxy/TextProxy.dart
line 4:

static String TEXT_CHANGED = "text/changed";

should be:

static final String TEXT_CHANGED = "text/changed";
(expected constant expression)

B______________________________
Demo_Dart_ReverseText.dart

line 5:
#import('http://svn.puremvc.org/PureMVC_Dart/trunk/src/puremvc.dart');

this is still the SVN path, shouldn't it be the git one?
or
#import('../PureMVC_Dart/src/puremvc.dart'); //when working with local

Hello Cliff,

to start with thank you for having taken the early initiative of the Dart port of PureMVC, being a long time user and fan of PureMVC, it is a good starting point to me to come on known ground

Running Reverse Text Demo on latest Dart Editor Version 0.1.0.201206291313, Build 9261
Dart SDK version 9258, I had errors. The version of Reverse Text example I'm using was checked out 07.03.2012 17h.

I know you are aware of this (from g+), but I feel this info could help before you fix this:

A:

since dart:dom is deprecated

Demo_Dart_Reversetext.dart Line 1:
// DART DOM Library
#import('dart:html');//before #import('dart:dom');
...
B:

TextComponent.dart

vars definition (changes of class denominations):

  FormElement   textForm;
  InputElement  textInput;
  InputElement  textOutput;
  LabelElement  textOutputLabel;
  InputElement  checkbox;
  ButtonElement reverseButton;

components initialization ($dom_ prefix must be added to querySelector method):

  TextComponent()
  {
    // use HTML5 querySelector for DOM retrieval
    textForm         = document.$dom_querySelector('#textForm');
    textInput        = textForm.$dom_querySelector('#inputText');
    textOutput       = textForm.$dom_querySelector('#outputText');
    textOutputLabel  = textForm.$dom_querySelector('#outputTextLabel');
    checkbox         = textForm.$dom_querySelector('input[type=checkbox]');
    reverseButton    = textForm.$dom_querySelector('button[type=submit]');

...
C:
every
.addEventListener(
become:
.$dom_addEventListener(

...
D:
 ProcessTextCommand.dart

    while (chars.length > 0) {
      buffer.add(chars.removeLast());
    }

does not work it sends an exception, since List chars is considered to be fixed size List (which doesn't allow removeLast), if I understand this correctly.

instead I did the following:
    var i = chars.length;
    while (i > 0) {
      buffer.add(chars[i -1]);
      i--;
    }
    chars = null;


Best regards.
Cedric Madelaine aka maddec

Hi there,

I wonder if they are best practice suggestion regarding how to organize the use of mx.controls.Alert.

I wonder if gathering alert logic inside a Mediator is a good approach.

I mean having an AlertMediator which may be interested in every notifications related to alerts. Then modifing the Alert type depending to the context.
The question which remains open is how callbacks are used ( for example for confirmation Alerts (YES|NO) ).
Thank you for your interest.

Best regards.


Cedric M. (aka maddec)

----------------------------------------------------
http://analogdesign.ch
http://analogdesign.ch/blog
visual & interactive communication
----------------------------------------------------

I believe some thought should be put into the matter of states/effects/transitions being managed.

I agree with you I think it is necessary to find solutions to gather things related to Visual Transitions, and if what is proposed is as efficient as PureMVC and work well with it, it may be a great step forward.
 
I think the introduction of states and transitions is a very valuable one, but it brought out also questions and strategical decisions. I currently also use official state-transition within mxml components. But I now need to go a step further for Flex projects and I feel that relying on Adobe transitions, makes me loose a lot of flexibility I have when I use thirdparties tweening packages, like Fuse in Actionscript 2 or Tweener. By the way, Moses Gunesch who is behind the famous Fuse kit made public a new project named GO Asap (Actionscript Animation Platform) lately, which objective is to propose a generic Animation Platform to gather every Tweening packages and other animation engines like Physic Engines and Collada animations. I made a blog post on this subject if you are interested in:
http://analogdesign.ch/blog/index.php/archive/goasap-go-universal-tween-framework/

It can certainly help if you want to use your own tweens and custom reusable transitions and not rely on Adobe's one only.

I think there is an other point where solutions should be found: Flash projects which have not a State system, I think that we need such State System, for example for project which use Papervision3D/Away3d, because it can quickly become very hard to manage every visual transitions and their effects with a 3d approach.

To work on an independent State system as PureMVC propose its independent Events system aka Notifications, may be a solution?
- For Flex project you may rely on Flex States only (which scope is to remain at the periphery of the framework into mxml components changed by mediators) and/or use these "Framework Wide States".
- For Flash projects you may use it as an equivalent of Flex states?
The advantage is that you would have everything centralised and not depending on Flex, so if you want to re-use a transition or a state sequence into another project you could easily whether it is Flex or Flash. This is just suppositions, I am not very sure of putting it here, but I felt it may be worth something... 

The GO Asap project may help to propose something generic about animation/transitions/states management to "plug" to PureMVC. I have not yet dig enough into it, so I cannot give further clues at present time.

Thank you for your interest.
 

 

By the way, I think that chaining asynch transitions (I mean visual transitions), should be managed in the view region of the framework into a transition manager or something like that. Commands should only start a transition chain/sequence and let the transitionsManager or specialTransition mediator handle everything as a blackbox. It may send a notification when the sequence of transitions is finished. But such notifications should be used precautionously to avoid having visual transitions to call commands on proxy, which sounds to me not very clean and logicall, isn't it?

I wonder what is your recommandations on this point Cliff.
What would be the best practice to manage transitions and their chaining? (especially if they do not depends on built in Flex transition (between states), but on third parties Tweening packages). Should we use a kind of delegate on mediators to link to transition manager?

About managing visual transitions, what is your piece of advice on this point?
Is there a recommended approach complient to pureMVC best practices?

Thank you in advance for your answer.

I understand your point Graphex, I have asked myself this question several times. I understand your explanation Cliff and I will stick to the practice you are advising. It works perfectly welll when proxy send notifications back when asynch operations are complete. But it is right that sometimes it is a bit difficult to track the chain and also to give names to notifications I think that our natural practice to gather things to make them more understandable plays a role here.

My question is:
What about putting this multiple asynch Notifications management inside a special kind of mediator, which only purpose may be to listen to notifications and send new one? Does this causes the same conceptual problems as having a special kind of async macro command? Or is it a better practice?

By the way, I think that chaining asynch transitions (I mean visual transitions), should be managed in the view region of the framework into a transition manager or something like that. Commands should only start a transition chain/sequence and let the transitionsManager or specialTransition mediator handle everything as a blackbox. It may send a notification when the sequence of transitions is finished. But such notifications should be used precautionously to avoid having visual transitions to call commands on proxy, which sounds to me not very clean and logicall, isn't it?

I wonder what is your recommandations on this point Cliff.
What would be the best practice to manage transitions and their chaining? (especially if they do not depends on built in Flex transition (between states), but on third parties Tweening packages). Should we use a kind of delegate on mediators to link to transition manager?

Thank you for your interest.
Best regards.

maddec