Opened 11 years ago

Closed 6 years ago

#288 closed enhancement (fixed)

icon for mime-type text/x-python

Reported by: walter Owned by: eben
Priority: Unspecified by Maintainer Milestone:
Component: design Version: Unspecified
Severity: Minor Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: New

Description

It'd be nice to have a mime-type for python code so that it is easier to find when scanning the Journal.

Change History (9)

comment:1 follow-up: Changed 11 years ago by eben

Hmm, right now we have a generic text icon. One option is to add additional icons for more mimetypes, but I wonder if we could instead dynamically create generic text icons by exposing an extension, if there is one, at the bottom of the icon, eg. TXT, RTF, ODT, PY, CSS, etc. Could we dynamically generate the default icons for text in this manner? It would be much more useful to have a generic solution, I'd think. We might also want to expose the extension for objects of type "data" as well.

As an aside, I've always envisioned extra info made available in the secondary palette for an activity in the Journal. We could expose the preview, tags/description, extension/type, size, and/or other details there as well.

comment:2 follow-up: Changed 11 years ago by walter

I am not sure that the secondary palette is the solution here. I want to be able to quickly visually scan through my Journal for python code. I don't know how to do it if the python isn't already associated with Pippy.

I haven't thought about other scenarios for text, but most of them (except CSS) would probably be OK to scan with a generic text-type search.

comment:3 Changed 11 years ago by eben

I'm not suggesting that it is a solution; just an auxiliary function...previews, specifically, would be really nice to have. Anyway, the core of my question is whether or not we have the ability to dynamically render text on top of (or into?) the generic mimetype icons in order to expose their extensions.

comment:4 in reply to: ↑ 1 Changed 11 years ago by tomeu

Replying to eben:

As an aside, I've always envisioned extra info made available in the secondary palette for an activity in the Journal. We could expose the preview, tags/description, extension/type, size, and/or other details there as well.

+1, I think this would improve usability quite a bit. Entered #292 about it.

comment:5 in reply to: ↑ 2 Changed 11 years ago by tomeu

Replying to walter:

I am not sure that the secondary palette is the solution here. I want to be able to quickly visually scan through my Journal for python code. I don't know how to do it if the python isn't already associated with Pippy.

What if we added the mimetype to the set of text that gets indexed for every entry? That way you could type python in the search field and see only entries that are python-related (mostly source code files).

comment:6 Changed 11 years ago by erikos

  • Bug Status changed from Unconfimed to New
  • Component changed from sugar to design
  • Milestone changed from Unspecified by Release Team to 0.86

Let's pick this up again in 0.86

comment:7 Changed 10 years ago by bernie

  • Milestone changed from 0.86 to 0.90

Is this still relevant?

comment:8 Changed 6 years ago by dnarvaez

  • Milestone 0.90 deleted

Milestone 0.90 deleted

comment:9 Changed 6 years ago by Ignacio Rodríguez

  • Resolution set to fixed
  • Status changed from new to closed

Add icon for the python mime type

Fix #288

Changeset: 8cc594edf07c0b2a80b93f3dc8b3eec46a26e95c

Note: See TracTickets for help on using tickets.