Wiki page by khorben on 13/03/2011 22:57:35
--- /var/www/	2010/07/04 14:25:53	1.4
+++ /var/www/	2010/10/13 00:24:08	1.5
@@ -1,33 +1 @@
-			<p>
-Even though the <a href="" title="DeforaOS Project Reference">
-project reference</a> is still not complete, plans are being made to help the
-decisions, and continue to learn about operating system development throughout
-the design process. An (outdated) roadmap can be downloaded here, in <a href="" title="Planner">planner</a> format:
-			</p>
-<div><a href="" title="DeforaOS roadmap"><img src="" alt=""><br>DeforaOS.planner</a></div>
-			<h3>1. POSIX environment</h3>
-			<p>
-It makes it easy to complete a lot of working code, it gives a good view of the
-needs of an Operating System, and makes one practice C and programming. A
-number of UNIX utilities are already functional, including a shell. The libc has
-enough code for the environment to be booted on top of a third-party kernel.
-Work is currently concentrated on, in order:
-			</p>
-			<ol><li><a href="">libc</a></li><li><a href="">bootable disk image creation</a></li><li><a href="">sh</a></li><li>the <a href="">utils</a>
-utilities suite</li><li>the <a href="">others</a>
-utilities suite (not part of the <a href="" title="The Open Group Base Specifications Issue 6">SUSv3</a>)</li><li>the <a href="">devel</a>
-utilities suite (part of the <a href="" title="The Open Group Base Specifications Issue 6">SUSv3</a> development extension)</li></ol>The aim is to provide a fully-functional working environment, eventually matching the hardware requirements of some embedded platforms. Besides, this environment proves great in helping to write portable code, the libc abstracting away the differences between the different kernels. Moreover, its code was kept simple enough to know instantly the differences between them, and then fasten and ease the implementation of tools parsing C code, such as compilers and static analyzers.<br>
-			<h3>2. DeforaOS System software</h3>
-			<p>Meanwhile, the actual implementation of DeforaOS, with its own original concepts, will be based on an entirely different ground. This will mean a focus on, in
-			</p>
-			<ol><li><a href=";action=default&amp;id=27">libSystem</a>'s AppInterface private class
-(distributed message passing)</li><li>Session, the users' login program</li><li><a href=";action=default&amp;id=41">Init</a> (the
-system's Session)</li><li><a href="/os/project/display/3304/VFS">VFS</a> (transparent file management over the network)</li></ol>The plan is to experiment outside of the historical and cryptic existing standards for C development, meaning that the libSystem will be the equivalent to the libc on the system. With an object-oriented approach, it is believed that this framework will then easily provide consistent backends for different, higher-level languages.<br>
-			<h3>3. DeforaOS graphical environment</h3>A strong focus on the usability of the system as a whole is also a major aspect of the development of this project. Notwithstanding the amount of work already required in the two first tasks, it is believed to be necessary to study and fulfill the requirements of actual users, so as to better design the underlying layers of the system.<br>Therefore, a full-featured desktop environment is also being developed actively as part of this project. It is achieved while trying to rely on fewer external resources wherever possible, meaning it will eventually be easy to integrate with the rest of the system. Another benefit of this approach is, again, to match the requirements of embedded platforms.<br><h3>4. DeforaOS micro-kernel</h3>
-			<p>
-If by the time the userland system is actually complete, there is not an
-existing kernel tailored to its requirements, then the development of a dedicated
-micro-kernel will be started. Meanwhile, portability across as many existing Operating Systems is the objective, including flavors of the Linux, BSD and Solaris-based distributions.<br></p>
\ No newline at end of file
+The current objectives of the project can be summarized as follows, with respect to their expected transition date. This estimation is detailed in the list of planned developments.<br><h3>1. Provide a graphical environment</h3>(Q1 2011)<br><br>First and foremost, a decent and featureful user interface should be developed and maintained for the project. It will help further implementation and integration of DeforaOS' own internal architecture, with the knowledge acquired for its actual, practical needs.<br>This effort can be partly driven through the DeforaOS Smartphone project, with the following steps:<br><ol><li>Complete the feature set of the Desktop software</li><li>Ensure the system also runs on embedded platforms<br></li><li>Provide seamless bootup, shutdown and user login procedures<br></li></ol><h3>2. Demonstrate the framework</h3>(Q2 2011)<br><br>Better sooner and later, the new concepts introduced by DeforaOS' framework should actually be extended and demonstrated. Some components will be of particular interest:<br><ol><li>VFS, accessing data remotely and securely<br></li><li>GServer, distributed and optimal backend for user interfaces<br></li><li>VPN, for seamless roaming operation<br></li></ol><h3>3. Build a complete system</h3>(Q3 2011)<br><br>Build and support a complete userland environment based on this framework. Emphasis will be placed on:<br><ol><li>The base library and associated APIs (libSystem, libParser, libDesktop...)<br></li><li>Other essential low-level components (Loader...)</li><li>Complete user-friendly operation (Splasher...)<br></li></ol><h3>4. Adapt the kernel</h3>(Q4 2011)<br><br>If relevant, apply changes to the kernel of choice, to better fit the design, performance and security requirements of the system.<br>
\ No newline at end of file
1.9 (diff)khorben
1.8 (diff)khorben
1.7 (diff)khorben
1.6 (diff)khorben
1.5 (diff)khorben
1.4 (diff)khorben
1.3 (diff)khorben
1.2 (diff)