From mnovotny at redhat.com Mon Dec 5 04:57:40 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Mon, 5 Dec 2016 10:57:40 +0100
Subject: [windup-dev] [WARNING] Windup-web master branch switched NPM with
YARN
In-Reply-To: <8fa9c764-ebef-3cdb-dc7f-856b0c3bd51f@redhat.com>
References: <8fa9c764-ebef-3cdb-dc7f-856b0c3bd51f@redhat.com>
Message-ID: <494f7903-0c7e-1757-e727-dcb0a304e008@redhat.com>
FYI
-------- Forwarded Message --------
Subject: [WARNING] Windup-web master branch switched NPM with YARN
Date: Mon, 5 Dec 2016 10:56:56 +0100
From: Marek Novotny <mnovotny at redhat.com>
Reply-To: mnovotny at redhat.com
Organization: Redhat
To: windup-eng at redhat.com
I merged the PR to use Yarn package manager from David and from now you need to use YARN instead of NPM
Run
npm install -g phantomjs-prebuilt
and
npm install -g yarn
Instructions are updated in windup-web root README.md too.
--
Marek Novotny
--
Windup team member
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From lincoln at redhat.com Mon Dec 12 17:20:33 2016
From: lincoln at redhat.com (Lincoln Baxter)
Date: Mon, 12 Dec 2016 17:20:33 -0500
Subject: [windup-dev] Access to https://vimeo.com/jbossdeveloper and
developers.redhat.com
In-Reply-To: <c714a92f-5035-5270-4c71-411b555850a2@redhat.com>
References: <c714a92f-5035-5270-4c71-411b555850a2@redhat.com>
Message-ID: <CAOB=qPWKggemJGWgdyKhLv6+nkEid0tNdviH8B61mFx=rbkqPQ@mail.gmail.com>
Hey Marek,
I am trying to track down the instructions for how to make this happen.
Have you gotten this taken care of yet?
Here is what I've found so far:
Checklist/Process for Submitting Videos
-
Upload video to Red Hat Developers - mark as private
-
Include:
-
Title
-
Description
-
Tags
-
Send contributors at redhat.com email with link to video, social post, blog
post if needed
-
Send personal social handles
-
Blog include:
-
Title
-
Tags
-
RHD team will review and approve video/blog and promote
-
Author to promote video and manage comments
I'm including the other members of my team who may be able to provide
additional information. (Emily provided the info above.) Emily, do you know
if users need special access to upload a video to the RHD account on
YouTube?
Thanks,
---
Lincoln Baxter, III
Chief Editor, Red Hat Developers
http://developers.redhat.com
On Fri, Nov 25, 2016 at 3:26 AM, Marek Novotny <mnovotny at redhat.com> wrote:
> Hi Lincoln and Pete,
>
> we have something (screencasts) to share not only on WindUp Blog space
> https://developer.jboss.org/en/windup/content?filterID=
> contentstatus%5Bpublished%5D~objecttype~objecttype%5Bblogpost%5D
>
> Could you give us a advice how to include our video content on
> https://vimeo.com/jbossdeveloper and http://developers.redhat.com/blog
> or where is a proper place to host our screencasts?
>
> Cheers,
>
>
> --
> Marek Novotny
> --
> Windup team member
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20161212/31df1fb8/attachment.html
From lincoln at redhat.com Mon Dec 12 17:21:23 2016
From: lincoln at redhat.com (Lincoln Baxter)
Date: Mon, 12 Dec 2016 17:21:23 -0500
Subject: [windup-dev] Access to https://vimeo.com/jbossdeveloper and
developers.redhat.com
In-Reply-To: <CAOB=qPWKggemJGWgdyKhLv6+nkEid0tNdviH8B61mFx=rbkqPQ@mail.gmail.com>
References: <c714a92f-5035-5270-4c71-411b555850a2@redhat.com>
<CAOB=qPWKggemJGWgdyKhLv6+nkEid0tNdviH8B61mFx=rbkqPQ@mail.gmail.com>
Message-ID: <CAOB=qPV45atCRJ7ZrWG_6BkJcyZ-VCtJCRCPN+xNuDSt322-VQ@mail.gmail.com>
Okay, a little more info.
It sounds like you'll need to have a discussion with Mike and our team to
go over our policies and requirements for participating in the YouTube
channel.
Mike?
Thanks,
---
Lincoln Baxter, III
Chief Editor, Red Hat Developers
http://developers.redhat.com
On Mon, Dec 12, 2016 at 5:20 PM, Lincoln Baxter <lincoln at redhat.com> wrote:
> Hey Marek,
>
> I am trying to track down the instructions for how to make this happen.
> Have you gotten this taken care of yet?
>
> Here is what I've found so far:
>
>
> Checklist/Process for Submitting Videos
>
> -
>
> Upload video to Red Hat Developers - mark as private
> -
>
> Include:
> -
>
> Title
> -
>
> Description
> -
>
> Tags
> -
>
> Send contributors at redhat.com email with link to video, social post,
> blog post if needed
> -
>
> Send personal social handles
> -
>
> Blog include:
> -
>
> Title
> -
>
> Tags
> -
>
> RHD team will review and approve video/blog and promote
> -
>
> Author to promote video and manage comments
>
>
> I'm including the other members of my team who may be able to provide
> additional information. (Emily provided the info above.) Emily, do you know
> if users need special access to upload a video to the RHD account on
> YouTube?
>
> Thanks,
>
> ---
> Lincoln Baxter, III
> Chief Editor, Red Hat Developers
> http://developers.redhat.com
>
> On Fri, Nov 25, 2016 at 3:26 AM, Marek Novotny <mnovotny at redhat.com>
> wrote:
>
>> Hi Lincoln and Pete,
>>
>> we have something (screencasts) to share not only on WindUp Blog space
>> https://developer.jboss.org/en/windup/content?filterID=conte
>> ntstatus%5Bpublished%5D~objecttype~objecttype%5Bblogpost%5D
>>
>> Could you give us a advice how to include our video content on
>> https://vimeo.com/jbossdeveloper and http://developers.redhat.com/blog
>> or where is a proper place to host our screencasts?
>>
>> Cheers,
>>
>>
>> --
>> Marek Novotny
>> --
>> Windup team member
>>
>> Red Hat Czech s.r.o.
>> Purkynova 99
>> 612 45 Brno
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20161212/73449da8/attachment-0001.html
From ozizka at redhat.com Tue Dec 13 21:47:43 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 14 Dec 2016 03:47:43 +0100
Subject: [windup-dev] Let's target ES 6?
Message-ID: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
Could we target ES 6?
Currently we can't use certain useful things like iterators, see
https://github.com/Microsoft/TypeScript/issues/6842
and
https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Map#Iterating_Maps_with_for..of
Are we assuming someone running 2+ years old browsers?
If yes, someone mentioned targetting ES 6 and then Babel to solve that.
Ondra
--
--
Ondrej Zizka, Windup project, Brno
From ozizka at redhat.com Wed Dec 14 04:44:42 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 14 Dec 2016 10:44:42 +0100
Subject: [windup-dev] JS tip: You can delete from a collection while
iterating
Message-ID: <95517850-e8b7-76c3-e488-d108106d28e8@redhat.com>
For instance, Set:
http://stackoverflow.com/questions/28306756/is-it-safe-to-delete-elements-in-a-set-while-iterating-with-for-of
--
--
Ondrej Zizka, Windup project, Brno
From dklingen at redhat.com Wed Dec 14 04:52:39 2016
From: dklingen at redhat.com (David Klingenberg)
Date: Wed, 14 Dec 2016 10:52:39 +0100
Subject: [windup-dev] Let's target ES 6?
In-Reply-To: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
References: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
Message-ID: <CAMB-fkpLvdN3snGweGHm2csgmoHkmw6hGGX=g3nBQUE7CeWKWQ@mail.gmail.com>
Well,
if we want to target ES6 I think we should do it directly using TypeScript.
IMHO we should avoid using Babel, because it would make our source maps
useless and debugging more difficult.
I checked browser support of ES6 and it seems good.
David
On Wed, Dec 14, 2016 at 3:47 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Could we target ES 6?
>
>
> Currently we can't use certain useful things like iterators, see
> https://github.com/Microsoft/TypeScript/issues/6842
>
> and
> https://developer.mozilla.org/en/docs/Web/JavaScript/
> Reference/Global_Objects/Map#Iterating_Maps_with_for..of
>
>
> Are we assuming someone running 2+ years old browsers?
> If yes, someone mentioned targetting ES 6 and then Babel to solve that.
>
> Ondra
>
> --
> --
> Ondrej Zizka, Windup project, Brno
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20161214/a3f7c66e/attachment.html
From ozizka at redhat.com Wed Dec 14 05:03:07 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 14 Dec 2016 11:03:07 +0100
Subject: [windup-dev] Caching - global or vertex only? And what to cache?
Message-ID: <5bf5b13f-b771-3ede-a653-6818ccaab1d0@redhat.com>
Hi team,
regarding graph REST HTTP requests caching - should it be global or
rather per-vertex (per-model)?
I started coding a global solution. If another model needs the same
data, it will request from the same URL. I see no reason not to return
the same object.
Another question is what to cache. Due to how it's currently done, the
getter is supposed to return Observable<...Model>. There are these options:
1) To cache an Observable which will wrap HTTP Observable. I don't know
yet whether this will cause re-sending HTTP request for another
subscriber. It will solve the Angular's change scanning, though, which
is the bigger problem. Also, RxJS's cache() operator could be used to
cache the HTTP response internally.
2) It can also resolve the Observable chain, and store the result into
the cache asynchronously.
So - when Angular would ask soon after, it would result in another
request (maybe?); when called later, it would return the already
available cached result.
This would reduce the HTTP requests, but would not necessarily
solve the Angular change scanning.
3) A combination of 1) and 2), which would cache
* the Observables from 1) internally, so that the getter gets the
same object each time,
* the results from 2) so that the subsequent requests to the same
URL don't generate another HTTP request, with some timeout so the page
won't get staled.
This one is a bit complicated but I think with some RxJS magic it
can be done.
Ondra
--
--
Ondrej Zizka, Windup project, Brno
From dklingen at redhat.com Wed Dec 14 10:34:18 2016
From: dklingen at redhat.com (David Klingenberg)
Date: Wed, 14 Dec 2016 16:34:18 +0100
Subject: [windup-dev] Caching - global or vertex only? And what to cache?
In-Reply-To: <5bf5b13f-b771-3ede-a653-6818ccaab1d0@redhat.com>
References: <5bf5b13f-b771-3ede-a653-6818ccaab1d0@redhat.com>
Message-ID: <CAMB-fkpTGb9zbtfmhdifh3OANjQcE+pPCrx8ts_bfrRsbMRtLA@mail.gmail.com>
I'm for combination.
I think we should have some global caching solution. And the best option
would be 3. We used to have similar caching in my previous company, so if
you want, I could help you with that.
David
On Wed, Dec 14, 2016 at 11:03 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Hi team,
>
> regarding graph REST HTTP requests caching - should it be global or
> rather per-vertex (per-model)?
> I started coding a global solution. If another model needs the same
> data, it will request from the same URL. I see no reason not to return
> the same object.
>
>
> Another question is what to cache. Due to how it's currently done, the
> getter is supposed to return Observable<...Model>. There are these options:
>
> 1) To cache an Observable which will wrap HTTP Observable. I don't know
> yet whether this will cause re-sending HTTP request for another
> subscriber. It will solve the Angular's change scanning, though, which
> is the bigger problem. Also, RxJS's cache() operator could be used to
> cache the HTTP response internally.
>
> 2) It can also resolve the Observable chain, and store the result into
> the cache asynchronously.
> So - when Angular would ask soon after, it would result in another
> request (maybe?); when called later, it would return the already
> available cached result.
> This would reduce the HTTP requests, but would not necessarily
> solve the Angular change scanning.
>
> 3) A combination of 1) and 2), which would cache
> * the Observables from 1) internally, so that the getter gets the
> same object each time,
> * the results from 2) so that the subsequent requests to the same
> URL don't generate another HTTP request, with some timeout so the page
> won't get staled.
> This one is a bit complicated but I think with some RxJS magic it
> can be done.
>
> Ondra
>
> --
> --
> Ondrej Zizka, Windup project, Brno
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20161214/e050fca4/attachment.html
From jsightle at redhat.com Thu Dec 15 12:06:15 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 15 Dec 2016 12:06:15 -0500
Subject: [windup-dev] Let's target ES 6?
In-Reply-To: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
References: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
Message-ID: <314f56ce-31b7-1c03-e965-ef3e03c81e1d@redhat.com>
Can't you just use map.forEach((value, index, map) => { }) ?
I think IE11 still doesn't support ES6 very well, does it? I am a little
concerned with removing all support for IE browsers.
On 12/13/2016 09:47 PM, Ondrej Zizka wrote:
> Could we target ES 6?
>
>
> Currently we can't use certain useful things like iterators, see
> https://github.com/Microsoft/TypeScript/issues/6842
>
> and
> https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Map#Iterating_Maps_with_for..of
>
>
> Are we assuming someone running 2+ years old browsers?
> If yes, someone mentioned targetting ES 6 and then Babel to solve that.
>
> Ondra
>
From jsightle at redhat.com Thu Dec 15 12:07:52 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 15 Dec 2016 12:07:52 -0500
Subject: [windup-dev] JS tip: You can delete from a collection while
iterating
In-Reply-To: <95517850-e8b7-76c3-e488-d108106d28e8@redhat.com>
References: <95517850-e8b7-76c3-e488-d108106d28e8@redhat.com>
Message-ID: <54f5aac8-6b9c-1bc4-b4f3-c903b7946293@redhat.com>
Nice, that is helpful. I had been assuming that these were limited
similarly to Java iterators.
On 12/14/2016 04:44 AM, Ondrej Zizka wrote:
> For instance, Set:
>
> http://stackoverflow.com/questions/28306756/is-it-safe-to-delete-elements-in-a-set-while-iterating-with-for-of
>
>
From ozizka at redhat.com Thu Dec 22 13:33:33 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Thu, 22 Dec 2016 19:33:33 +0100
Subject: [windup-dev] Let's target ES 6?
In-Reply-To: <314f56ce-31b7-1c03-e965-ef3e03c81e1d@redhat.com>
References: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
<314f56ce-31b7-1c03-e965-ef3e03c81e1d@redhat.com>
Message-ID: <46fff168-eefa-9410-7e75-09379183f27a@redhat.com>
You can't break from forEach... except an exception which is "fuj" [1].
Ondra
[1] https://translate.google.com/#auto/en/fuj
--
Ondrej Zizka, Windup project, Brno
On 15.12.2016 18:06, Jess Sightler wrote:
> Can't you just use map.forEach((value, index, map) => { }) ?
>
> I think IE11 still doesn't support ES6 very well, does it? I am a little
> concerned with removing all support for IE browsers.
>
> On 12/13/2016 09:47 PM, Ondrej Zizka wrote:
>> Could we target ES 6?
>>
>>
>> Currently we can't use certain useful things like iterators, see
>> https://github.com/Microsoft/TypeScript/issues/6842
>>
>> and
>> https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Map#Iterating_Maps_with_for..of
>>
>>
>> Are we assuming someone running 2+ years old browsers?
>> If yes, someone mentioned targetting ES 6 and then Babel to solve that.
>>
>> Ondra
>>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
From jsightle at redhat.com Thu Dec 22 15:55:01 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Thu, 22 Dec 2016 15:55:01 -0500
Subject: [windup-dev] Let's target ES 6?
In-Reply-To: <46fff168-eefa-9410-7e75-09379183f27a@redhat.com>
References: <51d80c49-a9cb-3274-4261-0e0727c1a1dc@redhat.com>
<314f56ce-31b7-1c03-e965-ef3e03c81e1d@redhat.com>
<46fff168-eefa-9410-7e75-09379183f27a@redhat.com>
Message-ID: <f43eea4d-3e20-4654-2e29-4b903f20b995@redhat.com>
Oh, that is a good point.
Anyway, I would be completely in favor of this if we can get
confirmation on the supported browser list.
On 12/22/2016 01:33 PM, Ondrej Zizka wrote:
> You can't break from forEach... except an exception which is "fuj" [1].
>
> Ondra
>
>
> [1] https://translate.google.com/#auto/en/fuj
>
>
>
> --
> Ondrej Zizka, Windup project, Brno
>
> On 15.12.2016 18:06, Jess Sightler wrote:
>> Can't you just use map.forEach((value, index, map) => { }) ?
>>
>> I think IE11 still doesn't support ES6 very well, does it? I am a little
>> concerned with removing all support for IE browsers.
>>
>> On 12/13/2016 09:47 PM, Ondrej Zizka wrote:
>>> Could we target ES 6?
>>>
>>>
>>> Currently we can't use certain useful things like iterators, see
>>> https://github.com/Microsoft/TypeScript/issues/6842
>>>
>>> and
>>> https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Map#Iterating_Maps_with_for..of
>>>
>>>
>>>
>>> Are we assuming someone running 2+ years old browsers?
>>> If yes, someone mentioned targetting ES 6 and then Babel to solve that.
>>>
>>> Ondra
>>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>