Awsome Claudio, I'm definitly interested on helping the macruby space out while I'm not committing C code :). I'm a bit over booked during the next week but I hope to pull the unity project apart a bit.
I think that representing all flavours of ruby on unity is an important step to bring thier authors closer together. Last night I was thinking that a "percentage of core" progress bar would be interesting to see between the projects. Sent from my iPhone On 03/10/2009, at 7:11 AM, Claudio Poli <masterk...@gmail.com> wrote: > hey, it's no problem :) > like Matt said if someone wants to fork/look the sinatra app is > located at http://github.com/masterkain/macruby-nightlies-web . > > the app itself it's considered somewhat stable but there's still > room for improvements that I will do in next days, anyway I'm not > going to change important functionality; it's open for forking. > > > otherwise I'm open to suggestions/direction on stuff to add to daily > jobs. > > cheers, > claudio > > Il giorno 02/ott/2009, alle ore 23.00, Matt Aimonetti ha scritto: > >> Wait, I said he "could" do it, or someone could fork the sinatra >> app and add it, it's not done yet tho :) >> Btw, thanks a lot Claudio for making a server available! >> >> - Matt >> >> >> On Fri, Oct 2, 2009 at 12:19 PM, Eloy Duran >> <eloy.de.en...@gmail.com> wrote: >> Oh serious?! I didn't know, awesome! Thanks Claudio, your my hero >> of the day! >> Sorry Laurent, there will be plenty of other days left for you to >> shine again ;-) >> >> Eloy >> >> On 2 okt 2009, at 21:16, Matt Aimonetti wrote: >> >>> Actually.... Claudio is doing that already ;) He might as well add >>> one more step to his nightly building app. >>> >>> - Matt >>> >>> On Fri, Oct 2, 2009 at 12:11 PM, Eloy Duran >>> <eloy.de.en...@gmail.com> wrote: >>> That looks great indeed Ben, much better than what my >>> investigation in exiting solutions resulted in :) >>> >>> It would be great if we'd have a osx machine that would >>> automatically run the suite at night and generate this from it. >>> Any idea if that would become a possibility in the near future >>> Laurent? >>> >>> Eloy >>> >>> >>> On 2 okt 2009, at 20:48, Laurent Sansonetti wrote: >>> >>> Hi Ben, >>> >>> I wasn't aware of that project, it looks good indeed. And the fact >>> that it can be reused for different implementations of Ruby is >>> very cool too :) >>> >>> Laurent >>> >>> On Oct 1, 2009, at 11:48 PM, Ben Schwarz wrote: >>> >>> Laurent, >>> >>> I just had a quick chat with Brian Ford (Rubinius) apparently >>> they're looking at using some incarnation of git://github.com/ >>> madriska/unity.git (http://unity.madriska.com/) >>> Which uses a YAML formatter for mspec. >>> (http://github.com/madriska/mspec/commit/36b8bce62c272d546bcbd8ab9f136576ff4701e5 >>> ) >>> >>> I think this might be the best way to get something that works >>> running. I'm sure that all the ruby implementations would benefit >>> from the shared work effort in this regard. >>> We could start by investigating unity, chatting to the author and >>> seeing if we can make some contributions. >>> >>> >>> >>> >>> On 02/10/2009, at 4:23 PM, Laurent Sansonetti wrote: >>> >>> Hi Ben, >>> >>> That sounds like a good idea and looks like what I had in mind. >>> >>> I was thinking of having a status page, that shows hitlist items >>> (critical bugs / things to do for the upcoming release), some >>> rubyspec progress, a link to the latest nighty build, etc. >>> >>> The hitlist thing could be generated from a local file from the >>> repository. We currently use TODO for that. >>> >>> We wrote a special mspec formatter in order to know what >>> percentage of a given spec category we do pass. But having a more >>> detailed view (classes / methods as you suggested) might be more >>> interesting, this way we know on what class / method to focus in >>> priority. Assuming that the mspec formatter is altered a little >>> bit, this information could also be generated after a spec:ci pass. >>> >>> Is that what you had in mind? >>> >>> I guess the challenge here is to write a program that generates a >>> Webby page for our website, commit it to the repository every time >>> a change is made, then we would re-deploy the site right after. >>> >>> Laurent >>> >>> On Oct 1, 2009, at 11:01 PM, Ben Schwarz wrote: >>> >>> Hi all, >>> >>> >>> I've had some loose discussions with @lrz regarding a visual >>> representation of classes and methods that are working via the >>> rubyspec. >>> This would enable developers to find an area of development to >>> focus on and also for end-users to understand what they might face >>> before >>> conducting any development using macruby (bringing real >>> applications closer to tuition, rather than a start/stop experience) >>> >>> I'm happy to offer some hours to get something together that is >>> styled like macruby.org but I obviously need to: >>> >>> A) consult the group >>> B) work out a spec >>> C) have something setup on the macruby.org infrastructure. >>> >>> >>> Discuss. >>> >>> >>> Cheers, >>> >>> - >>> >>> Ben Schwarz >>> Web architect >>> >>> Web: http://www.germanforblack.com >>> Mobile: +61 407 339 418 >>> >>> -- >>> Please consider your environment before printing or distributing >>> this material. >>> -- >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >>> >>> _______________________________________________ >>> MacRuby-devel mailing list >>> MacRuby-devel@lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> >> _______________________________________________ >> MacRuby-devel mailing list >> MacRuby-devel@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
