LibGDX module overview, libgdx module Overview

LibGDX module overview, libgdx module Overview
This article is translated from the official libGDX wiki. For more information, see "region ".Introduction:

LibGDX includes many modules that provide excellent services for every step of a normal game building.
 
 

  
  
Input: provides an undefined Input module and solutions for all platforms. Supports keyboard, touch screen, accelerator, and mouse.
 
 
 
 

  
  
Graphics *: Uses hardware-provided OpenGL ES to draw images on the screen.
 
 
 
 

  
  
Files: Abstract file operations are implemented by providing convenient read/write operations, regardless of media Files.
 
 
 
 

  
  
Audio: Recording and playing Audio on all platforms.
 
 
 
 

  
  
NetWorking: Provides network operation methods, such as simple HTTP get and post requests, and communicates with the socket of the TCP server/client.
 
 
The following icons demonstrate these modules in a complete game system:

Module: Input)

The input module makes it possible to poll the input status on each platform. It allows round-robin of every key. Touch screen. And the status of the accelerator. In a desktop program, the touch screen is replaced by a mouse, while the accelerator is unavailable. It also allows you to register an input processor to use an input module-based event. The following code snippet obtains the coordinates of the touch when a touch event occurs: System. out. println ("Input occurred at x =" + Gdx. input. getX () + ", y =" + Gdx. input. getY ());}

if (Gdx.input.isTouched()) {

Similarly, all supported input methods can be supported and processed.

Graphics (image)

The image module abstracts the communication with the GPU and provides a convenient way to obtain instances of the OpenGL ES package. Depending on different hardware platforms, the package may also be unavailable. The graphic module also provides methods to generate Pixmaps and Texture. For example, the following code snippet obtains an example of OpenGL API1.0: GL10 gl = Gdx. graphics. getGL10 (); this method returns an instance that can be drawn on the screen. If the hardware configuration is not supported, null is returned. The following code snippet clears the screen and draws the screen in Red: gl. glClearColor (0.1f, 0.0f, 0.0f, 1); gl. glClear (GL10.GL _ COLOR_BUFFER_BIT); it always returns the specified implementation of the specified API, so the main application does not need to pay attention to details (that is, do not pay attention to the platform used ), it automatically works on all supported platforms.

Files)

The file module provides a general method for operating files on unrelated platforms. It is easy to read and write files. File writing has some limitations, which are attributed to the security limitations of related platforms.

The most common use of file modules is to load game resources (textures, sound files) from subdirectories of applications on all platforms. It is also useful for writing the highest score or game status to a file.

The following code snippet creates a texture from the $ APP_DIR/assets/textures directory:

Texture myTexture = new Texture(Gdx.files.internal("assets/texture/brick.png"));

Audio (Audio)

The sound module makes it easy to create and play audio files. It can also directly access the audio hardware.

It processes two types of audio files: Music and Sound. Both types support wav, mp3, and ogg formats.

The Sound instance can be loaded to the inner and can be played at any time. This is to ensure that the sound effects in the game can be played multiple times, such as explosion and shooting.

The Music instance is a stream of files on the hard disk or SD card. Each time a file is played, it is processed as a data stream and handed over to the audio device.

The following code segment contains a soundfile, mymusicfilehistory, which is played repeatedly and the volume is 1/2.

Music music = Gdx.audio.newMusic(Gdx.files.getFileHandle("data/myMusicFile.mp3", FileType.Internal));music.setVolume(0.5f);music.play();music.setLooping(true);

Common transaction code of sap to sap material management module (mm)

Material Mangement:
MM01-create material master data
XK01-create supplier master data
ME11-create purchase information records
ME01-maintain the supply list
ME51N-create a purchase application
ME5A-display procurement Application List
ME55-approve procurement application (Approval Group: YH)
ME57-allocate and process procurement applications
MB21-Reserved
MB24-show Reserved List
ME21N-create purchase order
ME28-approve purchase order (Approval Group: YS)
ME9F-confirm the order
ME2L-query the supplier's purchase credential
ME31-create procurement agreement
MD03-manual MRP
MD04-inventory requirement list (MD05-MRP List)
MRKO-consignment settlement
MELB-Procurement Application List (Demand Tracking No)
ME41-create an inquiry ticket
ME47-maintenance quotation
ME49-price comparison list
MI31-Create Inventory check credential
MI21-print the inventory check credential
MI22-display the actual inventory check credential content
MI24-display the list of actual inventory creden
MI03-display the actual inventory list
MI04-enter inventory count based on inventory check creden04
MI20-inventory difference list
MI07-inventory difference overview and Accounting
MI02-change the inventory check credential
MB03-display material creden
ME2O-query supplier supply inventory
MB03-display material creden
MMBE-inventory overview
MB5L-query the inventory value balance list
MCBR-inventory batch analysis
MB5B-query the inventory of each day
MB58-query the customer's storage inventory
MB25-query reserved and shipping status MB51
MB5S-query the receipt and invoice differences of purchase orders
MB51-material creden query (you can search by mobile type)
ME2L-confirm the purchase order/dump order is correct
MCSJ-information structure S911 Procurement Information Query (Procurement quantity value, receipt quantity value, invoice quantity value)
MCBA-check inventory quantity and amount
MM04-display material changes
MMSC-centralized inventory Creation
MIGO_GR:
MB1C-Other Shipping
MB1A-input delivery
MB1B-dump
MB31-production receipt
MB01-purchase receipt)
MBST-cancel material creden
MM60-product list
ME31L-plan Creation Protocol
ME38-maintain Delivery Plan
ME9A-message output
MB04-subcontract adjustments afterwards
MB52-display existing warehouse stock
MB90-output from goods movement
CO03-display production order
IW13-material reverse query Order (list)
IW33-display repair order
VA01-create a sales order
VL01N-create an outward delivery order with reference to the sales order
VL02N-Modify the outgoing delivery order (configuration picking and delivery posting)
VL09-offset the movement of goods sold
VF01-issue sales invoice
VF04-process the invoice expiration list
VF11-cancel issuing sales invoice

Warehouse Mangement:
LB01 Create Transfer Requirement
LB02 Change transfer requirement
LB03 Display Transfer Requirement Display dump requirements
LB10 TRs for Storage Type dumping requests by Storage Type
LB11 TRs for Material Dump Request
LB12 TRs and Posting Change for MLEat. Doc. Transfer of Dump Request and material credential Change
LB13 ...... remaining full text>

What are some modules of OA Office software? What is a workflow?

Office Automation (OA) is a new Office method that combines modern Office and computer network functions. There is no uniform definition of office automation. All new technologies, machines, and equipment used in traditional office work belong to the field of office automation. In most administrative agencies, office automation is called e-government, and most enterprises and institutions are called OA, that is, office automation. By implementing office automation or digital office, you can optimize the existing management organization structure, adjust the management system, increase collaborative office capabilities, and strengthen decision-making consistency, finally, the goal of improving the decision-making efficiency is achieved.
Workflows are mainly determined based on the actual situation of each enterprise!