[Prototype-core] Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread T.J. Crowder

Hi all,

I don't seem to be seeing the unit test HTML files.  Apologies if I've
done something daft, but I'm running out the door so I thought I'd
ping in hopes of being able to work on stuff (I have a bunch of doc
tickets to deal with) later this afternoon.

I've installed Ruby, Git, etc. and have cloned the repo and
successfully built via rake dist.  According to the contribute page:

 To see what unit tests look like, open up any of the HTML documents
found in test/unit/ in your browser.  They run automatically, so you
should see a flurry of green-colored rows after a few moments.

There aren't any HTML files in test/unit at all (there are several
JavaScript files that look like they may well implement certain
specific tests).  There are some HTML files elsewhere in the tree, but
so far nothing I've found looks like the bunch of green rows
described.  Could someone point me at it or give me an idea where I
may have gone astray?

Thanks in advance,
--
T.J. Crowder
tj / crowder software / com
Independent Software Engineer, consulting services available

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread Tobie Langel

Sure.

And that would warrant some documentation too.

The tests are generated from the js test files.

You'll need to run rake test for that.

Which in turn will prompt you to require unittest_js submodules.

Let me know how things go.

Best,

Tobie

On Mar 20, 10:39 am, T.J. Crowder t...@crowdersoftware.com wrote:
 Hi all,

 I don't seem to be seeing the unit test HTML files.  Apologies if I've
 done something daft, but I'm running out the door so I thought I'd
 ping in hopes of being able to work on stuff (I have a bunch of doc
 tickets to deal with) later this afternoon.

 I've installed Ruby, Git, etc. and have cloned the repo and
 successfully built via rake dist.  According to the contribute page:

  To see what unit tests look like, open up any of the HTML documents
 found in test/unit/ in your browser.  They run automatically, so you
 should see a flurry of green-colored rows after a few moments.

 There aren't any HTML files in test/unit at all (there are several
 JavaScript files that look like they may well implement certain
 specific tests).  There are some HTML files elsewhere in the tree, but
 so far nothing I've found looks like the bunch of green rows
 described.  Could someone point me at it or give me an idea where I
 may have gone astray?

 Thanks in advance,
 --
 T.J. Crowder
 tj / crowder software / com
 Independent Software Engineer, consulting services available
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread T.J. Crowder

Thanks, Tobie.  That was the missing bit all right.  The contribute
page _does_ mention rake test, but much further down; I'll update
the page to tie things together a bit.

Out of curiousity, anyone successfully run the tests lately on Chrome,
IE7, or Opera on Windows?  For me, Firefox 3 runs and passes all
tests, but Chrome (1.0.154.48) doesn't even launch and I have to kill
rake; IE7 fails several tests; and Opera (9.64) runs many of the tests
(and as per the warning I have to manually close it per test), but
then dies in the middle -- Opera not running but rake seeming to be
waiting for it.  This is with rake version 0.7.3 (I just today
installed Ruby and rake via the One Click Ruby Installer linked from
the contribute page) and a fresh clone of the repo.

I haven't had time to look into these in any detail at all, but
thought I'd ask the question, in case someone already knows what's
going on there.

Thanks,

-- T.J. :-)

On Mar 20, 1:44 pm, Tobie Langel tobie.lan...@gmail.com wrote:
 Sure.

 And that would warrant some documentation too.

 The tests are generated from the js test files.

 You'll need to run rake test for that.

 Which in turn will prompt you to require unittest_js submodules.

 Let me know how things go.

 Best,

 Tobie

 On Mar 20, 10:39 am, T.J. Crowder t...@crowdersoftware.com wrote:

  Hi all,

  I don't seem to be seeing the unit test HTML files.  Apologies if I've
  done something daft, but I'm running out the door so I thought I'd
  ping in hopes of being able to work on stuff (I have a bunch of doc
  tickets to deal with) later this afternoon.

  I've installed Ruby, Git, etc. and have cloned the repo and
  successfully built via rake dist.  According to the contribute page:

   To see what unit tests look like, open up any of the HTML documents
  found in test/unit/ in your browser.  They run automatically, so you
  should see a flurry of green-colored rows after a few moments.

  There aren't any HTML files in test/unit at all (there are several
  JavaScript files that look like they may well implement certain
  specific tests).  There are some HTML files elsewhere in the tree, but
  so far nothing I've found looks like the bunch of green rows
  described.  Could someone point me at it or give me an idea where I
  may have gone astray?

  Thanks in advance,
  --
  T.J. Crowder
  tj / crowder software / com
  Independent Software Engineer, consulting services available


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread kangax

On Mar 20, 3:03 pm, T.J. Crowder t...@crowdersoftware.com wrote:
 Thanks, Tobie.  That was the missing bit all right.  The contribute
 page _does_ mention rake test, but much further down; I'll update
 the page to tie things together a bit.

 Out of curiousity, anyone successfully run the tests lately on Chrome,
 IE7, or Opera on Windows?  

I'm on mac. Trunk fully passes FF3 and Safari 4 here. There are a
couple of failures in Opera 9.64. I'm taking care of IE8 at the moment
- just pushed few fixes for DOM suite.

[...]

--
kangax
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Protopacked version bigger than original?

2009-03-20 Thread Simon Charette
You forgot scriptaculous effect.js

On Fri, Mar 20, 2009 at 4:32 PM, wes w...@70kilo.tv wrote:


 Am I missing something here?

 protoaculous1.6.packed.js is 146Kb

 prototype.js (1.6.0.2) is 123Kb and scriptaculous is 3Kb totalling
 126Kb.

 Isn't the packed version supposed to be smaller?
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Protopacked version bigger than original?

2009-03-20 Thread wes

my bad. but still, effects.js is only 37kb leaving the packed version
only 17kb smaller? I heard the other versions got 'em down to like
25k  and 35k?

On Mar 20, 1:57 pm, Simon Charette charett...@gmail.com wrote:
 You forgot scriptaculous effect.js

 On Fri, Mar 20, 2009 at 4:32 PM, wes w...@70kilo.tv wrote:

  Am I missing something here?

  protoaculous1.6.packed.js is 146Kb

  prototype.js (1.6.0.2) is 123Kb and scriptaculous is 3Kb totalling
  126Kb.

  Isn't the packed version supposed to be smaller?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---