Changes between Initial Version and Version 1 of CodingAgainstWorldPainter


Ignore:
Timestamp:
06/06/20 17:16:43 (5 months ago)
Author:
admin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodingAgainstWorldPainter

    v1 v1  
     1= Using !WorldPainter in your own code
     2
     3If you only want to write your own code ''making use of'' !WorldPainter, rather than make changes to !WorldPainter itself, then you don't need to build !WorldPainter! The !WorldPainter binaries, along with Javadoc and source code jars, are in Maven Central. Just declare the following dependency if you just need the core (and not any GUI components):
     4
     5{{{#!xml
     6<dependency>
     7    <groupId>org.pepsoft.worldpainter</groupId>
     8    <artifactId>WPCore</artifactId>
     9    <version>2.7.12</version>
     10</dependency>
     11}}}
     12
     13(Of course replace the version number with the most recent version of !WorldPainter.)
     14
     15This will allow you to load and save !WorldPainter worlds, read their contents and make changes, Export them to Minecraft, or Import Minecraft maps as !WorldPainter worlds. This should be enough for most uses. But if you need GUI components in addition, use the following dependency.
     16
     17{{{#!xml
     18<dependency>
     19    <groupId>org.pepsoft.worldpainter</groupId>
     20    <artifactId>WPGUI</artifactId>
     21    <version>2.7.12</version>
     22</dependency>
     23}}}
     24
     25For more details about these packages and other ways to declare the dependencies, see: https://mvnrepository.com/artifact/org.pepsoft.worldpainter
     26
     27== Building !WorldPainter
     28
     29If you do want to make changes to the !WorldPainter code, instructions for building it locally are [BuildingWorldPainter here].