[ANN] Struts Assistant 1.01 released

- The Diagram performance improved
- Read-only files handling fixed for Struts Configuration Wizard
- Tiles detection/installation fixed for Struts Configuration Wizard
- Checking for interference with other plugins removed
- Assorted bugfixes

18 comments

anima wrote:

- Checking for interference with other plugins removed


Does this mean that there is no longer any interference with the other Struts plugins, or
you just don't check for them any more?

0

The detection procedure was unstable, so i switched it off. The only plugin interferencing with Struts Assistant that i know is Struts Plugin, and it reports the interference by itself.

0

anima wrote:

The detection procedure was unstable, so i switched it off. The only plugin interferencing with Struts Assistant that i know is Struts Plugin, and it reports the interference by itself.


Sorry for stupid question but did you and authors of another Struts
plugins ever think about putting its together? Are there any reasons to
keep its separated?

0

I see no reason to integrate Struts Assistant with other plugins. It provides the same functionality in its own manner, and let the users choose what they like.

0

Hi,
Or mislead them and spread attention to Struts support in IDEA. I tried couple of Struts plugins and after this decided to back to pluginless development cause each has weak areas and competition in this case not very good. In my case it was refusing of use any plugin at all.

When Struts will merge with WebWorks it wil be 10 plugins too? Quality the main not quantity!

Thanks,
Dmitry

0

Hi,
If you want to earn some money for your plugin (and based on stacktraces in bugreports you planning it ) your plugin will be dropped during choise in favour of free ones.
It is better to join all Struts plugins developers efforts and make solid and high quality product without overlapped ones and then sell it.
(But personaly I doubt that anyone will pay money for such plugins anyway. Now JSF and other stuff is the mainstream.)

Thanks,
Dmitry

0

I guess it would be interesting for all parties to know where you see weaknesses of the plugins.

0

Hi,
You think time to compare functionality and evaluate each of at least 3 plugins not big issue?

Thanks,
Dmitry

0

Ofcourse, this is a valid point. Though Struts Navigator has much less features and development seems to have stalled since several months, so in the end there's only 2 plugins to compare.

Maybe this will help you:

http://www.intellij.org/twiki/bin/view/Main/StrutsPluginsFeaturesOverview

0

+Sorry for stupid question but did you and authors of another Struts
plugins ever think about putting its together? Are there any reasons to
keep its separated?
+

that's not a stupid, but valid question. let me cite from a mail where I answered exactly this question:

+Struts Navigator was the first (but very limited, feature-wise) navigation plugin, development seems to have stalled.

Earlier versions of Struts Assistant had no autocompletion/navigation, only the property table and visual wizards.

We cannot join forces because parts of my plugin were developed during my regular worktime at my employer, so he has the rights on the sources+

I agree that both plugins are now "competing" feature-wise, but it's very clear that Struts Plugin had all the autocompletion-stuff long time before Struts Assistant.

So for me the real question is: why does Struts Assistant try to "copy" features from my plugin instead of e.g. focussing/extending the visualization features? This would make more sense, so users could combine the power of the two plugins.. just my 2 cents..

0

Hi Yann,
I knew about it but it is not enough as for me. And StrutsNavigator looks like most fit my needs based on its screenshots ;)
Anyway better to merge your efforts and do plugin together...

One more I not doubt that your plugins very good but overlapped functionality is MAIN PROBLEM. Keep It Simple. And when user see 3 same plugins for first view first reaction is confusing nothing else.

Thanks,
Dmitry

0

I agree with Yann, Struts Assistant should focus on the visual part and
remove the navigation so I can use them both. Or combine the two but I know
from previous posts that isn't going to happen.

"Yann Cebron" <no_mail@jetbrains.com> wrote in message
news:12174098.1138125343048.JavaMail.itn@is.intellij.net...

+Sorry for stupid question but did you and authors of another Struts
plugins ever think about putting its together? Are there any reasons to
keep its separated?
+

>

that's not a stupid, but valid question. let me cite from a mail where I
answered exactly this question:

>

+Struts Navigator was the first (but very limited, feature-wise)
navigation plugin, development seems to have stalled.

>

Earlier versions of Struts Assistant had no autocompletion/navigation,
only the property table and visual wizards.

>

We cannot join forces because parts of my plugin were developed during my
regular worktime at my employer, so he has the rights on the sources+

>

I agree that both plugins are now "competing" feature-wise, but it's very
clear that Struts Plugin had all the autocompletion-stuff long time before
Struts Assistant.

>

So for me the real question is: why does Struts Assistant try to "copy"
features from my plugin instead of e.g. focussing/extending the
visualization features? This would make more sense, so users could combine
the power of the two plugins.. just my 2 cents..



0

Just turn off Struts Assistant completion in settings (File | Settings : IDE Settings -> Struts Assistant -> Code Completion). In this way, it is integration friendly :)

0

Let me give some explanations. When Struts Assistant development was started, the target IDEA version was 4.5, so the completion features could not be implemented.
Struts Plugin was the first to provide completion. It is a great job, and it is improving constantly. But i still have reasons to have my own implementation.
First, Struts Assistant GUI uses reference concept just like IDEA does it. For example, you can right click a tree or diagram node and choose "Find usages" or "Rename". This feature is supported by Struts Assistant Code Completion.
Then, Struts Plugin lacks some important (at least for me) functionality. It does not recognize complex urls (like /pages/login.jsp) and complex bean properties (like myBean.myProperty). Also, I love comforts, e.g. smart xml attribute completion, auto-popups etc. Even IDEA’s default implementation is not perfect so I had to override it for Struts attributes.
My understanding is that we both are trying to create the Struts plugin of our dreams and no wonder we have different ones... :) Good luck!

0

Don't know if for this version or previous.

java.lang.AbstractMethodError: anima.plugins.struts.A.B.D.isBold()Z
at
com.intellij.codeInsight.lookup.impl.LookupCellRenderer.a(LookupCellRenderer.java:43)
at
com.intellij.codeInsight.lookup.impl.LookupCellRenderer.a(LookupCellRenderer.java:67)
at
com.intellij.codeInsight.lookup.impl.LookupCellRenderer.getListCellRendererComponent(LookupCellRenderer.java:52)
at
javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:1155)
at
javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:1105)
at
javax.swing.plaf.basic.BasicListUI$Handler.valueChanged(BasicListUI.java:2226)
at
javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:187)
at
javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:167)
at
javax.swing.DefaultListSelectionModel.fireValueChanged(DefaultListSelectionModel.java:214)
at
javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:408)
at
javax.swing.DefaultListSelectionModel.changeSelection(DefaultListSelectionModel.java:417)
at
javax.swing.DefaultListSelectionModel.setSelectionInterval(DefaultListSelectionModel.java:441)
at javax.swing.JList.setSelectedIndex(JList.java:1732)
at com.intellij.codeInsight.lookup.impl.LookupImpl.b(LookupImpl.java:69)
at
com.intellij.codeInsight.lookup.impl.LookupImpl.updateList(LookupImpl.java:230)
at
com.intellij.codeInsight.lookup.impl.LookupImpl.]]>(LookupImpl.java:187)
at
com.intellij.codeInsight.lookup.impl.LookupManagerImpl.showLookup(LookupManagerImpl.java:4)
at
com.intellij.codeInsight.completion.CodeCompletionHandlerBase.showLookup(CodeCompletionHandlerBase.java:28)
at
com.intellij.codeInsight.completion.CodeCompletionHandlerBase.invoke(CodeCompletionHandlerBase.java:108)
anima wrote:

- The Diagram performance improved
- Read-only files handling fixed for Struts Configuration Wizard
- Tiles detection/installation fixed for Struts Configuration Wizard
- Checking for interference with other plugins removed
- Assorted bugfixes



--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Looks like another IDEA API change :) Which IDEA build do you use?

0

Last EAP build (stack trace was posted to IDEA exceptions)

anima wrote:

Looks like another IDEA API change :) Which IDEA build do you use?


--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

I see. Will be fixed in the next Struts Assistant release.

0

Please sign in to leave a comment.