Re: [jira] Resolved: (SHALE-24) [Shale] No clay component configuration for MyFaces Tomahawk
On 8/3/06, Gary VanMatre [EMAIL PROTECTED] wrote: Humm, I would be willing to start a project in the shale sandbox that was targeted at converting the tomahawk component examples into jsp/xml and clay templates. Clay supports html namespaces too. This is a new feature and would be a good method of working out the issues. I don't have the strength to try to do this on the myfaces JIRA. I'm only suggesting that you monitor the Facelets Tomahawk thread on myfaces-dev and let us know if anything we're doing can be improved to also support Clay at the same time -- ie, comment on missing or existing things that will prohibit the integration. IMO, if Clay can not capture the attention of the component providers, we can't expect them to invest the time in providing native support for something that the RI doesn't embrace. I agree that if Clay users aren't willing to show interest in getting this support into a component library, that it's unlikely that it will happen :) Personally, I'm exceedingly happy with Facelets and will likely never try Clay. But that doesn't mean I'm not willing to help make Clay more usable.
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Yep. What we would need to know is the from address on the commit emails, so we know what address to subscribe. I changed the email from public to moderated so I could discover the sender: [EMAIL PROTECTED] You'd think Google would have figured this stuff out already :-). Yes but its a work in progress so we will let it slide. I suspect we want minimal barriers to participation here, so I'd throw it open. We can change things later if we get too much spam etc. Google is warning about spam if you leave it wide open but I guess we can deal with that when the time comes. In particular, we should set the group to accept public email (it took my test message submitted via the web interface, but not the one I emailed from my gmail account). That should at least make the commit emails work, so we can see what the right from address is. That's weird taht you could only send email from your interface. Can you send again from your gmail account to test if its moderated or not? I changed you to owner as well so you can have the dubious honor of assisting in the group management. Go ahead an change it to wide open public email once you test your gmail again. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I think I prefer that too. shale.org doesn't appeal to me for some reason I can't really put my finger on. Greg On Aug 4, 2006, at 2:03 PM, James Mitchell wrote: I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) Sean On 8/4/06, Greg Reddin [EMAIL PROTECTED] wrote: I think I prefer that too. shale.org doesn't appeal to me for some reason I can't really put my finger on. Greg On Aug 4, 2006, at 2:03 PM, James Mitchell wrote: I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/4/06, Sean Schofield [EMAIL PROTECTED] wrote: The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) shale.goodies.petstore ? -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I'm cool with that too. It doesn't have to be a web address :-) Greg On Aug 4, 2006, at 2:47 PM, Wendy Smoak wrote: On 8/4/06, Sean Schofield [EMAIL PROTECTED] wrote: The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) shale.goodies.petstore ? -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
shale.goodies.petstore ? I like it except for one problem. What is the maven group id? If it starts with shale, people browsing ibiblio might get confused and wonder where the rest of the stuff is? Wendy Sean
