- This topic has 6 replies, 4 voices, and was last updated 19 years, 3 months ago by
ArmchairDeity.
-
AuthorPosts
-
jfrantziusMemberIn its editor outline, XMLBuddy shows the value of any existing “name” attribute next to all tag nodes. That’s very comfortable and for me personally highly missed in the MyEclipse XML editor…
January 7, 2005 at 10:33 am #222359
Scott AndersonParticipantNice idea! Thanks.
April 12, 2006 at 10:42 pm #250401
ArmchairDeityMemberany idea when this might be implemented? I use MyEclipse with CFEclipse and edit large XML documents with up to dozens of <event-handler /> tags that have a name attribute, but in the outline, all that’s there is the tags, not the name attribute.
It makes the outline far less usable for working with large documents.
Incidentally, I’m working with a freshly patched up 4.1.1 MyEclipse… I LOVE IT. This just one tweak that would dramatically improve my MyEclipse experience.
Thanks,
JApril 13, 2006 at 2:31 am #250409
Riyad KallaMemberJ,
Honestly besides about 4 people that wanted it no one else has ever asked for it, so when management sits down to plan out our releases it’s never been a huge line item (Although it is being tracked in our system internally).We might pick this feature up at some point but without the user demand I don’t know that we would implement it as the demand levels stand now.
April 13, 2006 at 9:40 am #250423
ArmchairDeityMemberRiyad,
Thanks for the reply… and I understand.
With these large documents for things as varied as Fusebox and MXML, sometimes there are many of the same tags with various and different attribute values. There are a few choices that really make life easier when working with documents like this.
#1 is a limited, unique attribute visible in the outline. If you ever pick this feature up I’ll be singing your praises like a flock of contented nightingales.
#2 is code collapse, because without it there’s no way to get certain blocks of text next to eachother so they can either be compared or used as reference (I have a sucky memory for certain types of information apparently, and I often need a visual reference).
#3 is drag-n-drop, because these documents are actually involved with application control flow, or in the case of MXML the actual code for the Flex app. Being able to move blocks of data around easily is important and, were you to implement this for the XML editor, you’d be the only major Eclipse XML tool available that supports DnD. Apparently that means that demand isn’t wide-spread, so I doubt I’ll get this, either… but still, if you never ask you never receive.
I can live without 1 and 3, but 2 is the critical feature… it would basically allow me to get around the other two.
Any idea when it’s coming?
Thanks,
JApril 13, 2006 at 9:47 am #250424
Riyad KallaMemberI *think* code folding in the other editors is in the works, I’m not positive though, I’ll check on that.
I’ll add your comments for the filing of #1 though.
April 13, 2006 at 9:55 am #250427
ArmchairDeityMemberThanks!
-
AuthorPosts