Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-devel] Document View RFC
From an initial code review this RFC is just covering the API.

The shapefile "reference" implementation is using a properties file to jot down which string attributes are to be treated as a document.

I note that ArcView has similar similar functionality called a "hotlink"; they do not record the hotlink type in the DBF file; but instead jot down the information in their LYR file (similar to our SLD file).

I am going to wait for the Document view and interface to settle down; and then check if I can use the GeoResource properties facilities (requested by John this week) as an alternate way of noting which attributes to treat as candidates for the document view treatment.

I was also going to check if we could list the documents as a result of the Info tool? Since that is a nice way to point and click for a feature.
-- 
Jody Garnett

On Friday, 23 December 2011 at 3:45 PM, andrea antonello wrote:

Hi Paul, my +1 come from the heart. I have been thinking about and
wishing this for much too long now.

From the RFC I do not understand how you want to handle this exactly?
Let's for example take a shapefile (it is a good move to start with
that one). Some fields will have documents, as for example pictures of
the single feature. Will the document view let the user define a field
that holds documents? The wireframe you created shows a lot of
documents, I am a bit confused.

Ciao,
Andre


On Fri, Dec 23, 2011 at 4:17 AM, Paul Pfeiffer <nightdrift@xxxxxxxxx> wrote:
Can I please get committee members to have a look at this RFC and vote.

I have begun work in my own fork and as part of this I have run into the
following issue

Cheers
Paul



_______________________________________________
User-friendly Desktop Internet GIS (uDig)
_______________________________________________
User-friendly Desktop Internet GIS (uDig)

Back to the top