[Sugar-devel] Chat Activity with translation

2013-04-21 Thread Prannoy M 
Hi,
I would like to work on the proposal 'Chat Activity with translation' for
GSoC.I'm a first time GSoCer and am really interested to contribute.Can
someone help me get started?
I tried running sugar-emulator on ubuntu 12.04 but lots of activities were
not working.So now I'm installing by the virtual box method.

Regards,
*M.Prannoy*
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Chat Activity with translation

2013-04-21 Thread Ignacio Rodríguez 
Try to install:
sugar-build
(https://git.sugarlabs.org/sugar-build/sugar-build)

For more info:
http://sugarlabs.org/~buildbot/docs/build.html
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Local Labs Wikis was: Re: [IAEP] wiki.sugarlabs.org ongoing maintenance

2013-04-21 Thread Ignacio Rodríguez 
I'm leaning to think the best option is to copy the pages that are good
from all {ar, co, cl, pe} wikis
into one single Sugar Labs / Laboratorios Azúcar América Latina instance.

+1 for the idea.
Maybe integrate Uruguay in SL pages {uy.sl.org?} ! [?]




2013/4/20 Sebastian Silva sebast...@fuentelibre.org

  Hi,
 When I did maintenance and upgrade of co.sugarlabs.org the only
 difference with the other local labs wikis,
 was that it had some extensions related to vandalism prevention:

 from LocalSettings.php:

 #dirakx para los vandalos
 # icarito - File Not Found
 #require_once( $IP/extensions/TitleBlacklist/TitleBlacklist.php );
 require_once( extensions/CheckUser/CheckUser.php );
 #require_once( includes/DatabaseFunctions.php );
 require_once( $IP/extensions/bad-behavior/bad-behavior-mediawiki.php );

 I had to disable the TitleBlacklist extension because I coudn't find it
 and did not have the time to go
 fishing for it.

 Perhaps this is a good opportunity to study what countermeasures / options
 we have to fix this issue,
 which is particularly grave for local labs wikis.

 I'm cc'ing Rafael (dirakx) who originally configured these countermeasures
 for co.sl.org.

 I'm leaning to think the best option is to copy the pages that are good
 from all {ar, co, cl, pe} wikis
 into one single Sugar Labs / Laboratorios Azúcar América Latina instance.

 This would reduce the maintenance burden and maybe revitalize /
 consolidate our spanish speaking
 community a bit more?

 Regards,
 Sebastian

 El 19/04/13 23:41, Stefan Unterhauser escribió:

 found one link ...
 http://co.sugarlabs.org/go/Eigene_Mail-Adresse_kostenfrei

  /me knows german :)

  by the way wonder why there is no sugarlabs favicon :(

  cu
 dogi

  PS: there are much more here http://co.sugarlabs.org/go/Especial:Todas

  Wonder if somebody is actively watching all
 http://co.sugarlabs.org/go/Especial:Seguimiento


 On Thu, Apr 18, 2013 at 5:39 PM, Bernie Innocenti ber...@sugarlabs.orgwrote:

 Cristian Paul detected a surge of spam on co.sugarlabs.org... can
 someone please check? I'll be on a bus to NYC this afternoon.

 On 04/18/2013 02:27 AM, Sebastian Silva wrote:
 
  El 16/04/13 00:03, Bernie Innocenti escribió:
  Our wiki has grown quite large and the upgrade from Mediawiki 1.19 to
  1.20 required several slow steps, so unfortunately I had to leave
 before
  fixing up the local wikis.
 
 
  I ran maintenance/update scripts for:
  pe.sugarlabs.org
  cl.sugarlabs.org
  ar.sugarlabs.org
  co.sugarlabs.org
 
  They are back up, spammy as they are.
 
  Regards,
  Sebastian


  --
 Bernie Innocenti
 Sugar Labs Infrastructure Team
 http://wiki.sugarlabs.org/go/Infrastructure_Team
 ___
  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


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

Re: [Sugar-devel] Chat Activity with translation

2013-04-21 Thread Aneesh Dogra 
Hey Prannoy,

Its good that you decided to do a GSOC project for us. Thanks! For Chat
Activity with translation project you need to first of all research on the
translation system options we have. Meeting uses Apertium, is it the best
alternative available? Then you need to form a blue print on how you would
the chat activity interact with the translation server?

For this particular task you'll be doing more work with translation systems
and the server end, than the sugar activity itself.

We'll be requiring an easily callable translation API at the server end.
The client (i.e the activity) will sent GET/POST requests to the server
containing in them the text to be translated.
The server should then respond with GET/POST requests containing in them
the translated text.
The client intercepts the request and displays the translated text.

Important trade-offs to compare when searching for a good machine
translation system:

1) Speed
2) Server Load/Requirements
3) Language Pairs


On Sun, Apr 21, 2013 at 11:54 AM, Prannoy M m.pran...@gmail.com wrote:

 Hi,
 I would like to work on the proposal 'Chat Activity with translation' for
 GSoC.I'm a first time GSoCer and am really interested to contribute.Can
 someone help me get started?
 I tried running sugar-emulator on ubuntu 12.04 but lots of activities were
 not working.So now I'm installing by the virtual box method.

 Regards,
 *M.Prannoy*


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




-- 
Thanks
Aneesh Dogra (lionaneesh)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Hacking on HTML activities UI (was Re: GSoC 13)

2013-04-21 Thread lionel 
 

Hi Suraj,

 

1) I’m used to develop using VirtualBox and Windows. But you’re right, it
need a powerful PC. Note that if you switch to GNU Linux, it could be better
to switch to Fedora instead of Ubuntu because Sugar is built on Fedora.

2) Nice. It’s a good start point.

3) Yes, a good understanding of interface between Python/Sugar and
JavaScript is very important. BTW do not spent lot of time on Enyo. In fact
Enyo is not at all a pre-requisite. At end we could hope to be JavaScript
framework agnostic. If you follow threads in this mailing list, you could
have enough lucky like me to learn a new JavaScript framework each day :-)
So yes, being JavaScript framework agnostic is interesting.

The issue about “console” is that the “console-message” is standardly use to
get output from the “console.log()” JavaScript function. So, it’s not at all
dedicated to communication between JavaScript and the embedding WebView. The
hack that I’ve used it that if the console message is prefixed by “enyo://”
it’s processed by the framework like a message to Sugar, else the framework
just pass the message. You could see this in the “Log” activity when you run
Grid paint activity. So the idea of improvement is to find a less hacky way
to interface Sugar and JavaScript. It’s one of objective of the IRC meeting.

 

About UI, yes the main part of the work is to do CSS files to reproduce the
Sugar UI. Then for non-UI Sugar features (datastore and collaboration) the
work is to write a JavaScript API to map the Sugar API.

 

Best regards.

 

Lionel.

 

 

De : suraj ks [mailto:suraj.gilles...@gmail.com] 
Envoyé : samedi 20 avril 2013 23:26
À : lio...@olpc-france.org
Cc : Sugar-dev Devel; Manuel Quiñones; Daniel Narvaez
Objet : Re: [Sugar-devel] Hacking on HTML activities UI (was Re: GSoC 13)

 

Hi lionel,

 

1)Done with setting up of virtual box and installed sugar. Seems to be
working fine.

   But, while running the Sugar in it, it slows down the pc a lot and
various other issues come in while developing activities.

   I guess it is better if I switch to Ubuntu asap while hacking.

 

 2)It was  a good read . Now, I have a basic understanding how activities
are developed and packed right from

making a standalone python program to packaging and distributing the
activities.

I did install the helloworld activity and it seems to working fine.

 

 3)I must admit, it is impressive work. 

   Went through your manual and understood how the enyo framework
alongwith,connect and sendmessage methods were used to interact between
the user interface, javascript and python code

 

 

 

I needed some clarifications,

Honestly, i did not grasp the console part, which needed improvement. 

Were you talking about the connect and sendmessage?

 

And, regarding the UI part, should I just create CSS files to replicate
default sugar toolbars and other sugar user interfaces? 

 

 

 

 

 

 

Also, looking forward to the IRC meeting on html activities on Mon. :)

 

 

 

 

Regards,

Suraj

 

 

On Tue, Apr 16, 2013 at 6:51 PM, lio...@olpc-france.org
mailto:lio...@olpc-france.org  wrote:

 

Hi Suraj,

 

To initialize your knowledge about the project, I can suggest you several
steps:

 

First, install Sugar on your computer. I understand that you're on Windows
but it's pretty easy to install SugarOnAStick in a Windows VirtualBox. It's
a good way to discover it. Have a look on [1] (in French but easy to
translate or follow steps using screen capture). 

 

Second, learn how Sugar activity are developed and packaged today. The
better introduction about that is in the great book of James, Make your own
Sugar activities [2]. It will be very interesting for you too to install
and explore the HelloWorld Activity [3] in your VirtualBox.

 

Third, explore the first experience of Sugar HTML5 activities I've wrote. A
chapter in the book Make your own Sugar activities talk about that [4].
Gridpaint [5] is one of the first activity to use this framework. Install it
and try to understand how it works: have specifically a look on Log (using
Log activity) then to Enyo.py and Sugar.js files.

 

Once you've done it, there is few issue with the current way of works of
this first Sugar HTML5 framework:

1.   It depends on console-message to interface WebKit and JavaScript.
It's a bad hack. This message could be deprecated on future version of
WebKit. We should work one another interface. Exploring PhoneGap/Cordoba way
of working for iOS (using a hidden Iframe) could be interesting.

2.   It depends of the standard Sugar Toolbar and HTML5 controls don't
have the Sugar LookFeel. We want integrate the full Sugar UI into the Sugar
HTML5 framework. So we need CSS files and an API to match the Sugar controls
and features.

3.   It don't expose the Sugar feature into JavaScript. So each time the
HTML5 application want to call Sugar, it need to call Python code. The Sugar
HTML5 framework should expose natively main

Re: [Sugar-devel] Local Labs Wikis was: Re: [IAEP] wiki.sugarlabs.org ongoing maintenance

2013-04-21 Thread Bernie Innocenti 
On 04/21/13 10:40, Ignacio Rodríguez wrote:
 I'm leaning to think the best option is to copy the pages that are good
 from all {ar, co, cl, pe} wikis
 into one single Sugar Labs / Laboratorios Azúcar América Latina instance.
 
 +1 for the idea.
 Maybe integrate Uruguay in SL pages {uy.sl.org http://uy.sl.org?} ! 

+1 from me, if the coordinators of the Local Labs agree to merge.

-- 
Bernie Innocenti
Sugar Labs Infrastructure Team
http://wiki.sugarlabs.org/go/Infrastructure_Team
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel