<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I agree with Pete ,there is definitely a lot of wiring that is currently going in building the remote object. Also I am not a big fan of dynamic typing
. I still think that code generation will solve both problems. I can understand the reluctance to use it, however I just can’t get past the dynamic typing issue though. Code generation will allow us to automatically create the wiring needed for the remote
object as well as remove the dynamic typing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I would love it if you made the faces messages agnostic! That would really reduce some of the code we had to create to integrate with messages and the lifecycle.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Venkat and I would love to see FlexBooking and documentation included into Seam examples at some point. If you guys could host the SVN there I think that
would be a great idea, it will give us all a common spot to collaborate. Just give me the location and I will up load the project.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">The booking application can be downloaded from
<a href="http://www.rationaldeveloper.com/downloads/granite/FlexBooking.zip">www.rationaldeveloper.com/downloads/granite/FlexBooking.zip</a> (Granite Version)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I included the granite seam code in the email, the whole project can be retrieved from the latest svn<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><a href="http://granite.svn.sourceforge.net/viewvc/granite/graniteds/trunk/">http://granite.svn.sourceforge.net/viewvc/granite/graniteds/trunk/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">I do have the blaze code available however there Is an issue with Flex 3 beta 3 and the way I am moving information back and forth. Sooo that means it's broken
right now. ;)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Keith Naas [mailto:keithnaas@gmail.com]
<br>
<b>Sent:</b> February 18, 2008 2:42 PM<br>
<b>To:</b> Pete Muir<br>
<b>Cc:</b> seam-dev@lists.jboss.org; Cameron Ingram; James Ward; Shashank Tiwari; Felipe Albertao; Blue; Chris Maki; Kunal Bajaj<br>
<b>Subject:</b> Re: Seam with Flex<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Since James asked so nicely, Kunal and I started working on a maven-flex-plugin. We plan on supporting swf/swc compilation, maven dependencies, asdoc generation, and automatic FlexBuilder artifact generation (e.g. namespace mappings, flexlibproperties,
actionscriptproperties). <br>
<br>
After seeing Cameron's great presentation, we were also thinking about the facesMessages/dataModel, validation, and automatic conversation handling. We were also wondering if it makes sense to tie into Seam's Component Driven Events.
<br>
<br>
I believe Kunal has been investigating how to get Flex to play better with Seam Security.
<br>
<br>
Keith Naas<o:p></o:p></p>
<div>
<p class="MsoNormal">On Feb 18, 2008 2:06 PM, Pete Muir <<a href="mailto:pmuir@bleepbleep.org.uk">pmuir@bleepbleep.org.uk</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">To consolidate various discussions on Seam with Flex.<br>
<br>
I liked the look of what Cameron had at JBW though there still seems<br>
to be quite a lot of wiring stuff in there - Cameron and I discussed<br>
this, and he thinks we can at least use code generation to help here.<br>
<br>
We need to make facesMessages view layer agnostic so that it can work<br>
with Wicket or Flex as well.<br>
<br>
We are very happy to host this on SeamFramework.org, Seam SVN,<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a> for discussions and Seam JIRA for issue<br>
tracking if that works well for everyone. At least, I would love to<br>
see an example distributed with Seam, and some documentation in the<br>
reference manual.<br>
<br>
Cameron, where can I download the booking application you were showing<br>
off at JBossWorld? I want to look at your DataModel adaptor in<br>
particular - see if we can't ease this integration some.<br>
<br>
What do people thing?<br>
<span style="color:#888888"><br>
--<br>
Pete Muir<br>
<a href="http://in.relation.to/Bloggers/Pete" target="_blank">http://in.relation.to/Bloggers/Pete</a><br>
<a href="http://www.seamframework.org" target="_blank">http://www.seamframework.org</a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">-----------------------------------------------------------------------<br>
This e-mail is intended for the addressee shown.<br>
It contains information that is confidential and<br>
protected from disclosure. Any review, dissemination<br>
or use of this transmission or its contents by persons<br>
or unauthorized employees of the intended organizations<br>
is strictly prohibited.<br>
<br>
The contents of this email do not necessarily represent<br>
the views or policies of PSCU Financial Services.<br>
</font>
</body>
</html>