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

[joedenly]

Thanks for sharing this as i am getting very helpful from this plugin as
chrome allowed to add this.  https://errorcode0x.com/error-code-0x80070002/
  helped me to get this
plugin so far.

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
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!

[Joachim Rohde]

For the NetBeans users who couldn't use this great tool till now: I just 
uploaded a NetBeans plugin under
https://github.com/JoachimRohde/NBWicketSourcePlugin

Joachim

On 08/22/2016 03: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
> 

-
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: 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

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!

[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!

[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!

[Tobias Soloschenko]

Great work!

Thank you so much for keeping this Apache Wicket extension up to date / make it 
runnable again.

kind regards

Tobias

> Am 22.08.2016 um 03:30 schrieb Jenny Brown :
> 
> 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

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

[Jenny Brown]

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