I have used eclipse to work on C++ in the past, and I am new to Java, and I get the basics there for the most part.
我过去曾使用eclipse来使用C ++,而且我是Java的新手,我在大多数情况下都有基础知识。
As for Java, I kept seeing all these tutorials and things about how useful UML is to Object Oriented Design, and how you should model your application before hand, etc, etc....
至于Java,我一直看到所有这些教程和关于UML对面向对象设计有多么有用的内容,以及你应该如何预先建模应用程序等等....
Ok, so I look for some modeling tools, you know, so, if I model it here in eclipse, from what I read, it will even convert it to Java for you, sounds kind of nice. Then, if I change some objects around, it would update the code. (at least, for laying things out, I understand this breaks down in usefulness as things get complicated.)
好的,所以我寻找一些建模工具,你知道,所以,如果我在eclipse中对它进行建模,从我读到的,它甚至会将它转换为Java,听起来很不错。然后,如果我改变一些对象,它将更新代码。 (至少,为了解决问题,我理解这会因为事情变得复杂而失效。)
Well, so I go looking.... and good grief! EMF XMI Acceleo EIB RDB GMF XML UML ... woah!, woah!, hold on there, I can figure something out if it make sense, but this feels like a government employee got a hold of it, acronyms everywhere!
好吧,所以我去看......好悲伤! EMF XMI Acceleo EIB RDB GMF XML UML ...哇!哇!,坚持到那里,如果有意义,我可以想出一些东西,但这感觉就像一个*雇员掌握它,到处都是首字母缩略词!
I tried tutorials I found off Google, but, it doesn't help when the tutorial says: "oh, here use our non-understandable example ((because we made it too complicated to start from scratch)) and you will know all you need to know" stuff that doesn't help.
我尝试过在Google上找到的教程,但是,当教程说:“哦,这里使用我们不可理解的例子((因为我们从头开始让它变得太复杂)”并且你会认识所有你需要知道“没有帮助的东西。
Anyway, is there a plain English set of tutorials and/or books I can get my hands on that can help me translate this mess into something I can model my Java with without needing a 2 year degree in Java l33t speak?
无论如何,是否有一套简单的英语教程和/或书籍,我可以帮助我将这些混乱翻译成我可以模拟我的Java,而不需要2年的Java学位课程?
I though modeling was supposed to be fast and simple, to get your objects laid out in general terms before you start stuffing in the details, so far, that is not what I am seeing.
我虽然建模应该是快速而简单的,但是在开始填充细节之前,为了让你的对象按照一般术语布局,到目前为止,这不是我所看到的。
1 个解决方案
#1
0
I give up, this mess is gibberish.
我放弃了,这个烂摊子是胡言乱语。
Maybe there is a use for it under specific circumstances, but it is just overhead non-sense. If it was really needed it wouldn't be so academic.
也许在特定情况下它有用,但它只是开销无意义。如果它真的需要它不会那么学术化。
I have went round and round and round with various tools, What I was expecting was, the ability to draw out the objects, list their properties, and methods, and sketch it up in a graphical form, then have the application generate the code framework that I just start filling in the meat of those objects. If I add or change stuff in the code, my graphical outline stays up to date.
我已经使用各种工具进行了回合和循环,我期待的是,绘制对象,列出其属性和方法的能力,并以图形形式绘制草图,然后让应用程序生成代码框架我刚开始填充那些物品的肉。如果我在代码中添加或更改内容,我的图形大纲将保持最新。
It appears I am asking for too much, especially from Eclipse. It is either too complicated to be useful, or so incomplete, or out of date, to function properly.
看起来我要求太多,特别是来自Eclipse。它要么太复杂,要么无用,要么不完整或过时,才能正常运行。
I get the point of the need of UML design, at least, I thought I did. I come from a classic C/Perl/Assembler function driven world, and I understand the need for flow-charts and diagrams for more complex projects, at it seemed to me, since Java was a different programming language of a different flavor, (Object Oriented, rather then function oriented) that the design stage should reflect this change of thought. UML didn't seem that hard to grasp, boxes that describe the objects, and their properties, and the way they act, and these interaction charts that show how things interact. Well, obviously the state of the art in this field is as not as advanced as I would have hoped.
我明白了UML设计的需要,至少,我以为我做到了。我来自一个经典的C / Perl / Assembler函数驱动的世界,我理解对更复杂项目的流程图和图表的需求,在我看来,因为Java是一种不同风格的不同编程语言,(对象)面向,而不是面向功能)设计阶段应该反映这种思想的变化。 UML似乎并不难理解,描述对象的框,它们的属性,以及它们的行为方式,以及这些交互图表显示了事物的交互方式。嗯,显然这个领域的技术水平并不像我希望的那样先进。
So, my answer to this question is, there is nothing usable that does this for Eclipse, at least, nothing someone new the the Java world can grab hold of and make use out of the box without tons of other things to know first. The wall is too high to climb for my needs right now, I have too much other stuff to do. I guess there's an opportunity for someone there.
所以,我对这个问题的回答是,没有任何东西可以用于Eclipse,至少,没有任何新的Java世界可以抓住并开箱即用,而不需要先了解其他许多东西。墙现在太高了,无法满足我的需求,我还有太多其他事情要做。我猜那里有人有机会。
#1
0
I give up, this mess is gibberish.
我放弃了,这个烂摊子是胡言乱语。
Maybe there is a use for it under specific circumstances, but it is just overhead non-sense. If it was really needed it wouldn't be so academic.
也许在特定情况下它有用,但它只是开销无意义。如果它真的需要它不会那么学术化。
I have went round and round and round with various tools, What I was expecting was, the ability to draw out the objects, list their properties, and methods, and sketch it up in a graphical form, then have the application generate the code framework that I just start filling in the meat of those objects. If I add or change stuff in the code, my graphical outline stays up to date.
我已经使用各种工具进行了回合和循环,我期待的是,绘制对象,列出其属性和方法的能力,并以图形形式绘制草图,然后让应用程序生成代码框架我刚开始填充那些物品的肉。如果我在代码中添加或更改内容,我的图形大纲将保持最新。
It appears I am asking for too much, especially from Eclipse. It is either too complicated to be useful, or so incomplete, or out of date, to function properly.
看起来我要求太多,特别是来自Eclipse。它要么太复杂,要么无用,要么不完整或过时,才能正常运行。
I get the point of the need of UML design, at least, I thought I did. I come from a classic C/Perl/Assembler function driven world, and I understand the need for flow-charts and diagrams for more complex projects, at it seemed to me, since Java was a different programming language of a different flavor, (Object Oriented, rather then function oriented) that the design stage should reflect this change of thought. UML didn't seem that hard to grasp, boxes that describe the objects, and their properties, and the way they act, and these interaction charts that show how things interact. Well, obviously the state of the art in this field is as not as advanced as I would have hoped.
我明白了UML设计的需要,至少,我以为我做到了。我来自一个经典的C / Perl / Assembler函数驱动的世界,我理解对更复杂项目的流程图和图表的需求,在我看来,因为Java是一种不同风格的不同编程语言,(对象)面向,而不是面向功能)设计阶段应该反映这种思想的变化。 UML似乎并不难理解,描述对象的框,它们的属性,以及它们的行为方式,以及这些交互图表显示了事物的交互方式。嗯,显然这个领域的技术水平并不像我希望的那样先进。
So, my answer to this question is, there is nothing usable that does this for Eclipse, at least, nothing someone new the the Java world can grab hold of and make use out of the box without tons of other things to know first. The wall is too high to climb for my needs right now, I have too much other stuff to do. I guess there's an opportunity for someone there.
所以,我对这个问题的回答是,没有任何东西可以用于Eclipse,至少,没有任何新的Java世界可以抓住并开箱即用,而不需要先了解其他许多东西。墙现在太高了,无法满足我的需求,我还有太多其他事情要做。我猜那里有人有机会。