> you will need some kind of "packer" (to condense music data from editable > format into something more memory friendly) and a "relocator" for your > player/editor anyways....what you are saying may sound "easier" at first, > but it has a lot of drawbacks for real world usage. just look at how > this kind of stuff is handled in other existing editors. (and dont get > fooled by the fact that some/a lot _do_ have the player at $1000 even > in the editor - that has other reasons) Well, I'm aware of how other editors/players work. I was intending to do the packing part as a part of this editor program, so one could choose to save a tune either as a RLE-packed dump of the music data for worktunes just to save disk space or as packed ready-to-be-used-binaries on the other hand. If I ever needed to relocate a tune I was hoping simply to be able to recompile the editor and specify a new location for the player and thus avoiding to write a special tool for relocation. But, then again, I guess I might just do precisely that.. Oh well.. /Mats ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Sep 25 21:26:21 2004
This archive was generated by hypermail 2.1.8 : 2004-09-25 21:26:30 CEST