[Sugar-devel] [IAEP] activities.sugarlabs.org

[Wade Brainerd]

Thanks for the link to the patch.  I have cloned your a.m.o Git
repository onto my webserver and made a little progress towards
getting a test installation working.

Just give me a task list when you're back home and I'll start on it
Monday night after work.

Cheers,
Wade

On Sun, Nov 23, 2008 at 1:03 PM, David Farning <dfarning at sugarlabs.org> wrote:
> Hey Wade,
> It has been a long time since I have looked at the AMO code.  The
> first step is to finish splitting up and updating the Addon type code.
>  There is an open bug at
> https://bugzilla.mozilla.org/show_bug.cgi?id=377513 .
>
> Originally, the AMO designers intended that Addon types be dynamic.
> During initial deployment they realized the having Addon types be
> dynamic caused a large number of database lookups.  As a result,  they
> started rewriting to code such that Addons types are static.  In their
> hast, the programmers left the bits of code relevant to types of
> Addons spread across the code base.
>
> This patch, starts moving the static Addon types to a central location
> so that we can easily add an .xo type.
>
> I'll be getting back home tomarrow and have access to desktop machine
> where I started the amo work.
>
> David
>
> On Sun, Nov 23, 2008 at 8:26 PM, Wade Brainerd <wadetb at gmail.com> wrote:
>> Hey David,
>>
>> I'm cloning git://src.develer.com/users/dfarning/a.m.o.git
>>
>> Does this contain your patch work thus far, and can you get me started
>> on what's left to do?
>>
>> I'll be able to work on this a little while tonight, and then for a
>> significant amount of time Monday night.
>>
>> Thanks,
>> Wade
>>
>> On Mon, Jun 23, 2008 at 11:16 AM, David Farning <dfarning at sugarlabs.org> wrote:
>>> On Mon, 2008-06-23 at 11:06 -0400, Greg Dekoenigsberg wrote:
>>>> >
>>>> > All of this happens through a nice set of web interfaces.
>>>>
>>>> There's also localization flow.  How well it works, I'm unsure.
>>>
>>> The dynamic strings are localized via the web interface and the static
>>> strings are localized via mozilla's mo->po translation mechanism.
>>>
>>>> I got a bit farther in my efforts, but unfortunately, my work bitrotted
>>>> over the last 18 months since I first made the effort, and the AMO
>>>> codebase has changed quite a bit.
>>>
>>> I have used amo on my local server to install activities on my niece's
>>> XO and the sugar install on my laptop.
>>>
>>>> There's also a large question that needs to be answered: will the
>>>> necessary changes be carried upstream, or will they constitute a fork?
>>>
>>> I have started submitting a series of patches upstream to a.m.o to help
>>> modularized how amo handles applications and addontypes.  Every thing
>>> from addons up can be used directly from the upstream a.m.o.  The three
>>> area that will require work are:
>>> 1.  Look and feel - this is basically applying the sugarlabs style
>>> sheets.
>>> 2. Applications - When amo made the upgrade to remona the intended
>>> Applications to be handled dynamically.  Since then application data has
>>> been hard coded as constants across the code base.
>>> 3.  Addontypes - amo can handle several addontypes such as extension,
>>> plugins, and and dictionaries.  As with applications they were intended
>>> to be handled dynamically.  Currently, they are handled using a
>>> combination of static code and dynamic db lookups.
>>>
>>> One of my main goals in not to fork amo.  There is really no way we
>>> could keep the code fresh with our current man power.  Instead I am
>>> hoping to push some patches that modularize how amo handles applications
>>> and addontypes upstream.  Then we can just plop in our own application
>>> and addontype code.
>>>
>>>> Are you working with anyone at AMO on this problem?  I'm guessing you know
>>>> some people, but if you don't, I can comb through my notes and maybe put
>>>> you in touch with some other people.
>>>
>>> I have been slowly introducing myself via irc and bugzilla.  Hopefully,
>>> they will find the patches useful which will help build sugar lab's
>>> reputation as contributors.  The amo staff is pretty busy right now
>>> cleaning up after the 3.0 release:)
>>>
>>>> Well done on tackling this problem, David, and good luck.  Maybe I'll jump
>>>> in and help at some point... or maybe I'll just cheer wildly from the
>>>> sidelines.  :)
>>>
>>> I would love the help. I'll be putting the code on
>>> https://www.develer.com/gitweb/pub?p=users/dfarning/w.s.o.git;a=summary
>>> as soon as I figure out how to push the necessary branches.  amo is
>>> stored in svn so there is a git-svn level which I have not used before.
>>>
>>> thanks
>>> Dfarning
>>>
>>> _______________________________________________
>>> Its.an.education.project mailing list
>>> Its.an.education.project at lists.lo-res.org
>>> http://lists.lo-res.org/mailman/listinfo/its.an.education.project
>>>
>>
>