that would rock my world Dimitar
On Monday, March 26, 2012 12:35:33 PM UTC-4, Nutron wrote: > > If you did that then you'll have a lib/bootstrap directory that has all my > js in it. If you want to add another repo, yes, you'll need to edit the > settings, but the easier thing to do is to fork my bootstrap repo and check > out your fork in lib/bootstrap. > > (after installing) > $ cd mootools-development/lib/bootstrap > $ git remote add me [your github repo url] > $ git checkout -b myNewFeature > $ # make some changes > $ git add . > $ git commit -m "some new feature" > $ git push me myNewFeature > $ # send me a pull request > > By working there you can author new specs and whatnot. Just add a new > specs file in lib/bootsrap/tests/specs and update the package.yml there, > then open the dev server in your browser and run the tests. > > I can, if it helps, make a quick screen cast of this. > > On Mon, Mar 26, 2012 at 8:33 AM, Dimitar Christoff <[email protected]>wrote: > >> On 26/03/2012 15:47, Aaron Newton wrote: >> >>> The specs for Behavior stuff are really easy to author. The test is >>> basically an HTML example that should instantiate your class and the >>> unit tester verifies that it does. You can then make additional >>> assertions. >>> >>> I'll grant that my testing environment has grown a bit esoteric, but it >>> is at least easy to install. >>> >>> $ git clone >>> git://github.com/anutron/**mootools-development.git<http://github.com/anutron/mootools-development.git> >>> <http://github.com/anutron/**mootools-development.git<http://github.com/anutron/mootools-development.git> >>> > >>> >>> $ cd mootools-development >>> $ git checkout behavior >>> $ ./install >>> $ ./go run >>> //then open http://localhost:9876 >>> >> >> I got that working fine already but what I don't get is how the test >> environment on that port relates to the mootools-boostrap repo, which lies >> elsewhere. >> >> do i mod the settings.py file to point to ../mootools-bootstrap/ ? >> >> sorry for being thick here. :) >> >> best regards, >> >> -- >> Dimitar Christoff >> >> "JavaScript is to JAVA what hamster is to ham" >> http://fragged.org/ | @D_mitar | >> https://github.com/**DimitarChristoff<https://github.com/DimitarChristoff> >> > > On Monday, March 26, 2012 12:35:33 PM UTC-4, Nutron wrote: > > If you did that then you'll have a lib/bootstrap directory that has all my > js in it. If you want to add another repo, yes, you'll need to edit the > settings, but the easier thing to do is to fork my bootstrap repo and check > out your fork in lib/bootstrap. > > (after installing) > $ cd mootools-development/lib/bootstrap > $ git remote add me [your github repo url] > $ git checkout -b myNewFeature > $ # make some changes > $ git add . > $ git commit -m "some new feature" > $ git push me myNewFeature > $ # send me a pull request > > By working there you can author new specs and whatnot. Just add a new > specs file in lib/bootsrap/tests/specs and update the package.yml there, > then open the dev server in your browser and run the tests. > > I can, if it helps, make a quick screen cast of this. > > On Mon, Mar 26, 2012 at 8:33 AM, Dimitar Christoff <[email protected]>wrote: > >> On 26/03/2012 15:47, Aaron Newton wrote: >> >>> The specs for Behavior stuff are really easy to author. The test is >>> basically an HTML example that should instantiate your class and the >>> unit tester verifies that it does. You can then make additional >>> assertions. >>> >>> I'll grant that my testing environment has grown a bit esoteric, but it >>> is at least easy to install. >>> >>> $ git clone >>> git://github.com/anutron/**mootools-development.git<http://github.com/anutron/mootools-development.git> >>> <http://github.com/anutron/**mootools-development.git<http://github.com/anutron/mootools-development.git> >>> > >>> >>> $ cd mootools-development >>> $ git checkout behavior >>> $ ./install >>> $ ./go run >>> //then open http://localhost:9876 >>> >> >> I got that working fine already but what I don't get is how the test >> environment on that port relates to the mootools-boostrap repo, which lies >> elsewhere. >> >> do i mod the settings.py file to point to ../mootools-bootstrap/ ? >> >> sorry for being thick here. :) >> >> best regards, >> >> -- >> Dimitar Christoff >> >> "JavaScript is to JAVA what hamster is to ham" >> http://fragged.org/ | @D_mitar | >> https://github.com/**DimitarChristoff<https://github.com/DimitarChristoff> >> > >
