Flex Pasta

Try Penne, have more fun adding new features!

I ponder a simple Cairngorm vs. Penne example. I want to add on to the Italian Store(find the code under Introducing The Penne Framework). I want to add a feature to the application to allow the user to delete a pasta type.

Using Cairngorm:

1. Add a trash can to the datagrid.
2. Add a new class DeletePastaTypeEvent.
3. Implement the clone method with the deleted pasta type as payload. Create a static variable for the event type making sure the “type string” hasn’t been used anywhere else.
4. Invoke the event from the trash can click handler.
5. Add a new DeletePastaTypeCommand.
6. Add a new method “deletePastaType()” in the PastaTypeDelegate Class.
7. Add a line in FrontController mapping the DeletePastaTypeEvent to the DeletePastaTypeCommand.
8. Fill in all the execute, result, fault methods in DeletePastaTypeCommand with the cookie cutter code.

Eight steps, which doesn’t even include having to add or change a model locator.

Using Penne:

1. Add a trash can to the datagrid.
2. Add a new method “deletePastaType()” in the IPastaRemoteRq, implementing it in PastaRemoteRq.
3. Add a new method “deletePastaType(pastaTypes:ArrayCollection)” in the IPastaRemoteRs, implementing it in PastaRemoteRs.
4. Invoke the request method from the trash can click handler.

Twice as many steps in Cairngorm vs Penne. Penne also required no class creation, vs two with Cairngorm. When looking at my datagrid in Penne, I can click right through to the deletePastaType and see what is happening. With Cairngorm, I have to dig up another file, DeletePastaTypeCommand.

I welcome your comments and feedback.