Login | Register
My pages Projects Community openCollabNet

Discussions > commits > svn commit: r2 - trunk/www

dotspect
Discussion topic

Back to topic list

svn commit: r2 - trunk/www

Reply

Author timewinds
Full name Pavan Podila
Date 2005-11-16 06:28:14 PST
Message Author: timewinds
Date: Wed Nov 16 06:28:14 2005
New Revision: 2

Modified:
   trunk/www/index.html
Log:
Updated project description

Modified: trunk/www/index.html
Url: http://dotspect.tigr​is.org/source/browse​/dotspect/trunk/www/​index.html?view=diff​&rev=2&p1=tr​unk/www/index.html​&r1=1&p2=trunk​/www/index.html&​r2=2
====================​====================​====================​==================
--- trunk/www/index.html (original)
+++ trunk/www/index.html Wed Nov 16 06:28:14 2005
@@ -13,94 +13,58 @@
 </head>
 <body>
 
-<p>This is the initial web content for your project. Please customize
-this to fit your project. You don't need to answer all these questions
-or follow this exact format, but we do like to see this kind of
-information before we approve projects for public viewing.
-</p>
-
-<p>Until your project is approved, only you can view it and work on
-it.
+<h3>Overview</h3>
+<p>dotSpect is a tool for aspecting .NET assemblies. The advice code
+can be written in any language as long as we have a compiler for that language and a mechanism to
+inject in the targeted assembly. Be default, dotSpect
+provides support for writing aspects in C# and
+VB.NET. The assemblies are aspected at Compile time (Static injection).
 </p>
 
+<h3>Motivatio​n</h3>
+<p>
+The reason I started working on this project is because there was no good tool
+for AOP in the .NET community similar to AspectJ for Java. Most tools were either
 <ul>
-<li>This index.html will be used if and only if you have the "Use
-Project Home Page" option checked on the "Administer Project" page
-(click the "Admin" tab).</li>
-
-<li>To edit this file, check out your project via CVS and edit www/index.html.
-
-<li>You can 'cvs add' and commit other files under the project's "www"
-directory and they will published to your project web site.</li>
-
-<li>Also, consider starting a thread in the "dev" mailing list to get
-these discussion started. A good one is an "introduction" thread where
-people post messages about themselves and their interest in the
-project.</li>
-
-<li>You can add a "Highlights:" line to the top of all web pages by adding a file www/project_highlights.html </li>
+ <li>XML based: Problem is XML is too verbose. Aspect definitions get lost in a
+ sea of tags, which start looking like a porcupine. Advice code is hidden in some
+ class, with a reference to the class-name in the XML. Not very intuitive.</li>
+ <li>No static injection facility. Most of them used dynamic proxies
+ which instruments code at runtime</li>
 </ul>
-
-
-<h3>Mission</h3>
-
-<p>What is the goal of this project?
-</p>
-
-<p>What is the scope of this project?
 </p>
 
-<p>For example:</p>
-
+<h3>Implement​ation</h3>
+<p>The way I have been able to solve most of these problems is as follows:
 <ul>
-<li>Develop just enough functionality to scratch a particular itch</li>
-<li>Build a tool just like XYZ, but less broken</li>
-<li>Build the best XYZ-tool ever!</li>
+ <li>Providing a new aspect oriented language similar to AspectJ</li>
+ <li>Language indepedence by allowing aspect code to be written in any
+ language. The header section of the aspect definition specifies which
+ language is being used</li>
+ <li>Extensible Grammar with support for custom handlers for various Reduction
+ Rules in the Parser. This makes it easy to add new types of joinpoints to the
+ grammar and also provide semantic support</li>
+ <li>Factory based language integration. This allows new languages to be introduced
+ for writing aspects</li>
 </ul>
-
-
-<p>What are high-level features you are sure to build?
 </p>
-<ul>
 
-<li>What would you write on a billboard about your project? Users
-might only look for a few seconds.</li>
-
-<li>Use the issue tracker to track features and enhancement
-requests. It is not just for bugs, pre-populate it with feature
-descriptions so that potential contributors know what you would like them
-to work on.</li>
-</ul>
-
-<p>What are the high-level assumptions or ground rules for the project?
-</p>
-
-<p>For example:
-</p>
 
+<h3>Status</h3>
+<p>
+The version I am working on right now includes:
 <ul>
-<li> we will use programming language X on operating system Y for now.
-
-<li>We will, or will not, consider certain functional areas like
-internationalization, high security, concurrency, etc. The list of
-functional areas will depend on what you are trying to do.
-
-<li>Try to keep this part short.
-</ul>
-
-
-<h3>Related resources</h3>
-
-<ul>
-<li>Link to other stuff that you know about. It will help you
-research requirements and provide a useful resource to potential
-contributors.</li>
-
-<li>Why reinvent the wheel? What is better about this wheel? Is there
-any existing project that you can partner with or reuse?</li>
-
-<li>Where would you go to try to find potential contibutors?</li>
+ <li>Support for <i>execution</i> joinpoints with <i>before</i> advice</li>
+ <li>Simple IDE for writing and testing aspects<br/><br/>
+ <img src="images/dotspect.jpg"/>
+ <p>[Note]: I had previously called this project NAspect but when hosting on tigris.org, I discovered
+ that the name was already taken. I resorted to using the name <i>dotSpect</i>, which
+ was suggested by a friend of mine.</p>
+ </li>
+ <li>Language support for C# and VB.NET</li>
+ <li>Command line tool for aspecting .NET assemblies</li>
 </ul>
+</p>
 
 </body>
 </html>

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

svn commit: r2 - trunk/www timewinds Pavan Podila 2005-11-16 06:28:14 PST
Messages per page: