Support: FAQ

What is the saved gincker?

After creating your charts, graphics, or trading strategies on the Gincker platform, you will save the result as a gincker - the unique URL link. [more]You can bookmark the gincker for later use or share it with friends, colleagues, or other users. The saved gincker has the ability to deliver DYNAMIC graphics content, namely, users can use the gincker to regenerate, manipulate, modify, and customize the chart/graphics or trading strategies to meet their own requirements.

Currently, we have place several hundreds of free and paid ginckers to the Marketplace. These sample ginckers not only show the power and capability of the Gincker platform, but also illustrate the procedure and format used in creating charts, graphics, and trading strategies using different templates.

Another advantage of using gincker is its small file size: it is simply a single line of text with the format “https://gincker.com/{template}#{xxxxxxxxxx}”, which is shorter than a Twitter message. A saved gincker consists of three parts: gincker.com that is our website name, the template name, and ten randomly generated characters that are used to identify the gincker. Therefore, exchanging ginckers over the Internet will be much faster and more efficient than transmitting large graphics or image files.

Why the gincker link does not work?

Usually, Gincker will automatically generate corresponding output when you click on a saved gincker link. For example, the platform will create a 3D globoid surface when clicking on this gincker. However, sometimes, some broswers may not generate the output automatically for you after clicking on the saved gincker. In  this case, you need to refresh your  broswer to get the result.

Why is the gincker.com website so slow?

Typically, a web application will always takes extra time to load if the page involves complicated implementations. After the first request, the compiled resources are cached, so the subsequent requests could be much faster. Gincker is a big and complicated platform. You may feel little bit slow on your first access to Gincker. Please be patient. It will become faster and faster for subsequent requests.

 

 

 

 

 

Future Gincker

Distributed platform, easy-to-use, and ability to create and deliver dynamic content are the key features of Gincker. These features make Gincker suitable not only for graphics and technical analysis but also for other fields [more]as well, i.e., Gincker is much bigger than graphics and technical analysis! In the future, we will extend Gincker’s applications to every aspects of our daily life.

Future Gincker will have the following features:

  • Gincker can be any app. Gincker can have wide applications in various fields. We plan to apply Gincker to the following fields in near future: numerical methods, education, mathematical and physics modeling, artificial intelligence (AI), gaming, and other scientific and engineering fields. In fact, we can convert any software packages, business applications, or software services from SaaS (Software as a service) or ASP (application service provider) into templates and integrate them into Gincker. It is also possible for Gincker to find applications in the social science fields. This means that any software package, business application, or software service is simply a template on the Gincker platform.
  • Gincker will be for everyone. We will keep the future Gincker as an SaaT-based web-distributed platform without the need to install anything on a user’s local machine. We will continue to improve Gincker’s user interface and put the easy-to-use feature as our top priority. Gincker will further encapsulate and centralize all the complex programming and implementation details into its internal core engine, while exposing a simple and common interface to users. We will let users believe that using Gincker is as simple as using a calculator.
  • Gincker will be everywhere. Due to its ability to create and deliver dynamic content, we will gradually make Gincker an effective communication tool in our daily life. For example, when communicating with colleagues to discuss computation results or a stock trading strategy, you do not need to send an email with a large attachment anymore; simply include a gincker in your email instead.
  • Gincker will be a live-trading platform. We will add more features to the technical analysis templates so that the individual traders and investors can backtest their trading strategies and go to live trading on Gincker in a seamless fashion. 
  • Private Gincker. Previously, we mentioned that the platform allows users to save their work as either open or confidential ginckers. However, both open and confidential ginckers are created using the public templates implemented on the Gincker platform. In the future, we will allow corporations, organizations, schools, or government agencies to implement their own templates on Gincker. We will provide support to help them convert their software packages, business applications, or software services into templates. Those templates and corresponding output ginckers will be private and will only be able to be used within the organization who developed them.
  • Smart Gincker. As the number of templates and ginckers on the platform increases, we will gradually make Gincker become a true expert system with AI capability. It will be able to pick and recommend the right templates and ginckers to users according to the user’s background and other attributes. We hope Gincker will become smart enough to generate graphics or other output content automatically according to the user’s specifications or simple descriptions without even needing to provide a mathematical formula or input data.

Gincker: A New Platform for Technical Analysis in Finance

Gincker is a new SaaT (Software as a Template) based platform for creating and delivering dynamic graphics content. It is also a powerful tool for technical analysis in quantitative finance. [more]Gincker converts different financial charts, technical indicators, trading strategies, back-testing approaches, and pricing engines into templates and exposes a simple and common interface that allows users to create stock charts, indicators, and trading strategies in just one click without the need to write a single line of code.

Traditional Method in Quantitative Analysis

Quantitative analysis, trading strategy development, and algorithm trading are often called the rocket science of Wall Street. This field applies mathematical and statistical methods in order to create algorithms to solve financial and risk management problems. Professionals who work in this field are usually required to have strong background and advanced degree in math, statistics, and computer programming. These professionals are known as quantitative analysts/developers, or simply "quants".

Quantitative analysis also requires a variety of resources, including large database for market data, fast and reliable computer services, IT department supports, libraries and software packages used for trading strategy development. In the past, due to the high cost and high entry barrier, only financial institutions and hedge fund firms can effectively carry out quantitative analysis.

For individual investors and traders, there are two options to perform quantitative analysis: implementing your own quantitative analysis system or using existing analysis tools. Implementing your own analysis tools from scratch requires you to have strong background in math and finance as well as programming skills; and also takes lots of effort and time. This is usually not the solution for most individual traders.

Most likely, you end up to use the existing quantitative analysis tools. Those tools, whether commercial or open sources, have the following issues:

  • Different tools may be implemented with different programming languages, such as C++, C#, Java, Python, VBA, Matlab, etc., which usually require users to write code have a strong mathematical background and programming experience. Therefore, these graphics packages are for technical professionals, but not for the general public – the user base is very limited.
    Waste resources and time. Independent graphics software packages are large and complicated and usually require installation on a local machine. Users need to install multiple packages in order to create different types of graphics, which takes up lots of computer resources and time for configuring the development environment.
  • Hard to use. Creating different types of graphics requires different graphics packages with different interfaces. Even for experienced graphics developers, it is still difficult to switch from one package to another because users have to learn how to use the new package in order to create a new type of graphics.
  • Hard to prepare the input data for the packages because each package requires different input format, which is not standardized.
  • Hard to share and explain the output results. The outputs from different graphics packages are unidirectional, i.e. independent of the package. They are usually a numerical data file with different formats, static graphics, or images with a large file size. Without accessing the original graphics package used to create those results, users have no way to confirm, reproduce, modify, and customize the graphics content. In addition, exchanging large graphics or image files over the Internet is slow and inefficient.
    Selecting, evaluating, and integrating suitable packages into applications can pose a significant challenge and take up a lot of time. This is usually not a recipe for rapidly building applications on web time.
  • Different packages may be implemented with different programming languages, which usually require users to have a strong mathematical background and programming experience. Therefore, these graphics packages are for technical professionals, but not for the general public – the user base is very limited.
  • Recently, the hosted solutions, such as SaaS (software as a service) or ASP (application service provider), allow users to access software over the Internet. The SaaS or ASP approach does solve the problems associated with installation and configuration of the development environment, however, the other issues remain. For example, different software services on SaaS or ASP are still independent – they are still have different user interfaces and input/output formats.

Gincker: A New Platform for Charts and Graphics

Gincker is a new SaaT (Software as a Template) based platform for creating and delivering dynamic graphics content. It converts different graphics software packages into templates [more]and expose a simple and common interface that allows users to create advanced graphics by entering a mathematical formula, pasting a dataset, or loading a data file without the need to write a single line of code. 

Traditional Graphics Software  

We have all heard the saying, "A picture is worth a thousand words." Charts and graphics are some of the most informative pictures and play an important role in every application. They make mathematical functions or data easier to understand, improve communication effectiveness, add interest to reports, and have wide applications in our daily life.

Generally, there are two options to create charts and graphics: implementing your own chart and graphics program or using existing (open-source or commercial) software packages. Implementing your own program for creating even simple charts and graphics from scratch takes lots of effort and time. This is usually not the solution for the web time.

Most likely, you end up to use the existing charts and graphics packages. Traditional graphics software, whether commercial or open sources, usually comes as independent packages. Different packages have different interfaces and output formats.

Those independent graphics packages have the following issues:

  • Waste resources and time. Independent graphics software packages are large and complicated and usually require installation on a local machine. Users need to install multiple packages in order to create different types of graphics, which takes up lots of computer resources and time for configuring the development environment.
  • Hard to use. Creating different types of graphics requires different graphics packages with different interfaces. Even for experienced graphics developers, it is still difficult to switch from one package to another because users have to learn how to use the new package in order to create a new type of graphics.
  • Hard to prepare the input data for the packages because each package requires different input format, which is not standardized.
  • Hard to share and explain the output results. The outputs from different graphics packages are unidirectional, i.e. independent of the package. They are usually a numerical data file with different formats, static graphics, or images with a large file size. Without accessing the original graphics package used to create those results, users have no way to confirm, reproduce, modify, and customize the graphics content. In addition, exchanging large graphics or image files over the Internet is slow and inefficient.
    Selecting, evaluating, and integrating suitable packages into applications can pose a significant challenge and take up a lot of time. This is usually not a recipe for rapidly building applications on web time.
  • Different packages may be implemented with different programming languages, which usually require users to have a strong mathematical background and programming experience. Therefore, these graphics packages are for technical professionals, but not for the general public – the user base is very limited.
  • Recently, the hosted solutions, such as SaaS (software as a service) or ASP (application service provider), allow users to access software over the Internet. The SaaS or ASP approach does solve the problems associated with installation and configuration of the development environment, however, the other issues remain. For example, different software services on SaaS or ASP are still independent – they are still have different user interfaces and input/output formats.

The Gincker Platform

Gincker aims to solve those issues by converting different graphics packages and programs into templates that have a simple and unified user interface. This interface consists of two modules: an input module and a graphics customization module. The input module allows users to enter a mathematical formula, paste a dataset, or load a data file, while the customization module is used to customize the graphics, such as color, axes, title, colormap, etc.

The Gincker platform first processes the inputs from the user interface and converts them into a standard graphic data format that can be used by Gincker’s render engine (GRE). The GRE then creates the graphics according to the specified template, processed data, and customization options from the user. The output results will be displayed on the screen.

Unlike traditional graphics packages or services that directly save the graphics content as output, the Gincker platform saves the output as a unique URL link called a gincker through the output routing engine (ORE). The ORE couples with the GRE and the state storage database that stores the development environment state and the template used to generate the output.

Comparing to traditional independent graphics packages or services, we can call the Gincker platform an application template provider (ATP) or software as a template (SaaT). The SaaT-based Gincker platform possesses the following advantages:

  • Wide user base. Gincker is developed not only for technical professionals, but also for teachers, students, and the general public. Gincker converts different software packages into templates. It encapsulates and centralizes internally all the complexities and details of computer graphics programming and implementation associated with each template and exposes a simple and unified interface to users. This allows users to create advanced graphics by simply entering a mathematical formula, pasting a data set, or loading a data file, without the need to write a single line of code. This way, Gincker can easily expand its user base to the general public.
  • Short learning curve. As long as users work through one template on the Gincker platform, they will be able to use all the other templates to create advanced charts and graphics. This is because all templates on Gincker share the same user interface and input/output formats.
  • Dynamic output results. The output from the Gincker platform is a gincker – a simple URL link. This gincker can be embedded in external websites, incorporated into desktop applications, or integrated into research papers or reports. Users can also bookmark the gincker for later use or share it with friends, colleagues, or other users. The advantage of ginckers over the static results from traditional software packages is that a gincker can deliver dynamic graphics content – users can use the gincker to regenerate, manipulate, modify, and customize the graphics to meet their requirements. This is because a gincker is bidirectional relative to the platform; namely, it interacts with the Gincker platform via the ORE and brings Gincker’s development environment state directly to users. Thus, users can access the same development environment as the gincker’s developer does. We can consider a gincker as a recorder of the development environment state used by its developer.
  • Small file size. Another unique feature of a gincker is its small file size: it is simply a single line of text with the format “https://gincker.com/{template}#{xxxxxxxxxx}”, which is shorter than a Twitter message. It consists of three parts: gincker.com that is our website name, the template name, and ten randomly generated characters that are used to identify the gincker. Therefore, exchanging ginckers over the Internet will be much faster and more efficient than transmitting large graphics or image files.