I have created a project using APGL version of iText. Now, I want to share this code in the Github account of mine. But, I donot know what should I do so that not breaking the rule. May you help me with clear instruction?
If licence.txt is enough, do you have a sample licences.txt?
Note: I am using Java verions of iText
Copy/paste from the iText mailing list where the exact same question was posted:
The source code headers of your own code should mention the AGPL
(similar to what is present in the iText source code headers, but with
references to your own project).
As for the licenses.txt: it is important that people downloading your
source code know that they are also using iText, so a licenses.txt
with a reference to the iText web site http://itextpdf.com and
especially where to find the iText code is sufficient, for instance a
link to https://github.com/itext/itextpdf/
Please avoid cross-posting questions on different forums. Pick the forum you like most and stick to it.
Related
I come from the world of JavaDocs and love the DX of working on a thoroughly-annotated application after a certain level of complexity.
Being able to hover over and peek all the props (and implied types) of a component with some brief documentation would save me so much time instead of having to open up and read through the whole component. Better yet, running a command to generate a documentation site just like you can with JavaDocs would be dope!
Are there any standards or tools built around creating SvelteDocs? I looked through the VS Code marketplace and didn't see any documentation tooling related to Svelte.
I stumbled upon this question in search of more in-depth documentation for the hover/peek documentation method I've been using. It seems that it is not very well documented (ironically) but it is a part of Svelte language-tools and I've been using it for some time with Svelte for VS Code so I'm sure there was more documentation at some point. The way it's used is as follows in your component. I remember reading somewhere that it needs to be the first thing in your component, but I can't find that source anymore.
<!--
#component
some markdown here
-->
For some reasons the only documentation I can find of it is here. But it provides very nice markdown support so you can craft some very informative hover/peek documentation for your components.
EDIT:
Still can't locate official documentation for the #component commenting feature but realized it is indeed described in the FAQ: https://svelte.dev/faq#how-do-i-document-my-components Does this information belong in the actual docs? Maybe.
After more digging, I found just a couple projects for documenting Svelte.
SvelteDoc Parser -- takes a VueDoc approach, based on JSDoc standards, generates JSON documentation for Svelte components
Svelte-Docs -- documentation in Markdown mixed with Svelte's features, can embed components in the generated doc pages
Both look interesting while taking completely separate approaches to solving the issue of application documentation. Perhaps there's still room to build a CLI-based site generator for the SvelteDoc Parser which could be turned into a VS Code plugin!
It is difficult to find a good one. I recommend
https://github.com/carbon-design-system/sveld
It looks very promising. It offers export in Typescript definitions, JSON and Markdown. In my opinion there is only one critical bug left (Markdown generation) so hopefully it can be used very soon.
I want to set up an open data website with the typo3 cms. For open data I do not know how I can manage with typo3. After a tour on google I found the CKAN API.
My questions: is it possible to integrate them? If not, are there any other solutions with Typo3?
Thank you for your possible answers
I don't know an implementation of the CKAN API and a quick search in the TER (TYPO3 extension repository) never showed any results.
Nevertheless there exists an extension filemetadata which is doing probably partially the requested features. Here the links:
filemetadata on Packagist.org
filemetadata on github.com
For the case that the features are not enough or the structure is not like desired a new extension could be programmed where some basics could be taken from the extension above, at least it could serve as example how some things are done.
It has to be mentioned that some extensions are never registered in TER but only available on github perhaps. So before programming something a deeper search might be advisable.
In former times another extension was common for Digital Asset Management, the extension-key and Name was dam. That extension is not compatible with current TYPO3 versions and taking it as example is probably no good idea as much outdated code had to be adjusted.
Nevertheless the advised example above is not the only possibility, the search for file metadata still shows other extensions that are compatible to current TYPO3 versions 7 and 8 which could be taken as examples. Perhaps changed search-words still let you discover more useful extensions.
The mentioned extension in the top is supported by the TYPO3 core team, the others are provided by other developers. I never compared the extensions and you had to see code or/and features by yourself. So I never endorse any of these solutions as usage is rarely requested.
If you search for the most recent code it's always good to search on github first for the development branch or a release that is not (yet) published in TER. Another source of information is forge.typo3.org, there many extensions are listed too, some even with repository on git.typo3.org, perhaps it's worth it to mention that this source is abandoned by some developers in favor of github.
Technically it would be even possible to extend any found extension and add more features or change something just by another extension - without touching the original extension. But before thinking too far you should first have a look if any found extension could satisfy your needs already.
For further questions that might be already related to coding you should open new question(s) with more detailed explanation and code-examples, even if that doesn't work yet.
EDIT 15th Oct 2018:
Just got a hint about a helpful extension for those purposes: extractor. Additional fields shall go to sys_file_metadata and be a part of the extraction service.
As I never did verified it by myself I can't give further hints in the moment.
I could not find the com.lowagie.database.DatabaseConnection and com.lowagie.database.HsqldbConnection in the itext-5.5.5.jar.
Thus I could not do the exercises in the book titled itext In Action. Does anyone know where they are?
You can find the classes here and here.
Which version of the book do you own? If you own the the first edition there was an update (second edition) released. In 2009 there was a bigger change to the iText library which also renamed the package from com.lowagie to com.itextpdf.
And as I just saw you may also have a look here.
The iText projects recently moved from SourceForge to Github. You can find all the code related to the second edition here: https://github.com/itext/book
Thanks all of you. My book is the second edition. According to my experience, I think the most convenient way to get the material needed for book's exercises is to go to the publisher website (www.Manning.com/lowagie2/) to download the source code (the big file 26MB).
Recently I have downloaded the Nuxeo code, SDK and Nuxio IDE for the development purpose. I am also able to do build the project run the SDK and importing project into eclipse. But as Nuxeo guys know, it's a huge project and document doesn't contains details about the Code Flow. So, I am sucked. To develop and fix bugs I need to know the existing code structure, functionality of each projects(modules/bundles) , how to identify the code flow if user click on a button. So, please help me
It depends on the UI you want to debug. If it's the JSF UI, then the buttons are usually associated with an "action" contributed from an XML file. You can then follow the thread.
Your question is too much generic to give you more details. Do look for development guidelines and/or how-to fix some bugs? In the latter case, it depends on each kind of bug, the Nuxeo version, the original code writer (Nuxeo legacy code or customized code), the use of Nuxeo Studio or not...
I am using iTextSharp version 4.1.2 and cannot update to newer version because iText changed
their licence agreement.
I am very satisfied with this version and it's working fine for me.
I can't find anywhere how to produce pie or bar or columns graphs and charts
with that version and looks like all documentation over the internet been removed.
If you are using older version and by the chance you have documentation can you please share
or point me to the source, or explain how?
iText doesn't have built-in support for charts or graphs. Instead you are encouraged to use a 3rd-party library to generate these and then add them as either graphics or PDFs.
Another option as outlined in this post is to use the iTextSharpExtensions. Please note that although it has the word "iText" in it is in no way endorsed by the makers of iText.
Also, as a quick side note, please read FAQ, specifically the "Why shouldn't I use iText 2.x (or iTextSharp 4.x)?" explaining some of the myths of the license of the version you are using.