Development Team/Project Ideas - Revision history

Quozl at 00:38, 23 December 2016

2016-12-23T00:38:45Z

← Older revision		Revision as of 20:38, 22 December 2016
Line 199:		Line 199:
	* Make a WYSIWIG GUI editor, like Glade. Note that GTK natively supports loading Glade-format interface definitions, although there would be some work involved making the Sugar interface elements available through this method.		* Make a WYSIWIG GUI editor, like Glade. Note that GTK natively supports loading Glade-format interface definitions, although there would be some work involved making the Sugar interface elements available through this method.
	* Integrate Sugarbot and auto-testing facilities.		* Integrate Sugarbot and auto-testing facilities.
	* Integrate a debugger, based on pdb or other.		* Integrate a debugger, based on pdb or other (see also [[Development Team/Debugging]]).

	*Priority for Sugar: Medium-High		*Priority for Sugar: Medium-High

EduardoR: walk-around solution: XO QR Reader on-line

2011-08-29T23:00:45Z

walk-around solution: XO QR Reader on-line

← Older revision		Revision as of 19:00, 29 August 2011
Line 407:		Line 407:
	==== Visual geometric (e.g. linear [http://en.wikipedia.org/wiki/Bar_code bar], [http://en.wikipedia.org/wiki/QR_code QR](matrix)) code recognition ====		==== Visual geometric (e.g. linear [http://en.wikipedia.org/wiki/Bar_code bar], [http://en.wikipedia.org/wiki/QR_code QR](matrix)) code recognition ====
	Robust, poor-man's alternative to OCR. These codes are used to track physical items, point at their use manuals, etc. Input devices: (for OLPC) integral camera; one-dimensional scanner like [http://en.wikipedia.org/wiki/CueCat CueCat ]. Some software already exists: [http://qrcode.sourceforge.jp/ Open Source QR Code Library]. (All camera cellphones in Japan bundle this function.)		Robust, poor-man's alternative to OCR. These codes are used to track physical items, point at their use manuals, etc. Input devices: (for OLPC) integral camera; one-dimensional scanner like [http://en.wikipedia.org/wiki/CueCat CueCat ]. Some software already exists: [http://qrcode.sourceforge.jp/ Open Source QR Code Library]. (All camera cellphones in Japan bundle this function.)

			A "walk-around" solution: [http://mnav.gub.uy/q.php XO QR Reader on-line (Spanish)] ZBar based in Ubuntu server.

	==== Sugar adaption for the Nasa ====		==== Sugar adaption for the Nasa ====

FGrose at 00:07, 11 March 2010

2010-03-11T00:07:33Z

← Older revision		Revision as of 20:07, 10 March 2010
Line 1:		Line 1:
	<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>		<noinclude></noinclude>
	==Introduction==		==Introduction==
	This page contains a list of project ideas. For now, the focus is on giving [[GSoC]] students an idea of the kind of thing we're looking for. Summer of Code applicants should also visit '''[[Summer of Code/Resources]]'''.		This page contains a list of project ideas. For now, the focus is on giving [[GSoC]] students an idea of the kind of thing we're looking for. Summer of Code applicants should also visit '''[[Summer of Code/Resources]]'''.
Line 14:		Line 14:
	To get in, you will need to design your project and find a mentor. On irc (#sugar on freenode) or the sugar-devel mailing list, you can briefly introduce yourself, state your interest, and ask relevant and specific questions about the state of the existing code. You should also do your own research for other open-source code that might help you. Get a [[Development Team#Development_systems\|development environment]] installed. We definitely appreciate it if you can show your readiness to help out - either joining [[BugSquad\|bug squad]] and [[BugSquad/Meetings\|helping]] to [[BugSquad/Triage Guide\|triage]], or actually helping fix some small [http://tinyurl.com/ctfkjl bug] (we've categorized [http://tinyurl.com/sugar-love some bugs as "sugar-love"], which means, not that they are easy to fix, but that they are good for beginners because they don't require much expert knowledge).		To get in, you will need to design your project and find a mentor. On irc (#sugar on freenode) or the sugar-devel mailing list, you can briefly introduce yourself, state your interest, and ask relevant and specific questions about the state of the existing code. You should also do your own research for other open-source code that might help you. Get a [[Development Team#Development_systems\|development environment]] installed. We definitely appreciate it if you can show your readiness to help out - either joining [[BugSquad\|bug squad]] and [[BugSquad/Meetings\|helping]] to [[BugSquad/Triage Guide\|triage]], or actually helping fix some small [http://tinyurl.com/ctfkjl bug] (we've categorized [http://tinyurl.com/sugar-love some bugs as "sugar-love"], which means, not that they are easy to fix, but that they are good for beginners because they don't require much expert knowledge).

	When you're ready, figure out a very basic, preliminary design (where does your new UI fit in? what about the code - what talks to what?) and post that to the [[Sugar_Labs/~~Contacts~~#Developer_Lists\|mailing list]], asking if anybody would be willing to mentor you. You will almost certainly get some response, but you may not find a prospective mentor right away. That's OK. If your idea is really not a good fit for us, we will let you know; otherwise, remember that several mentors are holding back for now to see which projects show the most feasibility, clarity, and creativity in their design ideas. Persistence should pay off.		When you're ready, figure out a very basic, preliminary design (where does your new UI fit in? what about the code - what talks to what?) and post that to the [[Sugar_Labs/Communication channels#Developer_Lists\|mailing list]], asking if anybody would be willing to mentor you. You will almost certainly get some response, but you may not find a prospective mentor right away. That's OK. If your idea is really not a good fit for us, we will let you know; otherwise, remember that several mentors are holding back for now to see which projects show the most feasibility, clarity, and creativity in their design ideas. Persistence should pay off.

	'''Want to apply with an idea not on this list?''' That's fine. Read the thread linked above about priorities - and remember, our highest priority is for you to have a successful GSoC, and we hope that you will want to continue to contribute afterwards. Do the steps above, paying particular attention to getting some community members' opinions on whether your idea would be valuable. The [[Sugar_Labs/~~Contacts~~#General_List\|"iaep" mailing list]] may be the best venue for this. We will not all agree with each other about how important your idea is - that's normal - but our feedback will almost certainly help you refine your idea.		'''Want to apply with an idea not on this list?''' That's fine. Read the thread linked above about priorities - and remember, our highest priority is for you to have a successful GSoC, and we hope that you will want to continue to contribute afterwards. Do the steps above, paying particular attention to getting some community members' opinions on whether your idea would be valuable. The [[Sugar_Labs/Communication channels#General_List\|"iaep" mailing list]] may be the best venue for this. We will not all agree with each other about how important your idea is - that's normal - but our feedback will almost certainly help you refine your idea.

	<div style="float:right;">		<div style="float:right;">

Patrol: moved Walter is a wanker 12/Project Ideas to Development Team/Project Ideas over redirect: revert

2010-02-24T01:33:16Z

moved Walter is a wanker 12/Project Ideas to Development Team/Project Ideas over redirect: revert

← Older revision	Revision as of 21:33, 23 February 2010
(No difference)

Page move vandal: moved Development Team/Project Ideas to Walter is a wanker 12/Project Ideas: Walter is a wanker

2010-02-24T00:21:34Z

moved Development Team/Project Ideas to Walter is a wanker 12/Project Ideas: Walter is a wanker

← Older revision	Revision as of 20:21, 23 February 2010
(No difference)

Patrol: moved Anal bleaching 15/Project Ideas to Development Team/Project Ideas over redirect: revert

2010-02-21T22:42:07Z

moved Anal bleaching 15/Project Ideas to Development Team/Project Ideas over redirect: revert

← Older revision	Revision as of 18:42, 21 February 2010
(No difference)

Anal bleaching: moved Development Team/Project Ideas to Anal bleaching 15/Project Ideas: Anal bleaching

2010-02-21T22:22:38Z

moved Development Team/Project Ideas to Anal bleaching 15/Project Ideas: Anal bleaching

← Older revision	Revision as of 18:22, 21 February 2010
(No difference)

Docdtv: oops on screen grabbing

2010-02-03T09:36:38Z

oops on screen grabbing

← Older revision		Revision as of 05:36, 3 February 2010
Line 123:		Line 123:
	:comments		:comments

	:Suggestion: To start, perhaps it might be simplest just to create a screen grab utility. The utility would not even support a printer, just queue grabs and later simply hand them off to a school print server. The grabs could be coded using any simple well-supported image file format. (One might also read [http://wiki.laptop.org/go/Printing_Culture Printing_Culture].)		:Suggestion: See [http://wiki.laptop.org/go/Printing_Culture Printing_Culture]. Oops, note screen-grabbing already exists -

	::There is already screen-grab support built into Sugar. Alt-1 puts a copy of the current screen into the Journal as a PNG file. --[[User:Walter\|Walter]] 13:03, 31 January 2010 (UTC)		::There is already screen-grab support built into Sugar. Alt-1 puts a copy of the current screen into the Journal as a PNG file. --[[User:Walter\|Walter]] 13:03, 31 January 2010 (UTC)

Walter: /* Print Support */

2010-01-31T13:03:12Z

Print Support

← Older revision		Revision as of 09:03, 31 January 2010
Line 121:		Line 121:
	*Skills needed: Python programming, API design, some communications		*Skills needed: Python programming, API design, some communications

	comments		:comments

	Suggestion: To start, perhaps it might be simplest just to create a		:Suggestion: To start, perhaps it might be simplest just to create a screen grab utility. The utility would not even support a printer, just queue grabs and later simply hand them off to a school print server. The grabs could be coded using any simple well-supported image file format. (One might also read [http://wiki.laptop.org/go/Printing_Culture Printing_Culture].)
	screen grab utility. The utility would not even support a printer,
	just queue grabs and later simply hand them off to a school print		::There is already screen-grab support built into Sugar. Alt-1 puts a copy of the current screen into the Journal as a PNG file. --[[User:Walter\|Walter]] 13:03, 31 January 2010 (UTC)
	server. The grabs could be coded using any simple well-supported
	image file format. (One might also read [http://wiki.laptop.org/go/Printing_Culture Printing_Culture].)

	==== Sugar Toolbar submenu support ====		==== Sugar Toolbar submenu support ====

Docdtv: Add visual geometric code reading

2010-01-26T18:07:34Z

Add visual geometric code reading

← Older revision		Revision as of 14:07, 26 January 2010
Line 406:		Line 406:

	== Brainstorm / unexplained ideas ==		== Brainstorm / unexplained ideas ==

			==== Visual geometric (e.g. linear [http://en.wikipedia.org/wiki/Bar_code bar], [http://en.wikipedia.org/wiki/QR_code QR](matrix)) code recognition ====
			Robust, poor-man's alternative to OCR. These codes are used to track physical items, point at their use manuals, etc. Input devices: (for OLPC) integral camera; one-dimensional scanner like [http://en.wikipedia.org/wiki/CueCat CueCat ]. Some software already exists: [http://qrcode.sourceforge.jp/ Open Source QR Code Library]. (All camera cellphones in Japan bundle this function.)

	==== Sugar adaption for the Nasa ====		==== Sugar adaption for the Nasa ====