The ten commandments to keep your hands off AndroWish 1. looks ugly, like stuff from the 90's (you're invited to design a ttk theme for it to look somewhat less anachronistic) 2. behaves not exactly like Tcl/Tk on the desktop (due to that pixel density war on mobile equipment) 3. has not reached maturity in years (and will take another century) 4. will never look native on Android (although nativity in terms of look is quite relative) 5. invites developers to combine it with unwanted ads (in the sense of free software) 6. follows not that hyped HTML5/CSS/JavaScript/WebGL/Canvas/Websocket/*whatever* inventions of W3C (which in modern times does not require to learn one programming idiom, but at least three, holy progress!) 7. will run for 74 minutes at most (not proved, but couldn't resist, since the 35 year old CD played not longer) 8. was a hack by a single individual not backed up by a conference or a consortium 9. (the most compelling point) was not designed from ground up to be something totally new 1. born out of pragmatism to be as portable as possible with oldish software which has been invented years ago in order to not re-invent the wheel. ---- [pdt] I could be a bit picky with ttk, e.g. under Linux scrollbar buttons don't look great, treeview defaults to bold column titles. Under Windows, notebook tabs don't look as good as under Linux. I'm sure I could come up with some other minor points as well. But I don't think there's too much wrong really with how ttk looks. The Linux tk file dialag leaves a lot to be desired. But I don't like the native Windows file dialog either. It's great if you like native, but what's native isn't always particularly good. I don't like the Microsoft ribbon much, and I don't like tool buttons in window title bars ... Am I sounding grumpy? :) I won't start on Gnome3. For cross-platform apps, attempting to look native is something I personally wouldn't go for. What I would go for is the app just must not be visually offensive. I haven't used it in a while, but Synplify Pro always looked ugly to me, with its quite strong gradient shading on its toolbars and buttons. tk under Linux looks bad. I used to write quite a bit of Java, and it's fairly easy to write an ugly Swing GUI as well, although with a bit of effort you can make them look just fine. Xilinx Vivado looks OK, I _think_ that's Swing ... If ttk on Android can look as good as it does on Linux/Windows, great! [chw] here's a snapshot made from a 7 inch tablet with 1024x600 resolution running [TkSQLite] which is ttk based. [http://www.ch-werner.de/AndroWish/tksqlite.png] Not that bad at all, I hope. ---- [nobelke] chw, again, your efforts should be praised! Don't be put off by negative comments. You provide us with a batteries included solution even with a nice interface to the android eco-system. What ever do you want more! Which other scripting solution gives us this write once run everywhere feeling. As you see on which devices it all works it's amazing. A TTk theme special for android would be nice. Here we need some graphical designers who can pop in. [APN] nobelke, it was chw himself who wrote those comments so not likely he will be put off :-) ---- [pdt] Yes, looks good. I don't have an Android tablet, but I think I'm going to have to get one. I haven't treated myself to much in the way of gadgets recently, so it's now at the top of my shopping list :) ---- '''[eds] - 2014-03-26 23:01:42''' Well, where do I begin? The bulk of the comments seems to be about the look and not the functionality, so in a word - who cares!? Looks good to me: [http://www.physics.brocku.ca/~esternin/IMAG0446.jpg] AndroWish provides an amazingly low-overhead way to program Android devices. It leverages an existing code base that actually DOES something, and not just LOOKS a certain way. The said code runs without modifications (more or less, some tweaks made for readability made it necessary to resize some of the fonts I had used back DOWN in size, for Android only). if { $tcl_platform(platform)=="unix" } { if {[catch {exec sdltk android}]} { ;# Linux set defaultfont "Arial"; set defaultsize 10 } } else { ;# Android set defaultfont "Arial"; set defaultsize 6 } } else { ;# Windows set defaultfont "Arial"; set defaultsize 8 } The fact that it was made by a single individual, who actually cares, listens and responds to user traffic, is a strength not a weakness. This is the only way to run a successful project. Once it matures, you can form a committee and start evolving a new "standard". I can teach a classroom full of novices to achieve something meaningful in a single lecture. It's a blessing, removing the overhead of multiple user interfaces on multiple platforms. The above list seems contrived. I think, [chw] is just fishing for compliments ;-) [chw] 2014-03-26: bull's eye, [eds]! Thanks. In your code snippet the '''exec sdltk android''' is wrong. It would use '''Arial 6''' on all UN*Xen. The photo is nice. What application is it? And on which device with which screen resolution did you shoot it. <>AndroWish | Android