Re: [Sugar-devel] New logo for Sugar Labs

2020-02-09 Thread Miracle Oti
Option 3


> On Feb 10, 2020, at 12:36 AM, Miracle Oti  wrote:
> 
> I so much love the first concept. 
> 
> 
>> On Feb 8, 2020, at 3:31 PM, Peace Ojemeh  wrote:
>> 
>> Hi everyone, 
>> 
>> I mentioned this earlier a few weeks ago. 
>> 
>> In the last couple weeks, I’ve been working with a small group of design 
>> volunteers(all cc'ed) to come up with a couple of new logo options for Sugar 
>> Labs given the fact that there wasn’t really a good design output from the 
>> last Google Code-In. 
>> 
>> We conducted a design sprint in Port Harcourt, Nigeria and we came up with 3 
>> options after several iterations, at this point I would want to share with 
>> the community what we've done so the community can decide what logo we 
>> should go on with.
>> 
>> 
>> Regard.
>> -- 
>> Peace Ojemeh(Perrie)
>> Twitter | Website
>> 
>> 
>> 
>> 
>> 
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] New logo for Sugar Labs

2020-02-09 Thread Miracle Oti
I so much love the first concept. 


> On Feb 8, 2020, at 3:31 PM, Peace Ojemeh  wrote:
> 
> Hi everyone, 
> 
> I mentioned this earlier a few weeks ago. 
> 
> In the last couple weeks, I’ve been working with a small group of design 
> volunteers(all cc'ed) to come up with a couple of new logo options for Sugar 
> Labs given the fact that there wasn’t really a good design output from the 
> last Google Code-In. 
> 
> We conducted a design sprint in Port Harcourt, Nigeria and we came up with 3 
> options after several iterations, at this point I would want to share with 
> the community what we've done so the community can decide what logo we should 
> go on with.
> 
> 
> Regard.
> -- 
> Peace Ojemeh(Perrie)
> Twitter | Website
> 
> 
> 
> 
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Port to Gtk3: Gdk.Image error

2020-02-09 Thread James Cameron
Thanks for working on this.

I'm looking forward especially to your porting of the C++ code in this
activity, as that will be critical to success of the porting.

For reference, the issue you are working is
https://github.com/sugarlabs/Bounce/issues/7

My further reply in context below.

On Sun, Feb 09, 2020 at 03:27:10AM +0530, Abhishek Tanwar wrote:
> I am porting BOUNCE ACTIVITY (https://github.com/sugarlabs/Bounce)
> to Gtk +3 and I have ported it to some extent but I am stuck at a
> point where I am not able to find a solution.

https://github.com/sugarlabs/Bounce/pull/13 is a pull request work in
progress that contains a similar change from gtk.gdk.Image to
Gtk.Image, but pygi-convert.sh from the GNOME project (which I've
reviewed just now) does not make such a change as you and @tonadev
have made.

So my first question is why this change was made.  It looks like a
guess.  It looks wrong.

An instance of gtk.gdk.Image is an area for bit-mapped graphics stored
on the X Windows client.  It is not a widget.

https://developer.gnome.org/pygtk/stable/class-gdkimage.html

An instance of Gtk.Image is a widget for showing an image.  It is not
an image storage class.

https://lazka.github.io/pgi-docs/Gtk-3.0/classes/Image.html

So it doesn't seem likely that this change from gtk.gdk.Image to
Gtk.Image is correct.  These are two very different levels of the
software stack.

> Here is the link to my repository for BOUNCE activity :
> https://github.com/abhishektanwar/Bounce

Thanks.  I was unable to understand the pattern of changes you've
made; the commit messages were vague and short.  I don't know which
changes happened because of pygi-convert.sh, sugar-convert.sh, or your
own edits.  I don't know why you made those edits.

https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#making-commits
has our advice on writing commit messages.

You have also committed the conversion scripts.  Please don't do that,
we don't need the scripts in the activity.

> I know that Gdk.Image is no more supported in Gdk3 and I have to use
> Cairo or Pixbuf but can't figure out how to convert it to Cairo.
> 
> Traceback (most recent call last):
>   File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1634, in 
> on_drawarea_expose
>     self.on_drawarea_resize()
>   File "/usr/share/sugar/activities/Bounce.activity/bounce.py", line 1623, in 
> on_drawarea_resize
>     self.drawimage = Gdk.Image(Gdk.IMAGE_FASTEST, Gdk.visual_get_system(), 
> rect.width, rect.height)
>   File "/usr/lib/python2.7/dist-packages/gi/overrides/_init.py", line 39, in 
> __getattr_
>     return getattr(self._introspection_module, name)
>   File "/usr/lib/python2.7/dist-packages/gi/module.py", line 139, in _getattr_
>     self._name_, name))
> AttributeError: 'gi.repository.Gdk' object has no attribute 'Image'

The traceback is not useful.

You must use Cairo for drawing, without using a separate image buffer.

Migrating from GTK+ 2.x to GTK+ 3 explains this;
https://developer.gnome.org/gtk3/stable/gtk-migrating-2-to-3.html#id-1.6.3.3.8

Instead of an expose signal and callback, you must connect a draw
signal and write a new callback.

The callback is given a Cairo context.  All drawing operations are
then performed on that context.

If you're not sure how to do this, look for another activity that was
ported from GTK 2 to GTK 3, and examine the changes made.  There are
many to choose from.  You must know how visualise git commit history
and how to read diffs.

Hope that helps!

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Introduction box code

2020-02-09 Thread James Cameron
Which application?

On Sat, Feb 08, 2020 at 08:15:03PM +0530, Rahul kohli wrote:
> In which file the code is available for introduction box which
> introduce us to the application?

-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Sugar AI

2020-02-09 Thread Srevin Saju
Thanks for the feedback Walter Bender. The python library I am using is
called, SpaCy has support for all popular languages
https://spacy.io/usage/models#languages
I had kept that language diversity in consideration when I started building
on it.
thanks for your interest. The current name for the sugar AI API is
sugaroid. looking for more suggestions :)

On Sun, 9 Feb 2020, 20:43 Walter Bender,  wrote:

>
>
> On Sun, Feb 9, 2020 at 12:02 PM Srevin Saju  wrote:
>
>> I am currently working on an Artificial Intelligence for Sugar (20%
>> complete), and I looking forward for suggestions of how good the idea might
>> be, or if its not necessary.
>>
>> The aim of the bot is to:
>> * An entirely new user to sugar might have to read the documentation to
>> understand how to use a Sugar DE properly, unless he/she doesn't read it,
>> or if a teacher explains a sugar de.
>> A student is more likely to ask questions on how to use sugar, rather
>> than expecting a third grader to read the documentation
>> * Use the documentation as source of information: The Help-activity
>> provides ReStructured text files, which can be easily parsed by Python. the
>> Sugar AI keeps the rst files as the corpus, and then answers a students
>> questions with an appropriate answer.
>> For example,
>> >>> What is the shortcut to switch to Neighborhood?
>> bot> F1
>>
>> and, additional tutorial kind of explanation to graphically explain by
>> showing images from the Rst.
>>
>> * Modular: The sugar AI is modular. The modular property can be utilized
>> by Sugar Activities to import the sugar_ai, and then provide specific help
>> within the activity:
>> For example:
>>
>> In terminal activity:
>> >>> How to find my files on the hardisk?
>> @> Use the find command
>>
>> These are some of the foreseen ideas to implement these (optionally) with
>> the target of Sugar 1.0, Please advise me, if a similar implementation
>> exists on Sugar.
>>
>
> A couple of thoughts come to mind:
>
> (1) Not sure how you plan to handle multiple languages. A majority of our
> users are non-English speakers.
> (2) That said, it may be fun to think about incorporating something like
> this inside the "brain" in the Speak activity.
>
>
>> Alternatively, if anyone like the idea, please put a +1, and, a sweet
>> name for the Sugar AI/
>> Else put a -1
>>
>> Thanks
>>
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Sugar AI

2020-02-09 Thread Walter Bender
On Sun, Feb 9, 2020 at 12:02 PM Srevin Saju  wrote:

> I am currently working on an Artificial Intelligence for Sugar (20%
> complete), and I looking forward for suggestions of how good the idea might
> be, or if its not necessary.
>
> The aim of the bot is to:
> * An entirely new user to sugar might have to read the documentation to
> understand how to use a Sugar DE properly, unless he/she doesn't read it,
> or if a teacher explains a sugar de.
> A student is more likely to ask questions on how to use sugar, rather than
> expecting a third grader to read the documentation
> * Use the documentation as source of information: The Help-activity
> provides ReStructured text files, which can be easily parsed by Python. the
> Sugar AI keeps the rst files as the corpus, and then answers a students
> questions with an appropriate answer.
> For example,
> >>> What is the shortcut to switch to Neighborhood?
> bot> F1
>
> and, additional tutorial kind of explanation to graphically explain by
> showing images from the Rst.
>
> * Modular: The sugar AI is modular. The modular property can be utilized
> by Sugar Activities to import the sugar_ai, and then provide specific help
> within the activity:
> For example:
>
> In terminal activity:
> >>> How to find my files on the hardisk?
> @> Use the find command
>
> These are some of the foreseen ideas to implement these (optionally) with
> the target of Sugar 1.0, Please advise me, if a similar implementation
> exists on Sugar.
>

A couple of thoughts come to mind:

(1) Not sure how you plan to handle multiple languages. A majority of our
users are non-English speakers.
(2) That said, it may be fun to think about incorporating something like
this inside the "brain" in the Speak activity.


> Alternatively, if anyone like the idea, please put a +1, and, a sweet name
> for the Sugar AI/
> Else put a -1
>
> Thanks
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Sugar-devel Digest, Vol 136, Issue 18

2020-02-09 Thread Srevin Saju
Out of the given options, Option 2 looks professional :)




On Sun, Feb 9, 2020 at 8:02 PM 
wrote:

> Send Sugar-devel mailing list submissions to
> sugar-devel@lists.sugarlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sugarlabs.org/listinfo/sugar-devel
> or, via email, send a message with subject or body 'help' to
> sugar-devel-requ...@lists.sugarlabs.org
>
> You can reach the person managing the list at
> sugar-devel-ow...@lists.sugarlabs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sugar-devel digest..."
>
>
> Today's Topics:
>
>1. New logo for Sugar Labs (Peace Ojemeh)
>
>
> --
>
> Message: 1
> Date: Sat, 8 Feb 2020 15:31:45 +0100
> From: Peace Ojemeh 
> To: sugar-devel , iaep
> 
> Cc: Legendary Ofor , Steve Anthony
> , domero13...@gmail.com
> Subject: [Sugar-devel] New logo for Sugar Labs
> Message-ID:
>  nbmc+...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi everyone,
>
>
> I mentioned this earlier a few weeks ago.
>
>
> In the last couple weeks, I’ve been working with a small group of design
> volunteers(all cc'ed) to come up with a couple of new logo options for
> Sugar Labs given the fact that there wasn’t really a good design output
> from the last Google Code-In.
>
>
> We conducted a design sprint in Port Harcourt, Nigeria and we came up with
> 3 options after several iterations, at this point I would want to share
> with the community what we've done so the community can decide what logo we
> should go on with.
>
>
>
> Regard.
> --
> *Peace Ojemeh*(Perrie)
> Twitter  | Website
> 
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200208/44eda59c/attachment.htm
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: Option 3.pdf
> Type: application/pdf
> Size: 542383 bytes
> Desc: not available
> URL: <
> http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200208/44eda59c/attachment.pdf
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: Option 2..pdf
> Type: application/pdf
> Size: 5733156 bytes
> Desc: not available
> URL: <
> http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200208/44eda59c/attachment-0001.pdf
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: Option 1.png
> Type: image/png
> Size: 8679086 bytes
> Desc: not available
> URL: <
> http://lists.sugarlabs.org/archive/sugar-devel/attachments/20200208/44eda59c/attachment.png
> >
>
> --
>
> Subject: Digest Footer
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
>
> End of Sugar-devel Digest, Vol 136, Issue 18
> 
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Sugar AI

2020-02-09 Thread Srevin Saju
I am currently working on an Artificial Intelligence for Sugar (20%
complete), and I looking forward for suggestions of how good the idea might
be, or if its not necessary.

The aim of the bot is to:
* An entirely new user to sugar might have to read the documentation to
understand how to use a Sugar DE properly, unless he/she doesn't read it,
or if a teacher explains a sugar de.
A student is more likely to ask questions on how to use sugar, rather than
expecting a third grader to read the documentation
* Use the documentation as source of information: The Help-activity
provides ReStructured text files, which can be easily parsed by Python. the
Sugar AI keeps the rst files as the corpus, and then answers a students
questions with an appropriate answer.
For example,
>>> What is the shortcut to switch to Neighborhood?
bot> F1

and, additional tutorial kind of explanation to graphically explain by
showing images from the Rst.

* Modular: The sugar AI is modular. The modular property can be utilized by
Sugar Activities to import the sugar_ai, and then provide specific help
within the activity:
For example:

In terminal activity:
>>> How to find my files on the hardisk?
@> Use the find command

These are some of the foreseen ideas to implement these (optionally) with
the target of Sugar 1.0, Please advise me, if a similar implementation
exists on Sugar.
Alternatively, if anyone like the idea, please put a +1, and, a sweet name
for the Sugar AI/
Else put a -1

Thanks
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel