>> so, im trying the ARP codegen from the service browser but i cant get it to >> compile straight away for a variety of reasons. >> >> I just downloaded ARP (2.02) as i am not normally an ARP user. >> > That's the reason! :) The packaged version is woefully out of date. > Since I'm now out of my latest project, I can start devoting time/energy > to Arp again. Next week, I'll remove the current installer and point to > the SVN repository. I'll also start porting the docs to the wiki.
ah ok.. i'll grab it from svn and try again :) > Hmm, not too sure about adding this to VOs. We need a workflow that will > work across AS2 and AS3, MTASC, Flash & Flex (1.5 & 2). Its something that can be moved to its own file (code or some kind of config) I guess at the code generation stage you would create plain VO's and then generate the supporting code / configuration as the user requested. > Very cool. I need to look into Cake as well. My to-do list grows! >> and hence be able to use most of the cake code for html and flash without >> any >> changes. >> > This is definitely a very important use-case. thats one of the key things for me as well, there shouldnt be a need to do any heavy refactoring for view implementations (flash / html). At the moment i first generate the html interface, seperate the html / form handling parts from the business logic and then create a flash interface (or facade if you like..) Really they should just be able to work with exactly the same methods. >> What would be great is to combine the cake bake script and amfphp code >> generator >> to generate the cake and arp code at the same time, models, commands, >> service >> locator etc. >> > Yes! :) Ideally, I want to be able to click a button in a browser > (Single Button Interface -- SBI -- back off, it's my concept dammit! :P > ) and have it do all that *and* create the scaffolding for a basic Flash > application for updating the database. Now that the Flex compiler is > free, it would be easiest to create the scaffolding in Flex 2/AS3 to > start with and then possibly also port to an MTASC version with one of > the open-source component frameworks. > > Of course, the key thing is to keep Arp compatible with Flash 6-9 (AS2 + > AS3), MTASC and Flex (1.5 & 2). For me personally developing to Flex 2 / AS3 is not a realistic target yet, whilst it may be the easiest approach as the Flex framework provides a good UI framework out of the box, my clients still require applications for fp7. So for now I will focus more on generation of vo's, commands, service locators etc and sometime in the future look to generating the UI as well. Of course if anyone else wants to do it that would be great for whatever framework (ASWing, ActionStep, MX v2 etc..) Martin _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
