[aerogear-dev] JS Team meet up highlights

[Bruno Oliveira]

Hi Luke, answers inline.

--  
abstractj

On April 2, 2014 at 12:06:54 PM, Lucas Holmquist (lholmqui at redhat.com) wrote:
> JS Cool Team Stuff

I liked the name

>  
> 1.5.0 - Early May
>  
> MQTT WS adapter
> code cleanup
> More Cookbook examples
> https://issues.jboss.org/browse/AGJS-41
> UnifiedPushClient jQuery Removal
> we need to polyfill it - pack that into client https://github.com/jakearchibald/es6-promise 

+1

> 1.6.0 - Mid July
>  
> Data Sync(?)

I would say yes, and the primary focus (https://issues.jboss.org/browse/AEROGEAR-1462)

Also, I reorganized our spec https://github.com/aerogear/aerogear.org/pull/290. We must start simple, to move forward.

> stalled, conversations started again
> is going liveoak to work on data sync?

No idea, maybe you should talk with Jay or Burr.

> Keycloak(?)
> keycloak examples mention private key in a client code

I started a discussion here http://lists.jboss.org/pipermail/keycloak-dev/2014-April/001621.html. Keycloak team don’t have any plans to change the server, but we can figure out together how to protect it, maybe, contribute back to the project.

> 1.7.0 - Late September
> 

Please add encrypted cache, that’s a douchebag but at least we have to try. Probably Webcrypto (/me looking to the sky and praying) will be ready ’til there.

> Offline(?)

+1 Also add encrypted storage.

> service workers?

This -> https://developer.mozilla.org/en-US/docs/Social_API/Service_worker_API_reference

Seems cool, but I have no idea.

> application cache is still a douchebag
> 2.0.0
>  
> ES6 modules(?) - transpile
> maybe include in 1.6/1.7
> we could leverage in custom builder, possibly
> challenge: compatibility w/ AMD / commonjs (UMD?)

YAY!

> No jQuery

Yay!

> Current Road Map
>  
> http://aerogear.org/docs/planning/roadmaps/AeroGearJS/
> 1.5.0 JIRA’s
>  
> https://issues.jboss.org/issues/?jql=project%20%3D%20AGJS%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%221.5.0%22%20ORDER%20BY%20priority%20DESC  
> Random Stuff
>  
> 2.0 collect ideas what people might struggle with?
>  
> pipelines - frameworks use usually own stuff
> improving documentation and getting started experience
>  
> getting started with AG + particular web frameworks
>  
> examples -> cookbook (complete stack)
> move tests to jasmine or something other than qunit(?) - not sure what the benefit could  
> be
>  
> https://issues.jboss.org/browse/AGJS-147
> move docs to something other than jsdoc, ex: yui doc - not sure what the benefit could be  
>  
> https://issues.jboss.org/browse/AGJS-143
> polymer components
>  
> dataManager
> dataSync
>  
> authentication buttons


Nice ideas.

>  
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev