Results 1 to 12 of 12

Thread: ArmorPaint - open source

  1. #1

    ArmorPaint - open source



    open-source 3D painting tool ArmorPaint

    http://www.cgchannel.com/2020/01/che...ool-armorpaint

    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  2. #2
    Registered User Oldcode's Avatar
    Join Date
    Jan 2004
    Location
    Boston
    Posts
    447
    That looks cool!

  3. #3
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,731
    Quote Originally Posted by Oldcode View Post
    That looks cool!
    What it doesn't look like is a "Feature Request".
    John W.
    LW2015.3UB/2019.1.4 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  4. #4

    why? implement the code.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  5. #5
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,731
    Did you notice it's mostly written in/for Haxe?

    Taking a decent-sized body of code written for a high-level cross-platform language/environment like Haxe, and integrating it into an native-code application which consists mostly of C and some C++ requires a very substantial amount of effort, both in design/planning and in implementation.

    Think of it this way: The simple LOGO app "REPEAT 4 [ FD 10 RT 90 ]" is a _tiny_ bit of code, and took a second or two to plan and implement. However, migrating the same app to C/C++ would require vastly more planning to replicate, both in planning (figuring out 2D gfx libraries, dealing with platform IO & gfx concerns, etc.) and in implementation (simply because it would take many, many more lines of code to replicate in C/C++).

    The problem moving from a high-level language and environment to a platform-specific low-level language is that first you need to figure out how to replicate all the environmental services and abstractions by the high-level code such that equivalents are available (where possible) for your low-level language coding. Then, not only do you have to implement low-level code to produce the same results, but also to replace any high-level environment services you weren't able to easily replicate (or for cases where the high-level service doesn't "mesh well" with your platform).

    It's not that it's impossible, but it's a HECK of a lot more work than integrating the same app if it were written in C/C++ for Windows or similar -- that would actually make the job much easier, mostly because it's at the "same linguistic level", and dealing with the same environmental services/abstractions as LW itself (and they understand how to map those to Mac, etc.).
    Last edited by jwiede; 01-24-2020 at 09:59 PM.
    John W.
    LW2015.3UB/2019.1.4 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  6. #6

    Did you notice it's mostly written in/for Haxe?
    Oops...!  no, sorry, I didn't.

    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  7. #7
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,731
    Just for completeness, there's another big issue I feel obliged to mention:

    You also definitely need someone very practically familiar with both Haxe, the application, and C/C++ to help with the migration.

    Why?

    Because as a working Haxe application, there is undoubtedly idiosyncratic code present in order to produce (or avoid) issues with the Haxe language/environment. It's vitally important that those idiosyncratic code sections are noted and the resultant idiosyncratic behavior is well-understood.

    Someone who just knows the language/environment "by book" won't easily be able to identify such idiosyncratic code "in the wild". As a result, they'll instead use a "literal translation" when migrating those areas, resulting in behavior different from the original application's behavior -- or, put better, it means they just introduced defects. Worse, if they don't understand the original app's behavior really well in the first place, chances are they'll also have difficulty identifying that their code's behavior difference is the cause of the problems (or even that there is a difference in behavior).
    John W.
    LW2015.3UB/2019.1.4 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  8. #8

    yep, sorry, i missed it.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  9. #9
    Newbie Member
    Join Date
    Dec 2003
    Location
    Florida
    Posts
    20
    Quixel Mixer is about to be updated to have 3D painting and its free. Just use that.

  10. #10

    well, not open source, not free after beta.

    other than that, it looks quite alright for OneManBand.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  11. #11
    Newbie Member
    Join Date
    Dec 2003
    Location
    Florida
    Posts
    20
    Quote Originally Posted by erikals View Post
    well, not open source, not free after beta.
    Mixer is free even after the beta. This is now the plan since they're owned by Epic Games. And it will make Armor Paint look quite tame in comparison.

  12. #12

    ah, sorry, seems i'm wrong about Quixel...

    https://help.quixel.com/hc/en-us/art...a-subscription
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •