From mghaught at gmail.com Thu Apr 3 00:36:16 2008 From: mghaught at gmail.com (Marty Haught) Date: Wed, 2 Apr 2008 22:36:16 -0600 Subject: [Yui4rails-discuss] Some thoughts Message-ID: <57f29e620804022136m476ca3e7u227636e43e44be75@mail.gmail.com> I had some ideas on how to move things forward. Before I get into it I hope you are receiving the emails that I've sent to the list. I haven't seen any replies so I'm not 100% certain that they made it out. So there are two ideas really. First, I'm wondering if we shouldn't move this list to Google groups. Thoughts? It would be more visible and easier for people to subscribe/drop. Second, I have started using git and I'm wondering if some of you might be more interested in collaborating that way than with subversion. I have a github, http://github.com/, account and we could drive the 'trunk' of this plugin through there. We could then put stable releases back into subversion if we wanted or just point people at the git repo. Thoughts? I also didn't get any responses on components that you're interested in seeing next or interested in developing. Unfortunately, my energies have been pulled in several other directions this last month. I still intend to work more on this plugin but nothing is pressing on my end. Cheers, Marty From javadragon at gmail.com Thu Apr 3 14:18:35 2008 From: javadragon at gmail.com (Lori Olson) Date: Thu, 3 Apr 2008 12:18:35 -0600 Subject: [Yui4rails-discuss] Some thoughts In-Reply-To: <57f29e620804022136m476ca3e7u227636e43e44be75@mail.gmail.com> References: <57f29e620804022136m476ca3e7u227636e43e44be75@mail.gmail.com> Message-ID: On Wed, Apr 2, 2008 at 10:36 PM, Marty Haught wrote: > I had some ideas on how to move things forward. Before I get into it > I hope you are receiving the emails that I've sent to the list. I > haven't seen any replies so I'm not 100% certain that they made it > out. So there are two ideas really. > > First, I'm wondering if we shouldn't move this list to Google groups. > Thoughts? It would be more visible and easier for people to > subscribe/drop. I would support that. I've been moving all my "list" traffic over to my GMail account anyway. > > > Second, I have started using git and I'm wondering if some of you > might be more interested in collaborating that way than with > subversion. I have a github, http://github.com/, account and we > could drive the 'trunk' of this plugin through there. We could then > put stable releases back into subversion if we wanted or just point > people at the git repo. Thoughts? Git looks pretty interesting. It might be nice to drop the stable releases into Subversion, though. Gotta keep the "bar to entry" low. > > > I also didn't get any responses on components that you're interested > in seeing next or interested in developing. Unfortunately, my > energies have been pulled in several other directions this last month. > I still intend to work more on this plugin but nothing is pressing on > my end. > I'm still just lurking, waiting to see what other people come up with. I suspect if you move to a Google Group, and post in the Rails groups about it, you might get more traffic and more interest. Regards, Lori -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/yui4rails-discuss/attachments/20080403/4cf3adb6/attachment.html From mghaught at gmail.com Thu Apr 10 00:17:33 2008 From: mghaught at gmail.com (Marty Haught) Date: Wed, 9 Apr 2008 22:17:33 -0600 Subject: [Yui4rails-discuss] Some thoughts In-Reply-To: References: <57f29e620804022136m476ca3e7u227636e43e44be75@mail.gmail.com> Message-ID: <57f29e620804092117u18226da4m43e801ad6bad9e2b@mail.gmail.com> > I would support that. I've been moving all my "list" traffic over to my > GMail account anyway. Is there any downside anyone can think to not move the list to google groups? > Git looks pretty interesting. It might be nice to drop the stable releases > into Subversion, though. Gotta keep the "bar to entry" low. Alright, I'm going to do this. I got a few comments offlist supporting this and Radiant is successfully doing this now. I'll see if I can get the repo up on my github account by the weekend. I'm still ironing out the details on how I'll integrate the changes back into the svn repo on RubyForge as well as doing plugin installs. I definitely plan to have stable releases on RubyForge. > I'm still just lurking, waiting to see what other people come up with. I > suspect if you move to a Google Group, and post in the Rails groups about > it, you might get more traffic and more interest. I really haven't advertised the plugin yet. I'm sure an email to the Rails list as well as YUI's list would generate a lot of traffic. Honestly, I want to make sure that we've got a bit more developed as well as the way to manage contributions before opening the gates. I think using git will make contributing really easy. I have had trouble doing patches painfree in svn and it looks super simple in git. FYI, I have integrated Bill Scott's carousel into one of my apps. I'll look to extract it into a helper and include it in the plugin. Cheers, Marty From mghaught at gmail.com Tue Apr 15 19:07:17 2008 From: mghaught at gmail.com (Marty Haught) Date: Tue, 15 Apr 2008 17:07:17 -0600 Subject: [Yui4rails-discuss] Yui4Rails upgraded to 2.5.1 Message-ID: <57f29e620804151607u13980a1bsf0d3d72742af30ab@mail.gmail.com> I've just upgraded the plugin to YUI 2.5.1 and have applied Bryan Donovan's datatable patch. Several of you have contacted me on how to take things forward. In effort to make things a bit easier I've made a git repository of the plugin that is cloned off the RubyForge svn repo. You can find it here: http://github.com/mghaught/yui4rails/tree/master We've got some new components that we've been developing lately. Carousel, lightbox and tooltip are close to being ready. One thing that has come up from this is that we've got some limitations with the current approach of including dependencies. I'm working on a new prototype that would ease this pain and output much nicer html/script tags. The basic idea is that you would add a helper method in the head section of you layouts. Later on, as you need a component you simply invoke its helper method and the rest is handled for you. I'm going to try this out with a prototype to make sure everything works fine. We also need to discuss design philosophies on how to develop new components to make sure the plugin is cohesive. The other important thing is to have this plugin well tested. While the nature of js based widgets makes testing incredibly difficult, I think we can provide some test coverage for how our helpers operate. I'll try to expand on this in another email/blog post in the future. For now I want to get this plugin to a good place where we can start building components, creating documentation and making the plugin user-friendly. Cheers, Marty From mghaught at gmail.com Fri Apr 18 23:15:17 2008 From: mghaught at gmail.com (Marty Haught) Date: Fri, 18 Apr 2008 21:15:17 -0600 Subject: [Yui4rails-discuss] YUI4Rails release 0.1.1 Message-ID: <57f29e620804182015g18b86c88j3b03893369c8231b@mail.gmail.com> Hi Everyone, I've just pushed up the next release of YUI4Rails to Rubyforge: http://rubyforge.org/projects/yui4rails/. This release contains YUI 2.5.1 files as well as Bryan Donovan's patch for the datatable widget. I've blogged about the release and some other thoughts on the plugin here: http://martyhaught.com/articles/2008/04/18/yui4rails-release-0-1-1/ I wanted to mention two things quickly here. First, I'm going to be pushing the new prototype of the plugin to my github repository, http://github.com/mghaught/yui4rails/tree/master. It's a fairly different approach to managing assets and making widgets easier to use. The carousel widget will be the first to use this new approach fully. I talk about it in my blog post above. As soon as I have it published I'll write a more details post about how to use it as well as ideas on how you can write widgets in this design. Second, it's time to kick this plugin to the next level by creating documentation, more robust tutorials as well as getting some of you involved in contributing. You should see more traffic on this list as we discuss design and improvements to the plugin. I also hope the github repository will make it easier for you to keep current and send me pull requests to integrate your changes. I'm still getting my git chops up so I may make some silly mistakes in managing it. Hopefully they won't be too bad but if you've got ideas/thoughts on how to improve that I'm all for it. As always your comments/bug reports are welcome on the plugin. Cheers, Marty Haught http://martyhaught.com