Ok, thanks - I'll watch the video afterwards! On 12 April 2015 at 12:49, Marc Fawzi <marc.fa...@gmail.com> wrote:
> Unfortunately yes. > > Only reason we wish to use it is how well it's integrated with Twitter > where the Clojure/script community comes into being, more or less, with > every tweet and retweet. Having the viewers comments automatically stream > via our Twitter account would be cool we thought. That and ease of use and > quality. > > Android version is coming soon. > > But my apologies to you and everyone with an Android device. It will > rectify soon. > > Sent from my iPhone > > On Apr 11, 2015, at 12:36 PM, Colin Fleming <colin.mailingl...@gmail.com> > wrote: > > Hi Marc, > > Is Periscope iOS only? > > Cheers, > Colin > > On 11 April 2015 at 23:58, Marc Fawzi <marc.fa...@gmail.com> wrote: > >> Here is the approved animated GIF version of the resuable components >> video I originally posted. >> >> http://imgur.com/04OaRw3 >> >> >> <reusable_input_component_demo.gif> >> >> I've been given go ahead to talk about these state-triggered animations >> in our logic-less re-usable Reagent components. The validation logic is >> happening in the app and on the server not in the components. All >> components do is react to changes in the app state, and in this case, they >> react when the errors subtree of the app-state atom changes (we use >> pre-defined, schema-checked cursors as the interface between app and >> components and the approach we've taken is to be simply careful in how we >> use cursors rather than avoid them and build more complicated >> abstractions). The components also react to other changes in the app-state >> such as their own focus/blur state which is tracked, and the animations are >> triggered based on that. >> >> These Resuable Components with their App-State-Driven CSS Transitions >> (sorry, only the input component is shown in the GIF) were built using >> bare-bone Reagent. >> >> There will be a 15 minutes presentation about them, how they are used and >> shared across our many teams and apps, versioned css styles in the css >> vault and the user classes that can be used to customize the default >> styling and animations, and show advanced use cases like inter-component >> interactions and how it's achieved with only bare-bone Reagent. >> >> I'll talk about the really simple way we build to share components that >> are actually worth sharing (as opposed to having resuable "dumb" components >> and "smart" ones that can't be shared, we found a 3rd class that is dumb in >> that it has no logic but is smart in that it has clever animations in >> response to changes in app state. >> >> We have found them to be easily usable by anyone on our team from junior >> devs to opinionated clojurists. The trick was to keep the abstractions dead >> simple: provide some pre-defined cursors (schema-checked by components) >> under the main.ratom namespace, where app state is kept, and the following >> lines to setup that sign up box you see in the GIF. It needs no callbacks, >> no crazy parameters for inline styles, and no other parameters in case of >> input component than the field name. >> >> [form/input-text-split {:name1 "firstName" :name2 "lastName"}] >> [form/input-text-split {:name1 "email" :name2 "email_repeat"}] >> [form/input-password {:name "password"}] >> >> That is ALL it takes to build what you see in the GIF if you use the >> aforementioned pure Reagent resuable input component. >> >> RSVP if you want hands on close up look at our approach to building and >> sharing resuable "logic-less" components with app-state-driven css >> animations. >> >> I guess it's a happy middle between smart and dumb. Give the users >> something they would actually want to use. >> >> By the way, tested on iOS and Android too, and modern desktop browsers. >> >> My talk will be the 3rd after Dmitri (Reagent-Template) and Dhruv >> (Re-frame) >> >> Please RSVP even if you're going to attend via Periscope (so we know >> who's attending and can communicate further info re meetup) >> >> >> http://www.meetup.com/Reagent-Minimalistic-React-for-ClojureScript/events/221710610/ >> >> One note is these components are not yet open source, but I can answer >> all your questions at the meetup, not on this thread, and show some sample >> code to get ClojureScript/Reagent n00bs like us going on their own possibly >> more elegant implementations. >> >> See u then. >> >> Marc >> >> >> >> >> >> >> >> >> >> On Fri, Apr 10, 2015 at 8:37 AM, Marc Fawzi <marc.fa...@gmail.com> wrote: >> >>> I tried join.me and the pro version ($) would indeed allow speakers to >>> share with up to 249 participants but the problem is that the pro account >>> holder is the one who can share with that many. Everyone else can share for >>> free with up to 10 participants. >>> >>> And the second approach of speakers capturing their screens and then >>> uploading the movie later puts too much burden on speakers since the >>> movie's file size will be in the gigabyte range, and in my case where I'm >>> going to showcase some reusable components with app-state-driven animations >>> those animations start to stutter when Quicktime is hogging cpu/gpu/memory >>> resources, so it's not really an ideal solution. >>> >>> What we'll do instead, CC-ing our video pro Brandon Moore, is to zoom in >>> to show the code on the screen whenever some coding is being done. >>> >>> So then you can see the code in the video we make (distributed , and >>> jump on Periscope if you wish to comment live, ask question or as the >>> Periscope web site advertises you may be able to influence what happens at >>> the meetup. I'll be broadcasting via Periscope off of my twitter handle >>> @marcfawzi and will relay all questions and comments to the speakers as >>> they come in. >>> >>> Full Periscope instructions will be posted soon on the meetup's page >>> >>> If you're going to attend via Periscope please RSVP so we can >>> communicate further info prior to the event. >>> >>> RSVP Here: >>> >>> http://www.meetup.com/Reagent-Minimalistic-React-for-ClojureScript/events/221710610/ >>> >>> Marc >>> >>> >>> >>> On Fri, Apr 10, 2015 at 7:26 AM, Marc Fawzi <marc.fa...@gmail.com> >>> wrote: >>> >>>> I think maybe the more technically feasible solution would be for all >>>> speakers to run QuickTime screen capture with microphone turned on while >>>> they give their presentations regardless of local or remote origin. >>>> >>>> That I know is doable. Then as a remote viewer you can watch live via >>>> Periscope for the interaction value and wait a bit for us to share the >>>> screen capture videos. >>>> >>>> Works? >>>> >>>> Sent from my iPhone >>>> >>>> > On Apr 10, 2015, at 7:16 AM, Marc Fawzi <marc.fa...@gmail.com> wrote: >>>> > >>>> > That gives me a great idea. >>>> > >>>> > We may be able to have speakers share their screens on something like >>>> join.me where we can simply throw the URL on Periscope and this way >>>> we'd have two view contexts: Internal, where people get to see the >>>> presenter live or coming via Google Hangouts (for remote presenters) or >>>> External where people get to see the presenters screen on join.me and >>>> be able to interact with the meetup via Periscope. >>>> > >>>> > I've BCCd the other two speakers on this and will rehearse the >>>> scenarios >>>> > >>>> > Thank you for letting me know that seeing the code is important. This >>>> means that you have to watch it live. But one of us here will also record >>>> the speakers' screen sharing sessions for potentially sharing later as >>>> linked videos. >>>> > >>>> > There is no substitute to being at the Meetup in person but if you're >>>> remotely located then this might be a good way to go about it. >>>> > >>>> > Sent from my iPhone >>>> > >>>> >>> On Apr 10, 2015, at 7:02 AM, simon lomax <simax.99...@gmail.com> >>>> wrote: >>>> >>> >>>> >>> On Wednesday, 8 April 2015 21:06:58 UTC+1, marc fawzi wrote: >>>> >>> Hi everyone! >>>> >>> >>>> >>> >>>> >>> As you may know, our first Reagent meetup at Loyal3 in SF/Bay Area >>>> on March 16th, 2015 (video: https://www.youtube.com/watch?v=DYzwfekWSzQ) >>>> went well and we've been planning a second meetup... >>>> >>> >>>> >>> >>>> >>> The date has been set for April 16th (so soon you say!!) >>>> >>> >>>> >>> >>>> >>> We've actually taken input from most of you who attended (I >>>> personally enjoyed meeting you all) and we're ready to go at it again but >>>> with more Reagent focused talks than last time (we'll still have the same >>>> awesome pizza with gluten/dairy free options but with more beer choices! >>>> >>> >>>> >>> >>>> >>> Meetups are about meeting other people and building relationships, >>>> maybe even starting companies and projects or sourcing folks to work on >>>> your next big thing, but the SF Reagent meetup is more than that: we'd like >>>> to *help* shape the future of our beloved Reagent. >>>> >>> >>>> >>> >>>> >>> Meetup Agenda: >>>> >>> >>>> >>> >>>> >>> 1. 6:30pm - 7:00pm: meet & greet, food ad drinks, social >>>> >>> >>>> >>> >>>> >>> 2. 7:00pm - 7:30pm: Intro to Reagent-Template (repo: >>>> https://github.com/reagent-project/reagent-template) --- by its author >>>> Dmitri Sotnikov (also author of Luminus.) Dmitri will be presenting via >>>> Google hangout on a big screen and you will be able to ask him questions >>>> live. This should be interesting. >>>> >>> >>>> >>> >>>> >>> 3. 7:30pm - 7:45pm: Re-frame port of Angular's phonecat example >>>> (repo: https://github.com/dhruvp/angular-phonecat-re-frame) -- by its >>>> author Dhruv Parthasarathy (MIT) -- In Person :) >>>> >>> >>>> >>> >>>> >>> 4. 7:45-8:00pm: Reusable Reagent Components with App-State Driven >>>> CSS Transitions (video of input component >>>> >>>> https://www.youtube.com/watch?v=dWCXAZ1XIKc) -- by Marc Fawzi -- this >>>> talk will also include a sub-talk on sharing the components via internal >>>> maven repo Artifactory and TeamCity deploy pipeline ... among other things >>>> >>> >>>> >>> >>>> >>> Most importantly, we want to start the conversation about the >>>> future of Reagent and React Native. If you have a clue come join us. >>>> >>> >>>> >>> >>>> >>> For those of you who are not in SF you may join us via Twitter >>>> Periscope! (it's an awesome way to stream and share meetups!) >>>> >>> >>>> >>> >>>> >>> Instructions for watching the meetup on Periscope will be posted in >>>> the comments and updated here. >>>> >>> >>>> >>> >>>> >>> See you on the 16th! Live or via Periscope. >>>> >>> >>>> >>> >>>> >>> Marc & the Loyal3 team >>>> >> >>>> >> Hi, >>>> >> >>>> >> Thanks for posting the video of the first meet up on youtube. I >>>> watched it, but it had the same old problem that so many programming videos >>>> have. We can't see the screen properly. ie. You will be talking about some >>>> code that you're displaying on screen but its just too small or the camera >>>> is too far away from the screen. For us watching on video this is uber >>>> frustrating. I was really excited to watch but then disappointed because of >>>> this perennial problem. Please remember us trying to view on youtube. Our >>>> first priority is being able to see the screenful of code - even if we can >>>> only hear your voice - we don't actually need to even see you, just the >>>> screen. >>>> >> >>>> >> Thanks for sharing the first talk though, we do appreciate it. >>>> >> >>>> >> >>>> >> -- >>>> >> You received this message because you are subscribed to the Google >>>> Groups "Reagent-Project" group. >>>> >> To unsubscribe from this group and stop receiving emails from it, >>>> send an email to reagent-project+unsubscr...@googlegroups.com. >>>> >> To post to this group, send email to >>>> reagent-proj...@googlegroups.com. >>>> >> Visit this group at http://groups.google.com/group/reagent-project. >>>> >> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- >> Note that posts from new members are moderated - please be patient with >> your first post. >> --- >> You received this message because you are subscribed to the Google Groups >> "ClojureScript" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojurescript+unsubscr...@googlegroups.com. >> To post to this group, send email to clojurescript@googlegroups.com. >> Visit this group at http://groups.google.com/group/clojurescript. >> > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > Visit this group at http://groups.google.com/group/clojurescript. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojurescript+unsubscr...@googlegroups.com. > To post to this group, send email to clojurescript@googlegroups.com. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
