<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/transmogrify/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/transmogrify/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 23 Mar 2007 09:39:21 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/transmogrify/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Refactoring via XSLT Transformation of AST Tree</title><link>https://sourceforge.net/p/transmogrify/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I think you could map the AST tree to XML then easily do refactoring using a standard technology like XSLT.&lt;/p&gt;
&lt;p&gt;Then people could write refactoring snippets easily and quickly. &lt;/p&gt;
&lt;p&gt;Furthermore you could easily store the AST Tree in binary XML form in the Database.&lt;/p&gt;
&lt;p&gt;I attempt to write a patch to do this.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">warren crossing</dc:creator><pubDate>Fri, 23 Mar 2007 09:39:21 -0000</pubDate><guid>https://sourceforge.netc23e32750c5c4327325f4e0b55b535b0bfaf5355</guid></item><item><title>CommentDef</title><link>https://sourceforge.net/p/transmogrify/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;Firstofall, I think this Transmogrify idea is great. I plan to realize some special refactorings on top &lt;br /&gt;
of it. Therefore I got the following feature request.&lt;/p&gt;
&lt;p&gt;It would be great to have the source code comments as part of the tree. I propose this because I &lt;br /&gt;
would like to analyse the comments especially for methods and classes.&lt;br /&gt;
A possible solution for this might be to include a CommentDef class into the symtab package that &lt;br /&gt;
could be accessed as part of the normal ast. That shouldn't be too complicated to realize, I think &lt;br /&gt;
from my poor understanding of the parser and grammar internals. An advanced solution would be to &lt;br /&gt;
have an access method at class ClassDef to get the comment for the method.&lt;br /&gt;
For any modification it would be suitable to have the option to set the comment text via the ast &lt;br /&gt;
tree node like any other changes to the ast.&lt;/p&gt;
&lt;p&gt;What do you think of this idea? Do you have any proposals how I might be able to realize it myself?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;
Martin&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Lippert</dc:creator><pubDate>Fri, 03 Aug 2001 20:47:36 -0000</pubDate><guid>https://sourceforge.net422af9d4be7ee44e3a7b1c604aef73bd65defd8c</guid></item><item><title>refatoring to patterns</title><link>https://sourceforge.net/p/transmogrify/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;OK - this is a stretch, but is there any plan to do symantic analysis on source code for potential &lt;br /&gt;
matches to &amp;amp;quot;known&amp;amp;quot; &amp;amp;quot;popular&amp;amp;quot; patterns such as &lt;/p&gt;
&lt;p&gt;Encapsulate Constructors with Factory Methods &lt;br /&gt;
Encapsulate Subclasses with Factory Methods &lt;br /&gt;
Replace Primitive Tree Construction with Composite &lt;br /&gt;
Encapsulate Composite with Builder &lt;br /&gt;
Extract Special-Case Logic into Decorators &lt;br /&gt;
Replace Hard-Coded Notifications with Observer &lt;br /&gt;
Move Accumulation to Collecting Parameter (draft) &lt;br /&gt;
Replace One/Many Distinctions with Composite (draft) &lt;/p&gt;
&lt;p&gt;as i've seen on &lt;a href="http://www.industriallogic.com/xp/refactoring/" rel="nofollow"&gt;http://www.industriallogic.com/xp/refactoring/&lt;/a&gt; ?&lt;/p&gt;
&lt;p&gt;i would think that an automated tool like that that could dig through hundreds or thousands of&lt;br /&gt;
documents of source code might be very interesting and revealing if feasible.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew Sandoz</dc:creator><pubDate>Tue, 24 Jul 2001 05:29:50 -0000</pubDate><guid>https://sourceforge.nete7c0538bc1d2cc87b043307055278bd83fd853a1</guid></item><item><title>Tree should have some persistent form</title><link>https://sourceforge.net/p/transmogrify/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In fact, when the source base is large, it takes a lot &lt;br /&gt;
of time to parse source code and to resolve a tree. &lt;br /&gt;
There should be some mechanism, which will enable to &lt;br /&gt;
save the built tree for the future usage.&lt;/p&gt;
&lt;p&gt;The simpliest solution is to make a tree serializable.&lt;br /&gt;
The more advanced one is to create ORDBMS mapping and &lt;br /&gt;
to save tree there.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Aizatsky</dc:creator><pubDate>Fri, 22 Jun 2001 08:19:32 -0000</pubDate><guid>https://sourceforge.net167c093e541f4a3571dea00121486c52bb200a06</guid></item><item><title>IMethod Modifiers Access</title><link>https://sourceforge.net/p/transmogrify/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;IMethod should directly provide an access to the &lt;br /&gt;
method modifiers.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike Aizatsky</dc:creator><pubDate>Mon, 18 Jun 2001 14:22:32 -0000</pubDate><guid>https://sourceforge.netc76b7d8000b07d940155b8aaa2f46915bfb2f50b</guid></item></channel></rss>