From: Kevin A. <al...@se...> - 2005-12-26 08:59:52
|
I haven't scanned through all of the cvs commits for the last year or so, but the changelog.txt for 0.8.2 definitely doesn't reflect all of the additions and fixes that have been done, especially the new samples and tools. Feel free to add some descriptive lines for each of your contributions. As we approach an actual release I'll add, trim and edit as necessary to the changelog if you (Alex, Andy, Phil, etc.) don't have time. ka |
From: Alex T. <al...@tw...> - 2005-12-26 23:28:32
|
Kevin Altis wrote: > I haven't scanned through all of the cvs commits for the last year or > so, but the changelog.txt for 0.8.2 definitely doesn't reflect all of > the additions and fixes that have been done, especially the new > samples and tools. Feel free to add some descriptive lines for each of > your contributions. As we approach an actual release I'll add, trim > and edit as necessary to the changelog if you (Alex, Andy, Phil, etc.) > don't have time. > Sorry Kevin - I had totally forgotten to add anything to changelog.txt I've put added brief description for most things I did - but should probably put in a longer description or documentation somewhere for the multiresourceEditor (and maybe tabcodeEditor). -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.5/212 - Release Date: 23/12/2005 |
From: Kevin A. <al...@se...> - 2005-12-26 23:49:27
|
On Dec 26, 2005, at 3:29 PM, Alex Tweedly wrote: > Kevin Altis wrote: > >> I haven't scanned through all of the cvs commits for the last year or >> so, but the changelog.txt for 0.8.2 definitely doesn't reflect all of >> the additions and fixes that have been done, especially the new >> samples and tools. Feel free to add some descriptive lines for each >> of your contributions. As we approach an actual release I'll add, >> trim and edit as necessary to the changelog if you (Alex, Andy, Phil, >> etc.) don't have time. >> > Sorry Kevin - I had totally forgotten to add anything to changelog.txt > > I've put added brief description for most things I did - but should > probably put in a longer description or documentation somewhere for > the multiresourceEditor (and maybe tabcodeEditor). > > -- > Alex Tweedly http://www.tweedly.net > Thanks Alex. readme.txt should be adequate for both of the new apps. Do you think multiresourceEditor should have a shortcut in 0.8.2 or wait another release? I need to look at my script for generating the samples HTML from the readme.txt files and run through it again for the new stuff. ka |
From: Alex T. <al...@tw...> - 2005-12-29 17:14:57
|
Kevin Altis wrote: > > Thanks Alex. readme.txt should be adequate for both of the new apps. > Do you think multiresourceEditor should have a shortcut in 0.8.2 or > wait another release? > I think it could have one now - I have no outstanding bugs I'm aware of, and although I couldn't claim to have "tested it thoroughly" on Python 2.4 / wxPython 2.6.1, I have given it a fair work-out over the last couple of days and seen no problems. (That is, of course, ignoring all the raise / lower issues ..... which I don't think are any different in the multiresourceEditor) (I did discover one problem with the tabcodeEditor - report coming shortly unless I stumble into understanding it myself ....) -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 29/12/2005 |
From: <bra...@om...> - 2006-01-03 22:38:16
|
> Kevin Altis wrote: > > > > > Thanks Alex. readme.txt should be adequate for both of the new apps. > > Do you think multiresourceEditor should have a shortcut in 0.8.2 or > > wait another release? Alex Tweedly replied: > I think it could have one now - I have no outstanding bugs I'm aware of, > and although I couldn't claim to have "tested it thoroughly" on Python > 2.4 / wxPython 2.6.1, I have given it a fair work-out over the last > couple of days and seen no problems. (That is, of course, ignoring > all the raise / lower issues ..... which I don't think are any different > in the multiresourceEditor) > > (I did discover one problem with the tabcodeEditor - report coming > shortly unless I stumble into understanding it myself ....) MultiResourceEditor has been very robust for me. I've used it regularly for the past few months. It's not perfect--for instance, I wish the Vary checkbox defaulted to "off" and was renamed to something more obvious "Auto-Naming". But's that just my preference, not a bug. There are probably bugs I haven't noticed, of course, since I only use 14 out of the 25 widgets available. I haven't used the old Resource Editor in a long time. MultiResourceEditor is just too useful for me to consider going back. It's great to be able to see all the properties for a widget displayed simultaneously, and for that matter it's also frequently useful to be able to select multiple widgets simultaneously. The old Resource Editor also had a number of frustrating glitches in relation to moving and resizing objects. Alex fixed those issues for MultiResourceEditor. Overall, I think the MultiResourceEditor puts a better face on PythonCard and is less likely to scare off newbies. |
From: Alex T. <al...@tw...> - 2006-01-04 02:17:04
|
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.9/217 - Release Date: 30/12/2005 |