Canvas element rolodex

[paulmtrueba]

build canvas element rolodex for UI/UX

[paulmtrueba]

https://popmotion.io/pose/

[TadKaput]

Hey !!! We love this. Tallman especially liked the "flippin great" and "awesome with react dom" stuff. we both love the concept!

[Optominer]

Love the "FLIPpin Great" and "Awesome with react DOM". The "awesome" seem to be more in line with how i want the "tabs" to move around, and the "FLIP" looks perfect for when you are actually interacting within each "tab". Question: The orchestrate - is it similar to these and does it encompass both into one style?

[paulmtrueba]

Excellent! We just got turned on to this lib at work, haven't even gotten a chance to dig into it yet but I'll add it to the package.json and see what I can do with FLIPpin Great and Awesome with react DOM.

@Optominer I think that the orchestrate is using similar elements to the other two but using a simpler animation. It's all just standard HTML DOM elements so we have a lot of freedom for restyling or making changes to any of the animations. The lib contains all of the animations for every current major browser so we would have a lot of freedom to make customizations if you're seeing something that you like in one of these that you feel would work well with another

[paulmtrueba]

think that I just cracked the container architecture for this, albeit theoretically but from what I have built in the past i see no reason why it shouldn't hold up. Going to just fill this up with a long sting of notes so that it's attached to the project owned by the company and it's all being written on my personal computer so there is no attachment to my current full-time job or employer. I'm going to scrap a bit of the form stuff that I was preparing for tomorrow and begin to move some things around to make use of this new hierarchical UI/UX system

[paulmtrueba]

scrap the existing system where a single form container delegates param props from the router to determine which form is shown and which page of the form the user is currently viewing and move to a system where every form is built within its own container and that container is able to render as many of the form pages as are required based on existence of currentPage.

  return(
  <rolodexPageLayout>
    {page === 1 &&
      <TraditionalMortgage page={1} />
    }
     {page === 2 &&
      <TraditionalMortgage page={2} />
    }
     {page === 3 &&
      <TraditionalMortgage page={3} />
    }
    {currentPage === <num> &&
      <TraditionalMortgage />
    }
  </RolodexPageLayout>
  );

[Optominer]

Can’t wait to talk tomorrow. I found a great “example” site. Similar in concept but lacks the pop i am going for. We will have to share screens when we talk so i can show you.

On Fri, May 4, 2018 at 9:01 PM Paul Trueba notifications@github.com wrote:

scrap the existing system where a single form container delegates param props from the router to determine which form is shown and which page of the form the user is currently viewing and move to a system where every form is built within its own container and that container is able to render as many of the form pages as are required based on page.

return(

{page === 1 && } {page === 2 && } {page === 3 && } {currentPage === && }

);

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TheArchitypes/mini-app/issues/5#issuecomment-386777109, or mute the thread https://github.com/notifications/unsubscribe-auth/AkPCPR5EMte5TBov15PTYt4C_7l__pNbks5tvSQlgaJpZM4Tg5UB .

[Optominer]

Whats up PABLO!!!!

Couple of things I noticed:

1) The top of the webpage "header" (I guess) needs to look like this:

I noticed the "boxes" around the words and all the contact info is at the bottom.

Second: The "mission statement, social media stuff I want on the left of the page, not the bottom. The bottom needs to be left for the NLMS ID, DRE ID, etc etc (lending BS acronyms).

Lastly - The background image should be "blurred" - if you need me to - I can take care of that in Adobe PS. Let me know and I will get that updated and over to you asap :)

Thanks man - talk soon.

On Mon, Apr 30, 2018 at 8:53 PM, Paul Trueba notifications@github.com wrote:

Excellent! We just got turned on to this lib at work, haven't even gotten a chance to dig into it yet but I'll add it to the package.json and see what I can do with FLIPpin Great and Awesome with react DOM.

@Optominer https://github.com/Optominer I think that the orchestrate is using similar elements to the other two but using a simpler animation. It's all just standard HTML DOM elements so we have a lot of freedom for restyling or making changes to any of the animations. The lib contains all of the animations for every current major browser so we would have a lot of freedom to make customizations if you're seeing something that you like in one of these that you feel would work well with another

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TheArchitypes/mini-app/issues/5#issuecomment-385593213, or mute the thread https://github.com/notifications/unsubscribe-auth/AkPCPapF_roDfBBsWXoItceSUZA521tpks5tt9wkgaJpZM4Tg5UB .

[paulmtrueba]

I can blur out with css no problem, I'll make the other adjustments in the morning, just getting out of work

[Optominer]

Paul - check this out:

http://wowslider.com/jquery-photo-gallery-strict-photo-demo.html

carousel view is PERFECT...

On Wed, May 23, 2018 at 9:26 PM, Paul Trueba notifications@github.com wrote:

I can blur out with css no problem, I'll make the other adjustments in the morning, just getting out of work

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TheArchitypes/mini-app/issues/5#issuecomment-391584128, or mute the thread https://github.com/notifications/unsubscribe-auth/AkPCPQgIc9dj2hd8EJauu_Az-C5oQbj9ks5t1jZ7gaJpZM4Tg5UB .