date:20091001

#361: Embed MacRuby Target Adds 60+ MB to .app
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--
 Expected:

 Between 17(mentioned in presentation, not verified) MB and 30 MB (size of
 .dylib file) to be added to the output .app file on build from Xcode of
 the 'Embed MacRuby' target.

 Observed:

 The actual output file is over 69 mb, even with a base project with no
 code.

 Steps to reproduce:

 1.) open the attached project in Xcode
 2.) select the embed macruby target in the Active Target box
 3.) build
 4.) check the file size of the resulting .app file

 This embeds the whole framework, including all of the installed gems
 (including gems installed by the user!), tools, etc.

 Work around:

 Manually embedding the 'libmacruby.1.9.0.dylib' and using a copy files
 build step seems to work, but I haven't tested on systems without MacRuby
 yet.

 Even with this 30mb seems a bit on the large side.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Xcode Project Template with Testing Baked In

So, I've been mucking about with MacRuby lately. It's been fun so far.
Thanks to all the devs for this great project.
I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby on
Rails and similar frameworks nudge you in the right direction by baking in
an existing testing infrastructure.

I've got testing pretty much figured out and was wondering if the team would
be open to modifying the basic Xcode project template to add unit testing,
with a stub test and test_suite file to get started. This would also involve
creating a framework for any objective-c code that the user writes so that
it can be included in both the .app and the test files.

In addition it might be useful to include the 'embed mac ruby' and possibly
a macrubyc target as well by default. These can always be removed if a user
doesn't want them.

I can supply preliminary patches if this seems like a good route to go.

- Dylan Bruzenak
www.ideaswarm.com
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In

2009-10-01 Thread Matt Aimonetti

Hi Dylan,

Why don't you you post your template so people can look at it and give their
feedback? People like Eloy would probably give their feedback ;)

- Matt



On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak  wrote:

> So, I've been mucking about with MacRuby lately. It's been fun so far.
> Thanks to all the devs for this great project.
> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby on
> Rails and similar frameworks nudge you in the right direction by baking in
> an existing testing infrastructure.
>
> I've got testing pretty much figured out and was wondering if the team
> would be open to modifying the basic Xcode project template to add unit
> testing, with a stub test and test_suite file to get started. This would
> also involve creating a framework for any objective-c code that the user
> writes so that it can be included in both the .app and the test files.
>
> In addition it might be useful to include the 'embed mac ruby' and possibly
> a macrubyc target as well by default. These can always be removed if a user
> doesn't want them.
>
> I can supply preliminary patches if this seems like a good route to go.
>
> - Dylan Bruzenak
> www.ideaswarm.com
>
>
>
> ___
> MacRuby-devel mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
>
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In

Message is being held pending moderator approval; let me know if I should
post the actual file somewhere else :)

- Dylan

On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak  wrote:

> Good idea. I've attached it here. I may have accidentally added the build
> directory as well; this should be deleted from the template.
>
> To test you can copy it to one of the template directories such as :
> ~/Library/Application Support/Developer/Shared/Xcode/Project
> Templates/Application/MacRuby Application With Testing
>
> Differences:
>
> - Embed MacRuby target is included by default to easy deployment for first
> time users
> - Tests directory has been added for tests
> - test_stub.rb has been added with a starting test::unit case
> - Unit Tests target has been added to run the tests
> - test_suite.rb has been added to load up all tests from the Tests
> directory. This can easily be made recursive using Dir.glob.
>
> I've left out the framework/obj-c testing stuff because it is difficult to
> get it working in cases where there is no objective-c; building the
> framework requires at least one class. A better way to handle that would be
> to write up a blog post on how to do this; mainly:
>
> 1.) Create a new Cocoa -> Framework target
> 2.) add the new framework to your unit test and .app targets so that it
> gets built when either target is run
> 3.) add a copy files step, targeting frameworks, to your .app target
> 4.) add the new framework(drag from the products folder) to both the link
> and copy steps of your .app target to include it with your .app file
> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
> test_suite.rb file
>
> After following these steps you can test any Obj-c classes added to the
> framework from Ruby, as well as any Ruby classes that depend on these custom
> classes.
>
> - Dylan
>
>
> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti wrote:
>
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak wrote:
>>
>>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>>> Thanks to all the devs for this great project.
>>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>>> on Rails and similar frameworks nudge you in the right direction by baking
>>> in an existing testing infrastructure.
>>>
>>> I've got testing pretty much figured out and was wondering if the team
>>> would be open to modifying the basic Xcode project template to add unit
>>> testing, with a stub test and test_suite file to get started. This would
>>> also involve creating a framework for any objective-c code that the user
>>> writes so that it can be included in both the .app and the test files.
>>>
>>> In addition it might be useful to include the 'embed mac ruby' and
>>> possibly a macrubyc target as well by default. These can always be removed
>>> if a user doesn't want them.
>>>
>>> I can supply preliminary patches if this seems like a good route to go.
>>>
>>> - Dylan Bruzenak
>>> www.ideaswarm.com
>>>
>>>
>>>
>>> ___
>>> MacRuby-devel mailing list
>>> [email protected]
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>>
>>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+ MB to .app

#361: Embed MacRuby Target Adds 60+ MB to .app
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by lsansone...@…):

 Are you using 0.4 or 0.5 (trunk)? The rewrite of the new VM in C++ plus
 the static inclusion of LLVM unfortunately grew up the size of MacRuby in
 trunk. The dylib is about 28MB here (which contains code for both i386 and
 x86_64, so it can be cut in half if necessary). Due to heavy STL inlining
 certain object files are very big, this is a shame. We have a plan to put
 some object files on diet and also move the LLVM stuff we need into a
 shared library.

 Also, the Embed MacRuby target embeds everything, including the standard
 library, gems, and so on as you may have noticed. Most programs probably
 only need libmacruby.dylib. The target could potentially be changed to
 allow 2 modes, one that embeds everything and one that only embeds the
 dylib.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In


Hi Dylan,

Could you open a trac ticket and attach your new template there? It  
would be a better idea I guess, and we can also track its inclusion to  
trunk from there.


Thanks for the work, it looks great :)

Laurent

On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:

Message is being held pending moderator approval; let me know if I  
should post the actual file somewhere else :)


- Dylan

On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak   
wrote:
Good idea. I've attached it here. I may have accidentally added the  
build directory as well; this should be deleted from the template.


To test you can copy it to one of the template directories such as :  
~/Library/Application Support/Developer/Shared/Xcode/Project  
Templates/Application/MacRuby Application With Testing


Differences:

- Embed MacRuby target is included by default to easy deployment for  
first time users

- Tests directory has been added for tests
- test_stub.rb has been added with a starting test::unit case
- Unit Tests target has been added to run the tests
- test_suite.rb has been added to load up all tests from the Tests  
directory. This can easily be made recursive using Dir.glob.


I've left out the framework/obj-c testing stuff because it is  
difficult to get it working in cases where there is no objective-c;  
building the framework requires at least one class. A better way to  
handle that would be to write up a blog post on how to do this;  
mainly:


1.) Create a new Cocoa -> Framework target
2.) add the new framework to your unit test and .app targets so that  
it gets built when either target is run

3.) add a copy files step, targeting frameworks, to your .app target
4.) add the new framework(drag from the products folder) to both the  
link and copy steps of your .app target to include it with your .app  
file

5.) add "framework 'newframeworkname'" to your rb_main.rb file
6.) add "framework 'build/Debug/newframeworkname.framework' to your  
test_suite.rb file


After following these steps you can test any Obj-c classes added to  
the framework from Ruby, as well as any Ruby classes that depend on  
these custom classes.


- Dylan


On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti > wrote:

Hi Dylan,

Why don't you you post your template so people can look at it and  
give their feedback? People like Eloy would probably give their  
feedback ;)


- Matt



On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak   
wrote:
So, I've been mucking about with MacRuby lately. It's been fun so  
far. Thanks to all the devs for this great project.


I'm a pretty firm believer in unit testing my Ruby code. I love how  
Ruby on Rails and similar frameworks nudge you in the right  
direction by baking in an existing testing infrastructure.


I've got testing pretty much figured out and was wondering if the  
team would be open to modifying the basic Xcode project template to  
add unit testing, with a stub test and test_suite file to get  
started. This would also involve creating a framework for any  
objective-c code that the user writes so that it can be included in  
both the .app and the test files.


In addition it might be useful to include the 'embed mac ruby' and  
possibly a macrubyc target as well by default. These can always be  
removed if a user doesn't want them.


I can supply preliminary patches if this seems like a good route to  
go.


- Dylan Bruzenak
www.ideaswarm.com



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] Supported classes & methods diagram fed from rubyspec

2009-10-01 Thread Ben Schwarz


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
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

[MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed MacRuby to Project Template

#362: Add Unit Testing and Embed MacRuby to Project Template
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--
 I'm attaching a new version of the default project template.

 To test you can copy it to one of the template directories such as :
 ~/Library/Application Support/Developer/Shared/Xcode/Project
 Templates/Application/

 Differences:

 - Embed MacRuby target is included by default to easy deployment for first
 time users
 - Tests directory has been added for tests
 - test_stub.rb has been added with a starting test::unit case
 - Unit Tests target has been added to run the tests
 - test_suite.rb has been added to load up all tests from the Tests
 directory. This can easily be made recursive using Dir.glob.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed MacRuby to Project Template

#362: Add Unit Testing and Embed MacRuby to Project Template
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by dy...@…):

 If there's interest I can also port these changes to the other project
 templates.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In

Just opened https://www.macruby.org/trac/ticket/362 :)
As for the testing obj-c classes part, what is the best way to document that
? I'm not the best blogger in the world but I could write something up on my
personal blog or contribute a short how to somewhere in the documentation or
your website if that is preferred.

- Dylan

On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti
wrote:

> Hi Dylan,
>
> Could you open a trac ticket and attach your new template there? It would
> be a better idea I guess, and we can also track its inclusion to trunk from
> there.
>
> Thanks for the work, it looks great :)
>
> Laurent
>
>
> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>
>  Message is being held pending moderator approval; let me know if I should
>> post the actual file somewhere else :)
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak 
>> wrote:
>> Good idea. I've attached it here. I may have accidentally added the build
>> directory as well; this should be deleted from the template.
>>
>> To test you can copy it to one of the template directories such as :
>> ~/Library/Application Support/Developer/Shared/Xcode/Project
>> Templates/Application/MacRuby Application With Testing
>>
>> Differences:
>>
>> - Embed MacRuby target is included by default to easy deployment for first
>> time users
>> - Tests directory has been added for tests
>> - test_stub.rb has been added with a starting test::unit case
>> - Unit Tests target has been added to run the tests
>> - test_suite.rb has been added to load up all tests from the Tests
>> directory. This can easily be made recursive using Dir.glob.
>>
>> I've left out the framework/obj-c testing stuff because it is difficult to
>> get it working in cases where there is no objective-c; building the
>> framework requires at least one class. A better way to handle that would be
>> to write up a blog post on how to do this; mainly:
>>
>> 1.) Create a new Cocoa -> Framework target
>> 2.) add the new framework to your unit test and .app targets so that it
>> gets built when either target is run
>> 3.) add a copy files step, targeting frameworks, to your .app target
>> 4.) add the new framework(drag from the products folder) to both the link
>> and copy steps of your .app target to include it with your .app file
>> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
>> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
>> test_suite.rb file
>>
>> After following these steps you can test any Obj-c classes added to the
>> framework from Ruby, as well as any Ruby classes that depend on these custom
>> classes.
>>
>> - Dylan
>>
>>
>> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti 
>> wrote:
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak 
>> wrote:
>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>> Thanks to all the devs for this great project.
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>> on Rails and similar frameworks nudge you in the right direction by baking
>> in an existing testing infrastructure.
>>
>> I've got testing pretty much figured out and was wondering if the team
>> would be open to modifying the basic Xcode project template to add unit
>> testing, with a stub test and test_suite file to get started. This would
>> also involve creating a framework for any objective-c code that the user
>> writes so that it can be included in both the .app and the test files.
>>
>> In addition it might be useful to include the 'embed mac ruby' and
>> possibly a macrubyc target as well by default. These can always be removed
>> if a user doesn't want them.
>>
>> I can supply preliminary patches if this seems like a good route to go.
>>
>> - Dylan Bruzenak
>> www.ideaswarm.com
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>
> ___
> MacRuby-devel mailing list
> [email protected]
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed MacRuby to Project Template

#362: Add Unit Testing and Embed MacRuby to Project Template
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by lsansone...@…):

 I just gave it a try, it's awesome!

 I think we should definitely port the changes to the other templates, but
 we may first want to go with the main one and iterate on it until we are
 good. It's always painful to manage Xcode templates so it may be easier if
 we port the changes all in once.

 Also, regarding the test stuff, I think Eloy might want to comment, since
 he's our local test expert :)

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Supported classes & methods diagram fed from rubyspec


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
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel


___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In


Hi Dylan,

Ideally it would be awesome to have some documentation on the website  
(likely a tutorial):


http://www.macruby.org/documentation.html

The process of creating a website article is not trivial but Mike  
Sassak recently contributed a tutorial describing how to contribute to  
the website:


http://www.macruby.org/documentation/website-contributions.html

Laurent

On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:


Just opened https://www.macruby.org/trac/ticket/362 :)

As for the testing obj-c classes part, what is the best way to  
document that ? I'm not the best blogger in the world but I could  
write something up on my personal blog or contribute a short how to  
somewhere in the documentation or your website if that is preferred.


- Dylan

On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti > wrote:

Hi Dylan,

Could you open a trac ticket and attach your new template there? It  
would be a better idea I guess, and we can also track its inclusion  
to trunk from there.


Thanks for the work, it looks great :)

Laurent


On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:

Message is being held pending moderator approval; let me know if I  
should post the actual file somewhere else :)


- Dylan

On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak   
wrote:
Good idea. I've attached it here. I may have accidentally added the  
build directory as well; this should be deleted from the template.


To test you can copy it to one of the template directories such as :  
~/Library/Application Support/Developer/Shared/Xcode/Project  
Templates/Application/MacRuby Application With Testing


Differences:

- Embed MacRuby target is included by default to easy deployment for  
first time users

- Tests directory has been added for tests
- test_stub.rb has been added with a starting test::unit case
- Unit Tests target has been added to run the tests
- test_suite.rb has been added to load up all tests from the Tests  
directory. This can easily be made recursive using Dir.glob.


I've left out the framework/obj-c testing stuff because it is  
difficult to get it working in cases where there is no objective-c;  
building the framework requires at least one class. A better way to  
handle that would be to write up a blog post on how to do this;  
mainly:


1.) Create a new Cocoa -> Framework target
2.) add the new framework to your unit test and .app targets so that  
it gets built when either target is run

3.) add a copy files step, targeting frameworks, to your .app target
4.) add the new framework(drag from the products folder) to both the  
link and copy steps of your .app target to include it with your .app  
file

5.) add "framework 'newframeworkname'" to your rb_main.rb file
6.) add "framework 'build/Debug/newframeworkname.framework' to your  
test_suite.rb file


After following these steps you can test any Obj-c classes added to  
the framework from Ruby, as well as any Ruby classes that depend on  
these custom classes.


- Dylan


On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti > wrote:

Hi Dylan,

Why don't you you post your template so people can look at it and  
give their feedback? People like Eloy would probably give their  
feedback ;)


- Matt



On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak   
wrote:
So, I've been mucking about with MacRuby lately. It's been fun so  
far. Thanks to all the devs for this great project.


I'm a pretty firm believer in unit testing my Ruby code. I love how  
Ruby on Rails and similar frameworks nudge you in the right  
direction by baking in an existing testing infrastructure.


I've got testing pretty much figured out and was wondering if the  
team would be open to modifying the basic Xcode project template to  
add unit testing, with a stub test and test_suite file to get  
started. This would also involve creating a framework for any  
objective-c code that the user writes so that it can be included in  
both the .app and the test files.


In addition it might be useful to include the 'embed mac ruby' and  
possibly a macrubyc target as well by default. These can always be  
removed if a user doesn't want them.


I can supply preliminary patches if this seems like a good route to  
go.


- Dylan Bruzenak
www.ideaswarm.com



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel



___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #361: Embed MacRuby Target Adds 60+ MB to .app

#361: Embed MacRuby Target Adds 60+ MB to .app
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  defect   |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by dy...@…):

 I'm using trunk, so that explains the size discrepancy.

 How would I go about cutting the runtime size in half ?

 Two ideas related to the embedding:

 1.) Modify HotCocoa::ApplicationBuilder.deploy to take another argument,
 full deploy, which is false by default. If backwards compatibility is
 important here this could be changed to partial_deploy instead and default
 to the old behavior.

 OR

 2.) Add libmacruby.dylib to the project templates and use the standard
 copy framework build phase to deploy instead of the embed step

 There are two primary problems with embedding as it currently stands:

 1.) It picks up gems and probably shouldn't. The user should probably
 vendor any gems that should be included, explicitly.
 2.) It picks up both the libmacruby-static.a and libmacruby.1.9.0.dylib
 files, which is why the size is doubled. The extra .rb scripts are very
 small in comparison.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Xcode Project Template with Testing Baked In

How very self-referential; I love it :)
I'll have a look. Maybe wait until my fever goes away before I take a stab
at prose though.

- Dylan

On Fri, Oct 2, 2009 at 1:26 AM, Laurent Sansonetti wrote:

> Hi Dylan,
>
> Ideally it would be awesome to have some documentation on the website
> (likely a tutorial):
>
> http://www.macruby.org/documentation.html
>
> The process of creating a website article is not trivial but Mike Sassak
> recently contributed a tutorial describing how to contribute to the website:
>
> http://www.macruby.org/documentation/website-contributions.html
>
> Laurent
>
>
> On Oct 1, 2009, at 11:06 PM, Dylan Bruzenak wrote:
>
>  Just opened https://www.macruby.org/trac/ticket/362 :)
>>
>> As for the testing obj-c classes part, what is the best way to document
>> that ? I'm not the best blogger in the world but I could write something up
>> on my personal blog or contribute a short how to somewhere in the
>> documentation or your website if that is preferred.
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 11:07 PM, Laurent Sansonetti <
>> [email protected]> wrote:
>> Hi Dylan,
>>
>> Could you open a trac ticket and attach your new template there? It would
>> be a better idea I guess, and we can also track its inclusion to trunk from
>> there.
>>
>> Thanks for the work, it looks great :)
>>
>> Laurent
>>
>>
>> On Oct 1, 2009, at 7:50 PM, Dylan Bruzenak wrote:
>>
>> Message is being held pending moderator approval; let me know if I should
>> post the actual file somewhere else :)
>>
>> - Dylan
>>
>> On Thu, Oct 1, 2009 at 9:48 PM, Dylan Bruzenak 
>> wrote:
>> Good idea. I've attached it here. I may have accidentally added the build
>> directory as well; this should be deleted from the template.
>>
>> To test you can copy it to one of the template directories such as :
>> ~/Library/Application Support/Developer/Shared/Xcode/Project
>> Templates/Application/MacRuby Application With Testing
>>
>> Differences:
>>
>> - Embed MacRuby target is included by default to easy deployment for first
>> time users
>> - Tests directory has been added for tests
>> - test_stub.rb has been added with a starting test::unit case
>> - Unit Tests target has been added to run the tests
>> - test_suite.rb has been added to load up all tests from the Tests
>> directory. This can easily be made recursive using Dir.glob.
>>
>> I've left out the framework/obj-c testing stuff because it is difficult to
>> get it working in cases where there is no objective-c; building the
>> framework requires at least one class. A better way to handle that would be
>> to write up a blog post on how to do this; mainly:
>>
>> 1.) Create a new Cocoa -> Framework target
>> 2.) add the new framework to your unit test and .app targets so that it
>> gets built when either target is run
>> 3.) add a copy files step, targeting frameworks, to your .app target
>> 4.) add the new framework(drag from the products folder) to both the link
>> and copy steps of your .app target to include it with your .app file
>> 5.) add "framework 'newframeworkname'" to your rb_main.rb file
>> 6.) add "framework 'build/Debug/newframeworkname.framework' to your
>> test_suite.rb file
>>
>> After following these steps you can test any Obj-c classes added to the
>> framework from Ruby, as well as any Ruby classes that depend on these custom
>> classes.
>>
>> - Dylan
>>
>>
>> On Thu, Oct 1, 2009 at 6:31 PM, Matt Aimonetti 
>> wrote:
>> Hi Dylan,
>>
>> Why don't you you post your template so people can look at it and give
>> their feedback? People like Eloy would probably give their feedback ;)
>>
>> - Matt
>>
>>
>>
>> On Thu, Oct 1, 2009 at 4:26 PM, Dylan Bruzenak 
>> wrote:
>> So, I've been mucking about with MacRuby lately. It's been fun so far.
>> Thanks to all the devs for this great project.
>>
>> I'm a pretty firm believer in unit testing my Ruby code. I love how Ruby
>> on Rails and similar frameworks nudge you in the right direction by baking
>> in an existing testing infrastructure.
>>
>> I've got testing pretty much figured out and was wondering if the team
>> would be open to modifying the basic Xcode project template to add unit
>> testing, with a stub test and test_suite file to get started. This would
>> also involve creating a framework for any objective-c code that the user
>> writes so that it can be included in both the .app and the test files.
>>
>> In addition it might be useful to include the 'embed mac ruby' and
>> possibly a macrubyc target as well by default. These can always be removed
>> if a user doesn't want them.
>>
>> I can supply preliminary patches if this seems like a good route to go.
>>
>> - Dylan Bruzenak
>> www.ideaswarm.com
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>>
>>
>>
>> ___
>> MacRuby-devel mailing list
>> [email protected]

[MacRuby-devel] How to compile all ruby files in a project using macrubyc

I'm a bit of a newbie when it comes to command line compilation.
Is there an easy way for me to basically just say: compile everything
recursively, starting at this directory ? Given that, what would be the best
way to then integrate that with an Xcode project as part of a target ?

Also, is this far enough along to consider adding to the project templates
by default ?

thanks!

- Dylan
___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] Supported classes & methods diagram fed from rubyspec

2009-10-01 Thread Ben Schwarz

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
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] [MacRuby] #362: Add Unit Testing and Embed MacRuby to Project Template

#362: Add Unit Testing and Embed MacRuby to Project Template
-+--
 Reporter:  dy...@…  |   Owner:  lsansone...@…
 Type:  enhancement  |  Status:  new  
 Priority:  blocker  |   Milestone:   
Component:  MacRuby  |Keywords:   
-+--

Comment(by dy...@…):

 :)

 Good idea on the wait to merge part. I do so hate replicating work.

 I'm new to Ruby 1.9; looks like test::unit was pulled in favor of minitest
 and a thin interface layer wrapper around it to provide basic test::unit
 compatibility. I see a spec.rb in there as well; might be interesting to
 include a stub for that kind of test as well.

-- 
Ticket URL: 
MacRuby 

___
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Re: [MacRuby-devel] How to compile all ruby files in a project using macrubyc