Hello Folks, Brown Shoes are a walkin'! You can see the branch at https://github.com/shoes/shoes/tree/brown_shoes Pivotal Tracker is at https://www.pivotaltracker.com/projects/444909 Here's what we need, specifically : Ruby devs. Any level. Wether your a ninja of the metaprogramming black-arts, or juts trying to figure out what do..end is all about... we'll take your help. Java devs. Especially if you know SWT. We need you for "translating" from java TO ruby. Especially in SWT. The documents and samples online seem to be lacking at it takes us a really long time to figure out how to bend SWT to our will! The goal : cross-platform shoes that is simple to install and use! Thanks a lot for your time on this open source project! Peter Fitzgibbons Email: peter.fitzgibbons@gmail.com IM GTalk: peter.fitzgibbons IM AOL: peter.fitzgibbons@gmail.com
Helping out with Brown Shoes will also help Red, and maybe even Green. This work ties directly into the work I'm doing with extracting the classes out of C; if that's accomplished, brown and red can use the exact same logic, and just implement different shoes_native stuff.
I love that idea of other implementations just implementing the shoes_native stuff! Couldn't we maybe "steal" some of the classes you want to pull out from green shoes? I know some things are different (in green shoes color is simply an Array for example) but I bet some things are the same and we could save some work. I got a slightly related question: How could the other implementations get access to an up to date version of the "common" files without copying them by hand? Included as a gem? Cheers, Tobi On 01/04/2012 09:15 PM, Steve Klabnik wrote: > Helping out with Brown Shoes will also help Red, and maybe even Green. > This work ties directly into the work I'm doing with extracting the > classes out of C; if that's accomplished, brown and red can use the > exact same logic, and just implement different shoes_native stuff.
Hi Tobi, > I love that idea of other implementations just implementing the > shoes_native stuff! > Couldn't we maybe "steal" some of the classes you want to pull > out from green shoes? Oh, yeah. I was just thining the same thing. :) So, I just opened this trial repo: https://github.com/ashbb/brown_shoes I'm going to try porting from green shoes to brown shoes, not from red shoes to brown shoes. Green Shoes: Ruby and GTK2 Brown Shoes: JRuby and SWT I'd like to know how many code I can share. But, I have a big problem... I've never used JRuby and SWT. xx-P At first, I'll start from learning JRuby and SWT. :) ashbb
On 01/06/2012 03:29 PM, ashbb wrote: > Hi Tobi, > > > I love that idea of other implementations just implementing the > > shoes_native stuff! > > Couldn't we maybe "steal" some of the classes you want to pull > > out from green shoes? > Oh, yeah. I was just thining the same thing. :) > > So, I just opened this trial repo: https://github.com/ashbb/brown_shoes > I'm going to try porting from green shoes to brown shoes, not from red > shoes to brown shoes. > > Green Shoes: Ruby and GTK2 > Brown Shoes: JRuby and SWT > > I'd like to know how many code I can share. > But, I have a big problem... I've never used JRuby and SWT. xx-P > > At first, I'll start from learning JRuby and SWT. :) > > ashbb > Hi Ash, if you haven't seen it in the other thread, this link helped me very much a few weeks back: https://github.com/jruby/jruby/wiki/CallingJavaFromJRuby and although I'm not an expert I can try to answer questions in IRC. With the repository I think we should come to an agreement about the rep soon, two different repos are a haunting nightmare to me - or do I misunderstand something? Tobi
Tobi, Ash, I greatly encourage you to look at the Pivotal Tracker for Brown Shoes<https://www.pivotaltracker.com/projects/444909> It's admittedly small at the moment. If you want to join this, please tell me, I'll add you to the tracker account. As for branch vs repo... Steve and I discussed this and didn't find a compelling reason to break. After that discussion I've done a lot to the codebase. I agree to moving it to github:shoes/brown_shoes and I'll do that this afternoon if you all agree. Roll Call ? Steve Tobi Ash Peter Fitzgibbons (847) 859-9550 Email: peter.fitzgibbons@gmail.com IM GTalk: peter.fitzgibbons IM AOL: peter.fitzgibbons@gmail.com
I don't care what you do; it's your repo. :)
On Thu, Jan 5, 2012 at 10:37 AM, Tobias Pfeiffer < tobias.pfeiffer@student.hpi.uni-potsdam.de> wrote: > I got a slightly related question: How could the other implementations > get access to an up to date version of the "common" files without > copying them by hand? Included as a gem? > i think this is the aim of white shoes... the pair of shoes one can paint themself! though i'm at a loss as to where the white shoes repo is (if it even really exsists) hex -- * my blog is cooler than yours: http://serialhex.github.com * The wise man said: "Never argue with an idiot. They bring you down to their level and beat you with experience." * As a programmer, it is your job to put yourself out of business. What you do today can be automated tomorrow. ~Doug McIlroy No snowflake in an avalanche ever feels responsible. --- CFO: “What happens if we train people and they leave?” CTO: “What if we don’t and they stay?”
> i think this is the aim of white shoes... the pair of shoes one can paint > themself! though i'm at a loss as to where the white shoes repo is (if it > even really exsists) It does not exist. It's still more of a philosophical idea at the moment.
On 01/05/2012 06:14 PM, Steve Klabnik wrote: >> i think this is the aim of white shoes... the pair of shoes one can paint >> themself! though i'm at a loss as to where the white shoes repo is (if it >> even really exsists) > It does not exist. It's still more of a philosophical idea at the moment. And I always wanted to call shoes-mocks "white shoes", when (if) I get it really going.. well then gray will have to do... :-)
> Couldn't we maybe "steal" some of the classes you want to pull out from > green shoes? That is the entire idea, actually. And why brown shoes is a fork of shoes, rather than its own repo: we're going to use the brown shoes work to actively work on these kinds of things. > I got a slightly related question: How could the other implementations > get access to an up to date version of the "common" files without > copying them by hand? Included as a gem? Something like that could work, yeah. Ideally, it'd all be one repo: the colors would each be one of the different backends that would implement the native stuff.
Hi Steve, >> Couldn't we maybe "steal" some of the classes you want to pull out from >> green shoes? > > That is the entire idea, actually. And why brown shoes is a fork of > shoes, rather than its own repo: we're going to use the brown shoes > work to actively work on these kinds of things. Yeah, I totally agree. But in the beginning, I think that it's okay to have own rapo. For a short time, we need to do cut and try. After some study, we can merge Red and Brown also Green. ;-) ashbb
Hi Peter, Steve and folks,
> Brown Shoes are a walkin'!
Fantastic!
I'd like to dive into developing Brown Shoes.
Although I've never used jruby and SWT. :-P
BTW, I have a proposal.
I looked at the branch: https://github.com/shoes/shoes/tree/brown_shoes. In
the branch, there are so many unnecessary files for developing Brown Shoes.
So, could you move necessary files to shoes/brown_shoes repo (
https://github.com/shoes/brown_shoes) ?
I think that makes it easier to fork.
ashbb
I'd also like shoes/brown_shoes ! Tobi On 01/05/2012 01:50 PM, ashbb wrote: > Hi Peter, Steve and folks, > > > Brown Shoes are a walkin'! > Fantastic! > I'd like to dive into developing Brown Shoes. > Although I've never used jruby and SWT. :-P > > BTW, I have a proposal. > > I looked at the branch: https://github.com/shoes/shoes/tree/brown_shoes. In the > branch, there are so many unnecessary files for developing Brown Shoes. So, > could you move necessary files to shoes/brown_shoes repo > (https://github.com/shoes/brown_shoes) ? > > I think that makes it easier to fork. > > ashbb >