1 Reply Latest reply on Mar 28, 2007 12:00 PM by Justin_Makeig

    Bridge license

      The bridge license seems to have changed or at least become ambiguous. Initially the license in the code and in the license txt file was the same and was completely nonrestrictive. That no longer seems to be the case? Has there been a change in the policy, or is this some kind of mistake?

        • 1. Re: Bridge license
          It looks like FABridge is now part of LiveCycle. This presents a problem for me because I don't want or need all of the other stuff that comes with LiveCycle and the free version of LiveCycle is limited to one, single-CPU machine, if I'm not mistaken.
          Looks like I'll have to write my own slimmed down bridge using ExternalInterface. Ugh.