2010/1/21 James Paige <[email protected]>:
> On Thu, Jan 21, 2010 at 11:46:48AM +1300, Ralph Versteegen wrote:
>> The sprite editor needs to be updated to:
>> -use Frames instead of the old modex crud
>> -support 256 colour palettes
>> -support resizing frames from within the editor
>> -work on elements of SpriteSets instead of old-style frame arrays
>> -completely decouple from the current spriteset browser, which will be
>> thrown out
>> -variable resolution support would be nice
>>
>> At least it looks like sprite_editor is already mostly separated from
>> the sprite set browser, and everything is nice subified. But I don't
>> know how to answer this:
>>
>> Would it be easier to make these changes incrementally, or to start
>> from scratch and gradually update and move over components of the
>> existing editor?
>
> Good question. I normally favor incremental cleanup, but I think the
> sprite editor might be a case where we will be better off with a
> rewrite.
>
> I was thinking about using a saved slice collection to re-impelement the
> sprite editor's interface, but we don't have finalized slice collection
> saving/loading support yet...

Neat. That should mean automatic resolution independence as slices are
aligned to the sides of the screen, right? I think that was the whole
point of Seth originally using them in FMF.

> And I haven't worked on slice collection saving and loading because I
> haven't heard any agreement on declaring the RELOAD format stable or
> not.
>
> (Incidentaly that is the same thing that is stopping me from working on
> the new SAV format and working on the Editor Editor)
>
> ---
> James Paige

I'm pretty sure that the file format and loading/saving functions is
done. What's not is some of the rest of the API (particularly RPath?).
I don't know if this is actually a problem. Whenever I have an excuse
to use RELOAD (which was going to be for the new map format, but
that's stalled due to lack of feedback), I'll just finish off bits of
RELOAD as I need them. Also, the TODO list on RELOAD page on the wiki
looks out of date.


Also, I meant to say: because we couldn't come to agreement on the new
file formats for sprites & animations, I may just whip up something
temporary while I play around with it. I ought to try to write the
competing proposals up simply rather than leaving people to dig
through that enormous talk page on the wiki.
_______________________________________________
Ohrrpgce mailing list
[email protected]
http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

Reply via email to