famo.us

I'm trying to create a layout (using famous.js) similar to the BBC News native app; a vertical ScrollView, within which are numerous horizontal ScrollViews. I've got both 'working' to the extent that everything renders and the horizontal scrollers work perfectly. My issue is that the vertical scroll event won't fire if the user swipes a surface within a horizontal ScrollView. If i touch an area outside the horizontal scrollers, the vertical scroller will do its job and scroll... vertically Does anyone know what i'm missing? I have a feeling that a RenderNode may be needed, but have had no luck

Famo.us has a "Scrollview" but it only scrolls if you have multiple surfaces inside it. I would like a single long page of text, but this doesn't respond to scrolling. Given that famo.us deliberately overrides normal native scrolling views ( https://github.com/Famous/views/issues/45 ), what is the best method to get famous to scroll a long page of content? I'm considering breaking all the content html apart (eg div by div), and adding a bunch of surfaces into a normal scrollview. this may work for some simple content but would be complex for anything non-trivial - JS would have to parse the

I found Famo.us and it seemed pretty exciting but their docs are closed. I am very curios about WebGL so I started looking for alternatives. I found Three.js and Clara.io. How do they differ from famo.us? What is the main objective of each framework? Thanks. Edit : Rephrased. Three.js is a lightweight javascript library to create 3D visualisations (using WebGL, SVG, Canvas or another renderer). Clara.io is an online 3D modelling tool using WebGL. Famo.us is a javascript rendering engine to create web-apps with 3D user interfaces that promises to run smooth (60FPS) on mobile devices. Famo.us

2 Technologies: Meteor with the blaze templating engine Famo.us with their awesome gui framework I come from the meteor side, I personally like using {{mustache}} (handlebars) to drive the gui from data, the reactive session / database makes this really efficient and intuitive. Now came famo.us and all its advantages, but the drawback of a code based gui is that there is no place for handlebars anymore… What is the current practice for mixing both technologies together ? Are they completely dissociative ? Is using the "observe" / "Deps.autorun" mechanism a common practice everywhere a famo.us

I don't see any tutorials with text input on famo.us university. How can I add a text box surface to my app and handle onchange events? It is a bit hard to understand what you are looking to do.. But lets start out with your first question. There is currently no onchange handler option so if you want it now, you can write a subclass of InputSurface. By overriding the deploy function, while still calling InputSurface's deploy function, we can add the functionality we want, without messing around to much! Here is a way you could add an onchange handler to a subclass of InputSurface. Just

I am wanting to know what events are available to subscribe to, for the Famo.us Engine object. From the Famo.us university : the Engine also emits certain events such as 'prerender' and 'postrender.' However, due to the frequency of these events, they should be used only when absolutely necessary. There are other Engine events that are handy though, namely 'resize.' So, what are all of these 'certain events' the engine emits? Also, what 'other Engine events that are handy' are avaible to subscribe to? I can't find a list anywhere of what events are available. If someone know the answer to this

I'm looking for an event that tells me when a surface has been rendered so I can call methods like surface.focus(). If I call focus immediately after I create the surface it doesn't work. If I call it in a timer after some arbitrary time I expect it to be rendered, it works. So there must be an event I can use. For example if I create a widget that builds a bunch of surfaces inside a view, how do I know when that widget has been fully built and more importantly, when is it being rendered so I can set focus on an input surface? Thanks This is another case of when subclassing may be your easiest