- This topic has 162 replies, 89 voices, and was last updated 16 years, 8 months ago by
.
-
Posts
-
I work for Verizon Business and we are evaluting an IDE or Eclipse plugin fro 400+ developers. I’m in love with your plugin, but you are making my decission hard since there’s not plan for facelets support. I have weblogic folks giving me demos about weblogic studio with facelets support and I don’t have tools to fight back. The only issue so far with their product is $$, if I don’t get anything quickly from your side, I will be force to buy Weblogic Studio over ME. Hopefully we can get a quick answer about a possible or minimum support for facelets.
@mlsalcedo wrote:
I work for Verizon Business and we are evaluting an IDE or Eclipse plugin fro 400+ developers. I’m in love with your plugin, but you are making my decission hard since there’s not plan for facelets support. I have weblogic folks giving me demos about weblogic studio with facelets support and I don’t have tools to fight back. The only issue so far with their product is $$, if I don’t get anything quickly from your side, I will be force to buy Weblogic Studio over ME. Hopefully we can get a quick answer about a possible or minimum support for facelets.
The same counts for me, just for a smaller numer of licences. We have 90 MyEclipse licences, but we are starting to use Excadel Studio for the same reason. Also, Excadel has Shale support, which is good for the future in my opinion.
To finish, I think (basic) Facelets isn’t too hard to implement in MyEclipse, because the most important thing is good XML (schema/namespaces) support. The rest can come later. Putting a Facelets jar in the classpath at the start of a project is no big deal, but having no code completion is really horrible.
Guys we take our user requirements very seriously. When management is prioritizing features for each release we look at the level of demand from individuals and companies. There are times, like with 5.0, where we just flat out have infrastructure work that needs to get done before we can go back to addressing feature requests from our user base.
I have requested contact information from some of you already that has been sent to our management team to follow up with you individually about company requirements and we will continue to do so to make sure our customers are happy and don’t need to turn to competators for solutions. If at all possible we would like everyone to stay with us and will do what we can to make that happen.
@support-rkalla wrote:
If at all possible we would like everyone to stay with us and will do what we can to make that happen.
I personally didn’t mean to be pushing, but the fact is that we are currently developing Facelets with Excadel, just because it supports the framework and that saves a lot of time. We ARE using all other features MyEclipse offers us, like the excellent Hibernate support.
It’s just the JSF/Facelets web layer we are experiencing troubles with.
I can’t speak for the other replies, but that’s our opinion.
I was thinking about implementing Facelets support and especially code completion.
Code completion for the default Facelets tags like ui:composition and ui:define aren’t difficult to implement imho, but code completion for user defined components seems more difficult, (or impossible) because the validity of parameters is determined at runtime. To be more exact, all parameters for a user defined component are valid.
Passing a random parameter foo=”bar” is valid.
The only solutions I see are code completion for tags/attribs that have been passed earlier in the document and checking which variables are used in a template/composition/component, excluding beans.
Anyone an idea?
