>Would the single record editor have a fixed number of "cells" that
>could be incremented/decremented to view different parts of the
>record, or would it be dynamically constructed based on the number of
>attributes with a vertical scroll bar?

I like the second option.



On Wed, Dec 24, 2008 at 1:35 PM, Sunburned Surveyor <
[email protected]> wrote:

> I'm glad I'm not the only one that get's frustrated with the attribute
> tables.
>
> Larry wrote: "I've never found one.  I suspect that the programming to
> fix the things you mention would not be too difficult, but as you
> point out, the modifications wouldn't be there the next session so why
> bother."
>
> You are correct. This solution, if it was to be practical, would need
> to preserve the layout changes by saving the state of the table
> layout. This is doable, but could be messy.
>
> Larry wrote: "A suggestion someone made previously that would improve
> data entry and edit of attributes is to provide an option to go to a
> single record vertical layout.  I still like that solution."
>
> I was thinking about a flexible grid of text boxes that could be used
> to cycle trough the records in the table. I've seen something similar
> in AutoLisp's Dialog Control Language, which has no built in table
> component. However, I like the idea of a single record editor (in a
> vertical layout) better. Maybe I mess around with this concept a
> little bit.
>
> Would the single record editor have a fixed number of "cells" that
> could be incremented/decremented to view different parts of the
> record, or would it be dynamically constructed based on the number of
> attributes with a vertical scroll bar?
>
> SS
>
>
> On Wed, Dec 24, 2008 at 11:25 AM, Larry Becker <[email protected]>
> wrote:
> >>Does anyone ever get frustrated with the user interactions involving the
> >> attribute table?
> >
> > Yes.
> >
> >> There is no horizontal scroll bar.
> >
> > What is that thing at the bottom of the window?
> >
> >> Does anyone know if there is an open source component or JTable
> extension
> >> that solves some of these issues?
> >
> > I've never found one.  I suspect that the programming to fix the things
> you
> > mention would not be too difficult, but as you point out, the
> modifications
> > wouldn't be there the next session so why bother.
> >
> > A suggestion someone made previously that would improve data entry and
> edit
> > of attributes is to provide an option to go to a single record vertical
> > layout.  I still like that solution.
> >
> > regards,
> > Larry
> >
> > On Wed, Dec 24, 2008 at 11:51 AM, Sunburned Surveyor
> > <[email protected]> wrote:
> >>
> >> Does anyone ever get frustrated with the user interactions involving
> >> the attribute table? I keeping wanting it to behave like a spreadsheet
> >> in Excel, which it does not. :] Maybe I am spoiled and expecting too
> >> much from Swing. Here is a short list of what is irritating me:
> >>
> >> There is no horizontal scroll bar. This can be a pain when you have a
> >> FeatureSchema with lots of attributes.
> >> There is no way to double click on the seam between columns so that
> >> the columsn automatically "best fit" the data contained in the
> >> columns.
> >> There is no way to specify the alignment/justification of the data in
> the
> >> cells.
> >> There is no way to have the content of a columns cells "wrap" when a
> >> max width is hit.
> >>
> >> I was reading in one of my Swing books last night, and I couldn't
> >> immediately see ways to fix this using built-in JTable properties. It
> >> would likely have to be patched up with some custom cell renderers and
> >> some other tweaks.
> >>
> >> Does anyone know if there is an open source component or JTable
> >> extension that solves some of these issues? Do these issues bug anyone
> >> else?
> >>
> >> If I'm doing any serious attribute editing, I can always save my layer
> >> to a shapefile and open the DBF in something like Excel or Open
> >> Office, but I'd like to improve what I can with the attribute tables
> >> in OpenJUMP. I'm thinking I'd have to come up with a mechanism to save
> >> the user's table layout modifications, and that might be too
> >> complicated.
> >>
> >> Thanks for your thoughts.
> >>
> >> The Sunburned Surveyor
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> _______________________________________________
> >> Jump-pilot-devel mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >
> >
> >
> > --
> > http://amusingprogrammer.blogspot.com/
> >
> >
> ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Jump-pilot-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jump-pilot-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>



-- 
http://amusingprogrammer.blogspot.com/
------------------------------------------------------------------------------
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to