From: Matthew G. <mat...@gm...> - 2010-12-21 00:19:58
|
Here's a quick summary of some of the points from the developer meeting: Web Site Translations The web site translations are out of date. There was a proposal to get a non-coding volunteer to do the work of communicating with translators and collecting the translated .php files. It was agreed that the .php and .css files (basically the parts of the web site which are not mediawiki) should be put into the bzr repository in a branch called "domain". A more sophisticated method of doing translation through launchpad was mentioned by Fabien - perhaps generating the .php using a script, putting translatable strings through launchpad translations. User Guide into Wiki To crowd source maintenance of the User Guide, MG described the intent to move it into the wiki. The way forward is still not clear but there were numerous suggestions. Some experimentation is needed to find out if there is a good method to do the conversion from LyX to mediawiki format. Customizable Key Bindings It was generally agreed that there is a problem for people with some keyboard types and that we need the ability to customize keys some how. The task seems separable into two parts: not having hard-coded keys, and a GUI to configure it. Two ways of storing key bindings were mentioned - a json file or other binding-specific configuration file, and using a script. There was not total agreement about what was best. However, it should be possible to proceed with changes to the core which can be done before a decision on this needs to be made - i.e. making a KeyBindingsManager class, and getting it working with all keys (including this which are not directly associated with QActions, like the movement keys). Attracting Planetarium Users Several reasons were suggested why the planetarium crowd really stuck with Nightshade, and how we might attract some of them back: - no commercial plugins )probably not possible because of licensing issues) - scripting engine not supporting stratoscript (fixable with some effort) - instability from QT/GL/Video driver problems (need magic) - no script recording (no elegant solution is obvious) Plugin improvement Was raised but little said about it. Specific issues: run time loading/unloading of plugins, unified way to add toolbar buttons. Tasks Put out a call for volunteers for web site translation manager: MG Check web site files into bzr: MG Test LaTeX export -> Panodoc -> mediawiki for user guide import: TR Exploration of the key bindings solution: TR |
From: Reaves, T. <tr...@si...> - 2010-12-21 00:45:11
|
Matthew, thanks very much for writing these up! On Mon, Dec 20, 2010 at 7:19 PM, Matthew Gates <mat...@gm...> wrote: > Here's a quick summary of some of the points from the developer > meeting: > > Web Site Translations > > The web site translations are out of date. There was a proposal > to get a non-coding volunteer to do the work of communicating with > translators and collecting the translated .php files. > > It was agreed that the .php and .css files (basically the parts of > the web site which are not mediawiki) should be put into the bzr > repository in a branch called "domain". > > A more sophisticated method of doing translation through launchpad > was mentioned by Fabien - perhaps generating the .php using a script, > putting translatable strings through launchpad translations. > > > User Guide into Wiki > > To crowd source maintenance of the User Guide, MG described the > intent to move it into the wiki. The way forward is still not > clear but there were numerous suggestions. Some experimentation is > needed to find out if there is a good method to do the conversion > from LyX to mediawiki format. > > > Customizable Key Bindings > > It was generally agreed that there is a problem for people with > some keyboard types and that we need the ability to customize keys > some how. The task seems separable into two parts: not having > hard-coded keys, and a GUI to configure it. Two ways of storing key > bindings were mentioned - a json file or other binding-specific > configuration file, and using a script. There was not total > agreement about what was best. However, it should be possible to > proceed with changes to the core which can be done before a decision > on this needs to be made - i.e. making a KeyBindingsManager class, > and getting it working with all keys (including this which are not > directly associated with QActions, like the movement keys). > > > Attracting Planetarium Users > > Several reasons were suggested why the planetarium crowd really > stuck with Nightshade, and how we might attract some of them back: > - no commercial plugins )probably not possible because of licensing > issues) - scripting engine not supporting stratoscript (fixable > with some effort) - instability from QT/GL/Video driver problems > (need magic) - no script recording (no elegant solution is obvious) > > > Plugin improvement > > Was raised but little said about it. Specific issues: run time > loading/unloading of plugins, unified way to add toolbar buttons. > > > Tasks > > Put out a call for volunteers for web site translation manager: MG > > Check web site files into bzr: MG > > Test LaTeX export -> Panodoc -> mediawiki for user guide import: TR > > Exploration of the key bindings solution: TR > > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > |
From: Fabien C. <fab...@go...> - 2010-12-21 08:51:55
|
Thanks a lot Matthew! Little correction: I didn't meant to create a branch called "domain" for website translation. I wanted to create a new gettext domain called e.g. "website" in addition to the 2 domains we have: "stellarium" and "stellarium-skyculture" Fabien On Tue, Dec 21, 2010 at 01:45, Reaves, Timothy <tr...@si...> wrote: > Matthew, thanks very much for writing these up! > > > > On Mon, Dec 20, 2010 at 7:19 PM, Matthew Gates <mat...@gm...> wrote: >> >> Here's a quick summary of some of the points from the developer >> meeting: >> >> Web Site Translations >> >> The web site translations are out of date. There was a proposal >> to get a non-coding volunteer to do the work of communicating with >> translators and collecting the translated .php files. >> >> It was agreed that the .php and .css files (basically the parts of >> the web site which are not mediawiki) should be put into the bzr >> repository in a branch called "domain". >> >> A more sophisticated method of doing translation through launchpad >> was mentioned by Fabien - perhaps generating the .php using a script, >> putting translatable strings through launchpad translations. >> >> >> User Guide into Wiki >> >> To crowd source maintenance of the User Guide, MG described the >> intent to move it into the wiki. The way forward is still not >> clear but there were numerous suggestions. Some experimentation is >> needed to find out if there is a good method to do the conversion >> from LyX to mediawiki format. >> >> >> Customizable Key Bindings >> >> It was generally agreed that there is a problem for people with >> some keyboard types and that we need the ability to customize keys >> some how. The task seems separable into two parts: not having >> hard-coded keys, and a GUI to configure it. Two ways of storing key >> bindings were mentioned - a json file or other binding-specific >> configuration file, and using a script. There was not total >> agreement about what was best. However, it should be possible to >> proceed with changes to the core which can be done before a decision >> on this needs to be made - i.e. making a KeyBindingsManager class, >> and getting it working with all keys (including this which are not >> directly associated with QActions, like the movement keys). >> >> >> Attracting Planetarium Users >> >> Several reasons were suggested why the planetarium crowd really >> stuck with Nightshade, and how we might attract some of them back: >> - no commercial plugins )probably not possible because of licensing >> issues) - scripting engine not supporting stratoscript (fixable >> with some effort) - instability from QT/GL/Video driver problems >> (need magic) - no script recording (no elegant solution is obvious) >> >> >> Plugin improvement >> >> Was raised but little said about it. Specific issues: run time >> loading/unloading of plugins, unified way to add toolbar buttons. >> >> >> Tasks >> >> Put out a call for volunteers for web site translation manager: MG >> >> Check web site files into bzr: MG >> >> Test LaTeX export -> Panodoc -> mediawiki for user guide import: TR >> >> Exploration of the key bindings solution: TR >> >> >> ------------------------------------------------------------------------------ >> Lotusphere 2011 >> Register now for Lotusphere 2011 and learn how >> to connect the dots, take your collaborative environment >> to the next level, and enter the era of Social Business. >> http://p.sf.net/sfu/lotusphere-d2d >> _______________________________________________ >> Stellarium-pubdevel mailing list >> Ste...@li... >> https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Stellarium-pubdevel mailing list > Ste...@li... > https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel > > |
From: Alexander W. <ale...@gm...> - 2010-12-21 09:34:06
|
2010/12/21 Fabien Chéreau <fab...@go...>: > Thanks a lot Matthew! > > Little correction: I didn't meant to create a branch called "domain" > for website translation. I wanted to create a new gettext domain > called e.g. "website" in addition to the 2 domains we have: > "stellarium" and "stellarium-skyculture" KDE use svn-repository for translations of www sites -- With best regards, Alexander |