Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!

[Martin Grigorov]

Hi Jenny,

On Mon, Aug 22, 2016 at 3:30 AM, Jenny Brown  wrote:

> About 5 years ago, I created wicket-source, a set of extensions that let
> you inspect a wicket component in your browser, and click a button to go to
> that line of your source code in Eclipse.
>

Thank you once again for this plugin!
I've used every day since you released it the first time!


>
> As time went on, the browser extensions drifted out of compatibility, to
> the sadness of those who used them.  Eventually even the workarounds
> stopped working.
>
> So this weekend, I update the Chrome wicket-source extension for Chrome 48
> (updated in chrome web store) and updated the Eclipse plugin (jar is on
> github) for Eclipse Neon.   (Yeah!!!)
>

I use https://github.com/cleiter/wicketsource-contextmenu for Chrome.
I like it better because it requires less clicks to do the job


>
> Screenshots, details, and download links are on the wiki:
>
> https://github.com/jennybrown8/wicket-source/wiki
>
> The server-side wicket application module still works as before, and is
> available for Wicket 7.
>

It it time to make a release for Wicket 8 (8.0.0-M1)!
I think it should work without any modifications but still it will be
better to have version for 8.x so there won't be need to add exclusion for
Wicket 7.x.
I'll send you a PR in the coming days!


>
> The Firefox plugin was deprecated, and requires a full rewrite from
> scratch, so it's not usable for now.  I'll try to come back to this when
> Firefox Web Extensions and Firebug 3 stabilize and provide the APIs I need
> for it to work.
>
> I forked the project when I separated from the employer where it was
> created, so there is a new package name for the extensions that have been
> updated.  At this time, the maven coordinates for the web application
> server-side plugin remain with the old name.  The wiki documents all of
> this.
>
> I looked at Eclipse Marketplace and the self-hosting was confusing; if
> someone familiar with that wants to pair with me to try to get it properly
> submitted, I can try.  I don't have my own hosting service for the
> binaries.
>
> Jenny Brown
>


I have one more idea for improvement which I'll explain in another issue/PR.

Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!

[Martijn Dashorst]

WOOHOO!

Great work Jenny!

Martijn


On Mon, Aug 22, 2016 at 3:30 AM, Jenny Brown  wrote:
> About 5 years ago, I created wicket-source, a set of extensions that let
> you inspect a wicket component in your browser, and click a button to go to
> that line of your source code in Eclipse.
>
> As time went on, the browser extensions drifted out of compatibility, to
> the sadness of those who used them.  Eventually even the workarounds
> stopped working.
>
> So this weekend, I update the Chrome wicket-source extension for Chrome 48
> (updated in chrome web store) and updated the Eclipse plugin (jar is on
> github) for Eclipse Neon.   (Yeah!!!)
>
> Screenshots, details, and download links are on the wiki:
>
> https://github.com/jennybrown8/wicket-source/wiki
>
> The server-side wicket application module still works as before, and is
> available for Wicket 7.
>
> The Firefox plugin was deprecated, and requires a full rewrite from
> scratch, so it's not usable for now.  I'll try to come back to this when
> Firefox Web Extensions and Firebug 3 stabilize and provide the APIs I need
> for it to work.
>
> I forked the project when I separated from the employer where it was
> created, so there is a new package name for the extensions that have been
> updated.  At this time, the maven coordinates for the web application
> server-side plugin remain with the old name.  The wiki documents all of
> this.
>
> I looked at Eclipse Marketplace and the self-hosting was confusing; if
> someone familiar with that wants to pair with me to try to get it properly
> submitted, I can try.  I don't have my own hosting service for the binaries.
>
> Jenny Brown



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!

[Martijn Dashorst]

On Mon, Aug 22, 2016 at 3:30 AM, Jenny Brown  wrote:
> I looked at Eclipse Marketplace and the self-hosting was confusing; if
> someone familiar with that wants to pair with me to try to get it properly
> submitted, I can try.  I don't have my own hosting service for the binaries.

Our company's m2-settings plugin is hosted on github, so you might look at that.

https://github.com/topicusonderwijs/m2e-settings


Martijn


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!

[Andrea Del Bene]

Thank you VERY much Jenny!


On 22/08/2016 03:30, Jenny Brown wrote:

About 5 years ago, I created wicket-source, a set of extensions that let
you inspect a wicket component in your browser, and click a button to go to
that line of your source code in Eclipse.

As time went on, the browser extensions drifted out of compatibility, to
the sadness of those who used them.  Eventually even the workarounds
stopped working.

So this weekend, I update the Chrome wicket-source extension for Chrome 48
(updated in chrome web store) and updated the Eclipse plugin (jar is on
github) for Eclipse Neon.   (Yeah!!!)

Screenshots, details, and download links are on the wiki:

 https://github.com/jennybrown8/wicket-source/wiki

The server-side wicket application module still works as before, and is
available for Wicket 7.

The Firefox plugin was deprecated, and requires a full rewrite from
scratch, so it's not usable for now.  I'll try to come back to this when
Firefox Web Extensions and Firebug 3 stabilize and provide the APIs I need
for it to work.

I forked the project when I separated from the employer where it was
created, so there is a new package name for the extensions that have been
updated.  At this time, the maven coordinates for the web application
server-side plugin remain with the old name.  The wiki documents all of
this.

I looked at Eclipse Marketplace and the self-hosting was confusing; if
someone familiar with that wants to pair with me to try to get it properly
submitted, I can try.  I don't have my own hosting service for the binaries.

Jenny Brown




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Visibility/Enability change event

[guillaume.mary]

Hi,

I'm a Wicket user since several years and I regularly lack a feature in
Wicket : component state change.
I know that Event/Sink exists but it doesn't feets my need : when I use a
component that wraps others from a third party, I need it to be hidden or
disabled when *all* subcomponents are. Since subcomponents are third party
one I can hardly change them, so when they hide themselves it becomes very
tricky to hide the wrapping component. I think it would be smarter (in term
of code and complexity/readability) if I had a kind of visibility listener
without the need to override components. For my case (visibility and
enability) I thought that a Behavior could do that if it was notified of
component "flag" change, but the "flag" attribute contains much more
information (more internal management) that I need so I'm not sure that the
good solution.

Event/Sink is not a good solution for me since it requires that third party
components expose there changes and that's rarely the case.

Finally, if it can help the discussion, another use case would be to get
modelChanging event without overriding components (since they also come from
third party) because we need to track every model change for security
reason.

I use Wicket 6, but I didn't see any change of those points in Wicket 7 or 8
in release notes.

Thanks for ideas and advices.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Visibility/Enability change event

[Sven Meier]

Why not override #onConfigure() and check the visibility of the child
components from there?

Regards
Sven

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352p4675353.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!

[Jenny Brown]

On Mon, Aug 22, 2016 at 2:13 AM, Martin Grigorov 
wrote:

> Hi Jenny,
>
> On Mon, Aug 22, 2016 at 3:30 AM, Jenny Brown 
> wrote:
>
> > About 5 years ago, I created wicket-source, a set of extensions that let
> > you inspect a wicket component in your browser, and click a button to go
> to
> > that line of your source code in Eclipse.
> >
>
> Thank you once again for this plugin!
> I've used every day since you released it the first time!
>
>
Wow! I'm glad it was so helpful!



>
> >
> > As time went on, the browser extensions drifted out of compatibility, to
> > the sadness of those who used them.  Eventually even the workarounds
> > stopped working.
> >
> > So this weekend, I update the Chrome wicket-source extension for Chrome
> 48
> > (updated in chrome web store) and updated the Eclipse plugin (jar is on
> > github) for Eclipse Neon.   (Yeah!!!)
> >
>
> I use https://github.com/cleiter/wicketsource-contextmenu for Chrome.
> I like it better because it requires less clicks to do the job
>
>
Ok that's cool!  I hadn't seen that one before.  I might be able to include
that kind of feature in my plugin.  I'll have to explore a bit.



>
> >
> > Screenshots, details, and download links are on the wiki:
> >
> > https://github.com/jennybrown8/wicket-source/wiki
> >
> > The server-side wicket application module still works as before, and is
> > available for Wicket 7.
> >
>
> It it time to make a release for Wicket 8 (8.0.0-M1)!
> I think it should work without any modifications but still it will be
> better to have version for 8.x so there won't be need to add exclusion for
> Wicket 7.x.
> I'll send you a PR in the coming days!
>
>
That'd be great.  One thing to pay attention to is whether the stacktrace
(that it filters through to identify the line of code) might have changed
any as Wicket changed.  Usually it's fine.  Once in a while the structure
changes a bit.

I no longer have access to publish under the net.ftlines maven
coordinates.  I'll publish under com.github.jennybrown8.wicket-source
instead.  Although I need to get set up with Sonatype / maven central
publishing from the ground up, so that might be a little slow.

Thanks for the help!


Jenny

Re: Visibility/Enability change event

[guillaume.mary]

Well, in my use case, subcomponents use a Behavior#onConfigure() to change
their own visibility, and this method is called after
Component#onConfigure(), hence the visibility state is not uptodate.

Le 22 août 2016 13:54, "Sven Meier [via Apache Wicket]" <
ml-node+s1842946n4675353...@n4.nabble.com> a écrit :

> Why not override #onConfigure() and check the visibility of the child
> components from there?
>
> Regards
> Sven
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-wicket.1842946.n4.nabble.com/Visibility-
> Enability-change-event-tp4675352p4675353.html
> To unsubscribe from Visibility/Enability change event, click here
> 
> .
> NAML
> 
>


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352p4675360.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Visibility/Enability change event

[Sven Meier]

You can call #configure() on the subcomponents from your #onConfigure().

Have fun
Sven

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352p4675362.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Visibility/Enability change event

[guillaume.mary]

Thanks i'll give it a try.

Le 22 août 2016 18:45, "Sven Meier [via Apache Wicket]" <
ml-node+s1842946n4675362...@n4.nabble.com> a écrit :

> You can call #configure() on the subcomponents from your #onConfigure().
>
> Have fun
> Sven
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-wicket.1842946.n4.nabble.com/Visibility-
> Enability-change-event-tp4675352p4675362.html
> To unsubscribe from Visibility/Enability change event, click here
> 
> .
> NAML
> 
>


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Visibility-Enability-change-event-tp4675352p4675363.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org