Lithium Roadmap

199 views
Skip to first unread message

ijuma

unread,
Apr 28, 2013, 8:59:01 AM4/28/13
to scala-i...@googlegroups.com
Hi,

Is there a plan to update the Lithium Roadmap[1]? Curious about what is coming next. :)

Best,
Ismael

iulian dragos

unread,
Apr 29, 2013, 10:03:51 AM4/29/13
to scala-i...@googlegroups.com, scala-ide-dev
Hi Ismael,

This is a good moment to ask the community about what cool things they have in store! We've been getting recently some very cool contributions. It's been really great to see the community stepping up and lending a hand, and I'm confident that we'll have more and more great features coming our way! It'd be good to know what other things people feel like working on, and plan accordingly.

We'll update the page as soon as we have a better picture of what's next. On our side, we're looking into improving the Play development experience in Eclipse, so it's a safe bet that the roadmap will reflect that.

cheers,
iulian



--
You received this message because you are subscribed to the Google Groups "Scala IDE User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais

Fernando Racca

unread,
Apr 29, 2013, 11:22:23 AM4/29/13
to scala-i...@googlegroups.com, scala-ide-dev
My wishlist:

- Improvements to the Debugger: 
-- The new Scala Debugger already helps, but further improvements, for instance to make the Stack much more readable (rather than Clas$$anonfun$anonfun$apply($mcV$sp$6.apply and so on)
-- More intelligent step intos, that allow faster code navigation.
- SBT integration (there's a plugin going on to add SBT properties editor). In particular, it would be great to see ~ test within Eclipse, reporting to ScalaTest view.

Thanks!

Simon Schäfer

unread,
May 8, 2013, 6:21:01 PM5/8/13
to scala-i...@googlegroups.com

On 04/29/2013 05:22 PM, Fernando Racca wrote:
My wishlist:

- Improvements to the Debugger: 
-- The new Scala Debugger already helps, but further improvements, for instance to make the Stack much more readable (rather than Clas$$anonfun$anonfun$apply($mcV$sp$6.apply and so on)
-- More intelligent step intos, that allow faster code navigation.
- SBT integration (there's a plugin going on to add SBT properties editor). In particular, it would be great to see ~ test within Eclipse, reporting to ScalaTest view.
Could you please create tickets for these things? Here on the mailing list they are definitely lost.

Fernando Racca

unread,
May 9, 2013, 5:23:05 AM5/9/13
to scala-i...@googlegroups.com

Simon Schäfer

unread,
May 9, 2013, 6:14:54 AM5/9/13
to scala-i...@googlegroups.com
Thanks for that Fernando, nevertheless the ticket tracker is at https://www.assembla.com/spaces/scala-ide/support/tickets, could you please move the tickets to that place?

@typesafe team
Is it an oversight that it is possible to create tickets on GitHub? Some time ago I remember it was not possible at all.

Mirco Dotta

unread,
May 9, 2013, 7:18:18 AM5/9/13
to scala-i...@googlegroups.com
Hi Simon,

Yes, it was an oversight (don't know how/when it happened). I've disabled the GH issues - tickets should be filed here https://scala-ide-portfolio.assembla.com/spaces/scala-ide/support/tickets


On 05/09/2013 11:23 AM, Fernando Racca wrote:
I've created 3 tickets:



However, I'm not on clear on what the "Stack Trace Pretty Printer"  should do. Fernando, I commented on the ticket, could you please have a look and answer directly in the ticket?
These are definitely good suggestions, but they don't belong to the Scala IDE. These features should be supported by a Sbt Eclipse plug-in. You pointed to this project https://bitbucket.org/takezoe/eclipse-scala-tools/wiki/Home, any reason for not opening the tickets there?

By the way, thanks a lot for the link, I didn't know about it. Will have a look, maybe we could ask the maintainer to integrate the plug-in in the ecosystem...

-- Mirco

Roland Kuhn

unread,
May 9, 2013, 7:25:41 AM5/9/13
to scala-i...@googlegroups.com
Hi Mirco,

unless I misunderstood something we’ve been forced to enable the issues to make the new pull-request validator work; are you not using that? Or can we actually disable issues and still “have” them in some sense?

Regards,

Roland


Dr. Roland Kuhn
Akka Tech Lead
Typesafe – Empowering professional developers to build amazing apps.
twitter: @rolandkuhn

See you at Scala Days 2013 in NYC!
June 10th - June 12th
www.scaladays.org

Mirco Dotta

unread,
May 9, 2013, 7:34:27 AM5/9/13
to scala-i...@googlegroups.com
Hi Mirco,

unless I misunderstood something we’ve been forced to enable the issues to make the new pull-request validator work; are you not using that? Or can we actually disable issues and still “have” them in some sense?

Ah, I was not aware of this. I guess we'll find out soon if that was required.

iulian dragos

unread,
May 10, 2013, 9:18:44 AM5/10/13
to scala-ide-dev, scala-i...@googlegroups.com



On Fri, May 10, 2013 at 1:11 AM, Oscar Vargas Torres <oscar...@gmail.com> wrote:
What about Eclipse RCP applications with scala bundles? For example, this has been for a long time:

https://www.assembla.com/spaces/scala-ide/tickets/1919#/activity/ticket:

Is it still valid? could you please comment if that's still the case?

At any rate, I don't think we'll be working on this (community contributions welcome!) since maven/tycho can build everything correctly (and package products, etc.)

iulian
 


--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

Mirco Dotta

unread,
May 13, 2013, 10:42:19 AM5/13/13
to scala-i...@googlegroups.com
On May 9, 2013, at 1:34 PM, Mirco Dotta wrote:

Hi Mirco,

unless I misunderstood something we’ve been forced to enable the issues to make the new pull-request validator work; are you not using that? Or can we actually disable issues and still “have” them in some sense?

Ah, I was not aware of this. I guess we'll find out soon if that was required.

Turns out we need to keep GH issues enabled or the PR validator won't run. Please, do not open tickets on GitHub, use instead our Assembla page http://scala-ide-portfolio.assembla.com/spaces/scala-ide/support/tickets. I know this isn't ideal, but that's how things are at the moment, hopefully we can fix this limitation in the future.

-- Mirco


---------------
Mirco Dotta
PSE-D, 1015 Lausanne, Switzerland
Twitter: @mircodotta
Reply all
Reply to author
Forward
0 new messages