Re: [Sugar-devel] Google Summer of Code Blog

[suraj ks]

Thanks for the input Walter and Manuel.
I've sent a mail to the planetmas...@sugarlabs.org
Awaiting confirmation.

And yes, I'll keep updating it as I progress.


On 16 July 2013 06:58, Walter Bender  wrote:

> Having just gone through the process of writing my first JS Sugar
> activity, I think it would be good to document a few things that I
> found confusing. (Undoubtedly, much of my confusion stems from my
> unfamiliarity with JS.) Maybe you can add these tidbits, refined, to
> your blog:
>
> (1) It wasn't clear to me how to add new buttons to the toolbar. I needed
> to:
> * add the button to index.html
> 
> * define the button style in css/activity.css
> #main-toolbar #new-button {
> background-image: url(../icons/new-button.svg);
> }
> * add the callback to js/activity.js
> var newButton = document.getElementById("new-button");
> newButton.onclick = function () {
> new_positions();
> }
>
> (2) I suspect this is usual stuff for JS programmers, but new to me: I
> used handlebars.js to define templates for some labels I wanted to
> position onto some graphics. Important for the dynamic allocation of
> elements that I use in many activities.
> * in index.html, I added a div to hold the elements I define from the
> template
> 
> * in js/activity.js:
> // Create label elements for each of our dots
> template = Handlebars.compile(labelSource);
> var labelElem = document.getElementById("labelDiv");
> var html = template({labels:arrLabels});
> labelElem.innerHTML = html;
>
> (3) For my graphics, I used Easeljs [1]. Pretty straight forward.
> * Let me define graphical elements (i.e., sprites)
> * and a canvas for drawing
>
> -walter
>
>
> [1] http://www.createjs.com/#!/EaselJS
>
> On Mon, Jul 15, 2013 at 4:01 PM, suraj ks 
> wrote:
> > Hi,
> >
> > I started writing a blog tracking the development of the my GSoC '13
> project
> >
> > Sugar Framework for writing activity in full HTML5  here [1].
> >
> > Basically, I've summed up my understanding of the working of the
> framework.
> >
> > My initial plan was to post it on https://planet.gnome.org/ , but they
> seem
> > to be very selective on what blogs are relayed on the channel.
> > Since i started blogging very recently, I don't think I stand a chance of
> > getting my blog posted there.
> >
> > It would be very helpful if someone from the community could relay it on
> > planet.gnome.org.
> >
> > Will keep posting more stuffs in my blog as we progress.
> >
> >
> > Cheers!
> > Suraj
> >
> > ___
> > 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

[Sugar-devel] Google Summer of Code Blog

[suraj ks]

Hi,

I started writing a blog tracking the development of the my GSoC '13
project
Sugar Framework for writing activity in full HTML5  here
[1]
.
Basically, I've summed up my understanding of the working of the framework.

My initial plan was to post it on https://planet.gnome.org/ , but they seem
to be very selective on what blogs are relayed on the channel.
Since i started blogging very recently, I don't think I stand a chance of
getting my blog posted there.

It would be very helpful if someone from the community could relay it on
planet.gnome.org.

Will keep posting more stuffs in my blog as we progress.


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

Re: [Sugar-devel] Sugar terminates abruptly

[suraj ks]

Sure.


On Fri, Jun 28, 2013 at 11:06 PM, Daniel Narvaez wrote:

> Yes! It crashes even if I just over the entry here. I don't have time to
> debug it right now but we need to find out which python code is triggering
> it.
>
> Can you open a bug about it please? Including these steps and the fpaste.
>
>
> On 28 June 2013 18:44, suraj ks  wrote:
>
>> Tried that.
>> Running terminal activity from journal seems to be fine.
>>
>> Try this,
>> Run the pippy activity.
>> change the title of pippy activity in the activity toobar.
>> Close it.
>> Run pippy activity from journal.
>>
>> When i do that it crashes.
>> I got the same stuff http://fpaste.org/21715/37243708/
>>
>>
>> On Fri, Jun 28, 2013 at 9:26 PM, Daniel Narvaez wrote:
>>
>>> I wish I could see the python code which is triggering this. I cannot
>>> reproduce but it seems unlikely to be something you messed up, it's
>>> probably either a sugar or a glib/pygobject bug.
>>>
>>> Can you try this:
>>>
>>> Move away ~/.sugar/default
>>> Start sugar
>>> Start the terminal activity
>>> Close it
>>> Click on therminal entry in the journal
>>>
>>> I want to make sure we are doing the same exact test as much as possible.
>>>
>>>
>>>
>>> On 28 June 2013 13:18, suraj ks  wrote:
>>>
>>>> Wanted to know if anyone else out there is getting this problem.
>>>>
>>>> I open the journal.
>>>> Click one of the recent activities, then sugar terminated abruptly.
>>>> After it terminates, this is what i get on my terminal,
>>>> http://fpaste.org/21626/37241794/
>>>>
>>>> Did i mess up something in the journal or is it a bug?
>>>>
>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>
>>
>
>
> --
> Daniel Narvaez
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar terminates abruptly

[suraj ks]

Tried that.
Running terminal activity from journal seems to be fine.

Try this,
Run the pippy activity.
change the title of pippy activity in the activity toobar.
Close it.
Run pippy activity from journal.

When i do that it crashes.
I got the same stuff http://fpaste.org/21715/37243708/


On Fri, Jun 28, 2013 at 9:26 PM, Daniel Narvaez  wrote:

> I wish I could see the python code which is triggering this. I cannot
> reproduce but it seems unlikely to be something you messed up, it's
> probably either a sugar or a glib/pygobject bug.
>
> Can you try this:
>
> Move away ~/.sugar/default
> Start sugar
> Start the terminal activity
> Close it
> Click on therminal entry in the journal
>
> I want to make sure we are doing the same exact test as much as possible.
>
>
>
> On 28 June 2013 13:18, suraj ks  wrote:
>
>> Wanted to know if anyone else out there is getting this problem.
>>
>> I open the journal.
>> Click one of the recent activities, then sugar terminated abruptly.
>> After it terminates, this is what i get on my terminal,
>> http://fpaste.org/21626/37241794/
>>
>> Did i mess up something in the journal or is it a bug?
>>
>
>
>
> --
> Daniel Narvaez
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar terminates abruptly

[suraj ks]

Wanted to know if anyone else out there is getting this problem.

I open the journal.
Click one of the recent activities, then sugar terminated abruptly.
After it terminates, this is what i get on my terminal,
http://fpaste.org/21626/37241794/

Did i mess up something in the journal or is it a bug?
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar build break

[suraj ks]

Now it looks like it is alright after trying to clean and build.
FYI. I use Ubuntu 13.04

Thanks Daniel.


On Tue, Jun 18, 2013 at 4:17 PM, Daniel Narvaez  wrote:

> Yeah because Xephyr is not used when running from gdm.
>
> Even with sugar-build if you run from a text console it will use full X
> instead of Xephyr.
>
>
> On Tuesday, 18 June 2013, Ignacio Rodríguez wrote:
>
>> Mm, the problem is sugar-emulator running in terminal or launch the
>> aplication.
>>
>> If you run it from gdm it's work ok..
>>
>> The problem is Ubuntu 13.10 :-/
>>
>> I test it later in Lubuntu 13.10
>>
>> Grettings.
>> Ignacio
>>
>>
>> 2013/6/18 Daniel Narvaez 
>>
>> I would report it to launchpad too. Might be an ubuntu specific issue.
>> Also Xephyr is sort of unmaintaned upstream.
>>
>>
>> On 18 June 2013 11:51, Alan Jhonn Aguiar Schwyn wrote:
>>
>> Reported: https://bugs.freedesktop.org/show_bug.cgi?id=65887
>>
>> My explain it's very basic.. if someone can explain more, thanks!
>>
>> --
>> Date: Tue, 18 Jun 2013 11:34:56 +0200
>> From: dwnarv...@gmail.com
>> To: alan...@hotmail.com; nachoe...@gmail.com
>>
>> CC: sugar-devel@lists.sugarlabs.org; suraj.gilles...@gmail.com
>> Subject: Re: [Sugar-devel] Sugar build break
>>
>> I suggested to Ignacio to report it but I don't know if he did (ccing
>> him).
>>
>>
>> On 18 June 2013 11:33, Alan Jhonn Aguiar Schwyn wrote:
>>
>> Yes :-(
>> It's problem of my distro (Ubuntu 13.10).
>>
>> The error was reported??
>>
>> --
>> Date: Tue, 18 Jun 2013 11:30:34 +0200
>>
>> From: dwnarv...@gmail.com
>> To: alan...@hotmail.com
>> CC: sugar-devel@lists.sugarlabs.org; suraj.gilles...@gmail.com
>> Subject: Re: [Sugar-devel] Sugar build break
>>
>> Ignacio reported something similar and it appeared to be an Ubuntu bug.
>> Try to run "Xephyr :10" and see if that also crashes, if so it's a Xephyr
>> bug in your distro.
>>
>>
>> On 18 June 2013 11:25, Alan Jhonn Aguiar Schwyn wrote:
>>
>> That error appears only one time.. after a clean.. now builds all without
>> problem.
>> But give me this when try run (I attach the full log):
>>
>> alan@alan-pc:~/Documentos/GIT/sugar-build/sugar-build$ ./osbuild run
>> Type Shift-Alt-Q inside sugar to close.
>>
>> Command failed: sugar-runner --home-dir
>> /home/alan/Documentos/GIT/sugar-build/sugar-build/build/state/home/default
>>
>>
>>  Initializing built-in extension Generic Event Extension
>> Initializing built-in extension SHAPE
>> Initializing built-in extension MIT-SHM
>> Initializing built-in extension XInputExtension
>> Initializing built-in extension XTEST
>> Initializing built-in extension BIG-REQUESTS
>> Initializing built-in extension SYNC
>> Initializing built-in extension XKEYBOARD
>> Initializing built-in extension XC-MISC
>> Initializing built-in extension SECURITY
>> Initializing built-in extension XINERAMA
>> Initializing built-in extension XFIXES
>> Initializing built-in extension RENDER
>> Initializing built-in extension RANDR
>> Initializing built-in extension COMPOSITE
>> Initializing built-in extension DAMAGE
>> Initializing built-in extension MIT-SCREEN-SAVER
>> Initializing built-in extension DOUBLE-BUFFER
>> Initializing built-in extension RECORD
>> Initializing built-in extension DPMS<
>>
>> --
>> Ignacio Rodríguez
>>
>
>
> --
> Daniel Narvaez
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar build break

[suraj ks]

Everything seemed to be working fine yesterday.

But today morning when i try to run I get this,

[osbuild sugar-build]$ run

= Building =

* Cleaning webkitgtk
* Building node

Command failed: make install

make -C out BUILDTYPE=Release V=1
make[1]: Entering directory `/home/suraj/sugar-build/node/out'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/suraj/sugar-build/node/out'
ln -fs out/Release/node node
/usr/bin/python tools/install.py install
Traceback (most recent call last):
installing /usr/local/bin/node
  File "tools/install.py", line 156, in 
run(sys.argv[:])
  File "tools/install.py", line 151, in run
if cmd == 'install': return files(install)
  File "tools/install.py", line 122, in files
action(['out/Release/node'], 'bin/node')
  File "tools/install.py", line 79, in install
def install(paths, dst): map(lambda path: try_copy(path, dst), paths)
  File "tools/install.py", line 79, in 
def install(paths, dst): map(lambda path: try_copy(path, dst), paths)
  File "tools/install.py", line 71, in try_copy
return shutil.copy2(source_path, target_path)
  File "/usr/lib/python2.7/shutil.py", line 130, in copy2
copyfile(src, dst)
  File "/usr/lib/python2.7/shutil.py", line 83, in copyfile
with open(dst, 'wb') as fdst:
IOError: [Errno 13] Permission denied: '/usr/local/bin/node'
make: *** [install] Error 1
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] developer.sugarlabs.org index

[suraj ks]

Cool.
I've sent a pull request to the same.


On Sun, Jun 16, 2013 at 8:53 PM, Manuel Quiñones  wrote:

> Ah, right! Then...
>
> https://github.com/sugarlabs/docker
>
> 2013/6/16 Daniel Narvaez :
> > Isn't this a docker patch?
> >
> >
> > On 16 June 2013 17:18, Manuel Quiñones  wrote:
> >>
> >> Hey Suraj, great! The pull requests go to sugarlabs/REPO user in
> >> github, so in this case is:
> >>
> >> https://github.com/sugarlabs/sugar-docs
> >>
> >> Maybe we need to add this clarification in sugar-docs?
> >>
> >> 2013/6/16 suraj ks :
> >> > Hey,
> >> > Got the header rooted to the top.
> >> > Will remain appear on top of your screen even if you scroll down.
> >> > Wanted to know where I should send the pull request to?
> >> >
> >> >
> >> > On Thu, Jun 13, 2013 at 8:39 PM, Manuel Quiñones 
> >> > wrote:
> >> >>
> >> >> +1 this can be done with a few lines of CSS.  Can be a good task for
> a
> >> >> contributor to get in touch with the docs and CSS.  Adding Suraj to
> >> >> the CC.  The recent change in sugar-web to make the toolbar always on
> >> >> top can be a good reference.
> >> >>
> >> >> 2013/6/12 Daniel Narvaez :
> >> >> > It's a bit annoying when you navigate that you easily lose the
> header
> >> >> > (because you scroll down the text). I wonder if the header should
> >> >> > take
> >> >> > the
> >> >> > whole width and be always at the top.
> >> >> >
> >> >> >
> >> >> > On 10 June 2013 16:53, Manuel Quiñones  wrote:
> >> >> >>
> >> >> >> 2013/6/8 Daniel Narvaez :
> >> >> >> > On 8 June 2013 17:11, Manuel Quiñones  wrote:
> >> >> >> >>
> >> >> >> >> The index link can also be inside a site header, which can be
> >> >> >> >> consistently in every page of the developer site.  We can use
> >> >> >> >> this
> >> >> >> >> image:
> >> >> >> >>
> >> >> >> >> http://wiki.sugarlabs.org/images/e/e2/Join_Developer_BW.png
> >> >> >> >>
> >> >> >> >> Can also be the favicon :)
> >> >> >> >
> >> >> >> >
> >> >> >> > The way I'm doing this is to add an extra to docker and hacking
> >> >> >> > stuff
> >> >> >> > around
> >> >> >> >
> >> >> >> > #sidebar_switch {
> >> >> >> > display: none;
> >> >> >> > }
> >> >> >> >
> >> >> >> > function(){
> >> >> >> > var origSwitchTab = switchTab
> >> >> >> >
> >> >> >> > switchTab = function (tab) {
> >> >> >> > origSwitchTab("headings");
> >> >> >> > }
> >> >> >> > })();
> >> >> >> >
> >> >> >> > Nice eh? :P
> >> >> >> >
> >> >> >> > It should be easy to insert that link wherever we want. Do you
> >> >> >> > think
> >> >> >> > the
> >> >> >> > image is enough or should it have text too?
> >> >> >> >
> >> >> >> > Perhaps inside the sidebar it would be cleaner layout wise,
> though
> >> >> >> > if
> >> >> >> > you
> >> >> >> > have it hidden... Tough I'm not sure it make sense to hide the
> >> >> >> > sidebar
> >> >> >> > for
> >> >> >> > the introductory docs (it's useful when you have code on the
> >> >> >> > side).
> >> >> >> > Maybe we
> >> >> >> > just disable the hide thing..
> >> >> >>
> >> >> >> Header that links to index pushed, looks like:
> >> >> >> http://dev.laptop.org/~manuq/docs-header.png
> >> >> >>
> >> >> >> The sidebar change is the pending bit.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> .. manuq ..
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Daniel Narvaez
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> .. manuq ..
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> .. manuq ..
> >
> >
> >
> >
> > --
> > Daniel Narvaez
>
>
>
> --
> .. manuq ..
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] developer.sugarlabs.org index

[suraj ks]

Hey,
Got the header rooted to the top.
Will remain appear on top of your screen even if you scroll down.
Wanted to know where I should send the pull request to?


On Thu, Jun 13, 2013 at 8:39 PM, Manuel Quiñones  wrote:

> +1 this can be done with a few lines of CSS.  Can be a good task for a
> contributor to get in touch with the docs and CSS.  Adding Suraj to
> the CC.  The recent change in sugar-web to make the toolbar always on
> top can be a good reference.
>
> 2013/6/12 Daniel Narvaez :
> > It's a bit annoying when you navigate that you easily lose the header
> > (because you scroll down the text). I wonder if the header should take
> the
> > whole width and be always at the top.
> >
> >
> > On 10 June 2013 16:53, Manuel Quiñones  wrote:
> >>
> >> 2013/6/8 Daniel Narvaez :
> >> > On 8 June 2013 17:11, Manuel Quiñones  wrote:
> >> >>
> >> >> The index link can also be inside a site header, which can be
> >> >> consistently in every page of the developer site.  We can use this
> >> >> image:
> >> >>
> >> >> http://wiki.sugarlabs.org/images/e/e2/Join_Developer_BW.png
> >> >>
> >> >> Can also be the favicon :)
> >> >
> >> >
> >> > The way I'm doing this is to add an extra to docker and hacking stuff
> >> > around
> >> >
> >> > #sidebar_switch {
> >> > display: none;
> >> > }
> >> >
> >> > function(){
> >> > var origSwitchTab = switchTab
> >> >
> >> > switchTab = function (tab) {
> >> > origSwitchTab("headings");
> >> > }
> >> > })();
> >> >
> >> > Nice eh? :P
> >> >
> >> > It should be easy to insert that link wherever we want. Do you think
> the
> >> > image is enough or should it have text too?
> >> >
> >> > Perhaps inside the sidebar it would be cleaner layout wise, though if
> >> > you
> >> > have it hidden... Tough I'm not sure it make sense to hide the sidebar
> >> > for
> >> > the introductory docs (it's useful when you have code on the side).
> >> > Maybe we
> >> > just disable the hide thing..
> >>
> >> Header that links to index pushed, looks like:
> >> http://dev.laptop.org/~manuq/docs-header.png
> >>
> >> The sidebar change is the pending bit.
> >>
> >>
> >> --
> >> .. manuq ..
> >
> >
> >
> >
> > --
> > Daniel Narvaez
>
>
>
> --
> .. manuq ..
>
___
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)

[suraj ks]

Hi Lionel,

The page which you created summarizing the work plan for HTML activities
was very helpful in preparing my proposal.
I've submitted the first draft of my proposal.
Kindly go through it and help me improve the same.

Please note that, I'm yet to post links to my work in my proposal.
I'll be pushing all of it to github tomorrow and updating my proposal.
Yet to setup the development environment too.

Thanks,
Suraj



On Mon, Apr 22, 2013 at 1:32 AM,  wrote:

> ** **
>
> 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,  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). 
>
>  ***

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

[suraj ks]

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,  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 Look&Feel. 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 Sugar features:
> specifically DataStore (read/write to Journal), telepathy (Collaboration).
> 
>
> **4.   **Finally, as you read in this thread, embedding a WebView is
> not necessarily the best solution to write a Web activity. BTW as a first
> approach to the problem, we could start with it.
>
>  
>
> Point 2 could be started very quickly. You just had to list all Sugar
> Controls then think how they could be designed as HTML5 controls.
>
>  
>
> Lionel.
>
>  
>
> [1]
> http://olpc-france.org/blog/2013/02/decouvrez-sugar-depuis-votre-machine/*
> ***
>
> [2] http://www.flossmanuals.net/make-your-own-sugar-activities/
>
> [3] http://activities.sugarlabs.org/fr/sugar/addon/4418
>
> [4]
> http://en.flossmanuals.net/make-your-own-sugar-activities/developing-sugar-activities-using-html5/
> 
>
> [5] http://activities.sugarlabs.org/fr/sugar/addon/4647
>
> ** **
>
> ** **
>
> ** **
>
> *De :* suraj ks [mailto:suraj.gilles...@gmail.com]
> *Envoyé :* lundi 15 avril 2013 22:27
> *À :* Daniel Narvaez; lio...@olpc-france.org
> *Cc :* Sugar-dev Devel; Manuel Quiñones
> *Objet :* Re: [Sugar-devel] Hacking on HTML activities UI (was Re: GSoC
> 13)
>
> ** **
>
> Ok,
>
> ** **
>
> In a nutshell,
>
> These are the tasks for this project.
>
> ** **
&

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

[suraj ks]

Ok,

In a nutshell,
These are the tasks for this project.

Going by the way Lionel suggested,
Create a sugar activity with full screen web view control.
Modify the current  js framework and make use of "native features" to be
able to write html activities in Sugar.


Lionel mentioned,

"The step 1 need only to map a set of JavaScript
functions to a set of Sugar functions. Once the list of Sugar functions is
write, it’s not very complex to do."

So find those functions and tweak them to support the same.

And of course, work on the UI part.

Please correct if I'm wrong.

Also, how are we going to get the JS and Sugar to communicate without the
console?




On Sun, Apr 14, 2013 at 3:51 PM, Daniel Narvaez  wrote:

> On 13 April 2013 19:55, suraj ks  wrote:
>
>> Oh! Ok.
>> I'm getting a clearer picture of what you're trying to do.
>>
>> The application period is from 22nd April to 3rd May.
>> We have to submit it within this period.
>>
>> I was talking to a few seniors today from my college who got into GSoC 12.
>> They advised me to start working on the proposal atleast a week before
>> the actual application period starts.
>> They said, only when i start making the proposal I'll get to know more on
>> the finer details of the implementation of the project.
>> So the sooner I start the better it is.
>>
>>
>> Well. . . you are my mentor.
>> What do you suggest? :)
>>
>
>  It probably make sense for you to focus on step 1 (Lionel approach) in
> your proposal. It's simpler and he is actually going to mentor the GSOC
> task.
>
___
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)

[suraj ks]

Oh! Ok.
I'm getting a clearer picture of what you're trying to do.

The application period is from 22nd April to 3rd May.
We have to submit it within this period.

I was talking to a few seniors today from my college who got into GSoC 12.
They advised me to start working on the proposal atleast a week before the
actual application period starts.
They said, only when i start making the proposal I'll get to know more on
the finer details of the implementation of the project.
So the sooner I start the better it is.


Well. . . you are my mentor.
What do you suggest? :)



On Sat, Apr 13, 2013 at 11:00 PM, Daniel Narvaez wrote:

> On 13 April 2013 17:07, suraj ks  wrote:
>
>> Phew!
>> Finally I'm done with my exams. :)
>> Don't have to worry about writing another one until May 14(my semester
>> end exams start then.)
>>
>
> Great! :)
>
>
>> Meanwhile, I've been closely following the threads on HTML activities in
>> the mailing list.
>> As I was reading through, few basic doubts crept up.
>>
>> Do we have to build a sugar app which is supported by chrome in order to
>> integrate the chrome window inside the sugar shell?
>> Or are we building a chrome web app which is supported in sugar shell?
>>
>
> If we follow my approach, we are going to run chrome itself inside the
> sugar shell. A web activity is going to be installed in chrome and opened
> in a UI-less window (if you play with web apps in chrome, that should make
> more sense). The sugar shell is going to do some magic to make the chrome
> web activities look like native activities. Display an icon for them in the
> home etc.
>
>
>> Regarding the implementation of the same, which way will we be proceeding?
>> I meant, will we be following the implementation technique suggested by
>> you or the one suggested by Lionel?
>>
>
> Mine of course! :P
>
> Kidding, I don't know that yet. We are planning to meet when Simon (one of
> the sugar maintainers) is back and find a consensus on the way forward.
>
>
>> I'm planning to start work on the proposal in a few days.
>> It would help a great deal if you could throw some light on these.
>>
>
> When does the proposal need to be submitted?
>
___
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)

[suraj ks]

Phew!
Finally I'm done with my exams. :)
Don't have to worry about writing another one until May 14(my semester end
exams start then.)


Meanwhile, I've been closely following the threads on HTML activities in
the mailing list.
As I was reading through, few basic doubts crept up.

Do we have to build a sugar app which is supported by chrome in order to
integrate the chrome window inside the sugar shell?
Or are we building a chrome web app which is supported in sugar shell?

Regarding the implementation of the same, which way will we be proceeding?
I meant, will we be following the implementation technique suggested by you
or the one suggested by Lionel?

I'm planning to start work on the proposal in a few days.
It would help a great deal if you could throw some light on these.

Regards,
Suraj



On Thu, Apr 11, 2013 at 11:11 PM, Daniel Narvaez wrote:

> On 11 April 2013 18:41, suraj ks  wrote:
>
>> It might have messed up the installation part.
>> I will check up on that.
>> But, i can spot the xi-artwork folder in node_modules directory.
>> And  where do i set the NODE_PATH?  In the node terminal?
>>
>
>
> It's an environment variable, honestly I have no idea of how you set one
> in windows. Pretty sure google can find it for you though :)
>
>
>
>> What i meant was the
>> $volo create helloworld ayopa/omega-examples
>> command was executed without any errors
>>
>>
> Oh ok, that's because there is no xi-artwork in there. It doesn't make
> sense though the second argument to volo create should be the repository of
> an activiity template (which omega-examples is not).
>
>
>> Yes, i will familiarize myself with the existing code and will try
>> creating some sample activities.
>> Hopefully i will reach that stage in the forthcoming days where i'll be
>> able to write my own UI controls.
>>
>
> Cool!
>
___
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)

[suraj ks]

It might have messed up the installation part.
I will check up on that.
But, i can spot the xi-artwork folder in node_modules directory.
And  where do i set the NODE_PATH?  In the node terminal?


What i meant was the
$volo create helloworld ayopa/omega-examples
command was executed without any errors

Yes, i will familiarize myself with the existing code and will try creating
some sample activities.
Hopefully i will reach that stage in the forthcoming days where i'll be
able to write my own UI controls.

And thanks for the wishes
I'm off to study. :)

Cheers!



On Thu, Apr 11, 2013 at 9:26 PM, Daniel Narvaez  wrote:

> On 11 April 2013 16:43, suraj ks  wrote:
>
>> Still showing the same error.
>> Please bear with me. This is the first time I'm working with node and
>> volo.
>>
>
> I'm not sure how you installed nodejs but you might need to set NODE_PATH
> to point to the node_modules dir where xi-artwork was installed. The error
> means the xi-artwork nodejs module was not found.
>
>
>> But the volo create seems to working fine with the omega-examples.
>> It was created without any hassles.
>>
>
> I'm not sure what you mean here. volo create setups a template activity in
> a new directory, it shouldn't matter where you run it.
>
>
>> I'm going through the chrome app page which you suggested.
>>
>> Do I have to just tweak the "omega-examples" code to make it run on
>> chrome?
>> Or do i have to start with creating manifest, background script ,etc
>> as mentioned here
>>  http://developer.chrome.com/trunk/apps/first_app.html
>>  ?
>>
>
> I was suggesting to tweak the omega-examples as a way to get familiar with
> the existing code. It's also a useful task because we will need to fix
> those at some point. But it's up to you really... When you figured out the
> "volo create" stuff you might also want to try to write an example activity
> yourself just to see how the current stuff works.
>
> The real task will be to write more UI controls, but you probably need to
> understand pretty well what is there already before starting with that.
>
>
> Good luck with your exam :)
>
___
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)

[suraj ks]

Still showing the same error.
Please bear with me. This is the first time I'm working with node and volo.

But the volo create seems to working fine with the omega-examples.
It was created without any hassles.

I'm going through the chrome app page which you suggested.

Do I have to just tweak the "omega-examples" code to make it run on chrome?
Or do i have to start with creating manifest, background script ,etc
as mentioned here
 http://developer.chrome.com/trunk/apps/first_app.html
 ?





P.S : I have an exam day after tomorrow. That's why my progress is slow.
It is my last exam. Once i'm done with it i'll be able to devote all my
attention towards Sugar.






On Thu, Apr 11, 2013 at 5:26 PM, Daniel Narvaez  wrote:

> Oh. You need to install the xi-artwork nodejs module.
>
> I think you cloned that git repo already so
>
> npm install -g path/to/xi-artwork
>
> Then "volo create..." should work.
>
> On 11 April 2013 11:37, suraj ks  wrote:
>
>> Hi,
>> I'm having trouble creating an activity using volo.
>> i cloned the modules which you mentioned to D:\pesit\
>>
>> i tried creating a sample like how to suggested.
>> But it shows the following error:
>>
>> D:\pesit>volo create helloAgain ayopa/xi-activity
>> Downloading:
>> https://nodeload.github.com/ayopa/xi-activity/legacy.zip/master
>> Malformed volofile: D:\pesit\helloAgain\volofile: Error: Cannot find
>> module 'xi-artwork/update-artwork'
>> onCreate did not succeed. You can try later by typing "volo onCreate"
>> inside the
>>  project that was just created, passing any arguments you passed to the
>> create call.
>> https://api.github.com/repos/ayopa/xi-activity/zipball/master used to
>> create helloAgain
>>
>>
>> Please help me out here.
>>
>> Regards,
>> Suraj
>>
>>
>>
>> On Thu, Apr 11, 2013 at 12:01 PM, suraj ks wrote:
>>
>>> Hey,
>>>
>>> I work on Ubuntu.
>>> A couple of days back it crashed due to some inexplicable reason. :(
>>> For the past several hours, I've been trying to reinstall it and  get
>>> started on the UI part.
>>> My attempts were futile(re-installing ubuntu).
>>>
>>> I'm afraid the only alternative available to me is to switch to windows.
>>> Hope you don't mind me working on windows.
>>>
>>> I'm getting started with setting up the tools needed to work on the UI
>>> right away(on windows).  :)
>>>
>>>
>>> Regards,
>>> Suraj
>>>
>>>
>>>
>>> On Wed, Apr 10, 2013 at 11:55 PM, Daniel Narvaez wrote:
>>>
>>>> On 10 April 2013 19:54, suraj ks  wrote:
>>>>
>>>>> Hi,
>>>>> Its cool :)
>>>>> Which are the sugar modules that I should download to start working on
>>>>> the UI?
>>>>>
>>>>
>>>> Which OS are you using?
>>>>
>>>> Anyway I'd suggest
>>>>
>>>> 1 Install nodejs
>>>>
>>>> http://nodejs.org/
>>>>
>>>> 2 Install volojs
>>>>
>>>> http://volojs.org/
>>>>
>>>> 3 Install chrome
>>>>
>>>> 4 Clone the xi modules
>>>>
>>>> https://github.com/ayopa/xi-graphics
>>>> https://github.com/ayopa/xi-artwork
>>>> https://github.com/ayopa/xi-activity
>>>>
>>>> 5 Create an activity. Something like
>>>>
>>>> volo create helloworld ayopa/xi-activity
>>>> volo add xi-graphics
>>>>
>>>> Try to install the web app in chrome. There is great documentation
>>>> about chrome web apps here:
>>>>
>>>> http://developer.chrome.com/trunk/apps/about_apps.html
>>>>
>>>> Note that the xi libraries has been tested only on b2g (firefox) so
>>>> far, you might need small modifications to make them work. Please submit
>>>> these changes as pull requests.
>>>>
>>>> 6 Give a try to the two examples activities we have
>>>>
>>>> https://github.com/ayopa/omega-examples
>>>>
>>>>
>>>> Once that's working you should be all setup. And you can discuss with
>>>> Manuel the next development steps.
>>>>
>>>> Feel free to ask for help on the mailing list for any problem you run
>>>> into. I wrote the above list without testing it, so it might not work out
>>>> of the box... If you post any corrections here, it's going to be useful to
>>>> everyone.
>>>>
>>>> Also, i found a "GSoC mailing list", which hardly had any content
>>>>> relating to GSoC.
>>>>> Should i proceed further with my discussions in the current mailing
>>>>> list(sugar-dev) or should i switch to the GSoC mailing list?
>>>>>
>>>>
>>>> I don't know what that list is about exactly but anything about
>>>> development should definitely stay here on sugar-devel.
>>>>
>>>
>>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> --
> Daniel Narvaez
>
___
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)

[suraj ks]

Hi,
I'm having trouble creating an activity using volo.
i cloned the modules which you mentioned to D:\pesit\

i tried creating a sample like how to suggested.
But it shows the following error:

D:\pesit>volo create helloAgain ayopa/xi-activity
Downloading: https://nodeload.github.com/ayopa/xi-activity/legacy.zip/master
Malformed volofile: D:\pesit\helloAgain\volofile: Error: Cannot find module
'xi-artwork/update-artwork'
onCreate did not succeed. You can try later by typing "volo onCreate"
inside the
 project that was just created, passing any arguments you passed to the
create call.
https://api.github.com/repos/ayopa/xi-activity/zipball/master used to
create helloAgain


Please help me out here.

Regards,
Suraj



On Thu, Apr 11, 2013 at 12:01 PM, suraj ks wrote:

> Hey,
>
> I work on Ubuntu.
> A couple of days back it crashed due to some inexplicable reason. :(
> For the past several hours, I've been trying to reinstall it and  get
> started on the UI part.
> My attempts were futile(re-installing ubuntu).
>
> I'm afraid the only alternative available to me is to switch to windows.
> Hope you don't mind me working on windows.
>
> I'm getting started with setting up the tools needed to work on the UI
> right away(on windows).  :)
>
>
> Regards,
> Suraj
>
>
>
> On Wed, Apr 10, 2013 at 11:55 PM, Daniel Narvaez wrote:
>
>> On 10 April 2013 19:54, suraj ks  wrote:
>>
>>> Hi,
>>> Its cool :)
>>> Which are the sugar modules that I should download to start working on
>>> the UI?
>>>
>>
>> Which OS are you using?
>>
>> Anyway I'd suggest
>>
>> 1 Install nodejs
>>
>> http://nodejs.org/
>>
>> 2 Install volojs
>>
>> http://volojs.org/
>>
>> 3 Install chrome
>>
>> 4 Clone the xi modules
>>
>> https://github.com/ayopa/xi-graphics
>> https://github.com/ayopa/xi-artwork
>> https://github.com/ayopa/xi-activity
>>
>> 5 Create an activity. Something like
>>
>> volo create helloworld ayopa/xi-activity
>> volo add xi-graphics
>>
>> Try to install the web app in chrome. There is great documentation about
>> chrome web apps here:
>>
>> http://developer.chrome.com/trunk/apps/about_apps.html
>>
>> Note that the xi libraries has been tested only on b2g (firefox) so far,
>> you might need small modifications to make them work. Please submit these
>> changes as pull requests.
>>
>> 6 Give a try to the two examples activities we have
>>
>> https://github.com/ayopa/omega-examples
>>
>>
>> Once that's working you should be all setup. And you can discuss with
>> Manuel the next development steps.
>>
>> Feel free to ask for help on the mailing list for any problem you run
>> into. I wrote the above list without testing it, so it might not work out
>> of the box... If you post any corrections here, it's going to be useful to
>> everyone.
>>
>> Also, i found a "GSoC mailing list", which hardly had any content
>>> relating to GSoC.
>>> Should i proceed further with my discussions in the current mailing
>>> list(sugar-dev) or should i switch to the GSoC mailing list?
>>>
>>
>> I don't know what that list is about exactly but anything about
>> development should definitely stay here on sugar-devel.
>>
>
>
___
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)

[suraj ks]

Hey,

I work on Ubuntu.
A couple of days back it crashed due to some inexplicable reason. :(
For the past several hours, I've been trying to reinstall it and  get
started on the UI part.
My attempts were futile(re-installing ubuntu).

I'm afraid the only alternative available to me is to switch to windows.
Hope you don't mind me working on windows.

I'm getting started with setting up the tools needed to work on the UI
right away(on windows).  :)


Regards,
Suraj



On Wed, Apr 10, 2013 at 11:55 PM, Daniel Narvaez wrote:

> On 10 April 2013 19:54, suraj ks  wrote:
>
>> Hi,
>> Its cool :)
>> Which are the sugar modules that I should download to start working on
>> the UI?
>>
>
> Which OS are you using?
>
> Anyway I'd suggest
>
> 1 Install nodejs
>
> http://nodejs.org/
>
> 2 Install volojs
>
> http://volojs.org/
>
> 3 Install chrome
>
> 4 Clone the xi modules
>
> https://github.com/ayopa/xi-graphics
> https://github.com/ayopa/xi-artwork
> https://github.com/ayopa/xi-activity
>
> 5 Create an activity. Something like
>
> volo create helloworld ayopa/xi-activity
> volo add xi-graphics
>
> Try to install the web app in chrome. There is great documentation about
> chrome web apps here:
>
> http://developer.chrome.com/trunk/apps/about_apps.html
>
> Note that the xi libraries has been tested only on b2g (firefox) so far,
> you might need small modifications to make them work. Please submit these
> changes as pull requests.
>
> 6 Give a try to the two examples activities we have
>
> https://github.com/ayopa/omega-examples
>
>
> Once that's working you should be all setup. And you can discuss with
> Manuel the next development steps.
>
> Feel free to ask for help on the mailing list for any problem you run
> into. I wrote the above list without testing it, so it might not work out
> of the box... If you post any corrections here, it's going to be useful to
> everyone.
>
> Also, i found a "GSoC mailing list", which hardly had any content relating
>> to GSoC.
>> Should i proceed further with my discussions in the current mailing
>> list(sugar-dev) or should i switch to the GSoC mailing list?
>>
>
> I don't know what that list is about exactly but anything about
> development should definitely stay here on sugar-devel.
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC 13

[suraj ks]

Hi,
Its cool :)
Which are the sugar modules that I should download to start working on the
UI?

Also, i found a "GSoC mailing list", which hardly had any content relating
to GSoC.
Should i proceed further with my discussions in the current mailing
list(sugar-dev) or should i switch to the GSoC mailing list?

Regards,
Suraj


On Wed, Apr 10, 2013 at 9:31 PM, Daniel Narvaez  wrote:

> On 10 April 2013 17:48, suraj ks  wrote:
>
>> Hi,
>>
>> Awesome.
>> I will go through the mailing list archives.
>>
>> But I'm getting confused here.
>> Is the UI part which Manuel was talking about a part of the above idea?
>> Or a different one?
>>
>
> Yup, it's 2 in my list. Sorry about confusing you by phrasing it
> differently :)
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC 13

[suraj ks]

Hi,

Awesome.
I will go through the mailing list archives.

But I'm getting confused here.
Is the UI part which Manuel was talking about a part of the above idea?
Or a different one?



On Wed, Apr 10, 2013 at 9:01 PM, Daniel Narvaez  wrote:

> On 10 April 2013 17:17, suraj ks  wrote:
>
>> Hey Manuel,
>>
>> Oh yes, i do like working with CSS.
>> I'd love to get started now as soon as possible.
>> But, will it involve just working with the "look and feel"?
>>
>> When i checked the idea page, i found "Sugar Framework for writing
>> activity in full HTML5"
>> involved a framework to  write Sugar activities in full HTML5/JavaScript.
>>
>
> At very high level I think it will involve the following
>
> 1 Integrate one of the existing web application frameworks inside Sugar.
> Basically being able to run a web activity inside the Sugar shell,
> integrating with the window manager and the launcher.
> 2 Native-like UI implemented with HTML5 and CSS.
> 3 Javascript libraries providing access to Sugar collaboration and
> datastore.
>
> We did quite a bit of research and experimentation with these already and
> we have a pretty solid idea of how 2 should be done, so on that one I think
> it's worth to start coding.
>
> But of course we will have to get to the other points too.
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] GSoC 13

[suraj ks]

Hey Manuel,

Oh yes, i do like working with CSS.
I'd love to get started now as soon as possible.
But, will it involve just working with the "look and feel"?

When i checked the idea page, i found "Sugar Framework for writing activity
in full HTML5"
involved a framework to  write Sugar activities in full HTML5/JavaScript.

Regards,
Suraj.




On Wed, Apr 10, 2013 at 8:26 PM, Manuel Quiñones  wrote:

> Hi Suraj!
>
> If you go for the Sugar look&feel item, I can mentor you.  Do you like
> working with CSS?  This work can be started right now.
>
> Cheers,
>
> 2013/4/10 suraj ks :
> > Hi,
> >
> > I'm Suraj, a 3rd year Computer Science student from PESIT, India.
> > Firstly, my hearty congratulations to the organstion for getting selected
> > into GSOC 13.
> >
> > I'm looking forward to participate in GSOC 13 through this organisation.
> > I have a pretty decent hold on web development tools and
> > concepts(css,php,js,html)
> > I've also developed websites for my college.
> >
> >
> > I went through the idea list and some interesting ones.
> >
> > The one which caught my eye was
> >
> > Sugar Framework for writing activity in full HTML5.
> >
> > I dont know where to get started.
> > It would be very helpful if i could get in touch with the respective
> mentor
> > and start working on the proposal asap.
> > Please guide me.
> >
> > Thanking you,
> > Suraj
> >
> >
> >
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >
>
>
>
> --
> .. manuq ..
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] GSoC 13

[suraj ks]

Hi,

I'm Suraj, a 3rd year Computer Science student from PESIT, India.
Firstly, my hearty congratulations to the organstion for getting selected
into GSOC 13.

I'm looking forward to participate in GSOC 13 through this organisation.
I have a pretty decent hold on web development tools and
concepts(css,php,js,html)
I've also developed websites for my college.


I went through the idea list and some interesting ones.

The one which caught my eye was
Sugar Framework for writing activity in full HTML5.
I dont know where to get started.
It would be very helpful if i could get in touch with the respective mentor
and start working on the proposal asap.
Please guide me.

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