Walter Bender <walter.ben...@gmail.com> hat am 10. August 2011 um 16:07 geschrieben:
> On Wed, Aug 10, 2011 at 9:52 AM, si...@schampijer.de > <si...@schampijer.de>wrote: > > > Thanks for the icon! Has the design team talked about it already? Attached > > is a > > screen shot after duplicating the Memorize activity in the case they > > haven't. Do > > you intend to place the icon in the palette option as well where you do the > > actual cloning as well? About the naming, maybe something like > > 'activity-customize' or 'activity-duplicate' makes sense, what do you > > think? > > > > The intention of the icon is to make it clear that the activity is a > modified version of the original. Manuq is the one who came up with the hand > overlay concept, which was given an OK by the design team, although Manaq > had said he may try to fine-tune it somewhat. > > > Regarding the name, I had started off with something along the lines of your > suggestion, a generic name indicating a clone, but decided instead that > using the nick as part of the name was a better option: If both of us clone > memorize and then share our modifications, we won't have a naming conflict: > I'll get erikos_memorize and you'll get walter_memorize. A generic name > would result in a conflict. Hmm, maybe we misunderstood here. I just meant how to name the icon in sugar-artwork. Instead of 'customize.svg' 'activity-customize.svg' might be better. Hmmm, while writing this, as it is only an overlay, maybe 'customize.svg' is the best name... > regards. > > -walter > > PS: regarding the other changes to view source, I have made patches to (1) > update the title when you switch between the activity source and the > sugar-toolkit source; and (2) loading activity.py by default into the viewer > for sugar-toolkit source. However, in regard to #2, I am not sure how to > tell the TreeView what node is currently selected. Is there some standard > approach you can point me to: I have the file name, and need to associate it > with a node. Yes, I will have a look at that as well. Cheers, Simon _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel