Leejjon

import React from 'react';
import ReactDOM from 'react-dom';
import './index.css';
import App from './App';
import * as serviceWorker from './serviceWorker';
import {Config} from "./serviceWorker";

ReactDOM.render(
  <React.StrictMode>
    <App />

Leejjon

package com.example;

import com.example.controller.MyResource;
import org.glassfish.grizzly.http.server.HttpServer;
import org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpServerFactory;
import org.glassfish.jersey.server.ResourceConfig;

import java.net.URI;
import java.util.logging.Handler;
import java.util.logging.Level;

Leejjon

package com.example;

import org.glassfish.grizzly.http.server.HttpServer;
import org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpServerFactory;
import org.glassfish.jersey.server.ResourceConfig;

import java.net.URI;

/**
 * Main class.

Leejjon

After my previous gist about handling textures in a libGDX game, I am going to combine the libGDX AssetManager with my approach to see if we can get the best of both worlds.

Asset manager

LibGDX has an AssetManager included, in which you can put all your assets, and it will load them for you. After that, you can retrieve them for actually using them. Disposing the asset manager will dispose all textures inside it nicely.

Positives of using an asset manager:

• Synchronous and Asynchronous asset loading.
• All assets in one asset manager (fonts, textures, skins, sound files etc).
• Support for unloading when pausing and resuming your game.
• Can be extended and since LibGDX is opensource you can alter it.

Leejjon

Starting out

If you have started out to build a game with libGDX, you've were probably creating and disposing textures out like this:

public class MyGdxGame extends ApplicationAdapter {
    SpriteBatch batch;
    Texture badlogic;

    @Override

public void create () {