On 9/7/2010 7:38 AM, Sunburned Surveyor wrote:
Stefan,
... I have used Log4j before,
and it seemed a little complicated.
I find the log4j.properties variant complicated as well. But the
log4j.xml [1] configuration variant I find fairly straight forward [2].
I can include/exclude log
Hi Jukka,
Yes, inserts are more tricky than other modification types. However,
IMHO, a properly modeled database will include sequence generators,
rules, or triggers on database tables enforcing the primary key attribute.
My first iteration through this will be to simply target the most
I'm programmatically invoking a refresh on the layer - any data
currently in the bounding box of the viewport is reloaded from the
datastore ... which includes the newly inserted feature. I suppose I
could be smarter about this and reload all features whose bounding boxes
match the bounding
The FeatureCollectionWrapper.getUltimateWrappee() looks like this:
public FeatureCollection getUltimateWrappee() {
FeatureCollection currentWrappee = fc;
while (currentWrappee instanceof FeatureCollectionWrapper) {
currentWrappee = ((FeatureCollectionWrapper) currentWrappee).fc;
the
whole process.
And if we go this way, I wonder if cloning attributeReadOnly property
with the FeatureSchema is necessary.
What do you think ?
Michaël
Le 02/09/2010 17:59, Kevin Neufeld a écrit :
Patch has been committed at r2034, no problems. Let me know if anyone
has issues
Patch has been committed at r2034, no problems. Let me know if anyone
has issues with the addition.
Thanx all,
-- Kevin
On 9/2/2010 8:29 AM, Sunburned Surveyor wrote:
Kevin,
You've been added to the Jump Pilot Project on Sourceforge and now
have write access to the SVN. You can commit
Stefan mentioned that there isn't a road map for OJ, but is there a
place to jot down improvement ideas?
Here are a couple on my wishlist:
1) The ability to specify which columns are editable in an layer's
attribute table. Right now, the FID and geometry column are hard-coded
as being the
Kevin Neufeld wrote:
Stefan mentioned that there isn't a road map for OJ, but is there a
place to jot down improvement ideas?
Here are a couple on my wishlist:
1) The ability to specify which columns are editable in an layer's
attribute table. Right now, the FID and geometry column
to the maven directory.
I added it, but I am not sure if made things right.
As I said, I have never used Maven up to now... so if you can check and
help I would be greatful.
stefan
Kevin Neufeld schrieb:
If it helps, I just uploaded an org.math.jmathplot-20100827
Hi Stefan, thanx for the reply,
On 8/27/2010 3:47 PM, Stefan Steiniger wrote:
- tagging:
ok.. I may need to change something here w.r.t. the versioning/tagging.
I personally don't use the pom
just the ANT files for building. So I don't know. Any help would be
appreciated.
Ah, ok.
Can someone please clarify OpenJump's use of version tagging?
It makes sense that the trunk version of OpenJump [1] is tagged with
1.3.2-SNAPSHOT, but I don't understand the versioning of the tagged
releases.
The static tag of 1.3.1 [2] has a pom version of 1.3-SNAPSHOT.
The static tag of
FYI,
The current revision of /core/trunk/pom.xml (2015) lists
org.math.jmathplot as a dependency:
http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/pom.xml?view=diffr1=2015r2=1886diff_format=h
However, I'm pretty sure this dependency does not exist in any of the
listed
If it helps, I just uploaded an org.math.jmathplot-20100827 to
lists.refractions.net/m2
http://lists.refractions.net/m2/org/math/jmathplot/20100827/jmathplot-20100827.pom
-- Kevin
On 8/27/2010 10:47 AM, Kevin Neufeld wrote:
FYI,
The current revision of /core/trunk/pom.xml (2015) lists
My I suggest that System.out lines be replaced with appropriate log4j
statements in OpenJUMP?
One of the purposes/advantages of using log4j is that I can filter
output generated by other people's plugins that don't pertain to my own
development.
Attached is a couple of example patches that
: tip.toString();
-}
+// Removed by Kevin Neufeld on 2008-10-31 since it interferes with
useful
+// tooltips that custom layers create when they override
+// com.vividsolutions.jump.workbench.model.Layer#getDescription().
+// public String getToolTipText(MouseEvent e
15 matches
Mail list logo
