[Sugar-devel] [DESIGN] Display clock in frame

[James Cameron]

You could answer that yourself by reading the thread attached to the
patch, and the later threads in the same month.  Perhaps you could do
that and summarise?

http://lists.sugarlabs.org/archive/sugar-devel/2009-May/thread.html

http://lists.sugarlabs.org/archive/sugar-devel/2009-May/014253.html is
a later version of the patch you refer to.

My answer; because the task was way more complex than just adding the
clock to the frame; the team also decided that the clock should not be
visible if the system has suspended.  At the time, the OLPC XO was the
major platform for which design was focused.

Subtext of your question is; why should you work on this, won't it be
rejected again?  Probably not, if done well, because the gatekeepers
on Sugar now are more accepting of contributions, in turn because
there are so few of them.

Also, there is less focus on idle suspend from the non-XO platforms.

In turn, this is because of more efficient CPUs and the huge drop in
solar module pricing, which has kept electricity generation costs
lower than anticipated over the last ten years.

On Mon, Apr 11, 2016 at 09:38:06AM +0530, Utkarsh Tiwari wrote:
> Hi,
>     It seems that someone had already submitted a patch for the frame
> clock -> http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg03934.html.
> Then why isn't it yet implemented in Sugar?
> 
> Thanks,
> Utkarsh Tiwari
> 
> On 4/11/16, James Cameron <quozl at laptop.org> wrote:
> > Thanks for offering to work on these features.
> >
> > They have been discussed and designed previously, please do some
> > research into previous discussions.  Search sugar-devel@ archives
> > carefully, and summarise what you find.
> >
> > There are two features in the ticket;
> >
> > 1.  adjust clock,
> >
> > 2.  display clock.
> >
> > --
> >
> > For adjust clock, refer to my pull request (you have seen this
> > already) which uses NTP;
> > https://github.com/godiard/clock-activity/pull/2
> >
> > Let's call this "adjust clock to network time".  This function may be
> > moved from the clock activity to the My Settings control panel in
> > Sugar.
> >
> > Setting the clock manually could be offered if NTP fails.  Let's call
> > this "adjust clock manually".
> >
> > At OLPC, my main concern with an "adjust clock manually" feature is
> > that it may stop laptop boot because of deployment security and date
> > limited lease signatures.  To control for this impact, I suggest;
> >
> > 1.  provide GSettings to disable "adjust clock manually" feature,
> > which will be used by olpc-os-builder,
> >
> > Please make a feature page:
> > https://wiki.sugarlabs.org/go/Features
> >
> > --
> >
> > For displaying the clock, refer to previous discussions, for example;
> > https://wiki.sugarlabs.org/go/Design_Team/Proposals/Frame#Frame_Clock
> >
> > Please take over and update the feature page:
> > https://wiki.sugarlabs.org/go/Features/Clock_in_Frame
> >
> > At OLPC, my main concern with display clock feature is that it will
> > wake up the CPU and consume power on a regular basis.  This scales
> > across the laptop population.  To control for this impact, I suggest;
> >
> > 1.  by default, display hours and minutes, not seconds,
> >
> > 2.  blank the clock before an automatic power management suspend
> > event, which requires some interprocess communication with powerd.
> >
> > Hope this helps!
> >
> > On Mon, Apr 11, 2016 at 01:37:24AM +0530, Utkarsh Tiwari wrote:
> >> Hi,
> >>     I would like to work on this feature-enhancement ->
> >> https://bugs.sugarlabs.org/ticket/3829.
> >> Could anyone here please share the expected behaviors and design ?
> >>
> >> Thanks,
> >> Utkarsh Tiwari
> >
> > --
> > James Cameron
> > http://quozl.netrek.org/
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >

-- 
James Cameron
http://quozl.netrek.org/