JdeH
Joined 10 years ago
Joined 10 years ago
Meanwhile can you indicate what's most disturbing about it? I guess the mobile experience is the most problematic? Or just the layout? Fonts? Accessability? We should probably have a professionally designed logo as well. But currently we're focused on making the compiler better. 3.6 -> 3.7 was really a big step, due to the modules.
There will also be a special website to play with Transcrypt. The URL was already reserved: tsfiddle.org. But it will be a while until somebody finds the time to turn it into a playground / educational site. Everyone working on Transcrypt has a daytime job as well, that's how it is with open source, although the past months I think most of my time was spent on Transcrypt.
The project was born from practical needs for a medical imaging project. In my experience the switch to Python is a great improvement in productivity and clearness. And it's more fun, above all...
The project can be found at:
https://github.com/qquick/Transcrypt
Components can be freely mixed on a page without requiring recompilation. A developer doesn't need Transcrypt or any knowledge of it to use such a framework.
Each page has one unit that contains the Transcrypt runtime and, if needed, any central facilities. It is compiled with the -u .run switch. In addition each page can hold as many separate components as needed. Compile these with the -u .com switch.
A loader is generated, accepting a list of components. By varying this list, each page can have its own subset of components, without the need to recompile. The generated JavaScript code for components can be very small, typically a few hundred bytes. The runtime and central facilities are included in the page only once.
https://github.com/QQuick/Transcrypt/blob/master/transcrypt/...