I read your code but I can&#39;t understand why there are so many classes to provide such an API.<div><br></div><div><br></div><div>Ben<br><br><div class="gmail_quote">2012/2/1 S Krish <span dir="ltr">&lt;<a href="mailto:krishnamachari.sudhakar@gmail.com">krishnamachari.sudhakar@gmail.com</a>&gt;</span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I will provide this by the weekend<div><br></div><div>The code though has tests which are quite explanatory and the classside method of the ApplicationFrameworkdDocumentation has 6 odd methods that lead on from intent, what Pharo provides which maybe leveraged in future if not now and the current implementation as well as a roadmap.</div>

<div><br></div><div>I will read your specs and implementation to merge the stuff I envisage with��<div><div class="h5"><br><br><div class="gmail_quote">On Wed, Feb 1, 2012 at 5:14 AM, Benjamin <span dir="ltr">&lt;<a href="mailto:benjamin.vanryseghem.pharo@gmail.com" target="_blank">benjamin.vanryseghem.pharo@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">If you have around the pdf you are talking about on your website, I will be glad to read it.<div>

<br></div><div><br></div><div>Thanks in advance ;)</div><div><br></div><div>Ben</div><div><br><div><div><div>On Jan 31, 2012, at 5:58 AM, S Krish wrote:</div><br></div><div><div><blockquote type="cite">
<a href="http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework-aka-morphic-view-framework/" target="_blank">http://skrishnamachari.wordpress.com/2012/01/31/pharo-application-framework-aka-morphic-view-framework/</a><div>


<br></div><div>Obliged for feedback ...</div><div><br></div><div>For details and links..</div><div><span style="color:rgb(51,51,51);font-family:Verdana;font-size:12px;line-height:16px"><p>
Sharing this little framework that should go some way to ease creating large applications ( currently morphic oriented).</p><p>AbstractMorphicView subclass: #MyNewView ���</p><p>#createMorphsSpecs</p><p>^{</p><p>���panel1��� -&gt; #SomeOtherView.<br>


���label1��� -&gt; #LabelMorph.<br>���text1��� -&gt; #PluggableTextMorph.<br>���button1��� -&gt; #PluggableButtonMorph.<br>}</p><p>layoutSpecsArray</p><p>^{<br>���widgetNameInMorphsDictionary��� -&gt; {<br>#fractions -&gt; (0 @ 0 corner: 1 @ 0.5). ��� fractional value 0 to 1 range ���<br>


#offsets -&gt; (10 @ 10 corner: 0 @ 0). ��� offsets relative to the fractional position ���<br>}.</p><p>������ add other widgetspecs������<br>}</p><p>Thats it.. you should have a prototype UI neatly laid out.. and then specify: #morphsPrimaryPropertiesSpecs and #morphsSecondaryPropertiesSpecs for full functionality that composes views inside views and scales well.</p>

<p>AbstractSimpleMorphicView can make it simpler for TableLayout stuff without requiring #layoutSpecsArray.</p><p>..... the main post has other details and links to package...</p></span></div>
</blockquote></div></div></div><br></div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div>