313816 – CompletionCombo - custom combo with autocompletion

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313816 - CompletionCombo - custom combo with autocompletion

Summary: CompletionCombo - custom combo with autocompletion

Status:	RESOLVED FIXED

Alias:	None

Product:	Riena
Classification:	RT
Component:	ridget (show other bugs)
Version:	unspecified
Hardware:	PC All

Importance:	P3 normal (vote)
Target Milestone:	2.0.0.RC2
Assignee:	Elias Volanakis
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-05-20 16:56 EDT by Elias Volanakis
Modified:	2010-06-12 02:27 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
CompletionCombo.java (72.39 KB, text/plain) 2010-05-20 17:42 EDT, Elias Volanakis	elias: iplog+	Details
CompletionComboSelectionProperty.java (1.75 KB, text/plain) 2010-05-20 17:43 EDT, Elias Volanakis	elias: iplog+	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Elias Volanakis

2010-05-20 16:56:37 EDT

1. Create a custom combo with autocompletion
2. Add support for this to ComboRidget
3. Add support for editable combos

Comment 1 Elias Volanakis

2010-05-20 17:33:23 EDT

@Christian: FYI -- I'm committing two EPL classes from SWT and Databinding respectively. I assume this needs to be recorded in the IP log?

CompletionCombo is based on SWT's CCombo
CompletionComboSelectionProperty is based on CComboSelectionProperty from org.eclipse.jface.databinding

Comment 2 Christian Campo

2010-05-20 17:39:40 EDT

can you supply them both as attachment to this bug and mark the attachment with iplog + ?

Comment 3 Elias Volanakis

2010-05-20 17:42:29 EDT

Created attachment 169425 [details]
CompletionCombo.java

Comment 4 Elias Volanakis

2010-05-20 17:43:14 EDT

Created attachment 169426 [details]
CompletionComboSelectionProperty.java

Comment 5 Elias Volanakis

2010-06-11 19:03:30 EDT

This is already committed since RC2. Marking as resolved.