aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--README32
-rw-r--r--docs/ClientHamr/README.GuiLua6
-rw-r--r--docs/ClientHamr/README.woMan2
-rw-r--r--docs/ClientHamr/ScriptEditor.txt2
-rw-r--r--docs/README.Bookie2
-rw-r--r--docs/README.LuaSL6
-rw-r--r--docs/README.REST2
-rw-r--r--docs/The_Naminator.txt2
-rw-r--r--docs/love.txt4
-rw-r--r--docs/portals.txt8
10 files changed, 33 insertions, 33 deletions
diff --git a/README b/README
index 22bc899..a162e64 100644
--- a/README
+++ b/README
@@ -41,7 +41,7 @@ virtual worlds you can program a bare cube to act like a car that you
41sit on and drive, the rest is mostly for looks. 41sit on and drive, the rest is mostly for looks.
42 42
43There's no such thing as virtual wind in your hair, or smog in your 43There's no such thing as virtual wind in your hair, or smog in your
44nostrils, but if that eventualy gets invented, a generic virtual world 44nostrils, but if that eventually gets invented, a generic virtual world
45system should be able to hook into it easily enough. 45system should be able to hook into it easily enough.
46 46
47Generic. 47Generic.
@@ -57,7 +57,7 @@ philosophy, and you can do almost anything with the usual collection of
57small Unix tools. 57small Unix tools.
58 58
59So the design of SledjHamr involves lots of little bits of generic code 59So the design of SledjHamr involves lots of little bits of generic code
60that all work together seemlessly. A major design goal is to be as 60that all work together seamlessly. A major design goal is to be as
61generic, yet useful, as possible, to support future stuff that hasn't 61generic, yet useful, as possible, to support future stuff that hasn't
62been invented yet. As well as supporting stuff we need to do now. 62been invented yet. As well as supporting stuff we need to do now.
63 63
@@ -72,7 +72,7 @@ that computer storage, memory, and CPU power are all very cheap, so why
72bother making things small. Any long term computer user might have 72bother making things small. Any long term computer user might have
73noticed that despite our modern computers being many orders of magnitude 73noticed that despite our modern computers being many orders of magnitude
74faster and bigger than they where a decade or two ago, everything runs 74faster and bigger than they where a decade or two ago, everything runs
75slower than it did then. This proves the falacy of "everything is cheap 75slower than it did then. This proves the fallacy of "everything is cheap
76and getting cheaper, lets be wasteful" theory. People are just too 76and getting cheaper, lets be wasteful" theory. People are just too
77comfortable with their wasteful habits. Not to mention that the 77comfortable with their wasteful habits. Not to mention that the
78computer industry loves to get every one to throw out their computers 78computer industry loves to get every one to throw out their computers
@@ -83,7 +83,7 @@ computers, just to do what it did fine last year.
83Even a small virtual world can use up huge amounts of storage, large 83Even a small virtual world can use up huge amounts of storage, large
84amounts of memory and CPU power, and large amounts of network bandwidth. 84amounts of memory and CPU power, and large amounts of network bandwidth.
85This is the problem with simulating worlds, the bits might be small, but 85This is the problem with simulating worlds, the bits might be small, but
86there's an aweful lot of them. You can run a busy web site on a $5 per 86there's an awful lot of them. You can run a busy web site on a $5 per
87month web host, but you need to spend at least $100 per month on a 87month web host, but you need to spend at least $100 per month on a
88hosted server that's powerful enough to run a small OpenSim based 88hosted server that's powerful enough to run a small OpenSim based
89virtual world. 89virtual world.
@@ -102,11 +102,11 @@ Fast.
102Ask any current virtual world user, at least of the types based on SL 102Ask any current virtual world user, at least of the types based on SL
103technology, what the number one biggest problem is and they will tell 103technology, what the number one biggest problem is and they will tell
104you it's lag. So speed is important to everyone. Which makes me wonder 104you it's lag. So speed is important to everyone. Which makes me wonder
105why people use slow bloated things like interpretted scripting languages 105why people use slow bloated things like interpreted scripting languages
106and human readable network protocols / file formats for damn near 106and human readable network protocols / file formats for damn near
107everything? 107everything?
108 108
109People use interpretted scripting languages coz it's easy and convenient 109People use interpreted scripting languages coz it's easy and convenient
110for them. Not so convenient for the user though when it causes more 110for them. Not so convenient for the user though when it causes more
111lag. People invent human readable network protocols and file formats 111lag. People invent human readable network protocols and file formats
112coz it makes it easy for them to read when they need to debug the 112coz it makes it easy for them to read when they need to debug the
@@ -129,11 +129,11 @@ Once again it's a matter of scale for virtual worlds. Each part by
129itself might be barely fast enough that people don't notice, but it all 129itself might be barely fast enough that people don't notice, but it all
130adds up when you deal with the huge multitude of fiddly little details 130adds up when you deal with the huge multitude of fiddly little details
131in a virtual world. Which results in the number one problem being ... 131in a virtual world. Which results in the number one problem being ...
132lag. Often everything slows down so much it becomens unusable. 132lag. Often everything slows down so much it becomes unusable.
133 133
134We can have our cake and eat it to. So long as the crucial heavily used 134We can have our cake and eat it to. So long as the crucial heavily used
135parts of the system that need speed are written efficiently in a 135parts of the system that need speed are written efficiently in a
136decently fast language, then we can still use easy interpretted 136decently fast language, then we can still use easy interpreted
137scripting languages for other parts that wont suffer from scaling 137scripting languages for other parts that wont suffer from scaling
138issues. So long as we stick with efficient binary based network 138issues. So long as we stick with efficient binary based network
139protocols and file formats, the tiny percentage of developers that need 139protocols and file formats, the tiny percentage of developers that need
@@ -147,7 +147,7 @@ Assembler and C is used for OS kernels, embedded software, and other
147things that need to be efficient. So C is the major language used for 147things that need to be efficient. So C is the major language used for
148SledjHamr. Bits of assembler might be used if needed. 148SledjHamr. Bits of assembler might be used if needed.
149 149
150For the interpretted scripting language of choice used in SledjHamr, I 150For the interpreted scripting language of choice used in SledjHamr, I
151chose Lua. It's very generic in nature with it's wonderful tables and 151chose Lua. It's very generic in nature with it's wonderful tables and
152meta tables. It's tiny, designed to be embedded inside other languages. 152meta tables. It's tiny, designed to be embedded inside other languages.
153With the LuaJIT just in time compiler, it's the fastest scripting 153With the LuaJIT just in time compiler, it's the fastest scripting
@@ -164,7 +164,7 @@ when Apple based their new version of Mac Os X on BSD Unix, the OS wars
164where over. Everything now is some sort of Unix, except Windows. Hell, 164where over. Everything now is some sort of Unix, except Windows. Hell,
165iPhones OS is based on Mac OS X, and Android is based on Linux, so even 165iPhones OS is based on Mac OS X, and Android is based on Linux, so even
166the great majority of phones these days are Unix. Every one is a Unix 166the great majority of phones these days are Unix. Every one is a Unix
167user, wether they know it or not. 167user, whether they know it or not.
168 168
169Windows makes a nod to being Posix compliant, though it's barely a nod. 169Windows makes a nod to being Posix compliant, though it's barely a nod.
170Cygwin however can be installed on Windows to make it more like the Unix 170Cygwin however can be installed on Windows to make it more like the Unix
@@ -253,7 +253,7 @@ Secure.
253------- 253-------
254 254
255One of our developers is a cypherpunk / cryptogeek / whatever term she's 255One of our developers is a cypherpunk / cryptogeek / whatever term she's
256comfortable being labelled as. Our team is very privacy focused. So 256comfortable being labeled as. Our team is very privacy focused. So
257security and privacy are important goals as well. Small modular code is 257security and privacy are important goals as well. Small modular code is
258better for security, is there is less code to look at to do security 258better for security, is there is less code to look at to do security
259audits, and less places for things to go wrong, or escape attention. 259audits, and less places for things to go wrong, or escape attention.
@@ -346,7 +346,7 @@ goes against our goals, so expect that to be temporary. Specifically,
346once we get around to actually implementing the nails protocol stuff, 346once we get around to actually implementing the nails protocol stuff,
347some of the Lua network and file formats will get replaced be nails. 347some of the Lua network and file formats will get replaced be nails.
348 348
349The Lua GUI code is losely based on my ancient matrix-RAD stuff that was 349The Lua GUI code is loosely based on my ancient matrix-RAD stuff that was
350written in Java. The fact that I had most of it working within a week 350written in Java. The fact that I had most of it working within a week
351is a tribute to how easy Lua is. The original Java took me years to 351is a tribute to how easy Lua is. The original Java took me years to
352write. On the other hand, I'm not that happy with the syntax of the 352write. On the other hand, I'm not that happy with the syntax of the
@@ -385,7 +385,7 @@ my vote, so I experimented with it. There was no EFL integration, so I
385had to write some, which wasn't that hard. A year later, a new version 385had to write some, which wasn't that hard. A year later, a new version
386of EFL managed to bit rot my EFL/Irrlicht integration, so I fixed that. 386of EFL managed to bit rot my EFL/Irrlicht integration, so I fixed that.
387But now it flickers like crazy. After much discussion with other EFL 387But now it flickers like crazy. After much discussion with other EFL
388develpors, and some preliminary work by the Irrlicht developers, an 388developers, and some preliminary work by the Irrlicht developers, an
389experimental version of Irrlicht is underway that might integrate better 389experimental version of Irrlicht is underway that might integrate better
390with EFL. I've not tried it yet, but it was on my TODO. 390with EFL. I've not tried it yet, but it was on my TODO.
391 391
@@ -401,7 +401,7 @@ released, Irrlicht is much more mature. So Evas_3D only has basic
401stuff, though it's mostly complete basic stuff. On the other hand, a 401stuff, though it's mostly complete basic stuff. On the other hand, a
402lot of what's missing in Evas_3D I was thinking about rewriting for 402lot of what's missing in Evas_3D I was thinking about rewriting for
403Irrlicht anyway. So far one major missing bit is Bullet Physics 403Irrlicht anyway. So far one major missing bit is Bullet Physics
404intergration, or any other physics engine. Irrlicht has Bullet, and 404integration, or any other physics engine. Irrlicht has Bullet, and
405another part of EFL also has Bullet. I'm hoping the authors of that 405another part of EFL also has Bullet. I'm hoping the authors of that
406other EFL part get together with the Evas_3D authors and figure 406other EFL part get together with the Evas_3D authors and figure
407something out. 407something out.
@@ -428,7 +428,7 @@ extantz
428 or even just different camera views 428 or even just different camera views
429 could use the same thing for generating two views for stereo viewing. 429 could use the same thing for generating two views for stereo viewing.
430 Nails interface to virtual world backend modules. Each module converts nails commands to / from it's own network protocol. 430 Nails interface to virtual world backend modules. Each module converts nails commands to / from it's own network protocol.
431 A SledjHamr grid, which definately should be running independantly, 431 A SledjHamr grid, which definitely should be running independently,
432 so others can log on and stay on when extantz closes down 432 so others can log on and stay on when extantz closes down
433 which may be a local or remote grid 433 which may be a local or remote grid
434 might be part of some other grid (a sim) 434 might be part of some other grid (a sim)
@@ -464,7 +464,7 @@ GuiLua
464 464
465Edje Lua 465Edje Lua
466 Lua embedded in edje files, and sandboxed to them. 466 Lua embedded in edje files, and sandboxed to them.
467 add table marshalling into an edje message 467 add table marshaling into an edje message
468 add host proggy supplied Lua functions 468 add host proggy supplied Lua functions
469 So we can add nails.foo(), GuiLua.foo(), and maybe even LSL.foo(). 469 So we can add nails.foo(), GuiLua.foo(), and maybe even LSL.foo().
470 All users of GuiLua and nails probably want to be sandboxed, the scripts should be loaded up by extantz, OpenSim, or SledjHamr, not run from the operating system. 470 All users of GuiLua and nails probably want to be sandboxed, the scripts should be loaded up by extantz, OpenSim, or SledjHamr, not run from the operating system.
diff --git a/docs/ClientHamr/README.GuiLua b/docs/ClientHamr/README.GuiLua
index f60d7b2..72f13f3 100644
--- a/docs/ClientHamr/README.GuiLua
+++ b/docs/ClientHamr/README.GuiLua
@@ -97,7 +97,7 @@ something else), then unmarshal the result before sending it back to
97Lua. 97Lua.
98 98
99The second alternative, which the host app must REALLY request, is for 99The second alternative, which the host app must REALLY request, is for
100the host app to say "I'm REALLY going out of my way to be threadsafe, 100the host app to say "I'm REALLY going out of my way to be thread safe,
101just call me direct". No edje wrapper function, BUT the host app still 101just call me direct". No edje wrapper function, BUT the host app still
102has to use edje to register this function. 102has to use edje to register this function.
103 103
@@ -568,8 +568,8 @@ Windows with widgets relative to each other.
568Manual association of widgets to methods. 568Manual association of widgets to methods.
569Can include tool tip string, enabled, visible, hover cursor, bounding rectangle?, mouse opaque?, tab groups, font (name, size, style, and alignment). 569Can include tool tip string, enabled, visible, hover cursor, bounding rectangle?, mouse opaque?, tab groups, font (name, size, style, and alignment).
570 More stuff, typically hidden in the OO somewhere. sigh 570 More stuff, typically hidden in the OO somewhere. sigh
571Generally uses fixed image and colour names, which skins overide. 571Generally uses fixed image and colour names, which skins override.
572Skins can also overide the XML files. 572Skins can also override the XML files.
573Translations provide override XML files that need only override the text bits. 573Translations provide override XML files that need only override the text bits.
574 574
575 575
diff --git a/docs/ClientHamr/README.woMan b/docs/ClientHamr/README.woMan
index 1b3bbe0..990f9c5 100644
--- a/docs/ClientHamr/README.woMan
+++ b/docs/ClientHamr/README.woMan
@@ -25,7 +25,7 @@ viewer is not TPVP (Third Party Viewer Policy, an LL thing) compliant,
25and LL are just more anal than the rest of the universe. 25and LL are just more anal than the rest of the universe.
26 26
27NOTE: since I started this, LL in their *cough* infinite wisdom *cough*, 27NOTE: since I started this, LL in their *cough* infinite wisdom *cough*,
28decided that support of OpenSIm was a Really Bad Thing, so their viewers 28decided that support of OpenSim was a Really Bad Thing, so their viewers
29are no longer capable of dealing with other grids. LL have even gone as 29are no longer capable of dealing with other grids. LL have even gone as
30far as try to get other viewers to not support other grids. As far as 30far as try to get other viewers to not support other grids. As far as
31woMan is concerned, this just means that LL viewers, and viewers that 31woMan is concerned, this just means that LL viewers, and viewers that
diff --git a/docs/ClientHamr/ScriptEditor.txt b/docs/ClientHamr/ScriptEditor.txt
index 357793a..28cb6a3 100644
--- a/docs/ClientHamr/ScriptEditor.txt
+++ b/docs/ClientHamr/ScriptEditor.txt
@@ -22,5 +22,5 @@ the command finishes. Naturally that command could be "vi script.lsl",
22 22
23Toybox and terminology works under cygwin and Mac OS X. 23Toybox and terminology works under cygwin and Mac OS X.
24 24
25Rob pulls his finger out and starts putting my editting stuff in toybox 25Rob pulls his finger out and starts putting my editing stuff in toybox
26so I can progress with this. 26so I can progress with this.
diff --git a/docs/README.Bookie b/docs/README.Bookie
index 1a49f27..bec4b19 100644
--- a/docs/README.Bookie
+++ b/docs/README.Bookie
@@ -28,6 +28,6 @@ versions of the libraries needed in that. If not found, it could invoke
28an OS specific method of installing a suitable library. If that fails, 28an OS specific method of installing a suitable library. If that fails,
29it can download a SledjHamr specific version into the SledjHamr 29it can download a SledjHamr specific version into the SledjHamr
30installed directory. So it tries to do the right thing first, and 30installed directory. So it tries to do the right thing first, and
31gradually fallsback to doing the wrong thing like LL does. 31gradually falls back to doing the wrong thing like LL does.
32 32
33That's the theory, in practice, gonna be a pain. 33That's the theory, in practice, gonna be a pain.
diff --git a/docs/README.LuaSL b/docs/README.LuaSL
index 69bb45c..ed2ffdd 100644
--- a/docs/README.LuaSL
+++ b/docs/README.LuaSL
@@ -1,7 +1,7 @@
1Refer to - http://www.infinitegrid.org/drupal/content/LuaSL_New_scripting_engine 1Refer to - http://www.infinitegrid.org/drupal/content/LuaSL_New_scripting_engine
2 2
3LuaSL is a Lua based LSL scripting engine that will aim for LSL 3LuaSL is a Lua based LSL scripting engine that will aim for LSL
4compatability first, then adding Lua extensions. It aims to replace the 4compatibility first, then adding Lua extensions. It aims to replace the
5woeful XEngine from OpenSim, and at a later stage, be the basis for a 5woeful XEngine from OpenSim, and at a later stage, be the basis for a
6client side scripting engine. 6client side scripting engine.
7 7
@@ -38,7 +38,7 @@ future.
38 38
39THIS IS WHERE WE ARE RIGHT NOW. 39THIS IS WHERE WE ARE RIGHT NOW.
40 40
41Should implement embedded Lua somehow. Probaly the best thing to do is 41Should implement embedded Lua somehow. Probably the best thing to do is
42to have comments like - 42to have comments like -
43 43
44//Lua: local t = {1, 3, 42, x='something', 'something else} 44//Lua: local t = {1, 3, 42, x='something', 'something else}
@@ -55,7 +55,7 @@ Incoming commands invoke LSL events via the LuaSL state metatable. LL
55and OS functions that impact the world will be converted to nails 55and OS functions that impact the world will be converted to nails
56commands sent to the command pump. 56commands sent to the command pump.
57 57
58Initialy, since this is the first thing being written, a nails command 58Initially, since this is the first thing being written, a nails command
59pump client needs to be installed into OpenSim's C# stuff. Though it 59pump client needs to be installed into OpenSim's C# stuff. Though it
60might be possible to talk directly to ROBUST instead. Think I'll try 60might be possible to talk directly to ROBUST instead. Think I'll try
61the ROBUST route, see how far I can get. That's the general principle 61the ROBUST route, see how far I can get. That's the general principle
diff --git a/docs/README.REST b/docs/README.REST
index 2981827..0d773f8 100644
--- a/docs/README.REST
+++ b/docs/README.REST
@@ -1,2 +1,2 @@
1REST is probaly good to apply to the web server part. Alice wants JSON 1REST is probably good to apply to the web server part. Alice wants JSON
2to, but see nails. 2to, but see nails.
diff --git a/docs/The_Naminator.txt b/docs/The_Naminator.txt
index 3465d44..8a6a25e 100644
--- a/docs/The_Naminator.txt
+++ b/docs/The_Naminator.txt
@@ -6,7 +6,7 @@ and URLs, so the names have to be munged accordingly. A further issue
6is that different in world objects can have the same name. Lots of 6is that different in world objects can have the same name. Lots of
7copies of the same thing, or two different things that happen to be 7copies of the same thing, or two different things that happen to be
8called the same thing. No one is gonna individually name each tree in a 8called the same thing. No one is gonna individually name each tree in a
9forest, or every lampost in the city. File names and URLs have to be 9forest, or every lamppost in the city. File names and URLs have to be
10unique. The Naminator deals with munging names to deal with these 10unique. The Naminator deals with munging names to deal with these
11issues. It should generate names that are compatible with a variety of 11issues. It should generate names that are compatible with a variety of
12operating and file systems, as well as being URL compatible. This is 12operating and file systems, as well as being URL compatible. This is
diff --git a/docs/love.txt b/docs/love.txt
index e21b18b..d95dc30 100644
--- a/docs/love.txt
+++ b/docs/love.txt
@@ -57,7 +57,7 @@ the major amounts of web infrastructure that already exists and already
57solves most of the problems that currently plague virtual worlds based 57solves most of the problems that currently plague virtual worlds based
58on SL tech. 58on SL tech.
59 59
60The down side of separated is that changes might be slower propogating 60The down side of separated is that changes might be slower propagating
61to the web server, and there might be two copies of any given set of 61to the web server, and there might be two copies of any given set of
62assets in memory at once. 62assets in memory at once.
63 63
@@ -127,7 +127,7 @@ inspired by git using SHA-1 hashes for content addressable assets.
127SHA-1 hashes are 40 character hex codes representing 160 bit numbers 127SHA-1 hashes are 40 character hex codes representing 160 bit numbers
128that are calculated based on the content. So the same content will give 128that are calculated based on the content. So the same content will give
129the same SHA-1 hash. Git has proved that you only need the first digits 129the same SHA-1 hash. Git has proved that you only need the first digits
130of the SHA-1 hash to ensure uniqueness, so it's feasable to use only the 130of the SHA-1 hash to ensure uniqueness, so it's feasible to use only the
131first 128 bits of SHA-1 hashes to squeeze it into a UUID for the 131first 128 bits of SHA-1 hashes to squeeze it into a UUID for the
132purposes of uniquely identifying assets. Precisely what git does. This 132purposes of uniquely identifying assets. Precisely what git does. This
133means it could be backwards compatible with LL's use of UUIDs. 133means it could be backwards compatible with LL's use of UUIDs.
diff --git a/docs/portals.txt b/docs/portals.txt
index c2ba0a1..d54c235 100644
--- a/docs/portals.txt
+++ b/docs/portals.txt
@@ -3,7 +3,7 @@ SledjHamrs killer feature, or one of them.
3A major reason for SledjHamr is to break down the garden walls. We do 3A major reason for SledjHamr is to break down the garden walls. We do
4this by allowing free travel between peoples virtual worlds. In OpenSim 4this by allowing free travel between peoples virtual worlds. In OpenSim
5this is done by HyperGrid, which is clunky and hard to use. Second Life 5this is done by HyperGrid, which is clunky and hard to use. Second Life
6deliberatly has no such system. Even worse, it's hard convincing people 6deliberately has no such system. Even worse, it's hard convincing people
7in SL to visit your grid, coz it's all very hard, again due to 7in SL to visit your grid, coz it's all very hard, again due to
8deliberate policy decisions by LL. LL knows their content is the key to 8deliberate policy decisions by LL. LL knows their content is the key to
9their business, even though almost all of it was created by the users, 9their business, even though almost all of it was created by the users,
@@ -31,7 +31,7 @@ using OpenSim and its HyperGrid system. Later it would be SledjHamr
31style worlds as well. 31style worlds as well.
32 32
33A portal would be like Cobalt style portals, you can see the destination 33A portal would be like Cobalt style portals, you can see the destination
34in real time, and step through it to go there. They can be permenant, 34in real time, and step through it to go there. They can be permanent,
35or temporary. You can carry them in your inventory, they could just be 35or temporary. You can carry them in your inventory, they could just be
36normal scripted in world objects. 36normal scripted in world objects.
37 37
@@ -46,7 +46,7 @@ rez it anywhere. Or you could rez this portal object in the world you
46are in. Either way, once the portal is in a world, it connects to your 46are in. Either way, once the portal is in a world, it connects to your
47home world, showing a view of your front gate, maybe including your 47home world, showing a view of your front gate, maybe including your
48lovely garden in your front yard. The portal connects to the "front 48lovely garden in your front yard. The portal connects to the "front
49gate" of your homeworld. 49gate" of your home world.
50 50
51Any one on your home worlds access list can step through this portal to 51Any one on your home worlds access list can step through this portal to
52get to your home world. Simple to use, no figuring out HyperGate URLs 52get to your home world. Simple to use, no figuring out HyperGate URLs
@@ -59,7 +59,7 @@ Portals rezzed in world could be temporary, and vanish after who ever
59you invited to come stepped through it. Or time out several minutes 59you invited to come stepped through it. Or time out several minutes
60later so as not to clutter the universe with left over portals. Or 60later so as not to clutter the universe with left over portals. Or
61deleted by the owner / managers of the world you left them, or deleted 61deleted by the owner / managers of the world you left them, or deleted
62yourself from your own world. Portals could be permenant. Say you 62yourself from your own world. Portals could be permanent. Say you
63found a larger world that you and the owner decide you wish to be a part 63found a larger world that you and the owner decide you wish to be a part
64of. Portals could be left on both worlds linking them. The "portal" 64of. Portals could be left on both worlds linking them. The "portal"
65could just be reconfiguring each world to locate the other world near 65could just be reconfiguring each world to locate the other world near