Re: Looking to pair
Thanks for the feedback! Are there some projects on github that would be good to watch? On Mon, Jul 8, 2013 at 8:56 AM, Sebastien seb...@gmail.com wrote: Ohh well, seems I didn't catch correctly... (sorry for the interference) Sebastien. On Mon, Jul 8, 2013 at 2:42 PM, Martin Grigorov mgrigo...@apache.org wrote: Hi Sebastien, On Mon, Jul 8, 2013 at 2:30 PM, Sebastien seb...@gmail.com wrote: Hi Martin, I have a doubt on the thread you answered... :) No. It is the correct thread. I suggest Mike Pence to watch some open source project, i.e. being notified when the project receives some commits. He actually asks exactly for this. On Mon, Jul 8, 2013 at 7:03 AM, Martin Grigorov mgrigo...@apache.org wrote: Hi, You can watch some Wicket project in GitHub. For example: https://github.com/l0rdn1kk0n/wicket-bootstrap https://github.com/sebfz1/wicket-jquery-ui https://github.com/wicketstuff/core On Sun, Jul 7, 2013 at 8:16 PM, Mike Pence mike.pe...@gmail.com wrote: Hi guys. Hope that this is appropriate for this list: I am looking for someone who is willing to pair program with me (although it would probably be mostly me on the watching side). I need to get strong with Wicket, Spring, and maybe even Neo4J as quickly as possible, as I have committed to using these technologies on a big new project. And I know from experience that pair programming with someone who is very proficient in those technologies is the quickest way to get there. I posted a job listing on Elance for a similar arrangement, but if any of you Wicket masters would let me look over your virtual shoulder for a few hours sometime, it would be much appreciated. FYI, I have been programming for 20+ years (VB, Delphi, Java, Ruby, etc.) so it is not like I am a total newbie. Thanks in advance. Mike Pence
Looking to pair
Hi guys. Hope that this is appropriate for this list: I am looking for someone who is willing to pair program with me (although it would probably be mostly me on the watching side). I need to get strong with Wicket, Spring, and maybe even Neo4J as quickly as possible, as I have committed to using these technologies on a big new project. And I know from experience that pair programming with someone who is very proficient in those technologies is the quickest way to get there. I posted a job listing on Elance for a similar arrangement, but if any of you Wicket masters would let me look over your virtual shoulder for a few hours sometime, it would be much appreciated. FYI, I have been programming for 20+ years (VB, Delphi, Java, Ruby, etc.) so it is not like I am a total newbie. Thanks in advance. Mike Pence
Re: Looking to pair
Remote pairing works, too, with some effort. I am working my way through Wicket in Action, and I am definitely very excited, at this point. But I know that watching a real Wicket expert in action would be extremely informative. On Sun, Jul 7, 2013 at 2:27 PM, Paul Borș p...@bors.ws wrote: Have you glimpsed over the few books offered under the Books section on Wicket's home page? In my experience pair programming works for two developers within the same physical location when one can explain the other quickly why it's best to archive something one way rather than the other. Have a great day, Paul Bors On Jul 7, 2013, at 1:16 PM, Mike Pence mike.pe...@gmail.com wrote: Hi guys. Hope that this is appropriate for this list: I am looking for someone who is willing to pair program with me (although it would probably be mostly me on the watching side). I need to get strong with Wicket, Spring, and maybe even Neo4J as quickly as possible, as I have committed to using these technologies on a big new project. And I know from experience that pair programming with someone who is very proficient in those technologies is the quickest way to get there. I posted a job listing on Elance for a similar arrangement, but if any of you Wicket masters would let me look over your virtual shoulder for a few hours sometime, it would be much appreciated. FYI, I have been programming for 20+ years (VB, Delphi, Java, Ruby, etc.) so it is not like I am a total newbie. Thanks in advance. Mike Pence - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: A Wicket in Ruby
Forgive my newbie questions, but what is Fodel? Is JBoss the most promising app server to build on? I have always felt like any sufficiently advanced Rails app is indistinguishable from an ad-hoc reinvention of a poorly spec'ed Java app server... On Thu, Jun 27, 2013 at 5:18 AM, Peter Henderson peter.hender...@starjar.com wrote: I've found the combination of Wicket + Scala to be very productive. Just make sure you use Fodel from Wicketstuff When things get tricky, simply reduce the problem down to a java quick start and proceed as usual. I find that 99% of the time making a quick start solves the problem, when I realize what I'm doing wrong. Peter. On 26 June 2013 17:28, Michael Pence mike.pe...@gmail.com wrote: Scala is even more expressive and powerful than Ruby, so Scala + Wicket is definitely my dream stack. I am just nervous about not having a big peer support community when things get tricky. On Jun 25, 2013, at 11:20 PM, Colin Rogers colin.rog...@objectconsulting.com.au wrote: Mike, Java is still pretty verbose, for all 'recent' improvements - I don't think that will really ever change, but then I don't see that as an issue. My personal style of coding is to write simple, obvious, testable, but ultimately verbose, code. Code that anyone can read, and understand what and why I'm attempting something - with the absolute minimum of comments. But that's just me! :) I've never understood writing one line of code, that takes five lines of comments to fully explain what and why it's attempting, when you could write 3 lines of code with no comments - and would be significantly easier to modify or extend later. When I was younger, and monitors smaller and lines constrained, I too loved ramming as much functionality into the smallest of visual spaces in code, but now I love tons of white space and simple, clean code. It's all about scroll wheels and big monitors! :) ... and Wicket and the super-fast modern JVMs... and t's still quicker and easier and ultimately less verbose to do something in Wicket/Java, than pretty much any other Web framework, IMHO - regardless of Java as a language. You could try Scala with Wicket, or Groovy with Wicket - both are native JVM languages - would these give you greater benefits to your style? Cheers, Col. -Original Message- From: Mike Pence [mailto:mike.pe...@gmail.com] Sent: 26 June 2013 06:48 To: users@wicket.apache.org Subject: Re: A Wicket in Ruby That is a good question that I have been mulling over these last few says. I think that I need to suck it up and just re-familiarize with Java -- it is less verbose, with annotations and closures now, right? -- for all of the benefits that the JVM with Wicket will bring me. I got a bit spoiled by years of Ruby, but man, do you pay for that lack of compile-time checking and type safety over and over again -- especially with regard to performance and endlessly climbing stack traces over typos. On Sun, Jun 23, 2013 at 8:25 PM, Colin Rogers colin.rog...@objectconsulting.com.au wrote: Mike, I hate to be the old cynic and doomsayer, but generally I find that whenever a two programming technologies are 'crossed' over, with the idea that you'll get the advantages of both - the exact opposite occurs and actually you end up with a technology that only has the disadvantages of both and the advantages of neither. After all, Wicket in Java works really well... how would ruby improve it over Java? Or Scala in the JVM? Or Groovy on the JVM? Like I said - sorry - I don't wish to negative, but it seems like a thankless task awaits you! :) Cheers, Col. -Original Message- From: Mike Pence [mailto:mike.pe...@gmail.com] Sent: 22 June 2013 02:21 To: users@wicket.apache.org Subject: A Wicket in Ruby So I have this crazy idea to try to write some subset of Wicket using CRuby and the variety of technologies it employs (EventMachine, etc.) Hard to know where to start though, or how best to form a mental model of what Wicket does vs. doing a straight class-to-class conversion. Maybe there is a test suite in the wicket source I should consider. Of course, there is nothing like stepping through the code to understand the lifecyle of a wicket request (and to see how it persists session data, especially). Am I crazy? EMAIL DISCLAIMER This email message and its attachments are confidential and may also contain copyright or privileged material. If you are not the intended recipient, you may not forward the email or disclose or use the information contained in it. If you have received this email message in error, please advise the sender immediately by replying to this email and delete the message and any associated attachments. Any views, opinions
Re: A Wicket in Ruby
That is a good question that I have been mulling over these last few says. I think that I need to suck it up and just re-familiarize with Java -- it is less verbose, with annotations and closures now, right? -- for all of the benefits that the JVM with Wicket will bring me. I got a bit spoiled by years of Ruby, but man, do you pay for that lack of compile-time checking and type safety over and over again -- especially with regard to performance and endlessly climbing stack traces over typos. On Sun, Jun 23, 2013 at 8:25 PM, Colin Rogers colin.rog...@objectconsulting.com.au wrote: Mike, I hate to be the old cynic and doomsayer, but generally I find that whenever a two programming technologies are 'crossed' over, with the idea that you'll get the advantages of both - the exact opposite occurs and actually you end up with a technology that only has the disadvantages of both and the advantages of neither. After all, Wicket in Java works really well... how would ruby improve it over Java? Or Scala in the JVM? Or Groovy on the JVM? Like I said - sorry - I don't wish to negative, but it seems like a thankless task awaits you! :) Cheers, Col. -Original Message- From: Mike Pence [mailto:mike.pe...@gmail.com] Sent: 22 June 2013 02:21 To: users@wicket.apache.org Subject: A Wicket in Ruby So I have this crazy idea to try to write some subset of Wicket using CRuby and the variety of technologies it employs (EventMachine, etc.) Hard to know where to start though, or how best to form a mental model of what Wicket does vs. doing a straight class-to-class conversion. Maybe there is a test suite in the wicket source I should consider. Of course, there is nothing like stepping through the code to understand the lifecyle of a wicket request (and to see how it persists session data, especially). Am I crazy? EMAIL DISCLAIMER This email message and its attachments are confidential and may also contain copyright or privileged material. If you are not the intended recipient, you may not forward the email or disclose or use the information contained in it. If you have received this email message in error, please advise the sender immediately by replying to this email and delete the message and any associated attachments. Any views, opinions, conclusions, advice or statements expressed in this email message are those of the individual sender and should not be relied upon as the considered view, opinion, conclusions, advice or statement of this company except where the sender expressly, and with authority, states them to be the considered view, opinion, conclusions, advice or statement of this company. Every care is taken but we recommend that you scan any attachments for viruses. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
A Wicket in Ruby
So I have this crazy idea to try to write some subset of Wicket using CRuby and the variety of technologies it employs (EventMachine, etc.) Hard to know where to start though, or how best to form a mental model of what Wicket does vs. doing a straight class-to-class conversion. Maybe there is a test suite in the wicket source I should consider. Of course, there is nothing like stepping through the code to understand the lifecyle of a wicket request (and to see how it persists session data, especially). Am I crazy?
Re: Introduction and some questions about Wicket
Thanks for all of the useful information and for your kindness. Having a supportive community -- something that the Ruby people are great at -- is a huge plus. Object-oriented Scala (being as functional in m approach as I can) and wicket look like the sweet spot for me. Here is hoping that big contract gets signed, now... FYI, here is me trying to explain the advantages of component-oriented development at the Ruby conference in '08: http://www.confreaks.com/videos/1162-rubyconf2008-components-are-not-a-dirty-word Best, Mike Pence On Thu, Jun 13, 2013 at 8:18 AM, Nick Pratt nbpr...@gmail.com wrote: For 3.) here are some of our experiences: 1.) If you are building from scratch and utilizing a separate design/styling team, we found its far easier/quicker to let the CSS folks do their thing and provide static pages, which the dev team then interprets and builds towards. Most devs can read HTML and understand its structure, so converting that in to Wicket components is straight forward. The inverse, in our experience, is far from true. While this approach gets you up and running the quickest (since you can find CSS styling consultants everywhere - at least you can here) it can leave you in a little bit of a hole unless you intend to hire someone on to the team full time with this knowledge. 2.) Having an employee with lots of current CSS knowledge on the dev team is a huge help. If they also have JS knowledge, thats an even bigger bonus. 3.) If you are trying to retrofit styling to an already built application (or where significant portions have been built), having a separate/isolated styling team is a major drag on app development. In our experience (and I don't intend this to be a blanket statement), most folks with good CSS knowledge are highly resistant to understanding Java and/or Wicket, and thus a significant impedance mismatch exists between the two efforts. If you find a Java dev with solid CSS knowledge, hang on to them! Nick On Wed, Jun 12, 2013 at 3:47 PM, Michael Pence mike.pe...@gmail.com wrote: Hi guys, My name is Mike Pence. I think that I have dipped into this list a time or two in the past, but I am here, this time, with serious intent to use Wicket for a very big project -- big both in terms of how many users it will have, and big in its impact. I have been doing Rails for the last 7 or 8 years (spoke at Ruby and Rails conferences about rich web apps), after coming from a Delphi and Java background (and Microsoft stuff, but I leave that out). So, Rails is great but does not give me the modularity and component re-use in the UI that I loved in Delphi. I am making some assumptions about Wicket, and would appreciate your feedback on these assumptions: 1. That wicket lets you model rich and highly interactive web apps that can feel like desktop apps, but in the browser. (Examples?) 2. That building complex UI widgets -- grids, trees, custom components like timelines or graphs or calendars -- is comparatively painless. 3. That you can largely leave the markup and styling to the people who like doing that kind of thing (why they would, I don't get…) I would love to do Scala with Wicket but I can't raise the bar that high, right now. If there was a JRuby version of wicket…that would be awesome. JVM runtime is a big win for this, because the project definitely will have many, many users. Has anyone done any work with wicket focused on mobile devices? Appreciate your thoughts. Mike Pence - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
