aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/README
diff options
context:
space:
mode:
authorDavid Walter Seikel2014-07-02 19:44:12 +1000
committerDavid Walter Seikel2014-07-02 19:44:12 +1000
commit02b9c48fd8d99d8128133692baf2e5c686c5590b (patch)
tree9eb4f5e5580b96c4f01f60e64d0dba7e8cb5fdc1 /README
parentTODO++ (diff)
downloadSledjHamr-02b9c48fd8d99d8128133692baf2e5c686c5590b.zip
SledjHamr-02b9c48fd8d99d8128133692baf2e5c686c5590b.tar.gz
SledjHamr-02b9c48fd8d99d8128133692baf2e5c686c5590b.tar.bz2
SledjHamr-02b9c48fd8d99d8128133692baf2e5c686c5590b.tar.xz
Fix a bunch of typos.
Diffstat (limited to 'README')
-rw-r--r--README22
1 files changed, 11 insertions, 11 deletions
diff --git a/README b/README
index a162e64..c2715d8 100644
--- a/README
+++ b/README
@@ -226,7 +226,7 @@ libraries for them more or less mature. Lots of research and
226standardisation effort has gone into the major popular ones. So we 226standardisation effort has gone into the major popular ones. So we
227don't really need to deal with that. Problem solved already. Well, 227don't really need to deal with that. Problem solved already. Well,
228except for JPEG 2000, which outside of SL and medical use, no one has 228except for JPEG 2000, which outside of SL and medical use, no one has
229even heard of. It's library support is not so good, and made even wosre 229even heard of. It's library support is not so good, and made even worse
230by the fact that the best decoding algorithm for it is patented and out 230by the fact that the best decoding algorithm for it is patented and out
231of reach to open source developers. Still, lots and lots of SL and 231of reach to open source developers. Still, lots and lots of SL and
232OpenSim content is in JPEG 2000 format, and it is good as a network 232OpenSim content is in JPEG 2000 format, and it is good as a network
@@ -283,7 +283,7 @@ Basically, you can think of EFL as a replacement for the GTK that SL
283viewers use. They both offer more or less a similar feature set, and 283viewers use. They both offer more or less a similar feature set, and
284both use more or less the same standard libraries underneath. GTK uses 284both use more or less the same standard libraries underneath. GTK uses
285the GLib main loop, which EFL supports via wrappers. I think that EFL 285the GLib main loop, which EFL supports via wrappers. I think that EFL
286fits the SLedjHamr design goals much better though. 286fits the SledjHamr design goals much better though.
287 287
288As a bonus, lots and lots of eye candy, complete with a system for 288As a bonus, lots and lots of eye candy, complete with a system for
289writing your own eye candy, and over riding the system supplied eye 289writing your own eye candy, and over riding the system supplied eye
@@ -344,7 +344,7 @@ Lua has been great for quickly building prototype stuff. So far most of
344the network protocols and file formats have been based on Lua. Which 344the network protocols and file formats have been based on Lua. Which
345goes against our goals, so expect that to be temporary. Specifically, 345goes 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 by nails.
348 348
349The Lua GUI code is loosely 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
@@ -391,13 +391,13 @@ with EFL. I've not tried it yet, but it was on my TODO.
391 391
392In the mean time, and so recently that it only gets released later 392In the mean time, and so recently that it only gets released later
393today, Evas_3D was added to EFL. Evas is one of the sub libraries of 393today, Evas_3D was added to EFL. Evas is one of the sub libraries of
394EFL that deals with canvasses, it's a 3D mesh, camera, and light system 394EFL that deals with canvasses. Evas_3D is a 3D mesh, camera, and light
395designed to be part of Evas. So it has the major advantage of already 395system designed to be part of Evas. So it has the major advantage of
396being well integrated, it's part of EFL. I've added test code for it 396already being well integrated, it's part of EFL. I've added test code
397now, and no flickering. I even have test code using both Irrlicht and 397for it now, and no flickering. I even have test code using both
398Evas_3D in the same window space. It's major disadvantage is that it's 398Irrlicht and Evas_3D in the same window space. It's major disadvantage
399only a very recent project that has (until later today) not been 399is that it's only a very recent project that has (until later today) not
400released, Irrlicht is much more mature. So Evas_3D only has basic 400been 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
@@ -476,7 +476,7 @@ Edje Lua
476 Edje Lua can add the bit library if it detects LuaJIT or 5.2. 476 Edje Lua can add the bit library if it detects LuaJIT or 5.2.
477 LuaSL stuff needs to be sandboxed as well, maybe we can use this new host function thingy to add LSL to? 477 LuaSL stuff needs to be sandboxed as well, maybe we can use this new host function thingy to add LSL to?
478 Really should investigate if this shit being duplicated in thousands of LuaSL scripts soaks up lots of memory? And require("LSL") versus this new host function thingy. 478 Really should investigate if this shit being duplicated in thousands of LuaSL scripts soaks up lots of memory? And require("LSL") versus this new host function thingy.
479 On the other hand, a lot oy this LSL library would end up being wrappers around nails in the future, which is a shared library. 479 On the other hand, a lot of this LSL library would end up being wrappers around nails in the future, which is a shared library.
480 LuaJIT? Optional? 480 LuaJIT? Optional?
481 Need to sort out it's memory allocator, coz apparently the one Edje uses is not thread safe, but the LuaJIT one does not limit memory per script like Edje does. 481 Need to sort out it's memory allocator, coz apparently the one Edje uses is not thread safe, but the LuaJIT one does not limit memory per script like Edje does.
482 Maybe Edje can use an Eina allocator? 482 Maybe Edje can use an Eina allocator?