Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nebula-dev] New control submission

The design and the API of the CompositeTable is definitely interesting. I'm not 100% convinced on it myself but I think its definitely worthwhile for Nebula.
+1

-Chris

David J. Orme wrote:
We're now ready to start reviewing contributions! I'm going to forward the older emails so we can start the discussion and the vote.

First, here's David's submission below.

I'm familiar the CompositeTable. The other contributions look interesting. My only concern is the dependencies. Dave, do these widgets require JFace? Do they depend on any databinding or ve libraries?

Sorry for the delay in replying.

CompositeTable depends only on SWT.

DayEditor depends only on CompositeTable and SWT.

MonthEditor depends only on SWT.

There are data binding classes for each of the above. They follow a similar architecture to JFace viewers: they depend on both the widget and on data binding which in turn depends on JFace. These probably should be moved to Nebula along with the widgets, but as was suggested elsewhere, they should be kept in their own plugin/project.


Regards,

Dave Orme


Regards,
-Chris

David J. Orme wrote:
Taking the contribution process steps from the web site in reverse order:

3) The controls I am contributing to Nebula have already passed the Eclipse IP process because they were developed as a part of work on the Eclipse Platform project's data binding framework entirely within the Eclipse IP guidelines. I am the sole committer on those controls and my IP paperwork is up to date.

2) I am already a committer on Eclipse Platform and Visual Editor and my IP paperwork is up to date with the Eclipse Foundation.

1) The controls:

a) CompositeTable. Is an SWT table control natively supporting in-place editing, custom row layouts like rows with two lines similar to a checkbook register and much more. It is fully virtual--it only creates graphical controls for data it can actually display and only requests data that it can currently display. It is designed to integrate nicely with the Eclipse Visual Editor. Without adding any special support to VE, you can edit CompositeTable objects graphically today.

b) DayEditor. This is a graphical calendar control similar to Outlook's or PalmOS's day or work week view. It supports laying out events that overlap in time, all-day events, and when driven using JFace data binding supports events that span multiple days. It can display one day column, two day columns, n day columns--as many as will fit on the screen comfortably. This work builds on and extends CompositeTable.

c) (coming soon): MonthEditor. Like the DayEditor, but displaying/editing a whole month at a time. This work builds on and extends CompositeTable.

The code:

Repository: :extssh:<username>@dev.eclipse.org:/home/eclipse
Project: org.eclipse.jface.examples.databinding
Packages: org.eclipse.jface.examples.databinding.compositetable.*

Regards,

Dave Orme
Visual Editor Project lead

_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev



Back to the top