<div class="gmail_quote">2012/7/18 Aleksey Lim <<a href="mailto:alsroot@sugarlabs.org" target="_blank">alsroot@sugarlabs.org</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> CCing to iaep@. This is a feedback reagarding Sugar Network[1] Web UI look&feel. Original post[2]. <div class="im"> On Tue, Jul 17, 2012 at 03:50:09AM -0500, Laura Vargas wrote: > De la jornada de la mañana quedaron documentadas las siguientes > recomendaciones de Julita, Alejandro y Ketty: > > 01 Interfase Gris? ("en Perú primaria es Sugar y Sugar es primaria") > Color* sobre los recursos problema/rojo idea/amarillo > pregunta/azul reseña/verde? </div>My own perception is. It might be good for Sugar Shell (and sometimes for Sugar Activities) to follow common design idea with having grey "background" and objects painted to user's colors to expose the ownership (or how the original design idea sounds). But I don't see any reasons to extrapolate this design solution to all software that people will use/run from Sugar Shell: * it is impossible because not all edu software is intended to be launched only from Sugar Shell; * well, maybe monotone coloring is a good (not sure here) for madhouses or prisons, but for my self, I'm preferring to switch my desktop theme/colors from time to time. So, I'm +1 for not strictly following Sugar Shell's coloring paradigm in Sugar Network UI. Partial implementation might be still useful though. For example, using user's colors to expose objects ownership. But maybe it makes sense to forget about this paradigm entirely. It works fine/as-assumed in Sugar Shell when there is a central user - local user and limited number of users that local one is participating with. So, the coloring variety is pretty limited. But, in Sugar Network case when objects are global (at least assumed to be) within the entire Sugar community, it is becoming meaningless - there is a big chance to see duplicates or similar looking colors. <div class="im"> > 02 Tool Tips para los íconos? </div>There a need to explain "what this button means". In regular desktop UI it is hints. Not sure whats the common practice in Web design for that. But for sure, +1 for somehow exposing such info. <div class="im"> </div></blockquote><div> +1 </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im"> > 03 Es posible que quede un histórico de la edición de los recursos? </div>Could you elaborate it in English. </blockquote><div class="im"> Ketty, is one of the teachers that took part in the Arahuay Pilot (first pilot for the OLPC project in Perú). As she was very enthusiastic testing the Network, her feedback here refers to the convenience (or need) for participants of being able to track all modifications made by authors to the resources (ideas, questions, problems, reviews). Basically Ketty's concern had to do with the fact that some comments will end up obsolete if not updated in accordance with the resource's evolution (editing). Currently only latest edition date and content is visible for participants. One step we could give in this direction, would be to implement notifications and define participants will automatically become "followers" of the X resource after having at least an effective interaction (like giving a solution or making a comment). > 04 Podremos Adjuntar imagenes (o cualquier tipo de archivo) a los recursos? </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I think it will be a good start to attach activity objects (from Journal). We can improve this workflow at any time later. </blockquote><div> +1 </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div class="im"> > 05 Cuales serán los mecanismoa de Acompañamiento y que eventos de > Activación? > 06 Sería conveniente una capacitación dirigida a los DAIPS durante periodos > largos (tipo 1 semana) dentro del horario de trabajo </div>These points is also not clear after mechanical translation. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div class="im"> > Los demás quedaron pendientes en la jornada de la tarde, tal vez se animen > a cmpartirlas en la Red Azúcar o por aqui en la Lista. > > Saludos cordiales a todos. > -- > Laura V. > I&D SomosAZUCAR.Org > > Skype acaire > IRC kaametza </div>> _______________________________________________ > somosazucar mailing list > <a href="mailto:somosazucar@lists.sugarlabs.org">somosazucar@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/somosazucar" target="_blank">http://lists.sugarlabs.org/listinfo/somosazucar</a> [1] <a href="http://wiki.sugarlabs.org/go/Sugar_Network" target="_blank">http://wiki.sugarlabs.org/go/Sugar_Network</a> [2] <a href="http://lists.sugarlabs.org/archive/somosazucar/2012-July/001314.html" target="_blank">http://lists.sugarlabs.org/archive/somosazucar/2012-July/001314.html</a> -- Aleksey _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> </blockquote></div> -- Laura V. I&D SomosAZUCAR.Org Skype acaire IRC kaametza