Opened 12 years ago

Closed 12 years ago

#3719 closed defect (fixed)

Turtle Art Activity secondary palette is overflowing

Reported by: garycmartin Owned by: walter
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Turtleart Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

Testing TurtleArt-145, the Activity secondary palette is now overflowing with tool features. See attached screen shot. Some space can be reclaimed by removing the invisible separator eating space after the new sharing blocks feature icon. Is there someway to consolidate the "loading" options so you just have one (smart) load from journal feature (perhaps merge Load Project and Load plugin seeing as Load Python block opens a non Sugar friendly GNOME file chooser)?

Attachments (1)

TurtleArt-145 Activity Toolbar Overflow.png (67.6 KB) - added by garycmartin 12 years ago.

Download all attachments as: .zip

Change History (5)

Changed 12 years ago by garycmartin

comment:1 follow-up: Changed 12 years ago by walter

Is this on an XO? On most platforms, it uses a palette for the load/save tools.

I am still interested in the concept of "mounting" activity-specific directories so that the Sugar chooser can be used in all cases... implementation, however, might require a major kludge.

comment:2 in reply to: ↑ 1 Changed 12 years ago by garycmartin

Replying to walter:

Is this on an XO? On most platforms, it uses a palette for the load/save tools.

Yes this is an XO.

I am still interested in the concept of "mounting" activity-specific directories so that the Sugar chooser can be used in all cases... implementation, however, might require a major kludge.

I'm not 100% sold on this yet, can you think of other Activities that would expose this or is it TA specific. Perhaps a way to hack on activity bundles generally, 'mount an activity' then use other Sugar tools to edit its resources directly? Hmmmm.

comment:3 Changed 12 years ago by walter

Toolbar overflow should be OK in v147.

Re the mounting of resources directly, I see this as something any activity offers examples, code snipets, plugings, etc. could use. But we should cpntinue this discussion on the list and/or on the feature page in the wiki.

comment:4 Changed 12 years ago by walter

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.