Ticket #1585 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

need some way to present examples to other activities

Reported by: dsd Owned by: tomeu
Priority: Unspecified by Maintainer Milestone: Unspecified by Release Team
Component: sugar Version: Git as of bugdate
Severity: Unspecified Keywords:
Cc: walter, sascha_silbe Distribution/OS: Unspecified
Bug Status: Needinfo

Description

Turtleart currently creates a journal entry for pippy to open some example code.

This isn't really standard journal usage (which generally just records things that you've done) but there is currently no better place.

Sugar should provide some mechanism for activities to export example content (to be processed in other activities) and a way for the user to access that.

Change History

  Changed 3 years ago by walter

  • cc walter added
  • type changed from defect to enhancement

  Changed 3 years ago by sascha_silbe

  • cc sascha_silbe added
  • version changed from Unspecified to Git as of bugdate
  • status_field changed from Unconfirmed to Needinfo

IMO examples belong into the Journal as much (or as few, depending on your POV) as activity bundles belong there.
Maybe we should "hide" them in the default view and just show them in specialised ones.
Splitting up the Journal into Object and Action views (as already in the designs for a long time) would IMO be a prerequisite for this.

I'll boldly set NEEDINFO on this as we need further discussion on the mailing list and designs before we can start working on it.

follow-up: ↓ 8   Changed 3 years ago by dsd

I think you should leave this bug open until it is implemented (or until the discussion outcome decides that this is not necessary).

Activity bundles only belong in the journal after the user has put them there. Same for examples, in my opinion.

In this case, opening Turtleart puts the example there without the user requesting, and without informing the user.

  Changed 3 years ago by carlo

Informing the user?

"Turtleart has just saved a few examples for you in the Journal: "entry-name"

follow-up: ↓ 6   Changed 3 years ago by dsd

Where does it say that?

in reply to: ↑ 5   Changed 3 years ago by carlo

Replying to dsd:

Where does it say that?

Sorry been too cryptic :)

it was a proposal for a potential workaround...

carlo

  Changed 3 years ago by dsd

Ah, OK. That would be helpful, but the original points behind this ticket would still stand.

in reply to: ↑ 3   Changed 3 years ago by sascha_silbe

Replying to dsd:

I think you should leave this bug open until it is implemented (or until the discussion outcome decides that this is not necessary).

Which is exactly what I did. :)
NEEDINFO just means we need outside action (e.g. mailing list discussion).

Activity bundles only belong in the journal after the user has put them there. Same for examples, in my opinion.

A friend of mine, Caspar, agrees with you (with had that discussion a few weeks ago), but I don't quite do so. Or at least I think it should be in the data store and retrievable from it's public API like any other content. Where in the UI to show it is a separate matter and I really think we should separate Objects and Actions view first.

Let's continue the discussion on the mailing list, please (I'll "cross-post" there).

Note: See TracTickets for help on using tickets.