<br><br>On Monday, November 20, 2017, Ralph Versteegen <<a href="mailto:teeemcee@gmail.com">teeemcee@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 November 2017 at 14:53, Ralph Versteegen <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','teeemcee@gmail.com');" target="_blank">teeemcee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On 12 November 2017 at 14:28, James Paige <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','Bob@hamsterrepublic.com');" target="_blank">Bob@hamsterrepublic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Nov 10, 2017 at 6:20 PM, Ralph Versteegen <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','teeemcee@gmail.com');" target="_blank">teeemcee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Ah, I see I was mistakenly counting the 3 months from Dwimmercrafty+1 rather than Dwimmercrafty!<br><br></div>What counts as something that "can't wait" for F? Only things to fix bugs or backcompat problems? Or does it include changes that other work depends on, and would result in too much being done in a branch?</div></div></div></div></div></blockquote><div><br></div></span><div>I would say any of the above. Basically is there anything you think is better to merge now rather than to wait to merge until after etheldreme?<br></div></div></div></div></blockquote><div><br></div></span><div>Feature-wise, anything that will make a major difference to users. But I don't have anything like that not already mentioned.<br></div><span><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>For how long before a release do we want to avoid major changes? Sitting around in nightlies is no substitute for testing with release candidates. People only download new nightlies rarely. I'd say how long to wait depends on how significant the change is rather than a hard cut-off.<br></div><div>Also, we can keep things out of the release either by not checking them into wip (eg by using git branches) or by branching etheldreme early in svn. I think it's easier not to branch stable releases long ahead.<br></div></div></div></div></div></blockquote><div><br></div></span><div>How about if we aim for a RC around the 18th and a release around the 25th if all goes well?</div><div><br></div><div>I know that is a short RC testing range, but I don't think a longer range will actually result in a lot more testing</div></div></div></div></blockquote><div><br></div></span><div>Sounds fine. I think a week is the right length of time. <br></div><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>I also agree that it is better not to branch the stable release long ahead. I think I didn't branch the dwimmercrafty release until the day of the release, and that worked fine for me.<br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div><br></div><div>I keep jumping between working on so many different things that I can't decide what to do next.</div><div><br></div><div>The biggest things I had been planning to work on in the next weeks was changing the graphics file format, replacing the spriteset browser, and to convert battles to slices.</div><div>That would allow raising the sprite size limits, and possibly the 16-color limit (with additional work in the sprite editor) without depending on the new animation system.<br></div><div>However it looks like I'll have little time to work on the OHR for the next 10 days anyway, so it's all moot.<br></div></div></div></div></div></blockquote><div><br></div></span><div>That sounds like a lot of work for just 10 days, even if you had nothing else to do in the world! :)<br></div></div></div></div></blockquote></span><div>Converting battles to slices will probably hit into some painful edge cases in the animation system, but is largely about replacing Frame with Slice, not new features.<br></div><div>I don't think a new spriteset browser is going to be that big a project, since it doesn't do terribly much (until animations are added.).</div><div>The new rgfx file format isn't finalised, but I've pretty much decided which changes I'm going to make to it. Saving, loading and upgrading to rgfx is largely implemented.</div><div><br></div><div>Anyway, once I have a free week and pull myself away from other OHR distractions, I'm going to spend a week just on animations. I think that's enough time to get them in place :)<br></div><span><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div><br></div><div>More realistically, I've been doing lots of work on slices recently, most of which isn't exposed yet. I'll think about whether it's ready to expose.</div><div>And I wanted to work on equip slots.<br></div><div><br></div>A general summary of stuff I'm actively working on but haven't merged yet:<br></div>-line slices</div><div>-template slices (hidden slices which are ignored for all purposes)</div><div>-refactoring embed_text_codes, so that you can use embed codes in text slices<br></div><div>-map editor improvements</div><div><br></div><div>And some stale stuff that's close to mergeable:<br></div><div>-nicer looking minimaps either using scale_surface (which require 32 bit color) or an alternative (which doesn't)</div><div>-joystick rewrite, to fix our utterly broken joystick handling (so little risk of breaking anything by merging it)</div><div>-a color replacement tool for backdrops, which REPLACES the 'disable palette colors for import' menu.<br></div></div></div></blockquote><div><br></div></span><div>Those last two especially sound like great things to sneak in before etheldreme. :)<br></div></div></div></div></blockquote><div><br></div></span><div>I was a little be worried about removing the 'disable colors' menu (I modified it into the remap tool). I was thinking that a color remapper (which is just a 'replace color' tool with undo) can't do everything color disabling does. If two colors in the original get mapped to black, then the remapper can't separate them again. But if you disabled black, they might get mapped to dark blue and dark red. Which is a crappy solution too!</div><div>And this is only a problem for 32 bit bmps; 8 bit bmps are fine, because you can remap colors during import, before the information gets lost.</div><div>And it would be possible to improve the remapper for 32 bit import too, by first converting them to 8-bit with an optimal palette.</div><div>So I'll merge it.<br></div><span><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div>BTW, don't forget to update this out-of-date whatsnew line:<br> * You can now browse for items rather than typing in their ID<br> numbers [James]<br></div></div></blockquote><div><br></div></span><div>I'm not sure what I need to change there... Maybe I phrased it badly?</div></div></div></div></blockquote><div><br></div></span><div>It's out of date because it only mentions items, but you can browse for other stuff too.<br></div></div></div></div></blockquote><div><br></div><div>Despite being a RC, we still didn't update whatsnew for that or the highlights.</div><div><br></div><div>The amount of unmerged stuff I have is only increasing!</div><div>Although I finished Line slices (after finally deciding that they should draw from x,y to x+w,y+h, not to x+w-1,y+h-1, and that using negative width and height is most natural, both of those things are necessary for lines properly connecting together when you parent one to another), I didn't merge them because I hadn't written the script commands... hmm, should do so anyway, and the commands are pretty easy to add anyway<br></div><div><br></div><div>The other thing was that I meant to expose the option to change the game resolution. Even though it's a RC, exposing it doesn't actually change anything, and it's been in testing for years. I'm sick of telling people that the option is still hidden.<br></div><div><br></div></div></div></div></blockquote><div><br></div><div>I would say go ahead and sneak that change in. After all, RC is just state of mind :)</div><div><br></div><div><br></div><div>Hopefully i'll have time to fix up the whatsnew.txt tomorrow</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>----</div><span><div>James<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On 11 November 2017 at 12:43, James Paige <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','Bob@hamsterrepublic.com');" target="_blank">Bob@hamsterrepublic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>It is almost time for the Etheldreme stable release!<br><br></div>If possible, I hope to release it by the end of this month (Last week of November, ideally)<br></div><div><br></div><div>My general impression of the current nightly wip builds is that they are pretty stable, not to crashy, and have a respectable amount of nifty new stuff.<br></div><div><br></div>I don't have any pending critical stuff that I need to finish. TMC, do you have anything that needs to be checked in that can't wait for the f* release?<br></div><div><br></div><div>The only halfway ambitious thing I might attempt before then (only if I have time) would be to try and do a little more work on ThingBrowser to enable editing while browsing (which currently only makes sense for ItemBrowser, but will be important for AttackBrowser, HeroBrowser, EnemyBrowser, etc...)</div></div></blockquote></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div><br></div><div>---<br></div>James<br><br></div>
<br>______________________________<wbr>_________________<br>
Ohrrpgce mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','ohrrpgce@lists.motherhamster.org');" target="_blank">ohrrpgce@lists.motherhamster.o<wbr>rg</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.org<wbr>/listinfo.cgi/ohrrpgce-motherh<wbr>amster.org</a><br>
<br></blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Ohrrpgce mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','ohrrpgce@lists.motherhamster.org');" target="_blank">ohrrpgce@lists.motherhamster.o<wbr>rg</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.org<wbr>/listinfo.cgi/ohrrpgce-motherh<wbr>amster.org</a><br>
<br></blockquote></span></div><br></div></div>
<br>______________________________<wbr>_________________<br>
Ohrrpgce mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','ohrrpgce@lists.motherhamster.org');" target="_blank">ohrrpgce@lists.motherhamster.o<wbr>rg</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.org<wbr>/listinfo.cgi/ohrrpgce-motherh<wbr>amster.org</a><br>
<br></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>
</blockquote>