== Integration of GHNS for GIMP ==
Though you can add more brushes, patterns, gradients can be added,
Most users, not even pros usually add them off the internet. This is
so as there is no architecture to quicky share/add from a centralized
repository. This seriously limits sharing of resources among the
users.
GetHotNewStuff (GHNS) could probably help out here.
On 3/8/08, Joao S. O. Bueno <[EMAIL PROTECTED]> wrote:
> Hi -
>
> here are the ideas listed again. I had trimmed down the previous list,
> as there are things that simply do not sound attractive enough for
> anyone to pick.
>
> Ideas for Gimp-python and the UF-Raw plug-in have been added.
> And we are still lacking mentors for pretty much everything else. :-)
>
> Also, there is still a little time for adding some more ideas, or try
> to focus some more.
>
> Regards,
> js
> -><-
>
> [http://wiki.gimp.org/gimp/SummerOfCode2008ideas]
>
> = GSoC2008 Project Ideas =
>
> ''
> Please note that, although you are welcome to look at what is here,
> this
> is a workspace for mentors to write down and modify their ideas, and
> suggestions here should not be taken as necessarily viable projects
> until they have been finalized. Also, the fact that something appears
> here does not necessarily mean that anybody has volunteered to mentor
> it.''
>
> Note to people who add stuff here: Please try to add information about
> a proposal's overall complexity and experience that could be
> helpful. E.G. experience with GTK+, image manipulation algorithms,
> web application development, ...
>
>
> == Tagging of GIMP resources ==
>
> Currently resources such as brushes, gradients etc are shown to the
> user in an unstructured way, only sorted alphabetically. This greatly
> limits the number of items a user can deal with.
>
> People love to make collections of things and think of them by names
> for these collections, like "sprinf flower brushes" or "fancy fonts".
> However, one resource can belong to more than one set, and there can
> be sets which are determined by other means than the content, maybe
> even without the user having to do anything manually -
> think "Favorites", "Most recently used" and "Most frequently used".
> It has been suggested that this should not be a finite set of
> categories, bug rather done by assigning tags.
>
> The tasks in this project include:
>
> * adding a way for gimp resources to be tagged
> * decide which types of resources (i.e. which types of gimp objects)
> should be tagged
> * find a nice way for users to manage tags (add them, remove them)
> * present tags in the UI (i.e. how do you show them in the brush
> list, font list, ...?)
> * think about how tags can assigned to resources (or resources to
> tags)
>
>
> == On-canvas text editing ==
>
> Right now, the text tool opens a dialog window where the text has to
> be put, thereby creating a new text layer. Nearly every other option
> of the text tool - font, font size, color, line height, ... - is
> available in the text tool options dialog, so it would be nice to get
> rid of this dialog as well. There have been feature requests about
> being able to edit text directly on the image, like for example
> Inkscape does it.
>
> It may be that getting to the point where editing text on the image
> canvas is possible isn't that much of work, actually. But this is
> where the interesting challenges do begin: eventually, we do also
> want multiple styles in one text layer. This is not so straight
> forward anymore if your enter text in the image. Not present right
> now, so not having it isn't exactly a showstopper, but making it hard
> to ever get there is.
>
> And you will have to consider support for GTK+ input methods. They may
> be used to enter characters from languages (or, more precisely,
> scripts) beyond the simple Western scripts which define how our
> common keyboards are layed out. This is supported right now in any
> GTK+ text entry, not having it for on-canvas editing would be a
> regression.
>
> Tasks for this project include:
>
> * port the text core to PangoCairo
> * get on-convas text editing implemented
> * figure out if we do still need a text entry dialog (even Inkscape
> still has it in the properties of the text object)
> * make sure that GTK+ input methods work this this new approach
> * think about making it possible or not making it impossible to style
> the text while editing it this way
>
>
> == GIMP Python ==
>
> mentors: Yosh or João
>
> With version 2.4, python becomes the preferred method
> of scripting plug-ins for GIMP. Python is an universal multipurpose
> cross-platform
> language, adopted as scripting language by several applicatives, easy
> to understand,
> with a feature rich set of standard libraries.
>
> GIMP python scripting is possible since 1999, before version 1.2 and
> it allows
> access either to GIMP's procedural database and to internal image
> pixel data, just like
> plug-ins written in C.
>
> However there are
