Refactorings

Hi,

Can I ask what your plan/roadmap is with respect to refactorings ?

The plugin is a extremely helpful in our work.

Give we work in a TDD style, the current main pain point for us is refactoring, such move class/object/trait and for it to work consistently.

Thanks

评论操作 固定链接

I'll add complete roadmap of our team for next two months:

My roadmap:
1. Improving completion, adding new completion features.
2. Implicits analyzes, intention actions (like make implicit explicit)
3. Improve current adding import/import ordering feature.
4. Fixing red code (it is always in my roadmap)
5. Finish smart step into (it's almost done, just few things left), and other debbugging improvements (if I have time).

Dmitry roadmap:
1. Finish all recent xml/scaladoc improvements
2. String interpolation feature support
3. Improving multiline string typing
4. Start to support Lift or Play 2.0 (I think Play 2.0 is more likely)

Pavel roadmap:
1. Move refactoding improvements and additional features (that is what are you looking for)
2. Project/module creation wizard usability improvements
3. JPS compilation server support.
4. Probably rewrite Live Templates feature to be much more usable

Best regards,
Alexander Podkhalyuzin.

0
评论操作 固定链接

Cool, thanks for the info.

Are you guys giving a talk at ScalaDays ?

0
评论操作 固定链接

On 3/14/12 2:26 PM, Alexander Podkhalyuzin wrote:

4. Start to support Lift or Play 2.0 (I think Play 2.0 is more likely)


Is there someplace where we can vote for Lift support?

Donald

0
评论操作 固定链接

+1 for Lift-support

--
Andreas

0
评论操作 固定链接

Lift support is major thing. So it's enough just to say here about your vote.

And yes. We are going to give a talk on ScalaDays 2012.

Best regards,
Alexander Podkhalyuzin.

0
评论操作 固定链接

+1 for official Lift support

0
评论操作 固定链接

We're using Lift (and expecting to take the new system operational this
summer!).

What, if I might ask, is on the plan for Lift support?

Thank you,

Donald

On 3/14/12 10:12 PM, Alexander Podkhalyuzin wrote:

Lift support is major thing. So it's enough just to say here about your vote.

>

And yes. We are going to give a talk on ScalaDays 2012.


0
评论操作 固定链接

Unfortunately I have no experience in Lift development.
Usually any framework support means understanding what usability problems current state have and removing this usability problems (so it means before starting to support it, you should do some project using IDEA).
First important thing, which is always important is project/module creation wizard. I think it must be implemented before IntelliJ IDEA 12 release. Second things on any framework support it's understanding xml <-> code references and fixing it (some of such things is done now, but it's not enough anyway). Any other specific things you can post to our tracker (so it can be fixed with other Lift development).

Best regards.
Alexander Podkhalyuzin.

0
评论操作 固定链接

+2 for Play 2 support
+1 for Lift support

Jon

0
评论操作 固定链接

Great will pop along and say hello.

0
评论操作 固定链接

i'd say go for lift. my reason is that play is easier to use out of the box, it would not benefit as much as lift. compared to play, lift is more complex to set up. play "just works".
but since idea already supports play for java, adding lift would also take longer. i don't know. throw a coin.

0
评论操作 固定链接

Hi Alexander,

Any specifics on #1 (completion)?

Thanks,
-tt

0
评论操作 固定链接

+1 for official Lift support


And I would buy Ultimate if you add Lift :)

0
评论操作 固定链接

There some usability problems with completion and even more, just not reported here: http://youtrack.jetbrains.com/issues/SCL?q=%23Completion+%23Unresolved
Also I want to add some features from Java editor: http://confluence.jetbrains.net/display/IDEADEV/Completion+features
Add name completion for class names (like companion object), not sure about members names, because type information is after name.

Best regards,
Alexander Podkhalyuzin.

0
评论操作 固定链接

+1 for official Lift support!

Thanks
Soeren

0
评论操作 固定链接

Hi Alexander,

I'm happy that the completion is going to get more attention.

Here are some addtional Scala code completion feature requests.

1. Smart completion for enum members.

When a method take an enum as a parameter, in IDEA Java editor I can simply invoke smart completion, and pick the right enum value.
Since many of the APIs we're interacting with are Java-based (Spring,JPA,etc,etc), having the same feature in the Scala editor would be very useful.

http://youtrack.jetbrains.com/issue/SCL-1567

2. Smart completion for enum annotation parameters

Closely related to previous request.
Again, typical Spring/JEE/JPA APIs are full of annotations having one of more enum parameters. IDEA Java editor saves a lot of typing here through smart completion.

http://youtrack.jetbrains.com/issue/SCL-2638

3. The new IDEA 11.1 EAP "chained completion" feature (http://blogs.jetbrains.com/idea/2012/02/chained-expression-completion/)

It would be nice to have it for Scala, obviously.
Shall I file a separate ticket?

Thanks,
Taras

0
评论操作 固定链接

You can create a ticket about chained completion too, I planned to implement it too.

Best regards,
Alexander Podkhalyuzin.

0
评论操作 固定链接

+(Price of at least one IDEA license) to Play 2.0 support. Currently the paid version offers no benefits to me as I'm not user of Hibernate, Spring, etc. But I would gladly pay for 2.0 support.

Please add it :)

0
评论操作 固定链接

++ Play 2.0 support

0
评论操作 固定链接

Hi Alexander,

Ok, here are two additional code completion feature requests:

"code completion: support "chained completion" feature":
http://youtrack.jetbrains.com/issue/SCL-4121

"code completion: suggest "classOf[]" in relevant context":
http://youtrack.jetbrains.com/issue/SCL-4120

Thanks in advance,
Taras

0

请先登录再写评论。