« Return to Thread: Merb support
Re: Merb support
by Erno Mononen
::
Rate this Message:
Hi Matt,
Matt Aimonetti wrote:
>
> Great job Erno,
>
> Anyway, I did this all before the Rails/Merb merge was announced,
> which obviously impacts this effort -- once Rails 3 is out
> separate Merb support in the IDE will gradually become obsolete.
>
> Actually, now that Rails 3 will support multiple stacks and modularity
> we will need all the features you worked on for Rails 3. After all
> merb 2 == rails 3 so it would be really too bad to give up on features
> that will be required very soon. (and which are already required for
> Merb devs and people wanted to have an idea of what kind of new stuff
> rails3 will have)
Yes, I think one option on how to support Rails 3 in the IDE is to build
on top of Merb support (the other options being building on top of the
existing Rails support or doing it separately). I think I read somewhere
that you should have an alpha version of Rails 3 out sometime in May, is
that correct? Would that mean a final version by the end of the year or
so, or is that too early to tell? We'll need to look at how this fits
into NetBeans schedules and consider what would be the best way to
deliver rails3/merb support -- a module on the update center gives us
more flexibility to deliver updates etc. until things stabilize.
Erno
>
> - Matt
>
>
>
> On Fri, Jan 9, 2009 at 6:51 AM, Erno Mononen <Erno.Mononen@...
> <mailto:Erno.Mononen@...>> wrote:
>
> Hi folks,
>
> Before Christmas I checked in basic support for Merb apps, the
> code is in the ruby.merbproject module, but it isn't part of the
> standard build. Currently it covers:
> - new project wizard
> - project customizer
> - logical view
> - running Merb apps
> - running tests
> - Rake runner
> - IRB
> - possibly some other standard project stuff that I don't recall now
>
> I haven't had much time to test, let alone to polish it, so except
> a rough ride if you give it a try.
>
> Anyway, I did this all before the Rails/Merb merge was announced,
> which obviously impacts this effort -- once Rails 3 is out
> separate Merb support in the IDE will gradually become obsolete.
> Given that and the fact that I've got a ton of other things on my
> plate, I'm afraid that I can't spend much more time on this. I'll
> try to find the time to do some rudimentary testing, fix the most
> obvious bugs and publish the module on the update center for 7.0.
> If anyone wants to take over the module and develop it further,
> you're most welcome to do so.
>
> Cheers,
> Erno
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> <mailto:dev-unsubscribe@...>
> For additional commands, e-mail: dev-help@...
> <mailto:dev-help@...>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
Matt Aimonetti wrote:
>
> Great job Erno,
>
> Anyway, I did this all before the Rails/Merb merge was announced,
> which obviously impacts this effort -- once Rails 3 is out
> separate Merb support in the IDE will gradually become obsolete.
>
> Actually, now that Rails 3 will support multiple stacks and modularity
> we will need all the features you worked on for Rails 3. After all
> merb 2 == rails 3 so it would be really too bad to give up on features
> that will be required very soon. (and which are already required for
> Merb devs and people wanted to have an idea of what kind of new stuff
> rails3 will have)
Yes, I think one option on how to support Rails 3 in the IDE is to build
on top of Merb support (the other options being building on top of the
existing Rails support or doing it separately). I think I read somewhere
that you should have an alpha version of Rails 3 out sometime in May, is
that correct? Would that mean a final version by the end of the year or
so, or is that too early to tell? We'll need to look at how this fits
into NetBeans schedules and consider what would be the best way to
deliver rails3/merb support -- a module on the update center gives us
more flexibility to deliver updates etc. until things stabilize.
Erno
>
> - Matt
>
>
>
> On Fri, Jan 9, 2009 at 6:51 AM, Erno Mononen <Erno.Mononen@...
> <mailto:Erno.Mononen@...>> wrote:
>
> Hi folks,
>
> Before Christmas I checked in basic support for Merb apps, the
> code is in the ruby.merbproject module, but it isn't part of the
> standard build. Currently it covers:
> - new project wizard
> - project customizer
> - logical view
> - running Merb apps
> - running tests
> - Rake runner
> - IRB
> - possibly some other standard project stuff that I don't recall now
>
> I haven't had much time to test, let alone to polish it, so except
> a rough ride if you give it a try.
>
> Anyway, I did this all before the Rails/Merb merge was announced,
> which obviously impacts this effort -- once Rails 3 is out
> separate Merb support in the IDE will gradually become obsolete.
> Given that and the fact that I've got a ton of other things on my
> plate, I'm afraid that I can't spend much more time on this. I'll
> try to find the time to do some rudimentary testing, fix the most
> obvious bugs and publish the module on the update center for 7.0.
> If anyone wants to take over the module and develop it further,
> you're most welcome to do so.
>
> Cheers,
> Erno
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> <mailto:dev-unsubscribe@...>
> For additional commands, e-mail: dev-help@...
> <mailto:dev-help@...>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: Merb support
| Free embeddable forum powered by Nabble | Forum Help |
