What is the state of Famous-Flex?

[ghost]

@IjzerenHein Could you please provide your thoughts about the future of famous-flex?

It is an excellent framework, however, I'm wondering whether there will be any further development, bug fixes, etc.?

Is there a possibility to support SamsaraJS instead of famous v0.3.x in the near future? I just asking since SamsaraJS looks promising and is under active development.

Thanks in advance for your clarification.
Stephan

[trbm1]

Hi Bardu. IjzerenHein is on a long holiday trip. Not sure what he's
planning to do, but it explains his idle communications. Cheers, Hans
On Tue, 5 Jan 2016 at 23:18, bardu [email protected] wrote:

@IjzerenHein https://github.com/IjzerenHein Could you please provide
your thoughts about the future of famous-flex?

It is an excellent framework, however, I'm wondering whether there will be
any further development, bug fixes, etc.?

Is there a possibility to support SamsaraJS
https://github.com/dmvaldman/samsara instead of famous v0.3.x in the
near future? I just asking since SamsaraJS looks promising and is under
active development.

Thanks in advance for your clarification.
Stephan

—
Reply to this email directly or view it on GitHub
#123.

[ghost]

@mysim1 So, what are your plans at https://arva.readme.io

[trbm1]

@bardu amongst a few:

• (unit)testing different aspects of the library. (progressing)
• Improving efficiency and cross-browser support. (progressing)
• Babel build speed increase from JSPM (see gitter discussions of 6-1-2016)
• Redefine the layouting approach using region/layer APIs (efficiency)
• Yeoman platform target seeds

We haven't put time in publishing a roadmap, but it's there are right now moving towards beta.3 release.

[IjzerenHein]

Hi guys,

I've been on a much needed vacation as Hans mentioned.

I've just put an update in the main readme, regarding what's up next:

Many people have asked me what the future of famous-flex holds, and I would like to shed some light on this.. I've been working on a big update to famous-flex for some time now. Initially it was to be based on the mixed-mode release of famo.us, but this doesn't seem future proof at the moment. It will therefore be based on (or rather run on top of) famous v3 and Samsara.js. The new library shall contain an extensive set of out-of-the-box controls such as a switch, slider, progress-bar, label, tab-bar, scrollview, etc... All controls will be highly customizable and highly animatable. The idea here is to have a complete and solid set of building blocks for quickly building web/apps.

A second goal will be to use famous-flex as an output target for NativeScript apps. Using NativeScript it is possible to write native apps (iOS/Android) using the power of javascript. How awesome would it be to be able to run these apps in the browser as well. I have clear use cases for this and my customers would benefit from this. I want the ability to be able to write a mobile app and website using a shared code-base, and have native performance characteristics for the mobile apps.

Let me know when you have any questions about this.

cheers,
Hein

[ghost]

Hein, this is great news, specifically I'm excited about a future support for SamsaraJS.
I think it would help many people to stick with famous-flex if you could provide your thoughts about a roadmap in the main readme.

All the best,
Stephan

[trbm1]

Hi @IjzerenHein Welcome back! Really nice to see you're ready for the next steps. What's your opinion about Famo.us 3.5 or SamsaraJS? I've seen the roadmap of SamsaraJS and would actually love to see an optimisation roadmap instead of seeing a feature roadmap. Pushing down memory and CPU usage is key for future features. Like any people within the WebGL space could write on-top features for the Famo.us engine (Three.JS, SeriouslyJS). Likewise for MV* framework, done by others. For example: we've made Arva work on Smart TVs and preferably work with more a more efficient rendering engine to boost the experience. Likewise we've build a new Component Layout system which we are experimenting with using a decoration (not declarative) approach to optimise coding where we leverage famous-flex (which proves you have a solid architecture there).