Reply to Re: New Development File: browser editor
If you don't have an account, just leave the password field blank.
#1: It may take a while, but it should eventually show the map. Did you open the debugging console (ctrl-shift-k), and does is show any messages?
One thing that may be a problem: all filenames must be lowercase.
#2: No, unfortunately the dink directory is required. It contains all the assets from the main game. Those can be used in a D-Mod without bundling them. This means the editor needs to bundle them or else it wouldn't be able to display them. They are modified slightly (dir.ff files have been unpacked, and filenames have been converted to lowercase), otherwise the location of the main game could have been used (/usr/share/games/dink/dink on Debian; probably the same on Ubuntu).
The 0.1 version contained an "orig" directory by accident which contained mostly the same things as the dink directory, in a format that this editor doesn't understand. So that was truly useless.
And one correction to Redink's introduction: Because I made it for a web browser, it will not only work on Linux, but possibly also on Windows. Not the other way around. I don't have Windows, don't want it, don't test on it and don't really care all that much about it. But if people use it and my programs work on it, that's good.
One thing that may be a problem: all filenames must be lowercase.
#2: No, unfortunately the dink directory is required. It contains all the assets from the main game. Those can be used in a D-Mod without bundling them. This means the editor needs to bundle them or else it wouldn't be able to display them. They are modified slightly (dir.ff files have been unpacked, and filenames have been converted to lowercase), otherwise the location of the main game could have been used (/usr/share/games/dink/dink on Debian; probably the same on Ubuntu).
The 0.1 version contained an "orig" directory by accident which contained mostly the same things as the dink directory, in a format that this editor doesn't understand. So that was truly useless.
And one correction to Redink's introduction: Because I made it for a web browser, it will not only work on Linux, but possibly also on Windows. Not the other way around. I don't have Windows, don't want it, don't test on it and don't really care all that much about it. But if people use it and my programs work on it, that's good.
