At UniDoc, we are always finding new ways to make life easy. Recently, we’ve been working on developing a playground, which allows you to test out the features of the Golang powered UniDoc libraries without having to configure a working environment on your local system.
You can test out your ideas, check the power of UniDoc libraries and see if a concept looks as good as you think it does, by using the playground. This will cut down development time and will instigate creativity by allowing you to test different concepts and ideas quickly.
Another benefit of having a playground is that you can test the power of UniDoc from anywhere. All you need is an internet connection and a browser. The playground runs on your smartphones as well but for the best experience, use a personal computer.
The playground also supports link sharing. This way, you can easily share your concepts and ideas with your colleagues and get their feedback. The playground can also be embedded on websites by using the embed code that is generated automatically with each playground example, it's that simple.
Take a look at what the Golang powered playground can do by checking out the following examples:
Create a New PDF
We create a simple playground that creates a basic PDF with an invoice. View and edit the code below to get familiar with how UniPDF works. The code is written in elegant and simple Golang:
Work with Excel Sheets
You can also work with excel sheets, validate formulas, create charts and do a whole lot more using the UniDoc playground. Here’s an example of a simple line chart in the playground.
Try it out, make changes and view the changes happen live with the power of Golang:
How to load Files on the Playground
The only major difference you'll observe while using UniDoc on the playground, is how the files are loaded. On the playground, we use filestore to upload and download files.
filestore.Open(path.file) is used for opening a file that is already uploaded on the playground.
filestore.Save(path.file, buffer) is used to store files onto the playground, from where you can download them. The first argument is the path to the output file. While the second argument is the stream buffer that contains the content to be written in the output file.
To make it easier for our customers to get started with our libraries, we’re planning on building a knowledge-base. The knowledge-base will comprise of various code samples that users can use to get started on their UniDoc projects and test out ideas without having to set up an environment.
We're always adding new features to UniDoc, to keep up-to-date with the latest additions, subscribe to our mailing list. If you want a feature added in the library or have any other query, contact us through the chat button on the bottom right.