Re: Re: JSF 'blockinput' component
It sure looks nice! Does it also support multiple characters in a single cell? Like [1234]-[5678]-[9012]-[3456]? I have a requirement like that in my current project (has to do with a Dutch payment method). I think it would fit in Tomahawk nicely. Would need some enhancements (like JSP support) though, but it for sure is a good start!! /Jan-Kees On Jun 18, 2009 3:53pm, Manfred Geiler manfred.gei...@gmail.com wrote: Yep, GPL might be a problem. Easiest think might be to switch to ASF-license prior to donating this bit. Thanks, Manfred On Thu, Jun 18, 2009 at 15:46, Cagatay civicicagatay.civ...@gmail.com wrote: Looks nice but not sure about the license. On Thu, Jun 18, 2009 at 8:44 AM, Roger Laenen roger.lae...@telenet.be wrote: Hello, I've made a custom facelets component that simulates 'cell/block based' input like you find on official input forms. This type of input field can be useful in some specific situations. We use it for a bankaccount field with specific formatting and validation. You can find binaries and svn-trunk on http://code.google.com/p/blockinput An example app is also included. I thought it would maybe be interesting for inclusion in tomahawk. If there is any interest, let me know. grtz, Roger.
Re: Re: [MyFaces 2.0] discussion on alpha plans
Hi, The end of my extremely busy project is near, so I should have more time to work on MyFaces. My last work was on the annotation processing stuff, but AFAIK, Leonardo has continued this work. @Leonardo: What's the current state? Something else, some weeks ago, there was a discussion about restructuring the SVN, but that was delayed to enable Leonardo to do a release. Maybe this is a good time for the restructuring, before starting with the real work. Maybe we should also cleanup the build. Now Shale has been moved to the attic, we can upgrade the Shale mocks to 2.0. Then we can try to make all tests pass. We might also standardize on a testing framework (JUnit or TestNG) to simplify things... When all tests are up and running, the build process should be more smooth. /JK On Jun 9, 2009 1:07am, Matthias Wessendorf mat...@apache.org wrote: Hey mike, I agree that we should try to get an *alpha* out of the door. Main mantra is: release often, release early q: what is the state on the facelets support, currently ? -Matthias On Mon, Jun 8, 2009 at 2:11 PM, Michael concinimconc...@gmail.com wrote: All, I thought it might be a good time to raise the issue of solidifying a plan for the MyFaces 2.0 alpha release now that we've had a little time to work with the release candidate draft of the spec. What are the thoughts in the community with respect to what should be included in an alpha release as well as what the time frame should be for a release. If we can come up with a target date as well as specific 2.0 features we want to target for inclusion, that should help in prioritizing the remaining work. From my end, I'd love to see a working runtime in some form by the end of August if that's reasonable. As for content, that is definitely more of an open question. Here is my top list of what I would like to see be at least partially functional for an alpha release. -backwards compatibility with JSF 1.x apps -base support for facelets and composite components -AJAX support (should hopefully be in pretty good shape here thanks to Ganesh and team) -System event support -Partial view traversal Thoughts/concerns/objections? -Mike -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: Re: MyFaces 2.0 development going forward
I'm currently working on the annotation processing stuff (@ManagedBean, @ManagedProperty...). Already made a first attempt for the managed beans, but there is still some work to do (converters, components, event listeners, etc). I hope I can apply the same logic for those other components as well. With Werner working on Ajax and Simon on Facelets, we already cover a large portion of JSF2. Facelets is big, though, since it also contains tags for all components, EZComp, JSF2-Facelets/Original-Facelets switching, etc... Resource handling/relocation is also a mandatory requirement for Ajax to work. But I think an alpha release should at least contain these essential JSF2 components: AJAX, Facelets, annotation based configuration. I think those components are the base of the JSF2 work. Adding in other features should not be too hard when those three are in place properly. About Shale-test, is it right to use Shale classes in MyFaces Core? Of course it's just the unit tests, but in some way it's still a cyclic dependency which is usually a bad thing... /Jan-Kees
