[Sugar-devel] [FEATURE] multiple home views

[Manuel Quiñones]

2013/5/2 Walter Bender <walter.bender at gmail.com>:
>
>
>
> On Thu, May 2, 2013 at 2:12 PM, Manuel Quiñones <manuq at laptop.org> wrote:
>>
>> 2013/5/2 Walter Bender <walter.bender at gmail.com>:
>> >
>> >
>> >
>> > On Thu, May 2, 2013 at 12:35 PM, Walter Bender <walter.bender at gmail.com>
>> > wrote:
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, May 2, 2013 at 12:27 PM, Manuel Quiñones <manuq at laptop.org>
>> >> wrote:
>> >>>
>> >>> After reading the old thread,
>> >>>
>> >>> I see there was agreement on the problem, but no one discussed the
>> >>> solution / workflow.
>> >>>
>> >>> I think multiple home views can complicate the Sugar interface.
>> >>> Overloading the favorites as proposed complicates things, IMHO.
>> >>>
>> >>> Here are two other options:
>> >>>
>> >>> - A School activity that is a launcher of other activities.  It can
>> >>> have collections like "Math", etc.
>> >>>
>> >>>
>> >>> - Enhace the search entry: search for tags.  Add tags to activities
>> >>> like "math". Provide autocompletion.
>> >>
>> >>
>> >> Yeah. I think either of these proposals are possible solutions, but at
>> >> a
>> >> cost:
>> >> (1) something more for teachers to learn (they already know how to use
>> >> the
>> >> homeview)
>> >> (2) something more to maintain
>> >> (3) something more to design/code
>> >> (4) not clear they actually lessen complexity
>> >>
>> >
>> > And another thing :)
>> >
>> > I am not convinced that searching by curriculum topic, e.g.,g searching
>> > for
>> > "math" is in line with how we want to encourage Sugar to be used in the
>> > classroom. A project-based approach is about tools, not curriculum. So,
>> > for
>> > example, if I wanted the kids to make a Fototoon, I'd want Fototoon,
>> > Record,
>> > Paint, Browse, Write, et al. on the desktop. Collections based on
>> > projects,
>> > not curricula, is what we should be promoting.
>>
>> Yes, couldn't agree more.  That's why I was a bit concerned on IRC
>> when you talked about one home view per lesson.
>>
>> --
>> .. manuq ..
>
>
> I guess we are talking past each other here. I wasn't intending that we
> implement one homeview per lesson but rather the teacher *may* choose to
> change the homeview per lesson (as per my Fototoon example above). I think
> that 2 home views: one for the classroom (fromal) and one for the kid
> (informal) covers most of what we'd need practically. But I could imagine
> building an extensible solution -- easy enough under the hood, but I fear
> that it may complicate things too much for the user. In terms of the
> implementation details, let's discuss that after we agree on the design.

I agree we should not discuss implementation datails yet.

--
.. manuq ..