In which version include Data Sync? 2.0 or 1.x?
by Lukáš Fryč
Hey guys,
on yesterday's Aerogear.js meeting we have discussed in which version we
should include Data Sync module. Since we are starting works on ES6
compatibility, which is one of the big features for 2.0, it make sense to
continue with Data Sync there.
What about Android and iOS SDKs? Do you plan to include new module in 2.0
or start that in 1.x and later backport to 2.0?
Cheers!
~ Lukas
11 years, 1 month
type of push notification - WP
by Majster Ahead
Hello,
is it possible to send RAW push notification using aerogear to Windows
Phone 8.1 device?
Thanks
11 years, 1 month
Re: [aerogear-dev] [keycloak-dev] Keycloak Ionic / Cordova theme
by Stian Thorgersen
Another thing we should consider is embedding of the login form. Instead of doing a full-page redirect we could allow embedding using a modal and/or iframe. In that situation you'd also want it to look slightly different than the full-page version.
----- Original Message -----
> From: "Lukáš Fryč" <lukas(a)fryc.eu>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>, keycloak-dev(a)lists.jboss.org
> Sent: Friday, 19 September, 2014 2:49:43 PM
> Subject: Re: [keycloak-dev] [aerogear-dev] Keycloak Ionic / Cordova theme
>
> I completely agree that the SSO should have same look for all applications
> using one realm.
>
>
> Yes, a customization can be partially achieved just with CSS tweaks, but it
> doesn't have to meet all requirements and further per-platform tweaks may
> be necessary.
>
> In the Ionic demo above I was to meet 70% cases by using built-in CSS
> classes. The rest had to be hard-coded. We can either extend CSS classes
> coverage or allow higher customization with e.g. theming per variants.
>
> This feature would make "theming per-platform" easier, I could achieve that
> with pure CSS/HTML tweaks and media-queries anyway.
>
> On Fri, Sep 19, 2014 at 1:40 PM, Stian Thorgersen <stian(a)redhat.com> wrote:
>
> >
> >
> > ----- Original Message -----
> > > From: "Lukáš Fryč" <lukas.fryc(a)gmail.com>
> > > To: "Stian Thorgersen" <stian(a)redhat.com>
> > > Cc: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>,
> > keycloak-dev(a)lists.jboss.org
> > > Sent: Friday, 19 September, 2014 1:30:21 PM
> > > Subject: Re: [aerogear-dev] [keycloak-dev] Keycloak Ionic / Cordova
> > theme
> > >
> > > That would be awesome,
> > >
> > > do I read correctly that it is not possible at the moment? Should I
> > create a
> > > feature request?
> >
> > Currently we can only configure the theme on a per-realm basis. With the
> > exception of css media-types there's not currently any way to modify the
> > l&f based on client (or client type).
> >
> > An alternative, which may make more sense, is to add multiple variants of
> > a theme. So for example you could have a theme that has web, android, ios,
> > etc variants. Then you have some way of specifying for the client what
> > variant it is. The reason this may make more sense is so that the SSO login
> > screen looks the same whichever application you come from.
> >
> > For example Acme Inc may have two applications (both with web, ios and
> > android variants):
> >
> > * calendar
> > * mail
> >
> > You want the login screen to be adapted to the variant of the apps. So the
> > login screens can look different if you use a browser or if you use a
> > mobile. What you don't want is the login screens to look different for the
> > calendar and mail applications, as it's SSO you're not logging in to an
> > app, you're looging in to a group of apps.
> >
> > Can we reliably detect what variant it is? Or does this have to be
> > configured in the admin console on a per-client basis?
> >
> > >
> > > On Fri, Sep 19, 2014 at 1:26 PM, Stian Thorgersen < stian(a)redhat.com >
> > wrote:
> > >
> > >
> > > ----- Original Message -----
> > > > From: "Lukáš Fryč" < lukas(a)fryc.eu >
> > > > To: "Stian Thorgersen" < stian(a)redhat.com >
> > > > Cc: "AeroGear Developer Mailing List" < aerogear-dev(a)lists.jboss.org
> > >,
> > > > keycloak-dev(a)lists.jboss.org
> > > > Sent: Friday, 19 September, 2014 1:18:19 PM
> > > > Subject: Re: [keycloak-dev] [aerogear-dev] Keycloak Ionic / Cordova
> > theme
> > > >
> > > > IMHO the SSO endpoint could either detect an incoming client (that
> > would be
> > > > rather complex)
> > > >
> > > > or simply allow user client preference. Can we allow more than one
> > theme
> > > > per realm and let the client app choohse?
> > >
> > > Not sure what you mean, we always know which client is requesting the
> > login
> > > (it's the client_id query param). The client should only be used for one
> > > variant of an application as well (so for an app that has a web, android
> > and
> > > ios variants, there should be 3 clients configured in KC). So there's no
> > > problem providing an option to override the theme on a per-client basis.
> > >
> > > >
> > > > On Fri, Sep 19, 2014 at 9:43 AM, Stian Thorgersen < stian(a)redhat.com >
> > > > wrote:
> > > >
> > > > > This raises the question. Should we allow overriding the theme on an
> > > > > per-application basis?
> > > > >
> > > > > It would allow a better integration with the app, but on the other
> > side
> > > > > does it even make sense to login to a SSO realm that way?
> > > > >
> > > > > ----- Original Message -----
> > > > > > From: "Erik Jan de Wit" < edewit(a)redhat.com >
> > > > > > To: "AeroGear Developer Mailing List" <
> > aerogear-dev(a)lists.jboss.org >
> > > > > > Cc: keycloak-dev(a)lists.jboss.org
> > > > > > Sent: Friday, 19 September, 2014 8:08:02 AM
> > > > > > Subject: Re: [aerogear-dev] Keycloak Ionic / Cordova theme
> > > > > >
> > > > > > Looks very nice, will this integrate well with the work that
> > Summers
> > > > > > did?
> > > > > >
> > > > > > On 18 Sep,2014, at 20:19 , Lukáš Fryč < lukas.fryc(a)gmail.com >
> > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Yeah and off course, the source is here:
> > > > > >
> > > > > > https://github.com/lfryc/keycloak/tree/ionic-styling
> > > > > >
> > > > > > On Thu, Sep 18, 2014 at 8:14 PM, Lukáš Fryč < lukas.fryc(a)gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hey guys,
> > > > > >
> > > > > > I've started some work on a theme for Keycloak that would include
> > Ionic
> > > > > > Framework styling.
> > > > > >
> > > > > > This makes sure that Ionic/Cordova demos that includes Keycloak has
> > > > > smooth
> > > > > > transition between application and login process / registration.
> > > > > >
> > > > > > See attached screenshots.
> > > > > >
> > > > > > It's still in early prototypal stage, so just just login,
> > registration
> > > > > and
> > > > > > social (only google) fully works so far, but others can be simply
> > > > > expanded.
> > > > > >
> > > > > > Feel free to use it in demos or so... ;-)
> > > > > >
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > ~ Lukas
> > > > > >
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev(a)lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > aerogear-dev mailing list
> > > > > > aerogear-dev(a)lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > > > >
> > > > > _______________________________________________
> > > > > keycloak-dev mailing list
> > > > > keycloak-dev(a)lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> > > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> >
>
11 years, 1 month
Re: [aerogear-dev] [keycloak-dev] Keycloak Ionic / Cordova theme
by Stian Thorgersen
----- Original Message -----
> From: "Lukáš Fryč" <lukas(a)fryc.eu>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>, keycloak-dev(a)lists.jboss.org
> Sent: Friday, 19 September, 2014 1:18:19 PM
> Subject: Re: [keycloak-dev] [aerogear-dev] Keycloak Ionic / Cordova theme
>
> IMHO the SSO endpoint could either detect an incoming client (that would be
> rather complex)
>
> or simply allow user client preference. Can we allow more than one theme
> per realm and let the client app choohse?
Not sure what you mean, we always know which client is requesting the login (it's the client_id query param). The client should only be used for one variant of an application as well (so for an app that has a web, android and ios variants, there should be 3 clients configured in KC). So there's no problem providing an option to override the theme on a per-client basis.
>
> On Fri, Sep 19, 2014 at 9:43 AM, Stian Thorgersen <stian(a)redhat.com> wrote:
>
> > This raises the question. Should we allow overriding the theme on an
> > per-application basis?
> >
> > It would allow a better integration with the app, but on the other side
> > does it even make sense to login to a SSO realm that way?
> >
> > ----- Original Message -----
> > > From: "Erik Jan de Wit" <edewit(a)redhat.com>
> > > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
> > > Cc: keycloak-dev(a)lists.jboss.org
> > > Sent: Friday, 19 September, 2014 8:08:02 AM
> > > Subject: Re: [aerogear-dev] Keycloak Ionic / Cordova theme
> > >
> > > Looks very nice, will this integrate well with the work that Summers did?
> > >
> > > On 18 Sep,2014, at 20:19 , Lukáš Fryč < lukas.fryc(a)gmail.com > wrote:
> > >
> > >
> > >
> > >
> > > Yeah and off course, the source is here:
> > >
> > > https://github.com/lfryc/keycloak/tree/ionic-styling
> > >
> > > On Thu, Sep 18, 2014 at 8:14 PM, Lukáš Fryč < lukas.fryc(a)gmail.com >
> > wrote:
> > >
> > >
> > >
> > > Hey guys,
> > >
> > > I've started some work on a theme for Keycloak that would include Ionic
> > > Framework styling.
> > >
> > > This makes sure that Ionic/Cordova demos that includes Keycloak has
> > smooth
> > > transition between application and login process / registration.
> > >
> > > See attached screenshots.
> > >
> > > It's still in early prototypal stage, so just just login, registration
> > and
> > > social (only google) fully works so far, but others can be simply
> > expanded.
> > >
> > > Feel free to use it in demos or so... ;-)
> > >
> > >
> > > Cheers,
> > >
> > > ~ Lukas
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> >
>
11 years, 1 month
Keycloak Ionic / Cordova theme
by Lukáš Fryč
Hey guys,
I've started some work on a theme for Keycloak that would include Ionic
Framework styling.
This makes sure that Ionic/Cordova demos that includes Keycloak has smooth
transition between application and login process / registration.
See attached screenshots.
It's still in early prototypal stage, so just just login, registration and
social (only google) fully works so far, but others can be simply expanded.
Feel free to use it in demos or so... ;-)
Cheers,
~ Lukas
11 years, 1 month
aerogear - wp support
by Majster Ahead
Hello,
We use aerogear to send push notification in android and iOS application,
and we need to find same technology for our windows phone application.
We are trying to use version 1.0.1. but this do not support windows phone.
Also we tried to use source code from master branch because we saw (
https://github.com/aerogear/aerogear.org/pull/384/files) that you work on
support for WP but we have problem with some maven plugins (javadoc ...)
and after deploying it. After deployment in wildfly 8 and going to
[address]/ag-push server responded with status Forbidden (403).
When do you plan to release aerogear with WP support? Or can you help us
with deployment problem?
Thank you.
--
11 years, 1 month
Aerogear.js Gang Meeting [Notes]
by Lukáš Fryč
#aerogear: Aerogear.js Gang MeetingMeeting started by lfryc at 12:43:50 UTC
(full logs
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>
).
Meeting summary
1. *Integration Tests* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:17)
1. integration tests are unstable (see travis builds) (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:29)
2. they also use several different approaches for managing and
executing external dependencies (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:29)
3. test code reusal (e.g. DataManager duplicates lot of code) (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:29)
4. https://issues.jboss.org/browse/AGJS-211 (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:48)
5. consider cross-browser testing (with Karma), Jasmine for BDD (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:44:59)
6. AGREED: lfryc: yea, what i was thinking (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:47:32)
7. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:47:41)
8. ACTION: lfryc write-up on ML about pros/cons of QUnit and Jasmine (
lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:50:06)
9. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:51:05)
10. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:51:09)
2. *DataSync/Conflict Resolution* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:51:58)
1. Dan works on creating JIRAs for Conflict Resolution (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:52:12)
2. https://github.com/aerogear/aerogear.org/pull/393 (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:52:16)
3. ACTION: lfryc lholmquist please review the PR (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:52:57)
4. continued work on Real Time DataSync in parallel (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:53:18)
5. AGREED: dbevenius (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:55:12)
6. ACTION: lholmquist create JIRAs for next steps for the realtime
sync js-client (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:56:03)
7. ACTION: dbevenius create JIRAs for extracting and moving the
DiffSync JS client/demo to aergear-js. (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:56:04)
8. I think it would be nice if it was separate. (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:57:26)
9. https://github.com/lholmquist/ag-js-ds-poc (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:58:52)
10. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
12:59:53)
11. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:01:30)
12. AGREED: (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:01:33)
13. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:01:38)
14. ACTION: lfryc review Luke's syncer (conflict resolution)
https://github.com/lholmquist/ag-js-ds-poc/blob/master/app.js (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:02:04)
15. API: consider Data Binding solution - object that is watched for
changes from outside and managed by API calls (save(), sync(), next()) -
Object.observe, Proxy (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:02:45)
16. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:04:50)
17. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:04:53)
18. AGREED: (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:04:55)
3. *ES6 modules* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:06:04)
1. i think this can be done for 1.X also. Transpiling can give us
AMD, Common.JS and Global versions (or use UMD) (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:06:12)
2. http://esnext.github.io/es6-module-transpiler/ (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:06:22)
3. Ember uses this one and is pretty nice (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:06:26)
4. https://github.com/umdjs/umd (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:06:54)
5. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:09:08)
6. ACTION: lholmquist check whether ES6 can be transpiled to AMD,
CommonJS and offer global access at same time (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:11:43)
7. Lukas was considering using Traceur for ES6 transpilation (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:12:32)
8.
https://github.com/google/traceur-compiler/wiki/LanguageFeatures#modules
(lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:12:41)
9. Luke pointed out: traceurs modules still need the traceur loader
api, so not sure i like this one (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:12:50)
10. https://github.com/lfryc/traceur-playground (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:13:55)
11. should we be creating separate repo's like the other libraries,
are the package managers mature enough for this. (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:14:41)
12. Lukas does not agree that more separate Git repositories are a
way to go unless there is specific technical need (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:14:55)
13. AGREED: , this is not a good idea (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:15:05)
14. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:15:16)
15. AGREED: (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:15:37)
4. *ES6 features* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:15:56)
1. Promises - probably pretty soon we can remove the polyfill from
being packaged with lib and just link to it (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:16:02)
2. take a look at some of the other features that are available or
easily shimmed (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:16:10)
3. https://github.com/paulmillr/es6-shim/ (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:16:15)
4. http://kangax.github.io/compat-table/es6/ (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:16:20)
5. AGREED: that sounds like a plan (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:17:23)
6. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:17:36)
7. ACTION: lfryc create a wiki page listing ES6 features we will aim
in next development (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:17:44)
8. idea: we can explore and use ES6 for new features as needed, use
transpilation to ES5 and revisit their use/shimmability/performance as we
reach beta/candidates for 2.0 (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:18:00)
9. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:18:41)
10. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:18:46)
11. concern: can we keep transpiled code as accessible to final user
on ES5 as it will be for ES6 user? (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:19:27)
5. *custom builder* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:22:56)
1. gulp might be a better fit for this on the server side (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:23:07)
2. gulp might be a better fit for this on the server side (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:23:35)
3. this depends on the modules topic, but probably should either have
an option for what you want, AMD, commonjs , Global or just package all
three together (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:23:35)
6. *possibility of removing Authentication Module from lib* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:26:25)
1.
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-android-Removing-A...
(lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:26:32)
2. Auth doesn't do anyting "security wise", the browser handles all
that anyway (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:26:39)
3. still may be beneficial for automatic data sync, server key
management (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:26:44)
4. there is an idea to implement Keycloak and Mozilla's Personas
adapters, do we want to keep this module around though? (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:26:53)
5. ACTION: lfryc start a ML discussion about removing or keeping Auth
with removed REST + mention Keycloak and Mozilla Personas (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:29:41)
7. *deprecating Pipelines* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:29:55)
1. to be removed in 2.0 (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:30:01)
2. need strategy how to fluently integrate with third-party libraries
(jQuery.ajax, AngularJS $resource / Restangular, Ember Data?) (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:30:08)
3. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:30:34)
4. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:32:39)
5. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:32:54)
6. AGREED: keep and support Pipelines in 1.x with no further
development, deprecate in 2.0 (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:33:18)
8. *Bower for dependency management* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:33:30)
1. https://github.com/aerogear/aerogear-js ? (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:35:03)
2. https://github.com/lholmquist/aerogear-js-dist (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:35:31)
3. ACTION: lholmquist look to see what external deps for aerogear.js
are now in bower (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:37:31)
4. ACTION: lholmquist think about using bower in cookbook examples (
lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:39:59)
9. *Integration with third-party libraries* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:40:25)
1. AngularJS, Ember (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:40:32)
2. Polymer?, jQuery Mobile? (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:40:32)
3. what about others? (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:40:32)
10. *Priorities for 2.0* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:45:09)
1. ES6 support: modularity, promises, ... (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:45:19)
2. focus on integration with 3rd party frameworks (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:45:22)
3. refactor build and tests (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:45:22)
4. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:46:37)
5. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:46:38)
6. AGREED: ES6 support, data sync, refactor build and tests (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:47:01)
7. AGREED: es6 modules should be sooner than later (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:47:35)
11. *When to start 2.0* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:47:42)
1. based on discussed usage of ES6 transpilation, I foresee a lot of
breaking changes that will disallow simple merges from one
branch to another
(lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:48:06)
2. at some point we have to start limit 1.x changes and focus on 2.0 (
lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:48:06)
3. ACTION: lfryc start a ML discussion about when and where to
include Data Sync module (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:49:44)
12. *use of Agile / Scrum Boards in JIRA* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:50:28)
1. Agile boads are awesome way to manage development, load and track
progress from version to version (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:50:34)
2. https://www.atlassian.com/software/jira/agile (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:50:39)
3. AGREED: we will try JIRA Agile / Scrum board (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:52:55)
13. *Documentation & Cookbooks* (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:53:48)
1. iOS team did very good job in bringing cookbooks to Aerogear.org
site (lfryc
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:54:08)
2. AGREED: (lholmquist
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:54:35)
3. AGREED: (dbevenius
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>,
13:54:40)
Meeting ended at 13:56:25 UTC (full logs
<http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...>
).
Action items
1. lfryc write-up on ML about pros/cons of QUnit and Jasmine
2. lfryc lholmquist please review the PR
3. lholmquist create JIRAs for next steps for the realtime sync js-client
4. dbevenius create JIRAs for extracting and moving the DiffSync JS
client/demo to aergear-js.
5. lfryc review Luke's syncer (conflict resolution)
https://github.com/lholmquist/ag-js-ds-poc/blob/master/app.js
6. lholmquist check whether ES6 can be transpiled to AMD, CommonJS and
offer global access at same time
7. lfryc create a wiki page listing ES6 features we will aim in next
development
8. lfryc start a ML discussion about removing or keeping Auth with
removed REST + mention Keycloak and Mozilla Personas
9. lholmquist look to see what external deps for aerogear.js are now in
bower
10. lholmquist think about using bower in cookbook examples
11. lfryc start a ML discussion about when and where to include Data
Sync module
Action items, by person
1. dbevenius
1. dbevenius create JIRAs for extracting and moving the DiffSync JS
client/demo to aergear-js.
2. lfryc
1. lfryc write-up on ML about pros/cons of QUnit and Jasmine
2. lfryc lholmquist please review the PR
3. lfryc review Luke's syncer (conflict resolution)
https://github.com/lholmquist/ag-js-ds-poc/blob/master/app.js
4. lfryc create a wiki page listing ES6 features we will aim in next
development
5. lfryc start a ML discussion about removing or keeping Auth with
removed REST + mention Keycloak and Mozilla Personas
6. lfryc start a ML discussion about when and where to include Data
Sync module
3. lholmquist
1. lfryc lholmquist please review the PR
2. lholmquist create JIRAs for next steps for the realtime sync
js-client
3. lfryc review Luke's syncer (conflict resolution)
https://github.com/lholmquist/ag-js-ds-poc/blob/master/app.js
4. lholmquist check whether ES6 can be transpiled to AMD, CommonJS
and offer global access at same time
5. lholmquist look to see what external deps for aerogear.js are now
in bower
6. lholmquist think about using bower in cookbook examples
People present (lines said)
1. lfryc (277)
2. lholmquist (103)
3. dbevenius (36)
4. jbossbot (8)
5. jbott (6)
6. aerobot (5)
7. corinnekrych (2)
Generated by MeetBot <http://wiki.debian.org/MeetBot> 0.1.4.
11 years, 1 month
