Login | Register
My pages Projects Community openCollabNet

Discussions > commits > svn commit: r2 - trunk/www/index.html

Discussion topic

Back to topic list

svn commit: r2 - trunk/www/index.html


Author tautologico
Full name Andrei Formiga
Date 2006-04-30 17:54:19 PDT
Message Author: tautologico
Date: 2006-04-30 17:54:19-0700
New Revision: 2


Initial contents of the project's frontpage

Modified: trunk/www/index.html
Url: http://gnop.tigris.o​rg/source/browse/gno​p/trunk/www/index.ht​ml?view=diff&rev​=2&p1=trunk/www/​index.html&p2=tr​unk/www/index.html​&r1=1&r2=2
--- trunk/www/index.html (original)
+++ trunk/www/index.html 2006-04-30 17:54:19-0700
@@ -13,94 +13,27 @@
-<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>Until your project is approved, only you can view it and work on
+<h2>The gnop project</h2>
-<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>
+The objective of this project is to create tools for the development of emulators.
+We will begin by creating specific emulators/simulators to simple processors; then
+the plan is to work on Domain-Specific Languages that will help the development of
+emulators, and using these languages we will generate emulators that will be compared
+with the hand-crafted ones. From this we expect to derive tools and knowledge to ease
+and diminish the repetitive aspects of developing an emulator.
+Although much used for development of old computer and video-game systems, emulation
+can be very useful as a testing platform for embedded systems software development.
+Simple techniques for emulation are relatively straight-forward but typically require
+a lot of repetitive work. Furthermore, to achieve better performance it is necessary
+to use more complex techniques. By factoring know-how into tools, we expect to both
+eliminate or diminish the repetitive aspects of emulator programming and enable the
+use of efficient implementation techniques, such as dynamic recompilation by users
+of the tool. Auxilliary tools for the emulator like debuggers and profilers can also
+be built automatically, at least in part, with the use of tools.
-<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
-<li>You can add a "Highlights:" line to the top of all web pages by adding a file www/project_highlights.html </li>
-<p>What is the goal of this project?
-<p>What is the scope of this project?
-<p>For example:</p>
-<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>
-<p>What are high-level features you are sure to build?
-<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>
-<p>What are the high-level assumptions or ground rules for the project?
-<p>For example:
-<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.
-<h3>Related resources</h3>
-<li>Link to other stuff that you know about. It will help you
-research requirements and provide a useful resource to potential
-<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>
+More details will be published here shortly.

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


Show all messages in topic

svn commit: r2 - trunk/www/index.html tautologico Andrei Formiga 2006-04-30 17:54:19 PDT
Messages per page: