From ozizka at redhat.com Tue Nov 1 00:38:10 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Tue, 1 Nov 2016 05:38:10 +0100
Subject: [windup-dev] @GraphAdjacency impl
Message-ID: <bc38940b-8de4-0269-8d6d-c6d794ca55b1@redhat.com>
Hi,
GraphAdjacency has this in the impl:
return this.http.get(url).map((vertices:any) => {
return graphService.fromJSON(vertices[0],
target.http);
});
What's the idea behind this.http vs. target.http?
`target` is the class where the decorator is present, and `this` is the
instance.
I can understand that it needs to be somewhere, but then why pass it in
the parameter?
And how does the value get to the model class? fromJSON() sets it on the
instance.
Ondra
--
--
Ondrej Zizka, Windup project, Brno
From jsightle at redhat.com Tue Nov 1 11:05:02 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Tue, 1 Nov 2016 11:05:02 -0400
Subject: [windup-dev] @GraphAdjacency impl
In-Reply-To: <bc38940b-8de4-0269-8d6d-c6d794ca55b1@redhat.com>
References: <bc38940b-8de4-0269-8d6d-c6d794ca55b1@redhat.com>
Message-ID: <16c2a32d-86e1-a386-9d06-6589a062cfd9@redhat.com>
Try it and see. :) Although, if I'm not mistaken, the use of
"target.http" in the method call is wrong.
On 11/01/2016 12:38 AM, Ondrej Zizka wrote:
> Hi,
>
> GraphAdjacency has this in the impl:
>
> return this.http.get(url).map((vertices:any) => {
> return graphService.fromJSON(vertices[0],
> target.http);
> });
>
> What's the idea behind this.http vs. target.http?
>
> `target` is the class where the decorator is present, and `this` is the
> instance.
>
> I can understand that it needs to be somewhere, but then why pass it in
> the parameter?
> And how does the value get to the model class? fromJSON() sets it on the
> instance.
>
> Ondra
>
From mnovotny at redhat.com Fri Nov 4 08:11:56 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 4 Nov 2016 13:11:56 +0100
Subject: [windup-dev] Windup 3.0.0.Alpha1 tagged and released
Message-ID: <bd7ba093-d816-d7e5-018b-42d0bd9ac051@redhat.com>
Windup 3.0.0.Alpha1 was tagged and uploaded to JBoss.org repository
(synchronization to Maven Central is in progress automatically)
What have been released?
Windup core
Windup rulesets
Windup distribution
Windup Maven plugin
Get released bits a warm welcome and use it while it is hot.
P.S. this release is the first signal of 3.x.
--
Marek Novotny
--
Windup team member
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
From ozizka at redhat.com Tue Nov 8 21:01:18 2016
From: ozizka at redhat.com (Ondrej Zizka)
Date: Wed, 9 Nov 2016 03:01:18 +0100
Subject: [windup-dev] NavigationService
Message-ID: <2fbf4eb9-cd0e-1745-191b-1e3d3ab862b4@redhat.com>
Devs.
In Angular, I miss a good routing mechanism like other web frameworks have
Angular:
editApplication(application: RegisteredApplication) {
this._router.navigate(['/edit-application', application.id]);
}
Other framework:
public void editApplication(Application application) {
setResponsePage(ApplicationPage.class, new
PageParameters().add("app", application));
}
Which is often shortened, if the components implements an interface,
setResponsePage(ApplicationPage.navigate(application));
How about creating a Navigator which would work similarly.
editApplication(application: RegisteredApplication) {
this._navigator.navigate(ApplicationComponent, application);
}
The advantage is that it's type safe and the constants are at a single
point rather than scattered across the web app (or at the component's
class).
WDYT?
Ondra
--
--
Ondrej Zizka, Windup project, Brno
From dklingen at redhat.com Wed Nov 9 04:11:29 2016
From: dklingen at redhat.com (David Klingenberg)
Date: Wed, 9 Nov 2016 10:11:29 +0100
Subject: [windup-dev] NavigationService
In-Reply-To: <2fbf4eb9-cd0e-1745-191b-1e3d3ab862b4@redhat.com>
References: <2fbf4eb9-cd0e-1745-191b-1e3d3ab862b4@redhat.com>
Message-ID: <CAMB-fkpw1xCndcdf1VXvw=A6KVPN8mwRHnjAw8rnSp5a2x+muw@mail.gmail.com>
I like the idea.
I'm not fan of angular router either.
David
On Wed, Nov 9, 2016 at 3:01 AM, Ondrej Zizka <ozizka at redhat.com> wrote:
> Devs.
>
> In Angular, I miss a good routing mechanism like other web frameworks have
>
> Angular:
>
> editApplication(application: RegisteredApplication) {
> this._router.navigate(['/edit-application', application.id]);
> }
>
> Other framework:
>
> public void editApplication(Application application) {
> setResponsePage(ApplicationPage.class, new
> PageParameters().add("app", application));
> }
>
> Which is often shortened, if the components implements an interface,
>
> setResponsePage(ApplicationPage.navigate(application));
>
>
> How about creating a Navigator which would work similarly.
>
> editApplication(application: RegisteredApplication) {
> this._navigator.navigate(ApplicationComponent, application);
> }
>
> The advantage is that it's type safe and the constants are at a single
> point rather than scattered across the web app (or at the component's
> class).
>
> WDYT?
>
> 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/20161109/69269733/attachment.html
From jsightle at redhat.com Wed Nov 9 12:00:05 2016
From: jsightle at redhat.com (Jess Sightler)
Date: Wed, 9 Nov 2016 12:00:05 -0500
Subject: [windup-dev] NavigationService
In-Reply-To: <CAMB-fkpw1xCndcdf1VXvw=A6KVPN8mwRHnjAw8rnSp5a2x+muw@mail.gmail.com>
References: <2fbf4eb9-cd0e-1745-191b-1e3d3ab862b4@redhat.com>
<CAMB-fkpw1xCndcdf1VXvw=A6KVPN8mwRHnjAw8rnSp5a2x+muw@mail.gmail.com>
Message-ID: <8edc7425-0b15-a307-e3a3-2718c44ec1c3@redhat.com>
As long as you aren't doing lazy loading, I would think that an API
similar to the one mentioned below would be fairly easy. The destination
component would simply have to specify a builder interface for building
the array that gets passed to "navigate".
I don't see this as having much to do with the router itself.
On 11/09/2016 04:11 AM, David Klingenberg wrote:
> I like the idea.
>
> I'm not fan of angular router either.
>
>
> David
>
> On Wed, Nov 9, 2016 at 3:01 AM, Ondrej Zizka <ozizka at redhat.com
> <mailto:ozizka at redhat.com>> wrote:
>
> Devs.
>
> In Angular, I miss a good routing mechanism like other web
> frameworks have
>
> Angular:
>
> editApplication(application: RegisteredApplication) {
> this._router.navigate(['/edit-application',
> application.id <http://application.id>]);
> }
>
> Other framework:
>
> public void editApplication(Application application) {
> setResponsePage(ApplicationPage.class, new
> PageParameters().add("app", application));
> }
>
> Which is often shortened, if the components implements an interface,
>
> setResponsePage(ApplicationPage.navigate(application));
>
>
> How about creating a Navigator which would work similarly.
>
> editApplication(application: RegisteredApplication) {
> this._navigator.navigate(ApplicationComponent, application);
> }
>
> The advantage is that it's type safe and the constants are at a single
> point rather than scattered across the web app (or at the component's
> class).
>
> WDYT?
>
> Ondra
>
>
>
> --
> --
> Ondrej Zizka, Windup project, Brno
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
> <https://lists.jboss.org/mailman/listinfo/windup-dev>
>
>
>
>
> _______________________________________________
> 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/20161109/2801655e/attachment-0001.html
From mnovotny at redhat.com Fri Nov 25 03:26:09 2016
From: mnovotny at redhat.com (Marek Novotny)
Date: Fri, 25 Nov 2016 09:26:09 +0100
Subject: [windup-dev] Access to https://vimeo.com/jbossdeveloper and
developers.redhat.com
Message-ID: <c714a92f-5035-5270-4c71-411b555850a2@redhat.com>
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