[Bugs] #1610 NORM: Alternative to Create a new wireless network.

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Tue Jun 29 04:12:57 EDT 2010


#1610: Alternative to Create a new wireless network.
----------------------------+-----------------------------------------------
    Reporter:  reuben       |          Owner:  erikos  
        Type:  enhancement  |         Status:  assigned
    Priority:  Normal       |      Milestone:  0.84    
   Component:  sugar        |        Version:  0.84.x  
    Severity:  Unspecified  |       Keywords:  r?      
Distribution:  Unspecified  |   Status_field:  Assigned
----------------------------+-----------------------------------------------

Comment(by erikos):

 Replying to [comment:8 sascha_silbe]:
 > Replying to [comment:7 erikos]:
 > > So, on machines like the XO-1.0 we will use the mesh as the hardware
 allows to. On the XO-1.5 we will present the user with the three adhoc
 networks, as there is no mesh hardware available. The XO-1.5 and XO-1.0
 will see adhoc networks in his neighborhood view, so it the XO-1.0 can
 connect to an adhoc network that has been created by a learner on the
 XO-1.5. What we removed is the option in the device palette to create
 adhoc networks, as we have now standard ways of creating networks without
 infrastructure.
 >
 > Do I understand correctly that in order to let XO-1s collaborate with
 XO-1.5s now an XO-1.5 user needs to initiate the connection as there's no
 way for the XO-1 user to create an ad-hoc network? If so, that seems
 cumbersome and confusing to me.

 Yeah true, I have overseen that point. Thanks for the comment. We
 concluded to remove the option from the palette as it might be confusing
 to the learner to have so many options. And in my opinion, once you have
 the three default adhoc networks there is not really a need to be able to
 create your 'own' new adhoc network (machines without mesh hardware). And
 we do not want to populate the neighborhood view on the XO-1.0 with three
 mesh icons and three default adhoc icons. Not sure yet, how/if we can do
 better here, suggestions welcome.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1610#comment:10>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list