.
macruby-devel@lists.macosforge.org
Subject: Re: [MacRuby-devel] The future of MacRuby
Message-ID: d23125eb-0b40-4f7b-bb6c-6d739ed4d...@gmail.com
Content-Type: text/plain; charset=windows-1252
Can we get the issues section enabled on github and move off of Trac?
(Not sure how hard it would
When I was still at Apple, I actually started work on a library for MacRuby
backed by CoreData, but I had to leave it before it was done. To address the
why question: CoreData ties in very closely with a lot of the Cocoa UI
libraries (and other libraries). It also has features that other Ruby
I can start migrating the macruby-Recipes repository to the wiki section of
Github, but I'd like to make the case they should be in a sub-module or
repository that users can download directly, not just view on the wiki.
I've started, but have largely failed -- due to a new job -- to port
Apr 2012 23:40:39 +0200
From: Eloy Duran eloy.de.en...@gmail.com
To: MacRuby development discussions.
macruby-devel@lists.macosforge.org
Subject: Re: [MacRuby-devel] The future of MacRuby
Message-ID: d23125eb-0b40-4f7b-bb6c-6d739ed4d...@gmail.com
Content-Type: text/plain; charset=windows-1252
I was wondering if there would be benefit to writing (a) Generator(s) ala'
Rails' rails script for the stubbing out of apps and m,v,c ? Imagine:
facet new application name
facet g model AwesomeModelName!
…
Thoughts?
I had started on rewriting my tools for that for MacRuby, actually
On 9/04/2012, at 8:23 PM, Joshua Ballanco wrote:
What sort of information would you like to see on such a page?
Your Boston.rb video covers most of what I wanted to know. I might write
something up myself and put it on the wiki for review.
Henry
eloy.de.en...@gmail.com
To: MacRuby development discussions.
macruby-devel@lists.macosforge.org
Subject: Re: [MacRuby-devel] The future of MacRuby
Message-ID: d23125eb-0b40-4f7b-bb6c-6d739ed4d...@gmail.com
Content-Type: text/plain; charset=windows-1252
Can we get the issues section enabled
, 7 Apr 2012 23:40:39 +0200
From: Eloy Duran eloy.de.en...@gmail.com (mailto:eloy.de.en...@gmail.com)
To: MacRuby development discussions.
macruby-devel@lists.macosforge.org
(mailto:macruby-devel@lists.macosforge.org)
Subject: Re: [MacRuby-devel] The future of MacRuby
Message-ID: d23125eb-0b40
@lists.macosforge.org
Subject: Re: [MacRuby-devel] The future of MacRuby
Message-ID: d23125eb-0b40-4f7b-bb6c-6d739ed4d...@gmail.com
Content-Type: text/plain; charset=windows-1252
Can we get the issues section enabled on github and move off of Trac? (Not
sure how hard it would be to import all
On 7/04/2012, at 11:24 PM, Francis Chong fran...@ignition.hk wrote:
Automatic Reference Counting implements automatic memory management for
Objective-C objects and blocks. If you read MacRuby source code, you will
found that the VM is not even written in Objective-C!
This is why a one page
On 6 Apr 2012, at 00:06, Matt Aimonetti wrote:
Many of you have been wondering what is going on with the MacRuby project
given the lack of up-to-date releases and overall communication.
I feel we owe you some explanation.
Matt, as someone trying to ship a product based on MacRuby, I'd
While i totally agree the points here, a more pressing need, IMHO, is fixing
bugs and incompatibility of MacRuby such that what works on other
implementation just works in MacRuby,
For instance, require_relative is not implemented which breaks a lot of 1.9
ruby code.
tl;dr: I propose getting tutorials and code under one structured collection, and
to create classes that wrap Core Data in the same way HotCocoa wraps NSViews.
I agree with the sentiments about setting ourselves apart. How do we do that?
Please allow me to pontificate. I apologize for the length.
Compare with ActiveRecord/DataMapper, i really have no love on Core Data.
If MacRuby could run all those ActiveRecord/DataMapper adapters, there are few
reason to use a Core Data wrapper (much like ruby dev will not ever normally
use mysql/postgres gem directly). Certainly if such wrapper
On Friday, April 6, 2012 at 11:06 PM, Henry Maddocks wrote:
The MacRuby VM is very nicely tailored to the job of running on top of the
Objective-C runtime. It is also fairly mature. Personally, I see no
technical reason that a proliferation of VMs should be a problem (there are
at least
On 7/04/2012, at 6:13 PM, Joshua Ballanco jball...@gmail.com wrote:
Regarding ARC, MacRuby cannot use ARC. That is, MacRuby cannot use the Obj-C
implementation of ARC.
Why is that?
Henry
___
MacRuby-devel mailing list
Yes, ARC as is can't be used in MacRuby, but the principles can be
ported. Which is what I did, more or less, in an experimental branch.
Now, there are various challenges to solve in order to reach
stability, but don't worry, we will get there.
Laurent
2012/4/7 Francis Chong fran...@ignition.hk:
this is a great news. looking forward to see it in action!
Laurent Sansonetti 於 2012年4月7日 下午8:37 寫道：
Yes, ARC as is can't be used in MacRuby, but the principles can be
ported. Which is what I did, more or less, in an experimental branch.
Now, there are various challenges to solve in order to
The technology by the name “ARC” actually inserts the required code at compile
time and only for Objective-C(++). The principal of ARC, however, can be
applied to MacRuby.
On 7 apr. 2012, at 13:13, Henry Maddocks wrote:
On 7/04/2012, at 6:13 PM, Joshua Ballanco jball...@gmail.com wrote:
Can we get the issues section enabled on github and move off of Trac? (Not
sure how hard it would be to import all of the old trac stuff to Github).
Would be nice to consolidate everything in one place.
dan
On Thu, Apr 5, 2012 at 3:06 PM, Matt Aimonetti mattaimone...@gmail.comwrote:
*Many
Can we get the issues section enabled on github and move off of Trac? (Not
sure how hard it would be to import all of the old trac stuff to Github).
Would be nice to consolidate everything in one place.
I think that’s an excellent idea. However, it’s probably better to first import
tickets
Can you import before it's open? I just assumed it wasn't accessible at all
until enable? It looks like forgeplucker (http://home.gna.org/forgeplucker/)
has support to pull tickets out of trac and dump to JSON. Should be pretty
easy to go from JSON to GitHub API I'd expect.
I can take a look and
Can you import before it's open? I just assumed it wasn't accessible at all
until enable? It looks like forgeplucker (http://home.gna.org/forgeplucker/)
has support to pull tickets out of trac and dump to JSON. Should be pretty
easy to go from JSON to GitHub API I'd expect.
Well, we’d open
I've been a lurker in this mailing list for a while now. Sad to hear we've lost
a project lead but glad to hear Matt has identified many of the issues I've
been feeling myself.
I'm a self-taught web developer. I never had any interest in learning native
app development until I heard about
Thanks a lot Andrew for the feedback. I think you have some really great
points in there.
I'm letting others weigh-in to gage the interest and then we can start
getting organized.
- Matt
On Fri, Apr 6, 2012 at 9:49 AM, Andrew Havens andrew.hav...@evanta.comwrote:
I've been a lurker in this
I've been a happy user of MacRuby for a while now and I have been intending to
give back by helping with the development, so Matt's message is timely and
inspirational. Here is a brain dump of some of the thoughts I've had about the
project.
I'd like to see a statement of the goal for MacRuby.
On Friday, April 6, 2012 at 8:00 PM, Henry Maddocks wrote:
I have Ruby, C, C++ and Obj-C experience, but the one thing that is holding
me up from contributing is a simple one page description from the source
level of what happens when you run a script in MacRuby. Is anyone able to
write
What I'd like to suggest is the following:
1. Define clear goals for MacRuby that we can easily evaluate:
- Focus primarily on making MacRuby the tool to use for quickly
prototyping OS X and iOS applications.
This is the wrong thing for MacRuby to focus on, in my opinion.
I've
*Many of you have been wondering what is going on with the MacRuby project
given the lack of up-to-date releases and overall communication.
I feel we owe you some explanation.
As a lot of you have noticed, our de-facto project leader Laurent
Sansonetti has been M.I.A since October 2011, his last
On Apr 5, 2012, at 4:06 PM, Matt Aimonetti wrote:
• the target platform (OS X) isn't the one we all really want to target
(iOS)
The target platform is only 1 of 2 that many of us really want to target?
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303)
Absolutely, thanks for clarifying my poorly worded statement.
- Matt
On Fri, Apr 6, 2012 at 12:12 AM, Scott Ribe scott_r...@killerbytes.comwrote:
On Apr 5, 2012, at 4:06 PM, Matt Aimonetti wrote:
• the target platform (OS X) isn't the one we all really want to
target (iOS)
The
Wow, lots of news there. Thanks for the explanation Matt.
I created a quick survey to help quantify and gauge how the community
feels. Please fill it out.
http://www.surveymonkey.com/s/J5JLMFT
Daniel
On Thu, Apr 5, 2012 at 4:06 PM, Matt Aimonetti mattaimone...@gmail.comwrote:
*Many of you
Personally, I want to see this project succeed like Rubinus and JRuby has,
but is it possible without some support from Apple? That said, I would love
to help out with building sample apps, docs, and building some gems. What
helped me the most when learning to develop on iOS was the availability
Thanks for the update Matt.
I haven't actually used MacRuby since my last app, although would love to see
it for iOS (as well as keeping OS X support). I guess that would get a lot more
people interested too, given the success and popularity of the iOS platform. I
think most of your other
Thanks for all the info Matt.
As a very new member of the MacRuby community, I don't feel like I have the
right to decide about it's future, but here are some of the things that I think
would help MacRuby create enough hype and get a lot more attention from
developers:
- Add the necessary
Thank you for your update. It's sad that Apple seems abandon the MacRuby
project, but this is also a chance to bring MacRuby closer to what we (as
developers and users) need instead of what Apple want.
I certainly agree that removing libauto is a primary goal, as OSX and iOS are
both going to
On Fri, 23 Dec 2011 09:23:25 -0800 Conrad Taylor conra...@gmail.com
wrote:
Objective-C isn't controlled by Apple. However, the Cocoa and iOS
It is for practical purposes controlled by Apple. Apple defines the
language and its semantics at this point, and the Mac is essentially
the only
On Thursday, December 22, 2011 at 11:15 PM, Jeff Hemmelgarn wrote:
I cannot separate the stakeholders (and their issues) from the roadmap.
MacRuby will go where people who care to push want it to go. Barring getting
a job where I am paid to push MacRuby in a certain direction, I will be at
Josh,
I guess I am just getting used to working with an open-source project. I am
used to discussing requirements and possible solutions with my cow-orkers
before writing code. It is a big change for me to just go ahead and write
something and ask to have it included. I'll give it a try.
I
On Wed, Dec 21, 2011 at 2:45 PM, Dan Farrand
d...@greenrivercomputing.comwrote:
It's been great to read everyones thoughts on this subject. It's helped
me get a better perspective on what MacRuby is.
I am a Ruby newbie but have been working on Mac for a long time, mostly in
the business
On Dec 23, 2011, at 2:47 AM, isaac kearse wrote:
Are you aware that HotCocoa is being actively developed again?
https://github.com/HotCocoa/hotcocoa/blob/master/History.markdown
That's good to know. It would also be good to know, if and when the subject
ever comes up, what its mission
Hey all,
I think we need to understand that this thread has been conflating two
different issues: 1. Apple support for MacRuby, and 2. the future roadmap
for MacRuby.
As for #1: I would respectfully suggest that if you feel you need some sort
of official blessing from Apple in order to continue
Hi Jordan,
Are you aware that HotCocoa is being actively developed again?
https://github.com/HotCocoa/hotcocoa/blob/master/History.markdown
There is a good overview of contributions over time here:
https://github.com/HotCocoa/hotcocoa/graphs/impact
Cheers,
Isaac
On Wed, Dec 21, 2011 at 8:56
All,
I cannot separate the stakeholders (and their issues) from the roadmap.
MacRuby will go where people who care to push want it to go. Barring getting a
job where I am paid to push MacRuby in a certain direction, I will be at best a
small addition to the overall effort. Given that, I
Jeff;
I probably can't help a lot here because frankly I'm not involved in
development and only come to the forums as a casual user. However I will add
my 2¢ below.
Sent from my iPad
On Dec 20, 2011, at 11:57 PM, Jeff Hemmelgarn jhemm...@gmail.com wrote:
I guess my main angst is with
This is a frustration of mind, that is Apples lack of buy in or official
support is frustrating. It is one of the reasons I don't invest a lot of
personal effort into following Mac Ruby. Going the Mac Ruby way means
spending a lot of effort to learn something that may never get the
I get the feeling few of you are every day ruby developers, there are
incompatibilities between all ruby versions, yes even between 1.9 and 1.8 so
why on earth should macruby be a finnished Sofa, snug and compfy. It is part of
rubys attraction that it still evolves.
If I want write a web
Apple has funded Laurent's work on MacRuby for quite a
while. Jordan has played a major role in this project
(and a number of other Open Source projects :-) and I'm
sure he is working to keep the effort going. However,
he can't make any promises. Specifically:
We don't comment on future
It's been great to read everyones thoughts on this subject. It's helped me get
a better perspective on what MacRuby is.
I am a Ruby newbie but have been working on Mac for a long time, mostly in the
business applications space.
Here is my 2 cents. I am very much a Mac fanboy and consequently
I would like to probe sentiment around the future for MacRuby ? is there a
future ? I am drawn to it - I like Ruby as a language and development
approach. I appreciate the entrance it provides into Cocoa without having to
sign up for Objective-C. But where does it fit within Apple's longer
if you don't have fun, you are doing it wrong.
On 20 Dec 2011, at 17:06, Dan Farrand d...@greenrivercomputing.com wrote:
I would like to probe sentiment around the future for MacRuby ? is there a
future ? I am drawn to it - I like Ruby as a language and development
approach. I
Ha. I like that. It should be fun.
MacRuby is fun. MacRuby is also not yet perfect. Whatever politics are
happening inside Apple, we're not privy to them. I don't think anyone at Apple
hates it, given that they've fixed major bugs relatively recently.
Don't consider it a waste of time. You
I wonder if we couldn't kickstarter a fund to let apple hire someone full time
to do macruby work?
Anyone @ the mothership know if that'd be well received?
-Kevin
On Dec 20, 2011, at 12:02 PM, Dominic Dagradi wrote:
Ha. I like that. It should be fun.
MacRuby is fun. MacRuby is also not
On Dec 20, 2011, at 6:07 PM, Kevin Poorman wrote:
I wonder if we couldn't kickstarter a fund to let apple hire someone full
time to do macruby work?
MacRuby is an open source project and, as such, is (and always has been) free
to seek or employ additional resources entirely on its own; it
As someone who has been trying to help in my vanishing spare time, the actions
of Apple with regard to MacRuby are very important to my motivation. No one
outside of Apple can integrate it with XCode, or allow it on iOS devices. If
these things don't happen, MacRuby will be much less than it
No one outside of Apple can integrate it with XCode, or allow it on iOS
devices.
While the XCode part is partly true (due to limited APIs to say the least),
MacRuby doesn't need to be blessed by Apple to run on iOS. Legally, Apple
isn't blocking anything.
I see that as a double edged sword,
Good questions.
I'd certainly like to see Apple put its weight behind MacRuby and leave us with
an official word of support. Like you I have a hard time putting much effort
into something that is wishy washy in its relationship with Apple. I still use
Python for most of my scripting needs
The XCode integration is actually something that I find bothersome, especially
the reliance upon nibs or whatever they are called. As an IDE goes XCode has
never really been professional level, though I know that statement frustrates
many it is very much true.
As to nibs well the whole
I guess my main angst is with the the direction and philosophy of the project.
One vision of MacRuby has it being a fully compatible ruby implementation, that
happens to be built on the Objective-C runtime and have good integration to all
of the libraries provided by Apple, but wrap the guts so
On Dec 21, 2011, at 12:43 AM, David Frantz wrote:
As to nibs well the whole thing is just very obtuse and frustrating to me.
Mind you my background is not the same as many here, being focused on
industrial automation, but if find the use of nibs and Interface builder to
be very taxing
60 matches
Mail list logo
