[Chandler-dev] [Sum] Aug 21 - 27

Katie Capps Parlante capps at osafoundation.org
Sun Sep 24 14:46:38 PDT 2006


Build, Release, QA
------------------
*XRC editors*
Morgen proposes that we stop using wxdesigner for XRC dialog editing as 
it is proprietary and generates "source" binary files that only it can 
read. We'll need to remove .wdr files and rename *_wdr.xrc files to 
*.xrc. Morgen asked for recommendations of open source xrc editors.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006640.html

Robin mentioned XRCed and wxGlade.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006643.html

John recommended DialogBlocks. John pointed out that one could use any 
tool that imported and exported xrc files.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006644.html

*Monday Aug 21 checkpoint*
Bear's checkpoint:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006645.html
Dan's report:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006653.html

*svn:ignore*
Bear explained that some svn clients (other than the command line 
client) don't handle changing svn properties correctly. If you want to 
use a tool to alter properties like svn:ignore, work with Bear to make 
sure the tool is not causing problems.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006648.html

*i18n*
i18n tests require French and and Spanish language support on the OS. 
These are installed by default on XP and OSX but not Linux. Brian gave 
steps for setting up Linux so that the tests pass.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006665.html

Intern, SoC projects
--------------------
*External Reminders, Memory*
Travis has an implementation of the reminders-as-separate-process idea 
-- its up and working. Travis observed that the reminder process chews 
up quite a bit of memory, and did a couple of tests/experiments. The 
first process to run (reminder app or chandler app) has a big memory 
footprint, which is likely problematic if one is only running the 
reminder app. He asked some questions: do we question the approach? Do 
we care if RAM is cheap? Proposals: (1) stick with Travis' first 
approach, despite RAM footprint (2) separate app using native 
notification frameworks and repository -- drop wx (3) reminder app 
without the repository.
http://wiki.osafoundation.org/bin/view/Projects/TravisVachonExternalReminders
http://wiki.osafoundation.org/bin/view/Journal/ReminderMemoryExperiments20060821
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006659.html

Travis experimented further with Pysizer, a summer of code project from 
2005 that helps one examine Python memory use. Travis has a branch of 
Chandler in his sandbox setup to use Pysizer (requires a full build for 
optimal use).
http://wiki.osafoundation.org/bin/view/Projects/ChandlerPysizer
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006684.html

*PMTool*
Markku is working on building a project management tool using Bugzilla.
http://wiki.osafoundation.org/bin/view/Projects/BugzillaProjectManagementTool
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006682.html 


Dev projects
------------
*Startup option fun*
Heikki proposed using --nocatch as the switch to prevent the feedback 
dialog (instead of --stderr). He also proposed not using --stderr by 
default in the do_tests and tinderbox scripts. Some folks had concerns 
about removing --stderr as an option (not part of the proposal). Heikki 
explained that the chandler.log with all traceback info is concatenated 
to the tbox log.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006629.html 


Heikki proposed getting rid of --prof, which profiles a single commit at 
startup. No objections.
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006660.html

*Repository*
Andi updated the afterChange method protocol, and updated all 
afterChange methods in the codebase (including @schema.observer declared 
  ones).
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006691.html

*Server side backups*
Thread starts here:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006666.html
Jared's summary:
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006736.html

Meetings
--------
Apps team meeting notes and status:
http://wiki.osafoundation.org/bin/view/Journal/AppsMeeting20060824

Platform team meeting notes and status:
http://wiki.osafoundation.org/bin/view/Journal/PlatformMtg20060822
http://lists.osafoundation.org/pipermail/chandler-dev/2006-August/006693.html



More information about the chandler-dev mailing list