celestia networking-patch (http/ftp)

[hank]

I made a new update which now makes "real" addon support possible.
meaning it can now create directorys under the "extras" folder and supports multiple URLs provided by the celestia.cfg

I also updated my original post with a detailed description of this patch.

phoenix,

How much of your patch could be implemented using Lua?

- Hank

[phoenix]

uhm I have no idea about lua and its possibilites so I'm only guessing here
but the basic changes to the celestia-code are insignificant.

considering only my http-patch (not the gzip-stuff) 99% of the new code is in http.cpp and md5.c which eventually can be compiled to be called with lua, i think

the hardcoded stuff in celestiacore.cpp is just 3 lines: calling the http-class and executing the download-process.
naturally the new config-options are included in configfile.cpp + header

so if this would be possible to be called with lua, how do we get the lua-stuff executed "before" file-parsing?

[hank]

uhm I have no idea about lua and its possibilites so I'm only guessing here ;)
but the basic changes to the celestia-code are insignificant.

considering only my http-patch (not the gzip-stuff) 99% of the new code is in http.cpp and md5.c which eventually can be compiled to be called with lua, i think :?:

the hardcoded stuff in celestiacore.cpp is just 3 lines: calling the http-class and executing the download-process.
naturally the new config-options are included in configfile.cpp + header

so if this would be possible to be called with lua, how do we get the lua-stuff executed "before" file-parsing?

It should be possible to hook into Lua immediately after the configuration file is read. Also, the hash table of configuration file entries could be retained and made accessible from Lua so that new configuration file entries could be processed via Lua. If the rest of your new code could be compiled externally and dynamically loaded from Lua, I think that might do it. Would you be willing to give it a try?

- Hank

[phoenix]

It should be possible to hook into Lua immediately after the configuration file is read. Also, the hash table of configuration file entries could be retained and made accessible from Lua so that new configuration file entries could be processed via Lua. If the rest of your new code could be compiled externally and dynamically loaded from Lua, I think that might do it. Would you be willing to give it a try?

- Hank

sure, why not.
I'll have my source-patchfile up in a few minutes and then will start looking for nice lua howtos and reference-pages.

I already found a libcurl-lua-port here.
but thats probably not the right approach to do this... i think

[phoenix]

the sources are up now including a few linux related bugfixes.

hank, by using lua I assume you refer to your posting about loadlib?

[hank]

hank, by using lua I assume you refer to your posting about loadlib?

That's part of it. I've also been experimenting with a scheme for hooking Lua code into Celestia at strategic points. To do this I've added a "LuaHook" entry in the Celestia configuration file which specifies a file containing Lua code to be run when Celestia starts up. The Lua code installs a table of Lua functions (a Lua object, actually) that can be called from Celestia at various points. For example, I put a call into Lua in CelestiaCore::draw() to implement custom overlays. I think this scheme can be made to work for your purposes without too much trouble. For now it still requires building a custom version of Celestia, but I'm hoping that Chris will consider including something like this in the 1.5 release.

I've started a new thread here to explain this in more detail.
- Hank