Eclipse Community Forums: Eclipse Scout

Home » Eclipse Projects » Eclipse Scout » Milestone 3.10.0-M4(Announcement of some larger changes)

Milestone 3.10.0-M4 [message #1219671]

Thu, 05 December 2013 05:51

Eclipse User

Hi,

We would like to announce some larger changes planned for the upcoming milestone 3.10.0-M4 (20th December 2013). The changes require some migration in Scout projects. If you have any concerns, please feel free to reply.

1) With Bugzilla 420491 several JRE 1.3 relevant code will be replaced with JRE 1.6+ implementations.

ICodeType, ICode, ILookupRow, ILookupService, ICodeRow and all its implementations become generic.
Several (return-) parameters will be changed from array to typed lists.
SmartFields allowing custom text become its own field 'ProposalField'. So the 'allowCustomText' member will be removed from ISmartField. The lookupCall and codeType members on IContentAssistField (common super class of ISmartField and IProposalField) will be typed.

2) We will remove all methods/classes/attributes marked with "@deprecated will be removed in 3.10.0". Moreover, we will also remove some "@deprecated" statements which are older than the 3.9.0 release. More specifically, the following functionality will be removed:

Legacy Testing Support: Legacy Integration Tests (e.g. DrilldownOutlineUnitTest) will be removed and should be replaced by junit based tests. See also Bugzilla 403310
We intend to support only the following Eclipse Platforms with Scout 3.10:
Scout RT: 3.6, 3.7, 3.8, 4.4
Scout SDK: 3.7, 3.8, 4.2, 4.3, 4.4
SQL Support in Client Code: SQL Code in the Scout Client was already deprecated in Scout 3.7. We plan to remove it with Scout 3.11, because it requires a larger migration. SQL in search forms needs to be migrated to the server. There will be no migration support: (Bugzilla 403545 will be closed)

Luna Release 3.10.0 [message #1232677 is a reply to message #1219671]

Fri, 17 January 2014 08:21

Eclipse User

Some of the points mentioned by Judith are still work in Progress for M5...

In the list of the legacy things we should consider for Luna, I like to add the deprecation of contextMap in pages.

The contextMap concept was introduced for historical reason. It is a bad practice to use it. Marking the contextMap as deprecated will inform people that they are using a concept that we do not plan to support in the long term.

Instead of using this contextMap, we recommend is to define variables in the page (with the corresponding typed getter and setter) and to propagate the values from a page to the child pages.

If some project still relies on contextMap in Page, they can re-implement this concept back in their project.

Depending on the feedback, we could remove the contextMap with the next version of Scout or let it in the framework a little bit longer.

Feel free to provide feedback.

Re: Luna Release 3.10.0 [message #1232689 is a reply to message #1232677]

Fri, 17 January 2014 09:04

Eclipse User

Yes, please deprecate the contextMap in pages and the ContextMap class, as it is completely untyped and therefore unsafe to use.

Adrian

Re: Luna Release 3.10.0 [message #1233713 is a reply to message #1232689]

Mon, 20 January 2014 05:18

Eclipse User

ContextMap will be marked as depreciated with Luna (Bug 426087) and will be removed with Bug 426088 (Version >= Luna + 1).

We encourage projects that still use ContextMap to put a comment in Bug 426088 to be informed and to influence when the code will be removed.

[Updated on: Mon, 20 January 2014 05:19] by Moderator

Previous Topic:	Feedback from Standalone Client Implementation
Next Topic:	Is it possible to export just the server product

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 05 05:12:07 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter