Written by deltrem the 9 Jun 10 at 01:33.

In Synaptic, for each package, I want a Develop button linked to a page with.
- the names of the programming languages used
- a link to the repository
- form mail contact with the developers

In Synaptic, for each package, I want a Develop button linked to a page with. - the names of the programming languages used - a link to the repository - form mail contact with the developers

Written by Eldmannen the 29 Mar 09 at 05:44.

I've noticed that some code contain almost no comments at all (example Compiz).
Which makes it difficult to understand what the functions and sometimes variables are used for. Sometimes functions call other functions which call other functions, which makes it a bit of a maze to grasp.

I think that developers should be encouraged to comment their source code. It can also be a good way for novices to help out, who understand the code, but may not be confident in their skills to write code.

I've noticed that some code contain almost no comments at all (example Compiz). Which makes it difficult to understand what the functions and sometimes variables are used for. Sometimes functions call other functions which call other functions, which makes it a bit of a maze to grasp. I think that developers should be encouraged to comment their source code. It can also be a good way for novices to help out, who understand the code, but may not be confident in their skills to write code.

Written by Eldmannen the 29 Mar 09 at 05:47.

Get all the source code for all software in the Ubuntu repository indexed by Google Code Search.

This makes it easier to search through source code, packages, etc, and also re-use code.

Get all the source code for all software in the Ubuntu repository indexed by <a href="http://www.google.com/codesearch">Google Code Search</a>. This makes it easier to search through source code, packages, etc, and also re-use code.

Written by Eldmannen the 29 Mar 09 at 05:53.

Use a documentation generator (such as Doxygen, HeaderDoc, Javadoc, etc) to automatically generate documentation for all software in the repository.

Use a documentation generator (such as <a href="http://en.wikipedia.org/wiki/Doxygen">Doxygen</a>, <a href="http://en.wikipedia.org/wiki/HeaderDoc">HeaderDoc</a>, <a href="http://en.wikipedia.org/wiki/Javadoc">Javadoc</a>, etc) to automatically generate documentation for all software in the repository.

Written by James_Lochhead the 30 Mar 09 at 15:24.

I think developers would be greatly encouraged to comment/explain there code in some way if there was a standard system for doing so.

The system would obviously have to have tiers as not every kind of explanation would be suitable for a given package.

Developers could then be encouraged to use the system.

I think developers would be greatly encouraged to comment/explain there code in some way if there was a standard system for doing so. The system would obviously have to have tiers as not every kind of explanation would be suitable for a given package. Developers could then be encouraged to use the system.

Written by tchalvakspam the 9 Apr 09 at 22:14.

The best way to learn about the most important parts of an application are to watch the changes that other developers make. Having not just the dead source code but also the very development history itself is key to a greater understanding of the source code itself, and is a natural workflow that adds to understanding on top of in-code-comment documentation.

For an example of the power of distributed source control, (git in this case), check out any popular source code repository on github.com.

The best way to learn about the most important parts of an application are to watch the changes that other developers make. Having not just the dead source code but also the very development history itself is key to a greater understanding of the source code itself, and is a natural workflow that adds to understanding on top of in-code-comment documentation. For an example of the power of distributed source control, (git in this case), check out any popular source code repository on github.com.

Written by rmyeid the 12 Dec 08 at 00:00.

Ubuntu Brainstorm was updated in January 2009. Since the idea #16437 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #16437 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by Endolith the 15 Apr 09 at 14:26.

When you open a file in a certain language in Gedit, it should have a very unobtrusive thing show up, that indicates "there are specialized plugins for this language, do you want to look through them and install any?"

Maybe a drop-down notification like it shows when you open a file it can't understand.

Maybe just an icon that appears in the toolbar?

Maybe a libnotify OSD thing would be better.

When you open a file in a certain language in Gedit, it should have a very unobtrusive thing show up, that indicates "there are specialized plugins for this language, do you want to look through them and install any?" Maybe a drop-down notification like it shows when you open a file it can't understand. Maybe just an icon that appears in the toolbar? Maybe a libnotify OSD thing would be better.

Written by hijstr the 19 Jan 09 at 02:38.

For anyone who uses Photoshop, they may have used the tag feature, where you can attach a pop up text box to a region of the image. This is the idea I have in mind (albeit in complete reverse).
The user could attach images to comments in the code. Every image saved would appear in the code as a small icon, and when clicked, expands into an image.
The image could be created on the fly by a pop-up drawing box, so other programs would not need to interact(alternatively, the user could opt to embed an image that is already on the disk). As drawing with a mouse is notoriously difficult, templates could be provide (like in the program Dia) for arrows, boxes, and other UML-like images.
The real consideration is how to embed these images, would the be embedded into the actual source file, would you need to create a completely new filetype, would the images accompany the source code - leaving the implementation of the idea completely down to the IDE? I don't know, but I think as a whole it would be a nice feature to look into

For anyone who uses Photoshop, they may have used the tag feature, where you can attach a pop up text box to a region of the image. This is the idea I have in mind (albeit in complete reverse). The user could attach images to comments in the code. Every image saved would appear in the code as a small icon, and when clicked, expands into an image. The image could be created on the fly by a pop-up drawing box, so other programs would not need to interact(alternatively, the user could opt to embed an image that is already on the disk). As drawing with a mouse is notoriously difficult, templates could be provide (like in the program Dia) for arrows, boxes, and other UML-like images. The real consideration is how to embed these images, would the be embedded into the actual source file, would you need to create a completely new filetype, would the images accompany the source code - leaving the implementation of the idea completely down to the IDE? I don't know, but I think as a whole it would be a nice feature to look into