[Sugar-devel] How to modify the sugar?

[Sourabha G]

Thanks, I thought so too. So I changed the text of placeholder of Journal
each time I executed to ensure the changed code is executed and it did
reflect in the text of the placeholder each time, but just the print
statements aren't shown in shell.log.

On Tue, Apr 27, 2021 at 2:57 PM Chihurumnaya Ibiam <ibiam at sugarlabs.org>
wrote:

> Sugar logs show in shell.log and activity logs show in activity specific
> log usually in the form bundle_id.log, your print statements not being
> shown might mean they were never executed. The other folder it showed in
> are older logs hence the print statement executed sometime when you tested.
>
> On Tue, Apr 27, 2021, 8:01 AM Sourabha G <sourabha.project at gmail.com>
> wrote:
>
>> Thanks for the detailed explanation. I tried modifying Sugar and the
>> changes persist. The traceback and errors are shown in the log files, but
>> the debug output(print statements) does not show up in log files (But it
>> did show only once in shell.log inside one of the 4 directories labelled
>> with 10 digits numbers). Is there any other files other than shell.log
>> where the output might get stored?
>>
>> On Sun, Apr 18, 2021 at 9:00 AM James Cameron <quozl at laptop.org> wrote:
>>
>>> Ibiam has answered you, but I'll just add a bit of context.
>>>
>>> Sugar is a "desktop environment", which means it is a graphical shell
>>> program and a suite of other programs activated from that shell.  It
>>> is run (using python module jarabe) as the first and only program of a
>>> graphical login session, e.g. through Xsession.
>>>
>>> Sugar uses GNU conventions for software package building and
>>> installing.  We know this as "configure, make, make install".  The
>>> method works on pretty much every major Linux distribution.
>>>
>>> Each Linux distribution may follow different conventions for how
>>> programs, or Python programs in particular, are installed.
>>>
>>> Sugar Live Build is built from the Debian distribution, and so most
>>> closely tracks how Debian developers install software.
>>>
>>> However, it does not exactly match.
>>>
>>> The domain specific knowledge needed is operating system software
>>> distribution internals, and specific knowledge about how Python
>>> programs are installed by distribution packages on a Debian system.
>>>
>>> Once you know how a Python program is installed on a system for all
>>> users of that system to use, you have the first step of many.
>>>
>>> On Sat, Apr 17, 2021 at 05:06:29PM +0530, Sourabha G wrote:
>>> > Hi everyone,
>>> >  How to test the modified source of sugar from within Sugar DE? I
>>> cloned the
>>> > sugar repo but not sure how to test the modification.
>>> >
>>> > Thank you.
>>>
>>> > _______________________________________________
>>> > Sugar-devel mailing list
>>> > Sugar-devel at lists.sugarlabs.org
>>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>>> --
>>> James Cameron
>>> https://quozl.linux.org.au/
>>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20210427/a411f923/attachment-0001.htm>