This is a fix (not necessarily a bug) needed for novice
users. The imports list needs to be more automatically
included in classes so that they won't need to show the
"file headers" and then copy the reference into the file.
Example 1 to reproduce:
In a new fragment, type:
import java.util.*;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class CheckNodeTreeExample extends JFrame
Then commit.
Note that it breaks these into two separate fragments,
but the import statements are NOT linked into the "file
headers" of that class -- you need to do this by hand.
This should be done automatically.
Example 2 to reproduce:
In a new fragment, type:
public class CheckNodeTreeExample extends JFrame
Then commit.
Then type at the top of that fragment:
import java.util.*;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
Then commit. See comments for Example 1 -- same
problem of not connecting the imports to the class
automatically.
Example 3 to reproduce:
In a new fragment, type:
import java.util.*;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class CheckNodeTreeExample extends JFrame
Then commit.
Add the imports to the file headers. Then, below that
fragment, hit enter to start a new fragment based off
of it and type:
public class CheckNodeTreeExample2 extends JFrame
Then commit.
Then commit. Note that the file header for the first
one doesn't get on the second one -- perhaps it should,
perhaps it shouldn't -- and perhaps it should ask the
user and give a little explanation about file headers.
Also, when you get an error about not being able to
find a class, it would be neat to give an explanation
how to fix it. (And even better if it would
automatically search for the class and offer to add it
to the imports list).
Log in to post a comment.
