Closed starsasumi closed 8 years ago
Don't get it. What's your point?
@starsasumi : problem in the test for #67 :
in the window the polyline is not filled in black
in the svgAndAwt.svg file the polyline is filled in black!
@anqitong As the prof required, Painting.java
is the "high-level language" that he wants. And codes in our presentations would be the "middle-level language"
So you're suggesting taht we use directly java in Painting as high-level language?
Yes, and the prototype of this Painting
is in our discussion in #19
I think using shape objetcts is already a high-level language.
I'm not sure it is necessary, but if you really want to use Painting as high-level language, I'm not against it. So I would like to know what @Thomas-dot-G thinks
@anqitong I understand, I am also not sure about this. This is why I re-open the issue to ask you two. But I think maybe make it as real RP would be more clear to discuss.
As you can see, codes in Painting
are much more clean. And with this, we have a simple-to-use high-level language and also a great GUI, which make our project rocks ;)
I think you're right about opening a PR to make it clearer!
I don't think this is required, but it can be nice to have a simpler code for the user. However, that should be well documented for M Grall.
@Thomas-dot-G If you two agree to merge this, I will rewrite the README.md first ;)
Not yet to merge, but I agree to merge it later (after some modifications)
Hey guys, I add tests in TestLanguage.java
. Is it better now?
I also update README.md. What do you think about it. I will add the insert back later in the Painter
API.
Okay for me
I will have to add a paragraph descrbing how to use the GUI
Is this good to go now?
Except for the Read Me, I am ok to merge. If you remove your changes for the read me and put them in another PR, I think we are ready to merge this.
OK
This is for issue #19
With this language, we can draw things with much simple codes.