[Dev] new "Edit" tab in the Repository Viewer
Brian Douglas Skinner
skinner at osafoundation.org
Mon Nov 17 18:21:21 PST 2003
FYI, for anybody interested in the Repository Viewer...
Jeffrey has been working on initial UI affordances for editing items. He
sent me a patch file and I checked it into main source tree, so the next
time you get a copy of Chandler it'll have the new "Edit" tab in the
Repository Viewer.
By default, the "View" tab is selected, and the Repository Viewer
behaves exactly like it used to. If you don't want to edit items, you
can just ignore the "Edit" tab.
At this early stage, only some fields are editable, and all of the
editable fields are treated as simple text strings. So for now, if you
use the editor, you'll want to be careful about what fields you edit.
It's safe to edit simple strings like description and display names, but
you'll probably want to steer clear of data types like booleans and
enumerations. Upcoming versions will have spiffy new features, like
tools for editing multi-valued attributes, and different UI widgets for
different data types.
Here's Jeffrey's summary of the changes:
Jeffrey Harris wrote:
> Here's a patch for RepositoryViewer. A few notes about changes:
>
> * I've changed the layout of the tree, adding a spacer so that there's
> visual separation of the UUID and the URL
>
> * Currently, you can only edit a few fields in any given item, and some
> things that you can currently edit you'll mess things up if you do edit
> them, since right now any changes are written as text.
>
> * For some odd reason, the scrolling window I've created doesn't
> actually scroll UNLESS you resize the splitter separating the "Submit
> Changes" button and the editing pane. Whether this a bug in wxWindows
> or I'm abusing wxWindows is hard to say.
>
> * I've started implementing a system that would ask for confirmation
> before leaving an item while changes haven't been submitted, this isn't
> done yet, so there are various bits of code (dirt tracking code, and an
> event to track when the notebook tab changes) that don't actually do
> anything yet.
>
> * I tried to make the system represent which notebook tab is selected as
> part of the URL, but I didn't have much luck, I think I'd need to delve
> deeper into the URL tracking code to make this work.
>
> Sincerely,
> Jeffrey
More information about the Dev
mailing list