diff options
author | David Walter Seikel | 2014-07-02 19:44:12 +1000 |
---|---|---|
committer | David Walter Seikel | 2014-07-02 19:44:12 +1000 |
commit | 02b9c48fd8d99d8128133692baf2e5c686c5590b (patch) | |
tree | 9eb4f5e5580b96c4f01f60e64d0dba7e8cb5fdc1 /README | |
parent | TODO++ (diff) | |
download | SledjHamr-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-- | README | 22 |
1 files changed, 11 insertions, 11 deletions
@@ -226,7 +226,7 @@ libraries for them more or less mature. Lots of research and | |||
226 | standardisation effort has gone into the major popular ones. So we | 226 | standardisation effort has gone into the major popular ones. So we |
227 | don't really need to deal with that. Problem solved already. Well, | 227 | don't really need to deal with that. Problem solved already. Well, |
228 | except for JPEG 2000, which outside of SL and medical use, no one has | 228 | except for JPEG 2000, which outside of SL and medical use, no one has |
229 | even heard of. It's library support is not so good, and made even wosre | 229 | even heard of. It's library support is not so good, and made even worse |
230 | by the fact that the best decoding algorithm for it is patented and out | 230 | by the fact that the best decoding algorithm for it is patented and out |
231 | of reach to open source developers. Still, lots and lots of SL and | 231 | of reach to open source developers. Still, lots and lots of SL and |
232 | OpenSim content is in JPEG 2000 format, and it is good as a network | 232 | OpenSim 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 | |||
283 | viewers use. They both offer more or less a similar feature set, and | 283 | viewers use. They both offer more or less a similar feature set, and |
284 | both use more or less the same standard libraries underneath. GTK uses | 284 | both use more or less the same standard libraries underneath. GTK uses |
285 | the GLib main loop, which EFL supports via wrappers. I think that EFL | 285 | the GLib main loop, which EFL supports via wrappers. I think that EFL |
286 | fits the SLedjHamr design goals much better though. | 286 | fits the SledjHamr design goals much better though. |
287 | 287 | ||
288 | As a bonus, lots and lots of eye candy, complete with a system for | 288 | As a bonus, lots and lots of eye candy, complete with a system for |
289 | writing your own eye candy, and over riding the system supplied eye | 289 | writing 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 | |||
344 | the network protocols and file formats have been based on Lua. Which | 344 | the network protocols and file formats have been based on Lua. Which |
345 | goes against our goals, so expect that to be temporary. Specifically, | 345 | goes against our goals, so expect that to be temporary. Specifically, |
346 | once we get around to actually implementing the nails protocol stuff, | 346 | once we get around to actually implementing the nails protocol stuff, |
347 | some of the Lua network and file formats will get replaced be nails. | 347 | some of the Lua network and file formats will get replaced by nails. |
348 | 348 | ||
349 | The Lua GUI code is loosely based on my ancient matrix-RAD stuff that was | 349 | The Lua GUI code is loosely based on my ancient matrix-RAD stuff that was |
350 | written in Java. The fact that I had most of it working within a week | 350 | written 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 | ||
392 | In the mean time, and so recently that it only gets released later | 392 | In the mean time, and so recently that it only gets released later |
393 | today, Evas_3D was added to EFL. Evas is one of the sub libraries of | 393 | today, Evas_3D was added to EFL. Evas is one of the sub libraries of |
394 | EFL that deals with canvasses, it's a 3D mesh, camera, and light system | 394 | EFL that deals with canvasses. Evas_3D is a 3D mesh, camera, and light |
395 | designed to be part of Evas. So it has the major advantage of already | 395 | system designed to be part of Evas. So it has the major advantage of |
396 | being well integrated, it's part of EFL. I've added test code for it | 396 | already being well integrated, it's part of EFL. I've added test code |
397 | now, and no flickering. I even have test code using both Irrlicht and | 397 | for it now, and no flickering. I even have test code using both |
398 | Evas_3D in the same window space. It's major disadvantage is that it's | 398 | Irrlicht and Evas_3D in the same window space. It's major disadvantage |
399 | only a very recent project that has (until later today) not been | 399 | is that it's only a very recent project that has (until later today) not |
400 | released, Irrlicht is much more mature. So Evas_3D only has basic | 400 | been released, Irrlicht is much more mature. So Evas_3D only has basic |
401 | stuff, though it's mostly complete basic stuff. On the other hand, a | 401 | stuff, though it's mostly complete basic stuff. On the other hand, a |
402 | lot of what's missing in Evas_3D I was thinking about rewriting for | 402 | lot of what's missing in Evas_3D I was thinking about rewriting for |
403 | Irrlicht anyway. So far one major missing bit is Bullet Physics | 403 | Irrlicht 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? |