Re: Chrome extension and Eclipse plugin for wicket-source helper are updated!
On Mon, Aug 22, 2016 at 2:13 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > Hi Jenny, > > On Mon, Aug 22, 2016 at 3:30 AM, Jenny Brown <jennybro...@gmail.com> > 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
Chrome extension and Eclipse plugin for wicket-source helper are updated!
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
Released wicket-source for Wicket 6
Wicket-Source is now compatible with Wicket 6. dependency groupIdnet.ftlines.wicket-source/groupId artifactIdwicket-source/artifactId version6.0.0.8/version /dependency Wicket-Source lets you click through from the rendered web page back to the exact line of Wicket source code that produced it. For an introduction and screenshots, here's the prior announcement. https://www.42lines.net/2012/01/31/announcing-wicket-source/ It is available for Wicket 1.4, 1.5, and 6.x. Browser plugins are available for Firefox and Chrome. Eclipse and IntelliJ are supported for opening Java files. Issues/bugs can be reported here: https://github.com/42Lines/wicket-source/issues
Re: Wicket-Source: Click-through from browser back to Java source
I've updated the Firefox plugin for wicket-source to include support for Firefox 10. This is just metadata so that Firefox updates will stop complaining, as it was already code compatible. The new wicketsou...@gmail.com.xpi plugin file is available from the downloads area. https://github.com/42Lines/wicket-source/downloads So far no bug reports, but do let me know if anything gives you trouble, so I can get it fixed. Thanks! Jenny Brown
Re: Wicket-Source: Click-through from browser back to Java source
Thanks! When you have a project url for the port, let me know, and I'll link it in from the project wiki. Jenny On Mon, Feb 6, 2012 at 12:30 PM, Minas Manthos minas.mant...@gmail.comwrote: Thanks for explanations Jenny. It was very easy to port... :-) And thank you again for your great work and for sharing. Well done. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Source-Click-through-from-browser-back-to-Java-source-tp4346532p4362279.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: Wicket 1.4 - 1.5: MarkupContainer.getMarkupStream()
I'm still a beginner myself, but upon looking at the Javadocs for MarkupContainer and MarkupStream, I am not sure where exactly the code is giving you trouble. Compile error? Runtime exception? Can you be more specific? On Mon, Feb 6, 2012 at 11:14 PM, Thomas Singer wic...@regnis.de wrote: Does nobody have an idea? This code prevents me from making progress in converting our application to Wicket 1.5. Tom
Re: Wicket-Source: Click-through from browser back to Java source
Chrome extension is available in the github downloads area now. The extension uses devtools APIs (but no longer experimental) which are currently only ready in the chrome dev channel version. However the plugin should be stable, so as chrome moves into beta and then stable release I believe it will continue to work. Note that when you install the extension, it will ask for permission for all your web pages (although it does nothing with that data; but it's the only way to read the wicketsource= attributes). If there's enough interest, I can try making a version that only needs permissions for localhost and shuts itself off for other websites. That does limit remote debugging uses a bit though. Jenny
Re: Wicket-Source: Click-through from browser back to Java source
Wicket-source 1.5.0.7 is available now as a full release in maven central. This fixes a bug where ajax components were skipped; should work solidly now in all cases. If you have a bug report, there's an issue tracker on the github project site. https://github.com/42Lines/wicket-source I also backported for wicket 1.4.x compatibility and that is available as a full release in maven central now. Version numbering is (wicket_version).(my_version). Jenny Brown
Re: Wicket-Source: Click-through from browser back to Java source
Yay, another platform! Thank you for porting it. Jenny On Fri, Feb 3, 2012 at 6:39 PM, armhold armh...@gmail.com wrote: Wow this is really handy, thanks Jenny. Looking forward to the Chrome port! I just whipped up a plugin for Intellij. It might not be publicly available until they have a chance to review it, but here's the link: http://plugins.intellij.net/plugin/?ideaid=6846 You can https://github.com/armhold/wicket-source-intellij/tree/master/artifacts install the jar manually if you don't feel like waiting for it to show up in the public repo. In the mean time source is on github: https://github.com/armhold/wicket-source-intellij. Minas: I've never done an Intellij plugin before so this is probably not the most idiomatic code, but feel free to copy the relevant bits into wicketforge if you find it useful. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Source-Click-through-from-browser-back-to-Java-source-tp4346532p4356257.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: Wicket-Source: Click-through from browser back to Java source
On Wed, Feb 1, 2012 at 3:57 AM, Minas Manthos minas.mant...@gmail.comwrote: Sounds great! Would be nice to have it for IDEA too... will look into it. :-) I'm glad it sounds useful! :) Let me know if I can be of any assistance in the porting effort. The core behavior is simply listening for an http get request with a parameter for which file to open, and optionally a password (to reduce dev team pranks!). So, it's hopefully very straightforward. Jenny Brown
Wicket-Source: Click-through from browser back to Java source
Working on someone else's complex wicket pages can result in a lot of time spent hunting for components in the source. What if you could click on an item in the web page and jump straight to the line of Java source that created it? The net.ftlines.wicket-source module, plus a couple of plugins, lets you do just that. There are three parts - a module for your WicketApplication, a Firefox plugin, and an Eclipse plugin. 1. Wicket module records where in the source code each component is constructed and saves it in an HTML attribute. 2. Firebug extension displays the html attribute in Firebug's sidebar and lets you click to open it in Eclipse. (Chrome extension pending.) 3. Eclipse plugin listens for clicks from Firefox and opens the file to that line of the Java source. These three pieces together close the circle from wicket components and html rendering, to the browser, and back to the wicket component source, speeding work on existing but unfamiliar pages, and making minor wording tweaks quick and easy. For more information and installation, check out https://www.42lines.net/2012/01/31/announcing-wicket-source/ Release 1.5.0_06 is available in maven central. 1.5.0.7-SNAPSHOT contains a bug fix for ajax components. Jenny Brown
