[haiku-commits] BRANCH looncraz-github.CAP-volatile - /
- From: looncraz-github.CAP-volatile <community@xxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Mon, 29 Oct 2012 10:48:51 +0100 (CET)
added 1 changeset to branch 'refs/remotes/looncraz-github/CAP-volatile'
old head: 0000000000000000000000000000000000000000
new head: 9a6145e94f3f2ede998299f7635db0b75d8fcaa2
----------------------------------------------------------------------------
9a6145e: Begin CAP: Compositing for Appropriate Purposes
Removed compositing branch, created several new ones.
ReadMe explains it all.
cap.looncraz.net will, in the near future, will be home
to supporting documents and packages and will be the
proper forum for announcements and detailed planning.
[ Yourself <user@shredder.(none)> ]
----------------------------------------------------------------------------
Commit: 9a6145e94f3f2ede998299f7635db0b75d8fcaa2
Author: Yourself <user@shredder.(none)>
Date: Mon Oct 29 03:47:05 2012 UTC
----------------------------------------------------------------------------
1 file changed, 76 insertions(+), 11 deletions(-)
ReadMe | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--------
----------------------------------------------------------------------------
diff --git a/ReadMe b/ReadMe
index 77ec0e9..a963881 100644
--- a/ReadMe
+++ b/ReadMe
@@ -1,3 +1,79 @@
+************
+looncraz/haiku
+ forked from haiku/haiku
+
+[Disclaimer]
+
+This project is not sponsored or endorsed by Haiku, INC. It is a "rogue"
project which
+hopes to ultimately be merged into HaikuOS.
+
+[/Disclaimer]
+
+~~~~~~~~~~~~Compositing for Appropriate Purposes (CAP).~~~~~~~~~~~~
+
+This repot plays host to a sharply focused project which aims only to achieve
+basic compositing features as required to improve the user experience. It does
+not include any intent for fancy window animations or to make accomodations
+for endless customizability. It is intended to help modernize the feel and
abilities
+of Haiku OS's app_server without going into feature creep or bloat. The
desire is to
+not clone the methods used by other compositing window manages or engines, but
+to instead leverage the unique capabilities and design of HaikuOS to provide
needed
+features and capabilities with minimal fuss - while being wholly robust.
+
+The "end" result should be an app_server which can utilize the full power of a
system
+to deliver an unparalleled degree of capability for processing performance
available.
+The goal is that a 2GHz Athlon II X2 with 1.5GB of RAM can run the full CAP
feature set
+in VESA mode. A laudible goal that can only be accomplished by treating
computing
+resources as being precious.
+
+In this line of thought, a process is being formulated by which progress will
be judged.
+
+[To be continued...]
+
+
+BRANCHES:
+ CAP, CAP-volatile, CAP-exp, CAP-stage, CAP-haiku
+
+WORK FLOW:
+ The work-flow for each individual commit may come as a surprise to many
- in that
+ it is quite involved - as opposed to the former method (or common
methods).
+
+ At this time this is a solo project, but I hope that it will not end
that way. My desire
+ is that the code resulting from this project will ultimately
+
+
+
+CAP: This branch will host only finalized commits.
+ Should ALWAYS build. Resulting product of that build should be as
stable as has
+ been achieved up to the given point in the project.
+
+CAP-volatile: In-process code changes.
+ This branch may often not build - it is mainly a way to prevent ongoing
work from
+ being stored in one location. Volatile will have frequent changes and
should not
+ be monitored too closely as ideas may come and go (in code) many times
a day.
+
+CAP-exp: Experimental modifications to CAP.
+ Will host changes from volatile that may be considered for staging.
+ Should almost always build without error, but stability is questionable.
+ Changes here may not always head to staging.
+
+CAP-stage: staging area for individual commits to CAP.
+ This is like a beta phase for commits. This will be tested and
bug-fixed and even
+ regression tested (as applicable) prior to a commit being moved on to
the main
+ CAP branch.
+
+CAP-haiku: Haiku final proposed commits.
+ Limited in scope, this branch plays host to changes Haiku would,
ideally, have
+ committed in order for ideal cross-compatility. Changes to add-ons,
additions of
+ capabilities not explicitely limited to compositing, or bug fixes will
be found here.
+ Each CAP* branch will have these changes within them.
+
+
+The work flow is meant to be tedious so that the end result is of an
apprecciably high
+quality - in the very least in the terms of stability and compatibility.
+
+************
+
Building Haiku from source
==========================
@@ -60,10 +136,6 @@ The following tools are needed to compile Haiku for the ARM
platform
* Mtools (http://www.gnu.org/software/mtools/intro.html)
* sfdisk
-Specific: Linux
----------------
- * zlib1g-dev (for building GCC4 buildtools on Linux hosts)
-
Specific: Mac OS X
------------------
@@ -75,13 +147,6 @@ The following darwin ports need to be installed:
* libiconv
* gnuregex
* gsed
- * cdrtools
- * yasm
- * wget
- * less
- * mpfr
- * gmp
- * libmpc
More information about individual distributions of Linux and BSD can be found
at http://haiku-os.org/guides/building/pre-reqs
Other related posts:
