Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
  You are not logged in - nap
DART - Directory Art Importer   [2022]

DART - Directory Art Importer Released by :
Genesis Project [web]

Release Date :
2 December 2022

Type :
Other Platform C64 Tool

AKA :
dirart importer - the tool everyone has to write at least once

User rating:awaiting 8 votes (1 left)   See votestatistics

Credits :
Code .... Sparta of Genesis Project, OMG, Propaganda Magazine Staff
Test .... jab of Artline Designs, Wrenchotron
  Ksubi of Genesis Project, Propaganda Magazine Staff
Help .... Ksubi of Genesis Project, Propaganda Magazine Staff

Download :

Look for downloads on external sites:
 Pokefinder.org


Summary
Submitted by Sparta on 2 December 2022
*****************************************
DART - DirArt importer by Sparta (C) 2022
*****************************************

DART is a simple command line tool that imports directory art from different source file types to D64 disk images.

Usage:
------
DART input[*] [output.d64]

By default, DART will overwrite any existing directory entries in output.d64.
To append the imported DirArt to the existing directory entries without overwriting them, mark the input file with an
asterisk (i.e. input*, see example below). Thus, multiple DirArts can be imported in the same D64 as long as there
is space in track 18.

The [output.d64] parameter is optional. If not specified, DART will create an input_out.d64 file.

Accepted input file types:
--------------------------
.D64 - DART will import all directory entries from the input file to the output file.

.PRG - DART accepts two file formats: screen RAM grabs (40-byte long char rows of which the first 16 is used as dir
       entries, can be more than 25 char rows long) and $a0 byte terminated directory entries*. If an $a0 byte is not
       detected sooner, then 16 bytes are imported per directory entry. DART then skips up to 24 bytes or until an
       $a0 byte detected. Example source code for $a0-terminated .PRG (KickAss format, must be compiled):

       * = $1000              // Address can be anything, will be skipped by DART
       .text "hello world!"   // This will be upper case once compiled
       .byte $a0              // Terminates directory entry
       .byte $30,$31,$32,$33,$34,$35,$36,$37,$38,$39,$01,$02,$03,$04,$05,$06,$a0

       *Char code $a0 (inverted space) is also used in standard directories to mark the end of entries on the disk.

.BIN - DART will treat this file type the same way as .PRGs, without the first two header bytes.

.ASM - KickAss ASM DirArt source file. Please refer to Chapter 11.6 in the Kick Assembler Reference Manual for
       details. The ASM file must only contain the file parameters within [] brackets, without disk parameters.
       DART only recognizes the name and type file parameters. Example:

       [name = "0123456789", type = "rel"],
       [name = @"\$75\$69\$75\$69\$B2\$69\$75\$69\$75\$ae\$B2\$75\$AE\$20\$20\$20", type="del"]

.C   - Marq's PETSCII Editor C array file. This file type can also be produced using PetMate. This is essentially a
       C source file which consists of a single unsigned char array declaration initialized with the dir entries.
       If present, DART will use the META: comment after the array to determine the dimensions of the DirArt.

.PNG - Portable Network Graphics image file. Image input files can only use a single foreground color. DART will use
       the darker of the two colors as background color. Image width must be 128 pixels (16 characters), no borders
       allowed. Image files must use the uppercase charset and their appearance cannot rely on command characters.

.BMP - Bitmap image file. Same rules and limitations as with PNGs.

Any other file type will be handled as a binary file and will be treated as PRGs without the first two header bytes.

Limitations:
------------
DART doesn't import the directory's header and ID. The input file must only consist of the directory entries (with
the exception of D64 files where the directory header and ID will be ignored).

Examples:
---------
DART MyDirArt.d64
DART will create MyDirArt_out.d64 (if it doesn't already exist), and will import the whole directory of MyDirArt.d64
in it overwriting any preexisting directory entries.

DART MyDirArt.c MyDemo.d64
DART will import the DirArt from a Marq's PETSCII Editor C array file in MyDemo.d64 overwriting any preexisting
directory entries.

DART MyDirArt.asm* MyDemo.d64
DART will append the DirArt from a KickAss ASM source file to the existing directory entries of MyDemo.d64.
Search CSDb
Advanced
Navigate
Prev - Random - Next
Detailed Info
· Summaries (1)
· User Comments (6)
· Production Notes
Fun Stuff
· Goofs
· Hidden Parts
· Trivia
Forum
· Discuss this release
Support CSDb
Help keep CSDb running:



Funding status:




About this site:
CSDb (Commodore 64 Scene Database) is a website which goal is to gather as much information and material about the scene around the commodore 64 computer - the worlds most popular home computer throughout time. Here you can find almost anything which was ever made for the commodore 64, and more is being added every day. As this website is scene related, you can mostly find demos, music and graphics made by the people who made the scene (the sceners), but you can also find a lot of the old classic games here. Try out the search box in the top right corner, or check out the CSDb main page for the latest additions.
Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.086 sec.