Gruntspud 0.4.0 is out
Submitted by on Saturday, 26 April, 2003 - 20:59
Here's just a few ...
You can now define 'projects'. When you add a project, you provide a home location for it much in the same way as always. However, when you change to a directory that is defined as a project, the entire tree file is loaded. This gives the ability to show that files need attention somewhere in the directory structure (modified, added, conflicts etc) even when the parent(s) are not expanded. The trade-off is that start-up time and memory consumption is higher (especially for large workspaces). I would recommend you try this one ...
An XML parser is now required (this is used for the projects file). Over the next few releases, more and more of gruntspuds configuration files will be migrated to XML. Xerces is included with the source distribution, so if you want (or need) to use JDK13 get that version. The jEdit plugin adds the 'XML' plugin as a dependency.
Fits into jEdit 4.1 look and feel better by using the same tree and file icons in both the tree and table views. Icon height is also used as the row height in these components and file are colored and styled as in the file browser.
Now dependant on ErrorList plugin. This shows conflict errrors when the update / import command is running. Opening a file that has conflicts also adds to the error list, highlight the line where the conflict occurs. Unfortunately, if you save the file, the conflict status is removed, so the conflicts cannot be checked for again. This may be fixed in a later version.
See RELEASE_NOTES.txt included with the source and binary distributions for a full list.
You can now define 'projects'. When you add a project, you provide a home location for it much in the same way as always. However, when you change to a directory that is defined as a project, the entire tree file is loaded. This gives the ability to show that files need attention somewhere in the directory structure (modified, added, conflicts etc) even when the parent(s) are not expanded. The trade-off is that start-up time and memory consumption is higher (especially for large workspaces). I would recommend you try this one ...
An XML parser is now required (this is used for the projects file). Over the next few releases, more and more of gruntspuds configuration files will be migrated to XML. Xerces is included with the source distribution, so if you want (or need) to use JDK13 get that version. The jEdit plugin adds the 'XML' plugin as a dependency.
Fits into jEdit 4.1 look and feel better by using the same tree and file icons in both the tree and table views. Icon height is also used as the row height in these components and file are colored and styled as in the file browser.
Now dependant on ErrorList plugin. This shows conflict errrors when the update / import command is running. Opening a file that has conflicts also adds to the error list, highlight the line where the conflict occurs. Unfortunately, if you save the file, the conflict status is removed, so the conflicts cannot be checked for again. This may be fixed in a later version.
See RELEASE_NOTES.txt included with the source and binary distributions for a full list.
