On Sun, Dec 13, 2009 at 08:10:48PM -0500, Wade Brainerd wrote:
Sure, shouldn't be hard.
It actually has no dependencies on the shell other than
jarabe.controlpanel.sectionview.SectionView which the dialog is based
on. What would I replace that with?
maybe just a page for report dialog?
it
On Mon, Dec 14, 2009 at 01:01:04PM +, Aleksey Lim wrote:
On Sun, Dec 13, 2009 at 08:10:48PM -0500, Wade Brainerd wrote:
Sure, shouldn't be hard.
It actually has no dependencies on the shell other than
jarabe.controlpanel.sectionview.SectionView which the dialog is based
on. What
Looks good ... though I haven't actually reviewed the patches.
I hope you've thought about what will happen if people report problems
that are part of the underlying software stack ... or even hardware.
Perhaps a way for mass deployments to customise the destination for the
problem report.
--
On Sun, Dec 13, 2009 at 7:23 PM, James Cameron qu...@laptop.org wrote:
Looks good ... though I haven't actually reviewed the patches.
I hope you've thought about what will happen if people report problems
that are part of the underlying software stack ... or even hardware.
It does bundle a
On Sun, Dec 13, 2009 at 8:26 PM, James Cameron qu...@laptop.org wrote:
On Sun, Dec 13, 2009 at 08:07:45PM -0500, Wade Brainerd wrote:
On Sun, Dec 13, 2009 at 7:23 PM, James Cameron qu...@laptop.org wrote:
Looks good ... though I haven't actually reviewed the patches.
I hope you've thought
On Sun, Dec 13, 2009 at 9:30 PM, Wade Brainerd wad...@gmail.com wrote:
On Sun, Dec 13, 2009 at 8:26 PM, James Cameron qu...@laptop.org wrote:
On Sun, Dec 13, 2009 at 08:07:45PM -0500, Wade Brainerd wrote:
On Sun, Dec 13, 2009 at 7:23 PM, James Cameron qu...@laptop.org wrote:
Looks good ...
On Sun, Dec 13, 2009 at 09:32:50PM -0500, Wade Brainerd wrote:
Honestly, I really have no idea what kind of data we'll get through
the feature. But any data is better than silence IMO.
Agreed.
Have you considered capturing non-problem experience reports as well?
In OLPC testing at the moment
Hi all,
Here is my feature proposal for Sugar Problem Reports. It's a quick
way for users to provide feedback about Sugar. Reports automatically
bundle relevant log files, and the PHP log server some simple scraping
for Python exceptions, logger.error() calls, etc.
The patches are all posted
Wade, could you prepare shell agnostic code,
it could be utilized in saccharin to report problems while
downloading/compiling, so having the same UI would be useful.
On Sat, Dec 12, 2009 at 08:47:05PM -0500, Wade Brainerd wrote:
Hi all,
Here is my feature proposal for Sugar Problem Reports.
On Sun, Dec 13, 2009 at 02:43:57AM +, Aleksey Lim wrote:
Wade, could you prepare shell agnostic code,
it could be utilized in saccharin to report problems while
downloading/compiling, so having the same UI would be useful.
btw that could be another point for Shell UI Integration proposal,
10 matches
Mail list logo
