Re: A UI design idea mockup for discussion

[Zhang Weiwu <zhangweiwu realss com>]

On Fri, 29 Aug 2014, Scott Furry wrote:

> My issue with running the mockup is what is it in? I'm assuming its a tk 
> script, but I don't use tk.  Is it pure tk? Python/tk? perl/tk?

Short answer: right click it and in the permission tab check execution, then 
double-click it to show the mockup.

Since the file name is mockup.tcl, it is tcl/tk. I have been using tcl/tk 
for a few years for building mockup, part of the reason is that it comes 
with everything: no dependency at all, no include/require statement to 
present the UI, hence I do not need to give a list of packages to install to 
prepare it; and since it is pretty hard to find anything as old as tk8.4 
nowadays, there is no need to address version neither. Last reason being it 
is clear coded - small in size and with no compilation or linked libraries.

There are two groups I often need to communicate with. One group has little 
programming knowledge, and would shun me away if I give a README/INSTALL 
file, tcl/tk is perhaps the only script that can do for the scenario; the 
other group are programmers, who would shun me away if I do not give a 
README/INSTALL. I usually work in half-closed environment when people 
already trust me sending scripts to them, and few intends to infect tcl 
script anyway.

The only line of instruction to open it is to chmod +x it, which I left out 
thinking I am talking to programmers - but I was wrong again, programmers 
think way different. For example, now it comes to my mind, a true programmer 
wouldn't be easily foold into thinking .tcl is a tcl script: it's perfectly 
valid to embed virus written in binary wrapped into #!/bin/sh and save as 
.tcl.

Never used pastbin (nor git for your information) but it's okay to learn 
them. To me looks like the urgent issue is to break the seemingly existing
communication barrier and learn any tool for the means of communication.