Hmmm... something just came into my mind...

How could we possibly combine the use of recordsets (using the mx.remoting.recordset class at the flash side) and VO mapping? I guess that if we use your Cake TypeMapper, Martin, it wouldn't be so hard becouse we just pass the Recordset.items array to be mapped to the typemapper, right?

Another solution would be to use the VO features of AMFPHP together with the new class-mapping features of Cake, haven't tested it, though.

Marcelo.

On 10/25/06, Marcelo de Moraes Serpa <[EMAIL PROTECTED]> wrote:
Hi Marco,

Thanks, nice solution...

Just found the page about Arrayf at amfphp.org: http://amfphp.sourceforge.net/docs/manualrecordsets.html

PS.: Martin, have you already tried the new class-mapping (return class objects instead of associative arrays, more Rails-like) features introduced in Cake?

Cheers!

Marcelo.


On 10/25/06, Marco Madarco <[EMAIL PROTECTED]> wrote:
Yes, *action*_count is a feature of AMFPhp, wrapping the array in a
Arrayf make it work like a (pageable) recordset.
In the client you do a normal service request,
but in your handleResult you should listen to the modelChanged event:

function handleResult(re:ResultEvent) {
  var rs:RecordSet = RecordSet(re.result);
  rs.addEventListener('modelChanged', this);
  ...
}
function modelChanged(info:Object) {
  //info={event:"addRows", firstRos:xxx, lastRow:yyy}
  ...
}
when you do a rs.getItemAt(x) and x isn't already fetched from the
server, a page request is made and then a modelChanged event is triggered.
You can find more info here:
http://amfphp.sourceforge.net/docs/pageablerecordsets.html

bye

Marcelo de Moraes Serpa ha scritto:
> Hi Marco,
>
> This *action*_count is a built-in feature of amfphp, right? What code
> should
> be on the client side for this to work? (AFAIK it only works when you are
> using the recordset class).
>
> Also, why do you wrap the array returned by Cake into the Arrayf object?
>
> Cheers,
>
> Marcelo.

--
Marco Madarco

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to