adonthell-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Adonthell-devel] Mapedit filtering


From: Kai Sterker
Subject: Re: [Adonthell-devel] Mapedit filtering
Date: Tue, 12 Jul 2011 22:34:08 +0200

On Mon, Jun 13, 2011 at 3:09 PM, Kai Sterker <address@hidden> wrote:

You probably noticed that there were some commits to adonthell-tools,
but let me give a brief update of what's in there and what needs to be
done yet.

> Basically, when you press the "Add Connector" button on the main gui
> meta-data tab, a dialog will open with a list of available connectors.

This dialog is completely implemented. You can create and edit
existing connectors and when you press OK, they will get saved into a
file. Whenever the dialog is opened, the file is loaded again and its
contents displayed.

Connectors have a unique id, as suggested in the distributed editing thread.

> Once a connector has been added to the list in the meta-data section,
> the face where it should be attached and its position can be updated
> directly in the list. There'll be a drop down for the four sides and
> the position can be entered directly..

That is done as of today.

There is no visualisation of the connectors yet and they do not get
saved with the model either. So this will be the next steps. For
simplicity, I will create a new file for the model meta data that will
sit next to the model.xml itself. That way, no changes need to be made
to the engine and the meta data could be left out of official releases
too.

Once stuff is implemented in modeller, I can then update mapedit to
make use of the meta data for the filtering and automatic positioning
of the grid.


There's one more thing on my mind, however. As discussed before, I
want to change the file extensions for models and maps at least, so
that they can be associated with the respective tools. My suggestion
would be .amdl and .amap (as it would be consistent with .adlg), but
I'm open to something else too. That will require a change to the
engine, so it can detect file type by peeking at the content instead
of just checking the extension. That way, existing models (like all
the test data) could keep their current .xml extension, but the new
ones we create for the WE remake should best be switched over to the
new naming scheme.

Maybe I should give that priority over the changes above, so that it
gets done before too many models are created.


As usual, comments and such welcome.

Kai



reply via email to

[Prev in Thread] Current Thread [Next in Thread]