Why declarative became synonym of nested hell? Can't you mimic an imperative flow of UI construction but under the hood have it declarative or whatever you want?
I plan on using it for semi throw away UIs for things where I don't want the user to have to spin up a Web server. Right now there's no canvas support, but there is that kind of thing in the Tk/Tcl docs (linked in the project). I probably need to add a way to reference a specific Widget so you can access the raw name and run taw Tcl against it.
I like the name, it’s a fun portmanteau of Tkinter and intergalactic. It’s also more search engine friendly and less likely to hit a name collision with another project.
Why declarative became synonym of nested hell? Can't you mimic an imperative flow of UI construction but under the hood have it declarative or whatever you want?
The sample reminded me of HTML. I couldn't hate it.
Nice! (starred and forked so I'll be more inclined to try it)
What projects do you feel this would be esp. well-suited to?
(your doing a "To-do" app where a list would normally appear was a fun bit)
Are there projects which you feel this would absolutely _not_ work for? In particular, I have an itch to do a line/arc drawing program w/ a canvas...
I plan on using it for semi throw away UIs for things where I don't want the user to have to spin up a Web server. Right now there's no canvas support, but there is that kind of thing in the Tk/Tcl docs (linked in the project). I probably need to add a way to reference a specific Widget so you can access the raw name and run taw Tcl against it.
why not just call it reactTK
I like the name, it’s a fun portmanteau of Tkinter and intergalactic. It’s also more search engine friendly and less likely to hit a name collision with another project.
Link gives a 404 :-(
Your repo link is probably not set to public.
Well that was dumb - fixed, sorry