Yay! Daniel sees what I see!<br><br>It really is not an issue of what they give up to switch but rather what they gain. The investment in time and cash is minuscule compared to the payoff in ability, security and maintenance.<br>
<br>Daniel: note that TeacherTool is very specifically a thin client, classroom server model tool. I've been looking at the process of extending that functionality to incorporate multiple classrooms on the same server (can't have two teachers at once currently doing spotlight :( and to also handle the next generation of chubby (LNS term - thanks Aaron) and thick client/diskless workstations. The rearchitech is required because the connectivity is different between the three different flavours. The teachers will need a single tol that is connection agnostic. That requires some elegance in server setup that does not currently exist.<br>
<br>For the definitions:<br>thin client - all processes run on server<br>chubby client - some processes run on client, most run on server<br>diskless workstation - al process run on client, server only provides binary bits and user authentication.<br>
<br><div class="gmail_quote">On Sat, Jun 21, 2008 at 10:38 PM, Daniel Howard <<a href="mailto:dhhoward@comcast.net">dhhoward@comcast.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks Mike for the Inkscape solution, I'll show my teachers that one<br>
first of next year. Coupled with the graphics on OpenClipArt, it should<br>
meet the needs of both teachers and non-profits.<br>
<br>
Jim's commentary got me thinking: what I need to do is stop arguing<br>
about supporting an old application, and focus on what they can do with<br>
the new system. With K12LTSP and TeacherTool, teachers have<br>
unprecedented control over what kids do with the computers, even beyond<br>
what they're seeing at the Educational Tech conferences to which Jim<br>
referred. So, for my next school, I'm going to include a demo of<br>
TeacherTool and show them why a thin client architecture makes sense and<br>
what they can do with it is well beyond what they currently do. I'm<br>
guessing that a new capability/software application will trump any<br>
resistance from supporting an old application, especially if I can show<br>
them they can still do the old stuff if they really want to.<br>
<br>
Still learning in Atlanta,<br>
<div class="Ih2E3d">Daniel<br>
<br>
--<br>
Daniel Howard<br>
President and CEO<br>
Georgia Open Source Education Foundation<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III <br>