507499 - adding python-hulahop and/org pyjamas-desktop

Status: RESOLVED WONTFIX

(www.mozilla.org :: Pages & Content, enhancement)

Description

[lkcl]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.14) Gecko/20080404 Iceweasel/2.0.0.14 (Debian-2.0.0.14-2)
Build Identifier: 

i've added these two here: https://developer.mozilla.org/en/XULRunner_Hall_of_Fame

but would like to suggest that pyjamas-desktop be added to the mozilla-based projects page.

the pyjamas project actually turns web engine technology into easy-to-use desktop widget technology (similar to pyqt4, python-wxWidgets and pygtk2), with the distinct advantage that HTML, CSS, NPAPI plugins etc. all are guaranteed to be standards-compliant and ... work!

writing new widgets is a simple matter of manipulating the DOM model (in python instead of javascript), which the pyjamas API helps you to do by providing base widget classes and plenty of existing examples.



Reproducible: Always

Comment 1

[David Boswell]

I've added these two projects to the List of Mozilla Based Applications page on MDC.

https://developer.mozilla.org/En/List_of_Mozilla-Based_Applications

The Mozilla-based Applications page is a subset of that other list.  I arbitrarily pick apps from there -- largely based on which apps have a pretty logo.  I didn't see a logo for either of these two, but maybe I missed them?

Comment 2

[lkcl]

(In reply to comment #1)
> I've added these two projects to the List of Mozilla Based Applications page on
> MDC.
> 
> https://developer.mozilla.org/En/List_of_Mozilla-Based_Applications
 
 cool.

> The Mozilla-based Applications page is a subset of that other list.  I
> arbitrarily pick apps from there -- largely based on which apps have a pretty
> logo. 

 ha ha :)

>  I didn't see a logo for either of these two, but maybe I missed them?

 i've been meaning to create one for pyjamas: i have a design in mind.

 l.

Comment 3

[lkcl]

http://git.sugarlabs.org/projects/browse/repos/mainline/blobs/raw/54be350982755e42c702f6e554cd59358e3c3fe6/activity/activity-web.svg

Comment 4

[lkcl]

http://pyjs.org/pyjamas.svg
http://pyjs.org/pyjamas.128x128.png
http://pyjs.org/pyjamas.64x64.png

Comment 5

[David Boswell]

Could you send me one that is 50px wide?  Thanks.

Comment 6

[Gordon P. Hemsley [:GPHemsley]]

Is this still desired?

Comment 7

[Naveen N]

I would like to work on this bug. I am new to Opensource. I'd love to learn more about this. I would like to know what the next step is, for working on this bug ?

Comment 8

[lkcl]

hi naveen, great to hear that you're interested in this, *but*, unfortunately i must describe the reality of working with mozilla foundation code.

the core issue is that the mozilla team have removed absolutely critical functions and header files from xulrunner, and they have also chosen a path for XPCOM that is ill-considered, focussed on short-term immediate solving of javascript-javascript-javascript problems and no other, the end result of which will be that they will only get themselves into deeper trouble from not having properly thought things through.

by not solving certain key strategic technical issues they have been causing third party developers (java and c++ ones) *massive* problems since the very beginning when XPCOM was first created, and the "fix" that they added completely violates common sense as well as not actually fixing the problem.

in short the mozilla team have lost their way and are sadly not listening or supporting anything beyond the immediate short-term goal of creating yet more firefox releases as fast as they possibly can.  i have pointed out that this is in direct violation of the mozilla foundation's charter but this was also ignored.

now, what you _can_ do is to download the versions of the xulrunner engine that have been compiled and maintained by ActiveState (for their editor, komodo).  the last time i checked, they were using xulrunner 7.0

xulrunner 7.0 was the last working stable version that supported the key strategic APIs needed, in a pre-bundled (pre-compiled) set of easily-available packages.

i did successfully compile up xulrunner 9.0 a couple of years back (with some minor modifications). xulrunner 10 was where the mozilla team completely lost the plot.

the only alternative is to begin and maintain a fork of the entire mozilla xulrunner codebase, fixing the problems that they have introduced, re-instating the key strategic code that they have removed, and then maintaining all the security patches needed on an ongoing basis.

in other words please be under no illusion that this is a huge commitment.

the incredible irony is that pyjamas=desktop running under the proprietary Internet Explorer Trident engine (MSHTML.DLL) works perfectly and will *continue* to work perfectly for decades to come, thanks to a committment by Microsoft to always provide backwards-compatibility via the COM interface that pyjamas-desktop uses.

no software libre project i know of can provide such a guaranteed committment, because no software libre project in existence provides an equivalent of COM.

Comment 9

[Naveen N]

lkcl: so i guess that i won't be able to handle this, being a beginner, right..? I think i will have to go first-bug hunting again.

Comment 10

[David Boswell]

(In reply to Naveen N from comment #7)
> I would like to work on this bug. I am new to Opensource. I'd love to learn
> more about this. I would like to know what the next step is, for working on
> this bug ?

Naveen, thanks for your interest in contributing to Mozilla.  This might not be a great first bug, but I would encourage you to look for other good webdev bugs on the page at:

https://wiki.mozilla.org/Webdev/GetInvolved

You can also use the Bugsahoy tool to look for other bugs that meet your interests at:

http://www.joshmatthews.net/bugsahoy/

Comment 11

[lkcl]

(In reply to Naveen N from comment #9)
> lkcl: so i guess that i won't be able to handle this, being a beginner,
> right..? I think i will have to go first-bug hunting again.

mmm... i don't want to say "no", as it depends on your level
of ambition and confidence, as well as the committment that
you are willing to put in.

that having been said there are some specific areas
that would be of enormous benefit to the mozilla foundation and
expand the reach of the entire mozilla codebase to not just web
browsers but the entire software libre community as a whole
[david i am talking about splitting out XPCOM as a separate
project and then adding in co-classes as they should have
been added back when XPCOM was first designed as a copy of
Microsoft COM]

however to be actually useful that would need the support of
the mozilla foundation and the developer teams, as any
middleware (which is what XPCOM is) is useless unless it is
actually *in* the middle of some active project!

basically, whatever you choose to do, what many people do
not realise when contributing to software libre projects is
that you need the "approval" of one or more people for what
you want to contribute... *or* you must decide to commit
to forking the *entire* code-base *and* maintaining it.

it is up to you: good luck in whatever you choose.

Comment 12

[Alessandro]

(In reply to David Boswell from comment #10)
> (In reply to Naveen N from comment #7)
> > I would like to work on this bug. I am new to Opensource. I'd love to learn
> > more about this. I would like to know what the next step is, for working on
> > this bug ?
> 
> Naveen, thanks for your interest in contributing to Mozilla.  This might not
> be a great first bug, but I would encourage you to look for other good
> webdev bugs on the page at:
> 
> https://wiki.mozilla.org/Webdev/GetInvolved
> 
> You can also use the Bugsahoy tool to look for other bugs that meet your
> interests at:
> 
> http://www.joshmatthews.net/bugsahoy/

This seems like a simple task to tackle just to get started, could I get this if Naveen is not working on this anymore?

If I'm correct it would be just a static change that requires a couple of logos and descriptions?

Comment 13

[Kohei Yoshino [:kohei]]

This page still exists but is orphaned, and XULRunner is dead. Closing as WONTFIX.