I have upgraded xep from 4.4 version to 4.30, bcs I need PDFForms.
I downloaded v4.30 from renderX page using my license.
But when I tried rendering PDFforms or BarCode with my license it didn't work.
I switched to trial license and it worked just fine.
So I think this license doesn't support new xep features.
<product name="XEP">
<limit name="server">1</limit>
</product>
<product name="DevKit">
<limit name="full">1</limit>
</product>
This is what the license looks like. I don't know if I have to buy new license or there is a way to update the license.
RenderX support won't answer me, that's why I'm asking here.
I eventualy got in contact with RenderX and they said that license key from 2005 is not available for the Interactive Forms or Barcodes add-ons.
I have to buy new license and the add-ons.
Related
I am looking for documentation for Ace to do "Floating UI" , i want to to like facebook "Chat Heads". So far there is no documentation only mentioning coming soon , which means avaliable but undocumented right?. Is it already available in github latest master?
They decided to close the support for this project:
As of December 2016, this project is no longer maintained by Microsoft. We built ACE to provide developers with an “escape hatch” to access native code from within JavaScript. After nearly a year in production, we learned that most developers are satisfied with the access granted by Cordova’s Plugin Model. Thus, we’ve discontinued active development. We appreciate your interest in the project and hope you found it exemplary of Microsoft’s commitment to experimentation and open source software. if you're interested in continuing this project, please feel free to fork it. As of December 2016, we will no longer monitor or respond to open issues. You can keep up with other projects from Microsoft’s Cordova team by visiting http://taco.visualstudio.com. Thanks for your support!
I was also looking some plugin to implement "chat heads" in Cordova, without any luck :(
I found the previous releases (tags) on github say "Z3 is licensed under MSR-LA (Microsoft Research License Agreement)".
My question is whether they are also on MIT license now. Could you kindly please clarify? Thanks!
I don't understand the legal world of licenses, but to be on the safe side I would assume that previous releases carry the old license since that's what's included in distribution packages.
I would like to use core-plot library for an app. But before I'm starting im confused where to put the license. In the App or on a website?
What should be included for the BSD license ?
You don't include a license for a 3rd party library. It's already included by the library developer. What you sometimes have to add is an attribution (depending on the license). That means you have to list the developer's name and maybe a link to the library home page in your docs, about box or a prominent readme file. From what I remember the BSD license doesn't require attribution, so just include the lib and your done.
However, it's considered a nice move to still give some attribution to the dev, regardless of whether the license requires it or not, as this shows your appreciation of the work done and gives the dev some reputation (which is often the only payment for their work).
I'm starting to dive into a customer requirement that we use FIPS 140-2 for data at rest and data in transit. From my (limited) reading so far, it sounds like iOS 7 and up have FIPS support built in. I've also seen articles on the subject (iOS with FIPS) point to building OpenSSL and including that in your project to get FIPS support. I'm not sure why OpenSSL is necessary if FIPS is already included in iOS 7+. Am I missing something?
At the time of this writing OpenSSL FIPS is pretty much broken for newer Apple devices and versions of iOS past 6, because getting it to compile requires heavy modification of the build process, which is absolutely disallowed for FIPS compliance. You get a library, but not FIPS compliance unless you re-certify. Try stepping through the documented build process to observe the minefield. Community contributions to help resolve the issues have not been incorporated. It is also not very secure because it isn't responsively updated for threats. Heartbleed will be with us for years, but CommonCrypto turns on a dime in comparison, being re-certified as needed and updated along with other OS updates. Use Apple CommonCrypto.
One of the many threads about why it is broken: https://groups.google.com/forum/#!topic/mailing.openssl.users/V_HITNhWaDA
A related(not duplicate) question by me. The only answer breaks FIPS compliance.
Unknown cpu type when compiling OpenSSL FIPS Capable libraries for arm64 or arm7s
Unless you need some functionality that is in OpenSSL that is not in Common Crypto use Common Crypto.
The reason that Apple no longer supplies OpenSSL is due to many instances where SSL is not backward compatible and an Apple supplied current version may not be compatible with an app that was built with an earlier version.
Further, Common Crypto uses the build-in hardware crypto and OpenSSL may not.
Why use OpenSSL for FIPS 140-2 vs relying on CoreCrypto on iOS?
OpenSSL is available on a wider array of iOS platforms. For example, OpenSSL includes iOS 5 through iOS 7 using the A4 through A6 processors. There are more iOS validations, but they have not been given to the public under Certificate 1747. For example, the foundation already has an iOS 8 validation in progress.
In addition, OpenSSL is available on non-Apple platforms. The latter is appealing because the means the same code base can be used on multiple platforms, including Windows, Linux and Android.
Apple got its first validation on May 2013, which meant there was nothing available from Apple from 2010 to summer of 2013. That was a big void. Apple still only provides a validated module up to iOS 7.
And during the time of missing vendor support, Apple made it appear they had a validated module through their marketing literature. (Apple had a "Module In Progress", which is different than a "Validated Module". And it took them years to get it validated, which was kind of unheard of).
As someone who follows these things, Apple's tactics from 2010 through 2013 were clearly meant to confuse those who were looking for FIPS 140 validated modules. (I wrote to the CMVP about Apple's despicable practices. The CMVP will request a Cease and Desist order for vendors like Apple. Apple is not the only vendor to confuse and lie to folks - CipherCloud did it too).
I've been working on an iOS project for some time now, creating hundreds of source files, and now that's it's good and done, I realize something sad : I edit the copyright file template before getting to work, and all of my files have this lame format :
//
// MyClass.h
//
// Created by Redwarp on 3/25/13.
// Copyright (c) 2013 Redwarp. All rights reserved.
//
And that's not cool ! I would like to replace it with something more like that :
/* This software is licensed under the Apache 2 license, quoted below.
Copyright 2013 Redwarp <redwarp#gmail.com>
Licensed under the Apache License, Version 2.0 (the "License"); you may not
use this file except in compliance with the License. You may obtain a copy of
the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under
the License.
*/
Anyway. I could probably write a script, that searches all my files and replace the first "//" lines with a better comment, but I'm sure there is a tool out there that does that perfectly.
Except : I can't find that tool anywhere.
Would anyone know of such a tool ? (Or might it be that I'm a fool ?)
I ended up using the script I found here : http://gergap.wordpress.com/2009/06/03/howto-recursively-replace-file-headers-of-source-files/
Does exactly the job I wanted to do, and spared me the burden of doing it myself.