Comments on: Cookbook http://jonniespratley.com Programming with Flash, Flex and PHP Tue, 23 Feb 2010 23:53:13 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: AMFPHP Cheat Sheet secure AMFPHP | JelloGroup http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-1552 AMFPHP Cheat Sheet secure AMFPHP | JelloGroup Fri, 15 Jan 2010 19:02:19 +0000 http://jonniespratley.com/?page_id=187#comment-1552 [...] Recipe 1.1. Installing AMFPHP [...] [...] Recipe 1.1. Installing AMFPHP [...]

]]> By: Mini Cookbook for people usig Flash/Flex and AMFPHP, in webtoolkit4.me http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-74 Mini Cookbook for people usig Flash/Flex and AMFPHP, in webtoolkit4.me Fri, 10 Oct 2008 10:33:12 +0000 http://jonniespratley.com/?page_id=187#comment-74 [...] Spratley released a really nice “cheat sheet” / guide for mostly beginners on how to use AMFPHP (flash remoting for PHP). It’s really easy to follow, the code is well commented and you can [...] [...] Spratley released a really nice “cheat sheet” / guide for mostly beginners on how to use AMFPHP (flash remoting for PHP). It’s really easy to follow, the code is well commented and you can [...]

]]> By: Jonnie Spratley’s Blog: Update of Flex/PHP Mini-Cookbook : Dragonfly Networks http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-73 Jonnie Spratley’s Blog: Update of Flex/PHP Mini-Cookbook : Dragonfly Networks Fri, 10 Oct 2008 10:25:21 +0000 http://jonniespratley.com/?page_id=187#comment-73 [...] has been noted by Hyder Alamgir, there’s been a recent big update to the Flex/Flash and PHP cookbook from Jonnie [...] [...] has been noted by Hyder Alamgir, there’s been a recent big update to the Flex/Flash and PHP cookbook from Jonnie [...]

]]> By: Hyder Alamgir http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-69 Hyder Alamgir Sat, 04 Oct 2008 03:28:36 +0000 http://jonniespratley.com/?page_id=187#comment-69 Oh and I wrote about it here: http://alamgirdesigns.blogspot.com/2008/10/flex-and-amfphp-cookbook-revamped.html Also, check out a flex website I developed and let me know what you think about it. www.GulfSpecials.com Oh and I wrote about it here:
http://alamgirdesigns.blogspot.com/2008/10/flex-and-amfphp-cookbook-revamped.html

Also, check out a flex website I developed and let me know what you think about it.
http://www.GulfSpecials.com

]]> By: Hyder Alamgir http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-68 Hyder Alamgir Sat, 04 Oct 2008 03:02:50 +0000 http://jonniespratley.com/?page_id=187#comment-68 Excellent work Jonnie! Even better this time around! How about one on deep-linking... I was planning to do one myself but I would get nowhere near doing it as good as you do. Ping me if you need an sort of assistance. Excellent work Jonnie! Even better this time around!

How about one on deep-linking… I was planning to do one myself but I would get nowhere near doing it as good as you do.

Ping me if you need an sort of assistance.

]]> By: Darren http://jonniespratley.com/mini-cookbook/comment-page-1/#comment-62 Darren Tue, 30 Sep 2008 23:55:28 +0000 http://jonniespratley.com/?page_id=187#comment-62 I'm a bit confused by your approach. It gives the appearance of mapping classes but then in the 1.7 AS code you are actually creating a new SnippetVO by iterating over the properties of a standard object and mapping them to the new SnippetVO object, ie. "new SnippetVO( resultArray[s])". This is fake class mapping. If the mapping has occurred correctly, the objects are already SnippetVOs so you only need to do "resultArray[s] as SnippetVO" and you can get rid of the constructor in the SnippetVO AS code. For me the point of class mapping is that the objects you are sending are already typed, your code seems to assume they aren't. Also, I think I'd make the PHP SnippetVO constructor look more like the AS constructor, ie. "public function SnippetVO($snip = null)" and do away with the mapObject function. Instead of "$vo = new SnippetVO();$vo->mapObject( $data );" you could just do "$vo = new SnippetVO($data);". Just a bit confused by your different approaches to your PHP and AS VO classes. I’m a bit confused by your approach. It gives the appearance of mapping classes but then in the 1.7 AS code you are actually creating a new SnippetVO by iterating over the properties of a standard object and mapping them to the new SnippetVO object, ie. “new SnippetVO( resultArray[s])”. This is fake class mapping. If the mapping has occurred correctly, the objects are already SnippetVOs so you only need to do “resultArray[s] as SnippetVO” and you can get rid of the constructor in the SnippetVO AS code. For me the point of class mapping is that the objects you are sending are already typed, your code seems to assume they aren’t.

Also, I think I’d make the PHP SnippetVO constructor look more like the AS constructor, ie. “public function SnippetVO($snip = null)” and do away with the mapObject function. Instead of “$vo = new SnippetVO();$vo->mapObject( $data );” you could just do “$vo = new SnippetVO($data);”.

Just a bit confused by your different approaches to your PHP and AS VO classes.

]]>