Downloads:

1,689

Downloads of v 1.0:

404

Last Update:

11 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Nick Prühs

Tags:

tome game data editor

Tome

  • 1
  • 2
  • 3

1.0 | Updated: 11 Jun 2017

Downloads:

1,689

Downloads of v 1.0:

404

Maintainer(s):

Software Author(s):

  • Nick Prühs

  • 1
  • 2
  • 3
Tome 1.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install Tome, run the following command from the command line or from PowerShell:

>

To upgrade Tome, run the following command from the command line or from PowerShell:

>

To uninstall Tome, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade tome-editor -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade tome-editor -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure tome-editor installed
  win_chocolatey:
    name: tome-editor
    state: present
    version: 1.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'tome-editor' do
  action    :install
  version  '1.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: tome-editor,
    Version: 1.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller tome-editor
{
   Name     = 'tome-editor'
   Ensure   = 'Present'
   Version  = '1.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'tome-editor':
  provider => 'chocolatey',
  ensure   => '1.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install tome-editor version="1.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator AdmiringWorm on 18 Jun 2017.

Description

Developing games is all about data. With game systems for modifying data and user interfaces for presenting it, finding a sophisticated data model is key to creating successful games. Even more, being able to change this data and iterate on a day-to-day basis is mandatory in today's production cycles.

Tome solves two problems that arise with every new game you build: First, you can import the definition of your game's data so game designers can create new data records and modify existing ones very conveniently. Second, you can export the results to any format your game engine understands.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName= 'tome-editor'

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$exampleDir = "$(Join-Path -Path $toolsDir -ChildPath ..\example)"

$url        = 'https://github.com/npruehs/tome-editor/releases/download/1.0/Tome-1.0-Windows-x86.zip'
$urlExample= 'https://github.com/npruehs/tome-editor/releases/download/1.0/Tome-1.0-ExampleProjects.zip'

# Install Tome.
Install-ChocolateyZipPackage $packageName $url $toolsDir

# Install example project.
Install-ChocolateyZipPackage $packageName $urlExample $exampleDir

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Tome 0.9-beta 232 Monday, March 13, 2017 Exempted
Tome 0.8-beta 268 Thursday, December 29, 2016 Exempted
Tome 0.7-alpha 255 Saturday, November 19, 2016 Exempted
Tome 0.6-alpha 267 Sunday, October 9, 2016 Exempted
Tome 0.5-alpha 263 Monday, September 12, 2016 Exempted

First major release.

This release contains usability improvements and bug fixes, only. It does not add any new features, export placeholders or integrity checks.

Data

  • Assigning pseudo-random integer record ids instead of increasing ones, in order to improve collaboration.

Usability

  • Showing record display names instead of ids in field value reference selection dropdowns, and for reference field values in the record table.
  • Sorting record tree and reference dropdowns by record display name.
  • Saving records sorted by ID in order to avoid merge conflicts.
  • Set record tree initial width to 1/5 of window width.
  • Automatically resizing first record table column to fit contents.
  • Disabled Reload Project menu item while no project is loaded.

Bug Fixes

  • Fixed multiple crashes that could occur when reference field values were is not set or invalid.
  • Fixed a crash that could occur when exporting map values.
  • Fixed a crash that could occur when adding a records file referencing a field or another record that does not exist.
  • Fixed multiple issues that could occur when assigning the same id to multiple records, only differing in lower and upper case characters.
  • Correctly prevent creating records with empty ids again.
  • Correctly detect whitespaces at the beginning or end of record ids.
  • No longer showing "prefix will automatically be removed" hint in Edit Field Value window if it isn't.
  • Showing correct question before discarding unsaved changes.
  • Adding the same file multiple times to the same project is no longer allowed.

This package has no dependencies.

Discussion for the Tome Package

Ground Rules:

  • This discussion is only about Tome and the Tome package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Tome, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus