Jump to content

Rekindled Phoenix

Members
  • Posts

    471
  • Joined

  • Last visited

Posts posted by Rekindled Phoenix

  1. Thanks Lazlo. I tried.

     

    Several people have different views on coding procedure. Eventually I will update your amazing library to be an extension of the official libraries.

     

    Your libraries had absolutely no bugs, which made maintenance easy!

  2. I know that you have opinions, and in most cases it's great. Your dedication to the fastest, optimized, game engine can be rewarding, especially when you come up with showcase worthy material like multi-threading examples.

     

    It's when you do spout nonsense that defending someone's personal knowledge becomes a burden.

     

    I wish that Josh's servers hadn't crashed, or I'd have more than a few links I could post right now.

     

    Recently, I have given up trying to argue against you, and treated your visits to the C# forums as a running joke. I even put part of that in the recent poll found here, mentioning Fortran as an option. I treat your comments with dignity, but when they seem false or made up, I find them amusing instead of factual.

     

    As the years have passed using Leadwerks I have realized that we cannot change your actions, opinions, nor would you us. I am not part of a 'hate clan', and I have not complained about these issues directly to Josh. Just provide the best applications you can, with solid references.

  3. If you haven't been following the recent LE news, Josh has said he will officially support .Net languages.

     

    Since Leadwerks.Net is an OO wrapper with inheritance, it will not be compatible with any "official" DLL releases in the future.

    I am debating the future of Leadwerks.Net, whether it be an abstracted DLL that is compatible with the official files, or stay a completely separate "unofficial" release.

     

    For those who use this library, what do you want?

    I'd prefer responses from those who use Leadwerks.Net over any other wrapper

     

    - Layer on top of official libraries (Compatibility!)

    - Separate download stay unofficial (Flexibility!)

  4. So why not join forces and make the official .NET library the best it can be?

    I will probably use Leadwerks.Net for a while, and in time, use the "official" libraries once released.

     

    join-the-dark-side.jpg

    Hahahaha. Nice.

     

    Do I get to wear black if I join?

  5. This might be a good time to change that seeing as LE.NET is becoming the official .NET library for LE2.

    It's not going to happen. The only thing that they might share would the be PInvoke'd methods to access the DLL entry points. It would be pointless just for one class to share similarities.

     

    I have a feeling you won't like it though as it seems it'll be more like LE.NET is today and not an OO library like Leadwerks.NET.

    I don't like the library, but that doesn't mean I have to use it. I realize that my opinion does not depict the entire forum either. I know that there are those who like the coding style of a C++ library. I accept the fact that it would cause Josh more strain to write different documentation, etc.

  6. It would seem a big criteria for Josh to officially support is documentation. So unless Leadwerks.NET is structured the same as LE3 C++ it seems it won't do.

    *sigh* Damn. It's upsetting that the libraries cannot be in the format that best suits the language, though I understand Josh's reasons. If it's a direct copy of the API, you will want to look at LE.Net, which ZioRed has taken the responsibility of managing.

     

    I think Leadwerks.Net will become the "optimized" version, still giving users an option to choose a particular style.

     

    At least the language will be officially supported, which is a big plus!

  7. The only difficulty are the calculations for a dynamic heightmap that updates a mesh. Everything that doesnt call the engine (math and algorithms) can be done in a separate thread.

     

    Try the demo for yourself and see the amazing performance.

  8. I mainly use Leadwerks.Net but what drives me nuts is that the actual dll commands are internal and you can't access them outside. (Which is disturbing if you need to add a yet not implemented feature).

    This is done on purpose. An inheritable strongly-typed library is structured to keep people from calling the standard Leadwerks functions (the dll commands). Lazlo's layout keeps developers from using one class to solve all of their needs. What's wrong with the "using" statement?

     

    If there are a few commands you think that should be accessible, post it as a reply to the pinned thread.

     

    I believe Leadwerks.Net should use LE.Net so you can seperate the engine and Leadwerks.Net commands and we only have to maintain one project which is handlicng directly with the engine.dll. Also it might be easier to extend current functionality. Also maybe separating the whole DllImport stuff into different files (based on there use, eg: Terrain, Entity, etc) may help to organise the whole project better.

    Leadwerks.Net will never use LE.Net as it's core. They are designed differently.

    Lazlo's library has layered-inheritance, updated namespaces, and events

    ZioRed's library is a clean, "TEntity" port of the API.

     

    I think we may disagree on the way the libraries should be structured. The dll commands for the importer should be in one maintainable class. Imagine trying to find a command with an incorrect "pInvoke" and scouring though the layers of inherited classes to find such a method.

  9. It can be depended on hardware, as you can see in source, there is so simple. I'm working on GeForce 250GTS, maybe for Radeons must be some different code. What hardware do you have?

     

    Windows 7 (64bit)

    ATI Radeon HD 5700

×
×
  • Create New...