logo
  • Home
  • Acerca
  • Autores
  • Faq
  • Rede
  Twitter   Feed-me! RSS!
Dez 28

Adobe Certified Expert!

Escrito por Mauro Martins em .NET, 1, 3d, 4, 6, Adobe, Adobe Certified Expert, AR, bar, BI, Blazeds, blog, certificação, class, Componente, Desenvolvimento, Design, Design Pattern, Design Patterns, development, email, event, Experiências, facebook, Flash / Flex, Flex, Flex 2, Flex 4, Flex4, for, framework, gmail, Google, html, ide, IE, if, image, linkedin, Links e sugestões, live, map, mg, O, on, Partilha, pattern, PHP, Ria’s Geral, Software, TAT, Twitter, UI, XP @ 12 28th, 2010 | via http://imauro.com/blog/ | Sem comentários
Mauro Martins
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

ACE Flex 2 Adobe Certified Expert!

Olá a todos!

Para os mais distraídos, há cerca de uma semana coloquei, do lado direito do blog, um logótipo do qual me orgulho muito. É o logótipo que é atribuído a todos os profissionais que possuem o título de Adobe Certified Expert.

Esta certificação deu-se, depois de ter completado, com sucesso, o exame da Pearson Vue sobre Flex 4.

Em termos de partilha de experiência, posso-vos dizer que o exame é difícil e que toca em bastantes pontos do desenvolvimento nesta plataforma.

As questões que nos são colocadas no exame vão desde o simples nome de uma propriedade de um componente, passando por casos de utilização ou não de certos tipos de design patterns, até a questões sobre BlazeDS, Adobe Live Cycle e consequentemente questões sobre model-driven development.

No meu caso, quando achei que estava na hora de obter a certificação, marquei logo o exame e dediquei cerca de dois meses a estudar a plataforma / framework e todos os seus pequenos detalhes. De forma a estar mais confortável no exame, comprei o software Attest 3 que tenta simular o ambiente de exame real e que se revelou essencial para o resultado final.

Esta foi, sem dúvida, a forma ideal de acabar 2010 icon smile Adobe Certified Expert!

Qualquer dúvida que tenham e esclarecimento que precisem sobre as certificações de Adobe Certified Expert, coloquem-nas aqui que tentarei responder o melhor que sei!

Bom 2011, Mauro.

  • Blog this on Blogger
  • Subscribe to the comments for this post?
  • Digg this!
  • Share this on Facebook
  • Email this via Gmail
  • Share this on LinkedIn
  • Email this to a friend?
  • Stumble upon something good? Share it on StumbleUpon
  • Tweet This!



Out 4

Codinomes dos Softwares da Adobe (e antiga Macromedia)

Escrito por Leonardo França em .NET, 1, 2.0, 4, 6, Adobe, Adobe Air, Air, AIR 2.0, api, Apollo, AR, Beta, BI, blog, Catalyst, class, ColdFusion, ColdFusion 8, cs4, Desenvolvimento, DRE, Dreamweaver, err, flash, Flash 10, Flash Catalyst, flash lite, flash media, Flash Media Server, Flash Platform, Flash Player, Flash Remoting, Flex, Flex 2, Flex 3, Flex 4, Flex Builder, fonte, for, gc, Gumbo, IE, if, image, lista, lite, Mac, mg, O, on, PHP, player, pt, Remoting, RIA, Ria’s Geral, RTW, server, Software, Sun, UI, update, Ved @ 10 4th, 2010 | via http://www.leonardofranca.com.br | Sem comentários
Leonardo França
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »



Segue alguns codinomes usados pela Adobe (e da antiga Macromedia) para o desenvolvimento de seus softwares. Lista em constante atualização, quem souber de algum codinome que não esteja na lista, pode deixar um comentário para atualização :D

Product Codename
Adobe AIR 2.5 ?
Adobe AIR 2.0 Athena
Adobe AIR 1.5 Cosmo
Adobe AIR 1.0 Apollo
Adobe Media Player Philo
VoIP for Flash Pacifica
Flash Player native 64-bit support Square
Flash Player 10 Astro
Flash Player 9.0.60 Moviestar
Flash Player 8.5 Zaphod
Flash CS5 Viper
Flash 10 CS4 Diesel
Flash 9 CS3 Bolero(Dot Release) > Blaze
Flash 8 8Ball
Flash Player 8 Maelstrom
Flash MX 2004 7.2 Ellipsis
Flash MX 2004 Matador
Flash MX Professional 2004 Toreador
Flash MX Fang
Flash 5 Gromit
Flash Remoting Salsa
Flash Media Server 2.0.1 Dynamo
Flash Media Server 2.0 Edison
Flash Communication Server 1.5 Kaiwa
Flash Communication Server 1.0 TinCan
Flash Lite 3.0 Authoring Rob Roy
Flash Lite 2.0 Deuce
Generator 2 Tsunami
Captivate Northshore
Central 1.5 Mercury > Gemini
Flash Catalyst Thermo
Flex 4.5 Hero
Flex 4.0 Gumbo
Flex 3.0 Moxie
FDS 2.x/3.0 ? Borneo
Flex Builder 2 Zorn
Flex 2.0 Mistral
Flex 1.5 for .NET Wondertwin
Flex 1.0 Illiad > Odyssey > RedHouse > Royale
Flex Builder 1.0 Brady
ColdFusion 9 Centaur
ColdFusion 8 (64Bit) Gemini
ColdFusion 8 Scorpio
ColdFusion MX 7.5 (?) Mystic
ColdFusion MX 7 Updater (7.0.1) Merrimack
ColdFusion MX 7 Elvis > Blackstone
ColdFusion MX 6.1 RedSky
ColdFusion MX 6 Neo
JRun 5 Cheetah
JRun 4 Nozomi
Director MX 2004 Woody
Director MX Foster
Director 8.5 Tron
Director 8 Woo
Director 6 Hopper
Director 5 Spike
Multiuser Server Mars
Contribute 2 Samwise
Contribute 1 Dashboard
Dreamweaver 10 CS4 Stiletto
Dreamweaver 9 CS3 Hanzo
Dreamweaver 8 Coltrane
Fireworks 8 Avedon

Fonte:
http://luar.com.hk/blog/?p=472

Jun 22

Tour de Flex 2.0 – Cerca de 500 exemplos Flex!

Escrito por Luis Messias em .NET, 1, 2.0, 4, 6, action, Adobe, Air, api, AR, auto, blog, class, err, erro, exemplo, Exemplos, Exemplos Flex, flash, Flash Player, Flex, Flex 2, Flex 4, for, handle, html, IE, if, int, LOB, mg, O, on, padrão, player, processo, redeRIA, RIA, Ria’s Geral, server, socket, try, UI, update, web @ 06 22nd, 2010 | via http://blog.luismessias.com | 1 comentário
Luis Messias
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »



Adobe acaba de lançar o novo Tour de versão Flex 2.0 , que agora contém cerca 500 exemplos Flex! A nova versão tem novos exemplos (apenas disponível na versão AIR do Tour de Flex), incluindo:

  • Detecção de armazenamento em massa
  • Processo Nativo
  • Abrir com o aplicativo padrão
  • Socket Server

Além disso, existem alguns bons exemplos do novo Flash Player 10.1 e AIR 2 APIs, incluindo:

  • Handler de erro global
  • Globalização / Internacionalização
  • Acesso ao Microfone

Aqui está um exemplo do Doug McCune’s Physics Form bem legal e um dashboard em tempo real do Tour de Flex: real-time Tour de Flex Dashboard.

Se você já tem instalado o Tour de Flex, então ele deve fazer o auto update para a versão mais recente quando você iniciá-lo. Caso contrário, instale-o a partir daqui:

Mar 4

Modules

Escrito por Fabio da Silva em 1, 2.0, 2009, 4, 6, action, Actionscript, Adobe, Adobe Flex, Air, api, Aplicativos, app, AR, BI, blog, Blogs, class, classe, classes, components, control, Controls, developer, Download, dynamic, event, EventListener, events, finally, flash, Flex, Flex 2, Flex 3, Flex Builder, for, framework, function, Google, handle, html, ide, IE, if, int, interface, map, mg, MXML, Number, O, on, player, pt, reference, RIA, Ria’s Geral, RTM, runtime, singleton, swf, TAT, Tech, UI, XML @ 03 4th, 2010 | via http://fabiophx.blogspot.com | Sem comentários
Fabio da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Estou estudando sobre módulos (Flex 3 Developer Guide) e fiz um resumo dos tópicos que achei importantes para melhor fixação e abaixo estou disponibilizando este resumo.

About modules

Modules
are SWF files that can be loaded and unloaded by an application. They cannot be run independently of an application, but any number of applications can share the modules.
The main application, can dynamically load other modules that it requires, when it needs them.


Benefits of modules
  • Smaller initial download size of the SWF file.
  • Shorter load time due to smaller SWF file size.
  • Better encapsulation of related aspects of an application.
A module is a special type of dynamically loadable SWF that contains an IFlexModuleFactory class factory. This allows an application to load code at run time and create class instances without requiring that the class implementations be linked into the main application. Modules are similar to Runtime Shared Libraries (RSLs) in that they separate code from an application into separately loaded SWF files. Modules are much more flexible than RSLs because modules can be loaded and unloaded at run time and compiled without the application.

ModuleManager and ModuleLoader

The ModuleManager manages the set of loaded modules, which are treated as a map of Singletons that are indexed by the module URL. The ModuleLoader class is a thin layer on top of the ModuleManager API that is intended to act similarly to the mx.controls.SWFLoader class for modules that only define a single visual UIComponent. The ModuleLoader class is the easiest class to use when implementing a module-based architecture, but the ModuleManager provides greater control over the modules.

Module domains

By default, a module is loaded into a child domain of the current application domain. You can specify a different application domain by using the applicationDomain property of the ModuleLoader class. Because a module is loaded into a child domain, it owns class definitions that are not in the main application’s domain. For example, the first module to load the PopUpManager class becomes the owner of the PopUpManager class for the entire application because it registers the manager with the SingletonManager. If another module later tries to use the PopUpManager, Adobe ® Flash® Player throws an exception. The solution is to ensure that managers such as PopUpManager and DragManager and any other shared services are defined by the main application (This technique also applies to components). Typically, this is done by adding the following to a script block:


import mx.managers.PopUpManager;

import mx.managers.DragManager;

private var popUpManager:PopUpManager;

private var dragManager:DragManager;

Because a Flex module must be in the same security domain as the application (SWF) that loads it, when you’re using modules in an AIR application any module SWF must be located in the same directory as the main application SWF or one of its subdirectories, which ensures that like the main application SWF, the module SWF is in the AIR application security sandbox.

Creating ActionScript-based modules

If your module does not include any framework code, you can create a class that extends ModuleBase. If you use the ModuleBase class, your module will typically be smaller than if you use a module based on the Module class because it does not have any framework class dependencies.

Reducing module size

Module size varies based on the components and classes that are used in the module. By default, a module includes all framework code that its components depend on, which can cause modules to be large by linking classes that overlap with the application’s classes.

To reduce the size of the modules, you can optimize the module by instructing it to externalize classes that are included by the application. The result is that the module includes only the classes it requires, while the framework code and other dependencies are included in the application.

To externalize framework classes with the command-line compiler, you generate a linker report from the application that loads the modules. You then use this report as input to the module’s load-externs compiler option. The compiler externalizes all classes from the module for which the application contains definitions. This process is also necessary if your modules are in a separate project from your main application in Flex Builder.

1. Generate the linker report and compile the application:
mxmlc -link-report=report.xml MyApplication.mxml

2. Compile the module and pass the linker report to the load-externs option:

mxmlc -load-externs=report.xml MyModule.mxml

Note: If you externalize the module’s dependencies by using the load-externs or optimize option, your module might not be compatible with future versions of Adobe Flex.

Using the ModuleManager class to load modules

To use the ModuleManager to load a module in ActionScript, you first get a reference to the module’s IModuleInfo interface by using the ModuleManager getModule() method. You then call the interface’s load() method.

Finally, you use the factory property of the interface to call the create() method and cast the return value as the module’s class.

1
<mx:application mx="http://www.adobe.com/2006/mxml" creationcomplete="initApp()"><mx:application mx="http://www.adobe.com/2006/mxml" creationcomplete="initApp()"><mx:vbox id="vb1"></mx:vbox></mx:application></mx:application>

import mx.events.ModuleEvent;
import mx.modules.ModuleManager;
import mx.modules.IModuleInfo;
public var info:IModuleInfo;

private function initApp():void {


info = ModuleManager.getModule(“ColumnChartModule.swf”);
info.addEventListener(ModuleEvent.READY, modEventHandler);
// Load the module into memory. Calling load() makes the
// IFlexModuleFactory available. You can then get an
// instance of the class using the factory’s create() method.
info.load();

}

private function modEventHandler(e:ModuleEvent):void {

// Add an instance of the module’s class to the display list.
vb1.addChild(info.factory.create() as ColumnChartModule);

}

See also:
Gerenciamento de memória e tamanho dos arquivos em grandes aplicativos utilizando o Modules do Flex 2.0.1

Fev 22

Lumine + ZendAmf + Flex

Escrito por Fábio Batista da Silva em 1, 4, 6, Adobe Flex, AMF, AR, back, blog, código, código fonte, Desenvolvedor, desenvolvedores, Dica, err, erro, Flex, Flex 2, Flex 3, Flex 4, fonte, IE, int, O, on, Pessoal, PHP, RIA, Ria’s Geral, Tutorial, UI, Ved, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Olá pessoal !!!
Uma das metas que me dei p esse ano de 2010 e colocar esse blog p funcionar de fato.
nos últimos dias postei aqui uma dica sobre Swiz Prototype e tive um otimo feedback oq me incentivou a escrever esse tutorial, uma serie de 5 posts que irão mostrar a integração entre Lumine, ZendAmf e Flex.
Desde já peço desculpas p qualquer erro e espero que possa ser util aos desenvolvedores.

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

O código fonte da aplicação pode ser baixado aqui

Valew pessoal, abraço e até a próxima !!!

Fev 22

Lumine + ZendAmf + Flex 5/5

Escrito por Fábio Batista da Silva em 1, 4, 6, action, Adobe, Adobe Flex, AMF, app, AR, Arquitetura, auto, back, backend, bar, BI, Bindable, busca, class, código, código fonte, control, Controls, DataGrid, DataProvider, demo, Desenvolvedor, desenvolvedores, dispatch, dispatchEvent, email, err, erro, event, EventListener, Evento, Eventos, events, Flex, Flex 2, Flex 3, Flex 4, fonte, for, framework, function, handle, ide, IE, if, Iniciando, Java, label, layout, MXML, Number, O, on, Pessoal, PHP, Projetos, pt, RIA, Ria’s Geral, servidor, tag, TAT, Tema, TextInput, Tutorial, tv, UI, update, Ved, vs, XML, XP, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Lumine + ZendAmf + Flex 5/5

Olá pessoal !!!

Agora que temos nosso backend e regra de negocio pronta podemos implementar nossas views e actions.

Application

Iniciando pelo nosso application que terá apenas as configurações do Swiz e uma instância de nossa view :

<?xml version="1.0" encoding="utf-8"?>
<mx:Application 
	xmlns:mx="http://www.adobe.com/2006/mxml" 
	xmlns:swiz="http://swiz.swizframework.org"
	xmlns:views="br.com.flexria.views.*"
	layout="absolute" xmlns:local="*"
	creationPolicy="all"
	height="100%"
	width="100%">
 
	<local:ApplicationSwizConfig/>
 
	<views:ContactView 
		horizontalCenter="0" 
		verticalCenter="0"
		width="600"
		bottom="20" 
		top="20"/>
</mx:Application>

Views

A aplicação possui 2 view extremamente simples ContactView e PhoneView, sendo que a segunda será utilizado como filha da primeira:

ContactView.mxml

<?xml version="1.0" encoding="utf-8"?>
<mx:Panel 
	xmlns:mx="http://www.adobe.com/2006/mxml"
	xmlns:views="br.com.flexria.views.*" 
 	creationComplete="{init()}"
 	title="Contatos">
	<mx:Script source="actions/ContactAction.as"/>
	<mx:ViewStack id="_vs" width="100%" height="100%">
		<mx:Canvas width="100%" height="100%" id="_canvasList">
			<mx:HBox left="20" right="20" top="5">
				<mx:Label text="Nome"/>
				<mx:TextInput id="_txFind" width="80%"/>
				<mx:Button label="Buscar" click="find()"/>
			</mx:HBox>
			<mx:DataGrid 
				id="_dataGrid"
				top="40"
				left="10"
				right="10"
				bottom="60" 
				doubleClick="update()"
				doubleClickEnabled="true"
				dataProvider="{contactController.dataProvider}" >
				<mx:columns>
					<mx:DataGridColumn headerText="Nome" 	dataField="name"/>
					<mx:DataGridColumn headerText="Email" 	dataField="email"/>
				</mx:columns>
			</mx:DataGrid>
			<mx:ControlBar bottom="10" width="95%" horizontalCenter="0" horizontalAlign="left" verticalAlign="middle">
				<mx:Button label="Novo" 	id="_btnCreate" 	click="{create()}"/>
				<mx:Button label="Editar" 	id="_btnUpdate" 	click="{update()}"		enabled="{_dataGrid.selectedItem!=null}"/>
				<mx:Button label="Remover" 	id="_btnRemove" 	click="{remove()}"		enabled="{_dataGrid.selectedItem!=null}"/>
			</mx:ControlBar>
		</mx:Canvas>
		<mx:Canvas  width="100%" height="100%" id="_canvasForm">
			<mx:TabNavigator width="100%" height="100%">
				<mx:Form 
					top="10"
					left="10"
					right="10"
					bottom="10" 
					borderStyle="solid" label="Contato">
					<mx:FormHeading label="{contact.id>0?'Editando':'Incluindo'} contato"/>
					<mx:FormItem label="Nome:" required="true">
						<mx:TextInput 
							width="339" 
							id="_txtName" 
							text="{contact.name}"/>
					</mx:FormItem>
					<mx:FormItem label="Email:">
						<mx:TextInput 
							width="339" 
							id="_txtEmail" 
							text="{contact.email}"/>
					</mx:FormItem>
					<mx:FormItem width="100%" direction="horizontal">
						<mx:Button label="Cancelar" id="_btnCancel" 	click="{cancel()}"/>
						<mx:Button label="Confirmar" id="_btnConfirm" 	click="{save()}"/>
					</mx:FormItem>
				</mx:Form>
                                <!--Instancia de PhoneView-->
				<views:PhoneView 
					id="_phoneView" 
					contact="{contact}" 
					label="Telefones" 
					enabled="{contact.id>0}"/>
			</mx:TabNavigator>
		</mx:Canvas>
	</mx:ViewStack>
</mx:Panel>

PhoneView.mxml

<?xml version="1.0" encoding="utf-8"?>
<mx:Canvas 
	xmlns:mx="http://www.adobe.com/2006/mxml" 
 	creationComplete="{init()}">
	<mx:Script source="actions/PhoneAction.as"/>
	<mx:ViewStack id="_vs" width="100%" height="100%">
		<mx:Canvas width="100%" height="100%" id="_canvasList">
			<mx:DataGrid 
				id="_dataGrid"
				top="10"
				left="10"
				right="10"
				bottom="60" 
				doubleClick="update()"
				doubleClickEnabled="true"
				dataProvider="{phoneController.dataProvider}" >
				<mx:columns>
					<mx:DataGridColumn headerText="Número" 	dataField="number"/>
				</mx:columns>
			</mx:DataGrid>
			<mx:ControlBar bottom="10" width="95%" horizontalCenter="0" horizontalAlign="left" verticalAlign="middle">
				<mx:Button label="Novo" 	id="_btnCreate" 	click="{create()}"/>
				<mx:Button label="Editar" 	id="_btnUpdate" 	click="{update()}"		enabled="{_dataGrid.selectedItem!=null}"/>
				<mx:Button label="Remover" 	id="_btnRemove" 	click="{remove()}"		enabled="{_dataGrid.selectedItem!=null}"/>
			</mx:ControlBar>
		</mx:Canvas>
		<mx:Canvas  width="100%" height="100%" id="_canvasForm">
			<mx:Form 
				top="10"
				left="10"
				right="10"
				bottom="10" 
				borderStyle="solid">
				<mx:FormHeading label="{phone.id>0?'Editando':'Incluindo'} telefone"/>
				<mx:FormItem label="Número:" required="true">
					<mx:TextInput 
						width="339" 
						id="_txtNumber" 
						text="{phone.number}"/>
				</mx:FormItem>
				<mx:FormItem width="100%" direction="horizontal">
					<mx:Button label="Cancelar" id="_btnCancel" 	click="{cancel()}"/>
					<mx:Button label="Confirmar" id="_btnConfirm" 	click="{save()}"/>
				</mx:FormItem>
			</mx:Form>
		</mx:Canvas>
	</mx:ViewStack>
</mx:Canvas>

Actions

E para finalizar as respectivas Actions para ContactView e PhoneView.
Essas action possuem os métodos que disparam os eventos de chamada ao servidor e métodos handler que serão chamados quando a requisição for completada.
Além disso temos a meta tag [Autowire] que faz a injeção do respectivo controller.
ContactAction.as

import br.com.flexria.controllers.ContactController;
import br.com.flexria.events.ContactEvent;
import br.com.flexria.vo.ContactVO;
import org.swizframework.Swiz;
import mx.events.CloseEvent;
import mx.controls.Alert;
 
 
[Bindable]
private var contact:ContactVO=new ContactVO();
 
[Bindable]
[Autowire]
public var contactController:ContactController;
 
/**
 * init()
 */
private function init():void
{
	find();
 
	Swiz.addEventListener(ContactEvent.SAVE_COMPLETE, saveCompleteHandler);
	Swiz.addEventListener(ContactEvent.REMOVE_COMPLETE, removeCompleteHandler);
}
 
/**
 * create()
 */
private function create():void
{
	contact=new ContactVO();
	_vs.selectedChild=_canvasForm;
}
 
/**
 * update()
 */
private function update():void
{
	contact=_dataGrid.selectedItem as ContactVO;
	_vs.selectedChild=_canvasForm;
}
 
/**
 * cancel()
 */
private function cancel():void
{
	contact=new ContactVO();
	_vs.selectedChild=_canvasList;
}
 
/**
 * find()
 */
private function find():void
{
	_vs.selectedChild=_canvasList;
	var event:ContactEvent=new ContactEvent(ContactEvent.FIND);
	event.contact=new ContactVO();
	event.contact.name=_txFind.text;
	Swiz.dispatchEvent(event);
}
 
/**
 * save()
 */
private function save():void
{
	contact.name=_txtName.text;
	contact.email=_txtEmail.text;
	var event:ContactEvent=new ContactEvent(ContactEvent.SAVE);
	event.contact=contact;
	Swiz.dispatchEvent(event);
}
 
/**
 * remove()
 */
private function remove():void
{
	Alert.show("Deseja realmente excluir o registro selecionado?", "Excluir", Alert.NO | Alert.YES | Alert.NONMODAL, null, function(e:CloseEvent):void
	{
		if (e.detail == Alert.YES)
		{
			contact=_dataGrid.selectedItem as ContactVO;
			var event:ContactEvent=new ContactEvent(ContactEvent.REMOVE);
			event.contact=contact;
			Swiz.dispatchEvent(event);
		}
	});
 
}
 
/**
 * saveCompleteHandler()
 */
private function saveCompleteHandler(event:Event):void
{
	_vs.selectedChild=_canvasList;
	find();
}
 
/**
 * removeCompleteHandler()
 */
private function removeCompleteHandler(event:Event):void
{
	_vs.selectedChild=_canvasList;
	find();
}

PhoneAction.as

import br.com.flexria.controllers.ContactController;
import br.com.flexria.controllers.PhoneController;
import br.com.flexria.events.ContactEvent;
import br.com.flexria.events.PhoneEvent;
import br.com.flexria.vo.ContactVO;
import br.com.flexria.vo.PhoneVO;
import org.swizframework.Swiz;
import mx.events.CloseEvent;
import mx.controls.Alert;
 
[Bindable]
private var _contact:ContactVO;
 
[Bindable]
private var phone:PhoneVO=new PhoneVO();
 
[Bindable]
[Autowire]
public var phoneController:PhoneController;
 
public function set contact(value:ContactVO):void
{
	_contact=value;
	if (_contact != null && _contact.id > 0)
	{
		load();
	}
}
 
/**
 * init()
 */
private function init():void
{
	Swiz.addEventListener(PhoneEvent.SAVE_COMPLETE, saveCompleteHandler);
	Swiz.addEventListener(PhoneEvent.REMOVE_COMPLETE, removeCompleteHandler);
}
 
/**
 * load()
 */
private function load():void
{
	_vs.selectedChild=_canvasList;
	var event:PhoneEvent=new PhoneEvent(PhoneEvent.LOAD);
	event.contact=_contact;
	Swiz.dispatchEvent(event);
}
 
/**
 * create()
 */
private function create():void
{
	phone=new PhoneVO();
	_vs.selectedChild=_canvasForm;
}
 
/**
 * update()
 */
private function update():void
{
	phone=_dataGrid.selectedItem as PhoneVO;
	_vs.selectedChild=_canvasForm;
}
 
/**
 * cancel()
 */
private function cancel():void
{
	phone=new PhoneVO();
	_vs.selectedChild=_canvasList;
}
 
/**
 * save()
 */
private function save():void
{
	phone.contactId=_contact.id;
	phone.number=_txtNumber.text;
	var event:PhoneEvent=new PhoneEvent(PhoneEvent.SAVE);
	event.phone=phone;
	Swiz.dispatchEvent(event);
}
 
/**
 * remove()
 */
private function remove():void
{
	Alert.show("Deseja realmente excluir o registro selecionado?", "Excluir", Alert.NO | Alert.YES | Alert.NONMODAL, null, function(e:CloseEvent):void
	{
		if (e.detail == Alert.YES)
		{
			phone=_dataGrid.selectedItem as PhoneVO;
			var event:PhoneEvent=new PhoneEvent(PhoneEvent.REMOVE);
			event.phone=phone;
			Swiz.dispatchEvent(event);
		}
	});
 
}
 
/**
 * saveCompleteHandler()
 */
private function saveCompleteHandler(event:Event):void
{
	_vs.selectedChild=_canvasList;
	load();
}
 
/**
 * removeCompleteHandler()
 */
private function removeCompleteHandler(event:Event):void
{
	_vs.selectedChild=_canvasList;
	load();
}

Assim finalizamos nossa aplicação !!!

O código fonte da aplicação pode ser baixado aqui

Espero que esse tutorial possa ser utíl aos desenvolvedores PHP que pretendem utilizar essa arquitetura em seus projetos e peço desculpas por algum erro ou se deixei de explicar algo durante o post.
Se houver alguma duvida podem podem perguntar via comentário no post ou email Q respondo na medida do possível..

Abraço a todos e até a próxima !!!!

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

Fev 22

Lumine + ZendAmf + Flex 4/5

Escrito por Fábio Batista da Silva em 1, 4, 6, action, Adobe Flex, AMF, AR, auto, BI, Bindable, boolean, class, classe, classes, collection, control, Controls, DataProvider, demo, Dica, dispatch, dispatchEvent, email, err, erro, error, event, Evento, Eventos, events, flash, Flex, Flex 2, Flex 3, Flex 4, for, framework, function, handle, ide, IE, if, int, Java, lista, map, MXML, Number, O, on, override, Pessoal, PHP, Remoting, RIA, Ria’s Geral, RoR, servidor, string, Sun, tag, TAT, Tutorial, tv, UI, uint, XML, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Lumine + ZendAmf + Flex 4/5

Olá pessoal !!!

Vamos dar continuidade a nossa serie de posts.
no ultimo posto configuramos da nossa aplicação flex, e agora iremos implementar nossas classes de modelo e regra de negocio.

VOs

Começamos criando nossos os VO’s/DTO’s, copias das classes que temos no PHP.
Possuem apenas seus atributos e as meta tag [Bindable] [RemoteClass(alias="xxx")]
Quem Tornam o objeto bindable e mapeiam a classe equivalente no PHP respectivamente.
br.com.flexria.vo.ContactVO e br.com.flexria.vo.PhoneVO

package br.com.flexria.vo
{
	/**
	 * @author Fabio B. Silva
	 */
	[Bindable]
	[RemoteClass(alias="ContactVO")]
	public class ContactVO
	{
		public var id:uint;
		public var name:String;
		public var email:String;
		public var phoneCollection:Array;
 
	}
}
 
package br.com.flexria.vo
{
	/**
	 * @author Fabio B. Silva
	 */
	[Bindable]
	[RemoteClass(alias="PhoneVO")]
	public class PhoneVO
	{
		public var id:uint;
		public var number:String;
		public var contactId:uint;
 
	}
}

Events

E agora os eventos de nossa aplicação que serão utilizados pelo Swiz.
Cada evento possui 6 constantes estáticas que identificarão o evento de chamada ao servidor e o evento de resposta.
br.com.flexria.events.ContactEvent e br.com.flexria.events.PhoneEvent

package br.com.flexria.events
{
	import br.com.flexria.vo.ContactVO;
	import flash.events.Event;
 
	/**
	 * @author Fabio B. Silva
	 */
	public class ContactEvent extends Event
	{
		public static const FIND		:String='ContactEvent.FIND';
		public static const SAVE		:String='ContactEvent.SAVE';
		public static const REMOVE		:String='ContactEvent.REMOVE';
		public static const FIND_COMPLETE	:String='ContactEvent.FIND_COMPLETE';
		public static const SAVE_COMPLETE	:String='ContactEvent.SAVE_COMPLETE';
		public static const REMOVE_COMPLETE	:String='ContactEvent.REMOVE_COMPLETE';
 
 
		public var contact:ContactVO;
 
		public function ContactEvent(type:String, bubbles:Boolean=false, cancelable:Boolean=false)
		{
			super(type, bubbles, cancelable);
		}
 
		public override function clone():Event
		{
			return new ContactEvent(type, bubbles, cancelable);
		}
 
	}
}
 
package br.com.flexria.events
{
	import br.com.flexria.vo.ContactVO;
	import br.com.flexria.vo.PhoneVO;
	import flash.events.Event;
 
	/**
	 * @author Fabio B. Silva
	 */
	public class PhoneEvent extends Event
	{
		public static const LOAD		:String='PhoneEvent.LOAD';
		public static const SAVE		:String='PhoneEvent.SAVE';
		public static const REMOVE		:String='PhoneEvent.REMOVE';
		public static const LOAD_COMPLETE	:String='PhoneEvent.LOAD_COMPLETE';
		public static const SAVE_COMPLETE	:String='PhoneEvent.SAVE_COMPLETE';
		public static const REMOVE_COMPLETE	:String='PhoneEvent.REMOVE_COMPLETE';
 
 
		public var phone:PhoneVO;
		public var contact:ContactVO;
 
		public function PhoneEvent(type:String, bubbles:Boolean=false, cancelable:Boolean=false)
		{
			super(type, bubbles, cancelable);
		}
 
		public override function clone():Event
		{
			return new PhoneEvent(type, bubbles, cancelable);
		}
 
	}
}

Delegates

Vamos então aos delegates que farão as chamadas as métodos remotos do PHP.
Apenas três métodos em cada um deles, para salvar/remover/listar.
Além disso temos a meta tag [Autowire(bean="xxx")] que indica ao Swiz que ali deve ser injetado o bean “xxx” mapeado no BeanLoader.

br.com.flexria.delegates.ContactDelegate e br.com.flexria.delegates.PhoneDelegate

package br.com.flexria.delegates
{
	import mx.rpc.remoting.mxml.RemoteObject;
	import br.com.flexria.vo.ContactVO;
	import mx.rpc.AsyncToken;
 
	/**
	 * @author Fabio B. Silva
	 */
	public class ContactDelegate
	{
		[Autowire(bean="contactRemote")]
		public var contactRemote:RemoteObject;
 
		/**
		 * find()
		 *
		 * @param 	contact:ContactVO
		 * @return 	AsyncToken
		 */
		public function find(contact:ContactVO):AsyncToken
		{
			return contactRemote.find(contact);
		}
 
		/**
		 * save()
		 *
		 * @param 	contact:ContactVO
		 * @return 	AsyncToken
		 */
		public function save(contact:ContactVO):AsyncToken
		{
			return contactRemote.save(contact);
		}
 
		/**
		 * remove()
		 *
		 * @param 	contact:ContactVO
		 * @return 	AsyncToken
		 */
		public function remove(contact:ContactVO):AsyncToken
		{
			return contactRemote.remove(contact);
		}
 
	}
}
 
 
package br.com.flexria.delegates
{
	import mx.rpc.remoting.mxml.RemoteObject;
	import br.com.flexria.vo.ContactVO;
	import br.com.flexria.vo.PhoneVO;
	import mx.rpc.AsyncToken;
 
	/**
	 * @author Fabio B. Silva
	 */
	public class PhoneDelegate
	{
		[Autowire(bean="phoneRemote")]
		public var phoneRemote:RemoteObject;
 
		/**
		 * load()
		 *
		 * @param 	contact:ContactVO
		 * @return 	AsyncToken
		 */
		public function load(contact:ContactVO):AsyncToken
		{
			return phoneRemote.load(contact);
		}
 
		/**
		 * save()
		 *
		 * @param 	phone:PhoneVO
		 * @return 	AsyncToken
		 */
		public function save(phone:PhoneVO):AsyncToken
		{
			return phoneRemote.save(phone);
		}
 
		/**
		 * remove()
		 *
		 * @param 	phone:PhoneVO
		 * @return 	AsyncToken
		 */
		public function remove(phone:PhoneVO):AsyncToken
		{
			return phoneRemote.remove(phone);
		}
 
	}
}

Controllers

Agora podemos implementar nosso controladores.
Eles estendem a classe org.swizframework.controller.AbstractController
e possuem 3 métodos publicos para salvar, remover e listar.
Esses métodos são mapeados pelo Swiz atraves da meta tag [Mediate(event='xxx')] que indica ao Swiz que sempre que o evento ‘xxx’ for disparado esse método deve ser chamado

package br.com.flexria.controllers
{
	import org.swizframework.controller.AbstractController;
	import br.com.flexria.delegates.ContactDelegate;
	import br.com.flexria.events.ContactEvent;
	import mx.collections.ArrayCollection;
	import mx.rpc.events.ResultEvent;
	import mx.rpc.events.FaultEvent;
	import org.swizframework.Swiz;
	import mx.controls.Alert;
 
 
	/**
	 * @author Fabio B. Silva
	 */
	[Bindable]
	public class ContactController extends AbstractController
	{
		[Autowire]
		public var contactDelegate:ContactDelegate;
 
		public var dataProvider:ArrayCollection;
 
 
		/**
		 * find()
		 *
		 * @param 	e:ContactEvent
		 */
		[Mediate(event='ContactEvent.FIND')]
		public function find(e:ContactEvent):void
		{
			executeServiceCall(contactDelegate.find(e.contact), findHandler, faultHandler);
		}
 
		/**
		 * save()
		 *
		 * @param 	e:ContactEvent
		 */
		[Mediate(event='ContactEvent.SAVE')]
		public function salve(e:ContactEvent):void
		{
			executeServiceCall(contactDelegate.save(e.contact), saveHandler, faultHandler);
		}
 
		/**
		 * remove()
		 *
		 * @param 	e:ContactEvent
		 */
		[Mediate(event='ContactEvent.REMOVE')]
		public function remove(e:ContactEvent):void
		{
			executeServiceCall(contactDelegate.remove(e.contact), removeHandler, faultHandler);
		}
 
		/**
		 * findHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		private function findHandler(e:ResultEvent):void
		{
			dataProvider=new ArrayCollection(e.result as Array);
			Swiz.dispatchEvent(new ContactEvent(ContactEvent.FIND_COMPLETE));
		}
 
		/**
		 * saveHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		private function saveHandler(e:ResultEvent):void
		{
			Swiz.dispatchEvent(new ContactEvent(ContactEvent.SAVE_COMPLETE));
		}
 
		/**
		 * removeHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		private function removeHandler(e:ResultEvent):void
		{
			Swiz.dispatchEvent(new ContactEvent(ContactEvent.REMOVE_COMPLETE));
		}
 
		/**
		 * faultHandler()
		 *
		 * @param 	e:FaultEvent
		 */
		private function faultHandler(e:FaultEvent):void
		{
			Alert.show(e.fault.message, "ERROR");
		}
 
	}
}
 
 
package br.com.flexria.controllers
{
	import org.swizframework.controller.AbstractController;
	import br.com.flexria.delegates.PhoneDelegate;
	import br.com.flexria.events.PhoneEvent;
	import mx.collections.ArrayCollection;
	import mx.rpc.events.ResultEvent;
	import mx.rpc.events.FaultEvent;
	import org.swizframework.Swiz;
	import mx.controls.Alert;
 
 
	/**
	 * @author Fabio B. Silva
	 */
	[Bindable]
	public class PhoneController extends AbstractController
	{
		[Autowire]
		public var phoneDelegate:PhoneDelegate;
 
		public var dataProvider:ArrayCollection;
 
 
		/**
		 * find()
		 *
		 * @param 	e:PhoneEvent
		 */
		[Mediate(event='PhoneEvent.LOAD')]
		public function find(e:PhoneEvent):void
		{
			executeServiceCall(phoneDelegate.load(e.contact), loadHandler, faultHandler);
		}
 
		/**
		 * save()
		 *
		 * @param 	e:PhoneEvent
		 */
		[Mediate(event='PhoneEvent.SAVE')]
		public function salve(e:PhoneEvent):void
		{
			executeServiceCall(phoneDelegate.save(e.phone), saveHandler, faultHandler);
		}
 
		/**
		 * remove()
		 *
		 * @param 	e:PhoneEvent
		 */
		[Mediate(event='PhoneEvent.REMOVE')]
		public function remove(e:PhoneEvent):void
		{
			executeServiceCall(phoneDelegate.remove(e.phone), removeHandler, faultHandler);
		}
 
 
 
 
		/**
		 * findHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		public function loadHandler(e:ResultEvent):void
		{
			dataProvider=new ArrayCollection(e.result as Array);
			Swiz.dispatchEvent(new PhoneEvent(PhoneEvent.LOAD_COMPLETE));
		}
 
		/**
		 * saveHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		public function saveHandler(e:ResultEvent):void
		{
			Swiz.dispatchEvent(new PhoneEvent(PhoneEvent.SAVE_COMPLETE));
		}
 
		/**
		 * removeHandler()
		 *
		 * @param 	e:ResultEvent
		 */
		public function removeHandler(e:ResultEvent):void
		{
			Swiz.dispatchEvent(new PhoneEvent(PhoneEvent.REMOVE_COMPLETE));
		}
 
		/**
		 * faultHandler()
		 *
		 * @param 	e:FaultEvent
		 */
		public function faultHandler(e:FaultEvent):void
		{
			Alert.show(e.fault.message, "ERROR");
		}
 
	}
}

Com nossa regra de negocio pronta podemos implementar nossas views e actions.
que é o assunto do próximo post : Tutorial : Lumine + ZendAmf + Flex 5/5

Até já !!!

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

Fev 22

Lumine + ZendAmf + Flex 3/5

Escrito por Fábio Batista da Silva em 1, 4, 6, Adobe, Adobe Flex, AMF, app, AR, as3, auto, back, backend, bug, class, control, Debug, demo, event, events, Flex, Flex 2, Flex 3, Flex 4, for, framework, frontend, IE, if, image, int, map, Messaging, mg, MXML, O, on, Pessoal, PHP, Projetos, pt, Remoting, RIA, Ria’s Geral, Swiz Framework, Tutorial, UI, uint, XML, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Lumine + ZendAmf + Flex 3/5

Olá pessoal !!!

Vamos dar continuidade aos posts anteriores que trataram do Backend da nossa aplicação.
Nesse post vamos codificar o frontend da nossa aplicação, para isso vamos utilizar a dubla que se tornou titular em meus projetos : Flex + Swiz framework.

Flex Project

A estrutura do nosso Flex Project fica da seguinte forma :

Estrutura do projeto flex

Estrutura do projeto flex

Flex Compiler

Como estamos usando Swiz e as configurações de remote através do services.xml precisamos adicionar alguns argumento ao Flex Compiler, nesse caso ficou assim : -locale en_US -services=..services.xml -keep-as3-metadata+=Autowire.

RemotingService

Agora podemos configurar nosso RemotingService com o arquivo services.xml
Lembrando que o endpoint uri deve ser alterado para apontar para o seu projeto php
services.xml

<?xml version="1.0" encoding="UTF-8"?>
<services-config>
    <services>
        <service id="zend-service"
            class="flex.messaging.services.RemotingService"
            messageTypes="flex.messaging.messages.RemotingMessage">
            <destination id="zend">
                <channels>
                    <channel ref="zend-endpoint"/>
                </channels>
                <properties>
                    <source>*</source>
                </properties>
            </destination>
        </service>
    </services>
    <channels>
        <channel-definition id="zend-endpoint"
            class="mx.messaging.channels.AMFChannel">
            <endpoint uri="http://localhost/lumine-zend-flex/php/gateway.php"
                class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>
    </channels>
</services-config>

Swiz

Então podemos configurar o Swiz para isso temos 2 arquivos :
ApplicationSwizConfig.mxml : Responsável pelas configurações básicas do Swiz
ApplicationBeans.mxml : Responsável pelo mapeamento dos nossos beans

ApplicationSwizConfig.mxml

<?xml version="1.0" encoding="utf-8"?>
<swizframework:SwizConfig
	xmlns:mx="http://www.adobe.com/2006/mxml" 
	xmlns:swizframework="org.swizframework.*"
	eventPackages="{['br.com.flexria.events']}"
	viewPackages="{['br.com.flexria.view']}"
	logEventLevel="{LogEventLevel.DEBUG}"
	beanLoaders="{[ApplicationBeans]}"
	injectionEvent="preinitialize"
	mediateBubbledEvents="true"
	strict="true">
 
	<mx:Script>
		<![CDATA[
			import mx.logging.LogEventLevel;
		]]>
	</mx:Script>
 
	<mx:TraceTarget id="logTarget"
		includeCategory="true"
	    includeLevel="true" 
	    includeDate="true" 
	    includeTime="true"/>
 
</swizframework:SwizConfig>

ApplicationBeans.mxml

<?xml version="1.0" encoding="utf-8"?>
<BeanLoader xmlns="org.swizframework.util.*"
		xmlns:mx="http://www.adobe.com/2006/mxml"
		xmlns:factory="org.swizframework.factory.*"
		xmlns:delegates="br.com.flexria.delegates.*"
		xmlns:controllers="br.com.flexria.controllers.*">
 
   <!--DELEGATES-->
   <delegates:ContactDelegate 	id="contactDelegate"/>
   <delegates:PhoneDelegate 	id="phoneDelegate"/>
 
   <!--CONTROLLERS-->
   <controllers:ContactController   id="contactController"/>
   <controllers:PhoneController   id="phoneController"/>
 
   <!--REMOTES-->
   <mx:RemoteObject destination="zend"   id="contactRemote" source="ContactService" />
   <mx:RemoteObject destination="zend"   id="phoneRemote"   source="PhoneService" />
 
</BeanLoader>

Agora que temos nosso projeto flex configurado e podemos começar a codificar p valer : Tutorial : Lumine + ZendAmf + Flex 4/5

Até já !!!

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

Fev 22

Lumine + ZendAmf + Flex 2/5

Escrito por Fábio Batista da Silva em 1, 4, 6, Adobe Flex, AMF, AR, arte, auto, back, backend, camp, class, classe, classes, código, collection, dados, demo, Desenvolvimento, email, Flex, Flex 2, Flex 3, Flex 4, for, framework, function, html, IE, int, lista, Number, O, on, Outros, padrão, Pessoal, PHP, Projetos, rest, RIA, Ria’s Geral, serviço, Tutorial, tv, UI, update, XP, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Lumine + ZendAmf + Flex 2/5

Olá pessoal !!!

No post anterior configuramos nosso projeto php com Lumine e ZendAmf.
Essa parte que veremos agora se refere as nossas classes de “modelo” : VO’s e ActiveRecord’s.
Pode parecer meio confuso ou “Muito código” porem tudo isso pode ser gerado no Lumine de maneira bem pratica e rápida através do Lumine reverse.

Entaum vamos lá !!!

ActiveRecord

O Lumine é um ORM Brasileiro para php que utiliza ActiveRecord.
Eu particularmente não gosto muito do padrão ActiveRecord nem do Lumine
porem outros ORM para php como Doctrine e Zend_Db não possuem integração com VO’s/DTO’s.
Então acabei adotando ele como padrão para meus projetos flex + php devido a agilidade no desenvolvimento.

as classes de ActiveRecord estendem o Lumine_Base e possuem o método _initialize que configura os campos da tabela e seus relacionamentos.
Temos então duas classes Contact e Phone.

models/entities/Contact.php e models/entities/Phone.php

class Contact extends Lumine_Base {
 
    protected $_tablename = 'contact';
    protected $_package   = 'models.entities';
 
    public $id;
    public $name;
    public $email;
 
    public $phoneCollection = array();
 
    /**
     * Inicia os valores da classe
     * @return void
     */
    protected function _initialize() {
 
        $this->_addField("id",      "id",       "int",      10,     array('primary' => true, 'notnull' => true, 'autoincrement' => true));
        $this->_addField("name",    "name",     "varchar",  200,    array('notnull' => true));
        $this->_addField("email",   "email",    "varchar",  200,    array());
 
        $this->_addForeignRelation("phoneCollection", self::ONE_TO_MANY, "Phone", "contactId", null, null, null);
    }
}
 
 
class Phone extends Lumine_Base {
 
    protected $_tablename = 'phone';
    protected $_package   = 'models.entities';
 
    public $id;
    public $number;
    public $contactId;
 
    /**
     * Inicia os valores da classe
     * @return void
     */
    protected function _initialize() {
        $this->_addField("id",      "id",       "int",      10,     array('primary' => true, 'notnull' => true, 'autoincrement' => true));
        $this->_addField("number",  "number",   "varchar",  45,     array());
 
        $this->_addField("contactId","contactId",  "int", 10, array(
                'notnull' => true,
                'foreign' => '1',
                'onUpdate' => 'RESTRICT',
                'onDelete' => 'RESTRICT',
                'linkOn' => 'id',
                'class' => 'Contact')
        );
    }
}

VO

Temos também os seus respectivos VO’s/DTO’s para o transporte do dados entre o php e o flex:models/vo/ContactVO.php e models/vo/PhoneVO.php

class ContactVO {
 
    public $id;
    public $name;
    public $email;
    public $phoneCollection = array();
 
    public $_explicitType = 'ContactVO';
}
 
class PhoneVO {
 
    public $id;
    public $number;
    public $contactId;
 
    public $_explicitType = 'PhoneVO';
}

Services

E finalmente nossas classes de serviço apenas três métodos para: salvar, remover e listar:
services/ContactService.php e services/PhoneService.php

class ContactService {
 
    /**
     * @var Contact
     */
    private $contact;
 
    /**
     * construct
     */
    public function __construct() {
        $this->contact = new Contact();
    }
 
    /**
     * getContact()
     *
     * @return Contact
     */
    public function getContact() {
        return $this->contact;
    }
 
    /**
     * findAll()
     *
     * @param   ContactVO $contact
     * @return  array<ContactVO>
     */
    public function find(ContactVO $contact) {
        $this->getContact()->find();
        return $this->getContact()->allToObject();
    }
 
    /**
     * save()
     *
     * @param  ContactVO $contact
     * @return ContactVO $contact
     */
    public function save(ContactVO $contact) {
        $this->getContact()->setFrom($contact);
        $this->getContact()->save();
        return $this->getContact()->toObject();
    }
 
    /**
     * remove()
     *
     * @param  ContactVO $contact
     * @return ContactVO $contact
     */
     public function remove(ContactVO $contact) {
        $phone = new Phone();
        $phone->where("contactId = '{$contact->id}'");
        $phone->delete(true);
 
        $this->getContact()->setFrom($contact);
        $this->getContact()->delete();
        return $this->getContact()->toObject();
    }
}
 
 
 
class PhoneService {
 
    /**
     * @var Phone
     */
    private $phone;
 
    /**
     * construct
     */
    public function __construct() {
        $this->phone = new Phone();
    }
 
    /**
     * getPhone()
     *
     * @return Phone
     */
    public function getPhone() {
        return $this->phone;
    }
 
    /**
     * load()
     *
     * @param   ContactVO $contact
     * @return  array<PhoneVO>
     */
    public function load(ContactVO $contact) {
        $this->getPhone()->where("contactId = '{$contact->id}'");
        $this->getPhone()->find();
        return $this->getPhone()->allToObject();
    }
 
    /**
     * save()
     *
     * @param  PhoneVO $phone
     * @return PhoneVO $phone
     */
    public function save(PhoneVO $phone) {
        $this->getPhone()->setFrom($phone);
        $this->getPhone()->save();
        return $this->getPhone()->toObject();
    }
 
    /**
     * remove()
     *
     * @param  PhoneVO $phone
     * @return PhoneVO $phone
     */
    public function remove(PhoneVO $phone) {
        $this->getPhone()->setFrom($phone);
        $this->getPhone()->delete();
        return $this->getPhone()->toObject();
    }
 
}

Com isso finalizamos tudo que precisamos em nosso Backend
e podemos partir para a aplicação flex : Tutorial : Lumine + ZendAmf + Flex 3/5

Até já !!!

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

Fev 22

Lumine + ZendAmf + Flex 1/5

Escrito por Fábio Batista da Silva em 1, 4, 6, abas, Adobe Flex, AMF, app, AR, auto, back, backend, BI, class, classe, classes, código, configuração, dados, demo, Dica, Download, email, engine, err, erro, error, Flex, Flex 2, Flex 3, Flex 4, for, framework, function, game, handle, IE, image, int, library, Links, mg, mysql, Number, O, on, Password, Pessoal, PHP, Projetos, pt, reference, RIA, Ria’s Geral, RoR, server, Tecnologia, Tutorial, UI, uint, zend, zendAMF, zendFramework @ 02 22nd, 2010 | via http://www.flexria.com.br/home | Sem comentários
Fábio Batista da Silva
? X
  • Bookmarks

Blinkbits BlinkLists BlogLines Blogmarks Buddymarks CiteULike Co.mments Del.icio.us Digg Diigo

Fark Feed Me Links Furl Google Linkagogo ma.gnolia Mister Wong Newsvine Propeller Rawsugar

Reddit Rojo Simpy Sphinn Spurl Squidoo StumbleUpon Tailrank Technorati Yahoo

More »

Lumine + ZendAmf + Flex 1/5

Olá pessoal !!!

Peço desculpas para os iniciantes mas este tutorial vai ser p pessoal + avançado, Então temos como requisito para esse tutorial que o leitor tenha um conhecimento básico de Lumine, ZendAmf e Flex.
Vou tentar focar na integração e não nas tecnologias utilizadas. Então vai ser bastante código e pouca teoria.

Parar o Backend vamos utilizar um trio que p mim tem se mostrado bastante produtivo nos últimos projetos e que pode ser baixada nos seguintes links: MYSQL + Lumine + ZendAmf

Base de Dados

Nossa base de dados será bem simples apenas 2 tabelas com um relacionamento 1 X N:

CREATE  DATABASE `lumine_zend_flex`;
 
CREATE TABLE  `contact` (
  `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,
  `name` varchar(200) NOT NULL,
  `email` varchar(200) DEFAULT NULL,
  PRIMARY KEY  (`id`)
) ENGINE=InnoDB;
 
CREATE TABLE  `phone` (
  `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,
  `number` varchar(45) NOT NULL,
  `contactId` int(10) UNSIGNED NOT NULL,
  PRIMARY KEY  (`id`),
  KEY `fk_phone_contact` (`contactId`),
  CONSTRAINT `fk_phone_contact` FOREIGN KEY (`contactId`) REFERENCES `contact` (`id`)
) ENGINE=InnoDB;

PHP Project

Bom, depois das libs baixadas e da base instalada vamos configurar nosso projeto php.
A estrutura fica da seguinte forma :

Estrutura do projeto php

Estrutura do projeto php

Arquivos de configuração

Temos 2 arquivos de configuração em nosso projeto
gateway.php : gateway para chamadas amf
lumine-conf.php : Arquivo de configuração do Lumine

gateway.php

//adiciona diretorios ao include path
set_include_path('.'
        . PATH_SEPARATOR . './library/'
        . PATH_SEPARATOR . './services/'
        . PATH_SEPARATOR . './models/vo/'
        . PATH_SEPARATOR . './models/entities/'
        . PATH_SEPARATOR . get_include_path()
);
 
 
//inclui bibliotecas
require_once 'lumine-conf.php';
require_once 'Lumine/Lumine.php';
require_once 'Zend/Loader/Autoloader.php';
require_once 'ApplicationLoader.php';
 
 
 
//seta tempo infinito de execucao
set_time_limit(0);
 
//Mostrar todos os erros independente qual seja
error_reporting(E_ALL|E_STRICT);
 
// indica o timezone padrao
date_default_timezone_set('Brazil/East');
 
// auto-carregamento de classes de Lumine
spl_autoload_register(array('Lumine','Import'));
 
// auto-carregamento de classes DTO de Lumine
spl_autoload_register(array('Lumine','ImportDTO'));
 
// instancia uma configuracao do lumine
$cfg = new Lumine_Configuration($lumineConfig);
 
// registra uma funcao para o fechamento da conexao ao termino do script
register_shutdown_function(array($cfg->getConnection(),'close'));
 
// carregamento automatico das classes zend
Zend_Loader_Autoloader::getInstance();
 
// carregamento automatico das classes da aplicação
ApplicationLoader::getInstance();
 
$server = new Zend_Amf_Server();
$server->addDirectory('./services/');
$server->addDirectory('./models/vo/');
echo($server->handle());

lumine-conf.php

$lumineConfig = array(
        'dialect'   => 'MySQL',
        'port'      => '3306',
        'user'      => 'xxxx',
        'password'  => 'xxxx',
        'host'      => 'localhost',
        'database'  => 'lumine_zend_flex',
        'package'   => 'models.entities',
        'class_path'=> 'xxxx\www\lumine-zend-flex\php',
 
        'options' => array(
                'auto_cast_dto' => '1',
                'dto_format'    => '%sVO',
                'dto_package'   => 'models.vo',
        )
);

Com isso finalizamos a configuração da Base de dados, Lumine e ZendAmf.
Agora podemos partir para a configuração das nossas classes de modelo de dados:
Tutorial : Lumine + ZendAmf + Flex 2/5

Até já !!!

Tutorial : Lumine + ZendAmf + Flex 1/5
Tutorial : Lumine + ZendAmf + Flex 2/5
Tutorial : Lumine + ZendAmf + Flex 3/5
Tutorial : Lumine + ZendAmf + Flex 4/5
Tutorial : Lumine + ZendAmf + Flex 5/5

|

ACERCA

O que é o RedeRIA ?

O redeRIA não é nada mais que um agregador de feed's que disponibiliza o conteudo de varios blogs e autores ao redor do mundo RIA, actualmente agregamos mais de 2755 entradas vindas de 53 blogs especializados em ria’s, pelo que só fica a ganhar em assinar o feed ou seguir a comunidade no twitter.

Se acha que o seu blog ou um blog de um amigo é interessante e util para os leitores o redeRIA, faça a sua submissão aqui.

Feed: assine já
Twitter: siga-nos

GOOGLE

Votação


Deveria o RedeRia agregar conteúdo em inglês?
Ver Resultados

AUTORES


Eduardo KrausAlexandre TadashiBindableCognitiva SoluçõesDaniel LopesDaniel SchmitzDanielPedrinhaDClick TeamEbercomEdgard DavidsonElvis FernandesErko BrideeFabiel PrestesFábio Batista da SilvaFabio da SilvaFabriccio BernardesFelipe BorellaFlavia MoreiraGabriel VersalliniGabriela T. PerryIgor MusardoJanderson CardosoJoão AugustoJose Carlos FielKelps SousaLeonardo FrançaLucas MarçalLuis MessiasLuiz TarabalMario JuniorMário SantosMauro MartinsPablo SouzaPedro ClaudioreneRia BrazilriaPTRicardo CerqueiraRobson FernandesRodrigo Pereira FragaSaintBrSamuelFacchinelloSergio SouzaSilva DeveloperStefan HorochovecTech CaffeTecinforThiago BuenoVedVinícius SandimWillian ManoXAML Cast

PUBLICIDADE








Powered by Wordpress & msdevstudio.com