Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Search results
Create the page "Coding rules" on this wiki! See also the search results found.
Page title matches
Page text matches
- == Technical Architecture rules == === coding rules ===15 KB (2,306 words) - 10:10, 7 September 2020
- Your new file will be open and ready for coding in the Editor pane. ...ng - Certain code items are colored in .stp and .c files based on a set of rules and colors.56 KB (9,297 words) - 12:33, 11 November 2022
- Your new file will be open and ready for coding in the Editor pane. ...ng - Certain code items are colored in .stp and .c files based on a set of rules and79 KB (13,224 words) - 08:46, 12 March 2012
- === Coding Conventions === ...the [http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html Sun Java Coding Conventions] except for the specific deviations from these conventions deta11 KB (1,605 words) - 11:21, 6 August 2015
- ...sing the Orion IDE, as its built-in validator will catch a lot of possible coding errors and anti-patterns (like accidental globals, for example). When in doubt about coding style, follow these general rules:51 KB (7,473 words) - 18:51, 16 November 2015
- '''Coding Conventions''' This document describes the basic Coding Conventions used by the RTP development team.2 KB (326 words) - 17:35, 9 February 2011
- == Icon Legend and Color Coding == See the legend below to interpret the icons and color coding in the task list. You can view this legend by selecting "Show UI Legend" fr46 KB (7,626 words) - 16:51, 6 June 2011
- XML configuration means that in most cases no special Java coding is enforce syntactic rules, numerical ranges (each with one or both76 KB (12,048 words) - 07:50, 5 February 2014
- == Coding Guidelines == *We use the default formating rules by Eclipse to format Java Code (Ctrl-Shift-F)4 KB (605 words) - 18:19, 7 December 2021
- ...erns, namely specific violations of well-established design principles and rules. To make the model comprehensive and balanced, we rely on a wide-range of s ...e community moves its projects from CVS and Subversion to Git. The "social coding platform" GitHub is rapidly increasing its number of hosted repositories. T4 KB (652 words) - 05:07, 29 November 2011
- ** What are the risks that more relaxed rules would introduce? ** What are the patterns of coding that (some) users would like to see accepted without a warning?20 KB (3,092 words) - 18:42, 24 August 2016
- = Rules = ...be an advanced Eclipse project. The student should already be comfortable coding in Java and developing OSGi bundles with Eclipse. A student with working k25 KB (3,910 words) - 11:09, 30 April 2012
- === Coding Conventions === ...nes]], and the [http://www.eclipse.org/jdt/ui/dev.php#documents additional rules used in JDT UI].12 KB (2,028 words) - 12:05, 24 November 2022
- Your coding task has the following aspects: = Coding details<br> =16 KB (2,411 words) - 16:20, 6 July 2012
- * clear rules for what constitutes an application comprising multiple bundles * community support, coding, and testing.12 KB (1,824 words) - 09:12, 9 May 2012
- = Coding rules for Papyrus plug-ins and features = These rules apply to all plug-ins and features developed for the Papyrus Eclipse projec3 KB (368 words) - 10:37, 19 November 2020
- ...: syntax, grammar or semantic are where we need to defines constraints and rules. ...rious VjO types can have a package component to their names. Here are some rules with packages:120 KB (13,295 words) - 22:00, 5 February 2013
- Charity institutions can register and describe their rules for accepting beneficiaries. ...ive implementations. '''*Angular*''' asa declarative approach with minimal coding, '''*JQuery*''' with low level control. Combinations are obviously possible11 KB (1,323 words) - 05:19, 29 January 2014
- ...probably more powerful ... but has lead to a few cases of confusion or mis-coding. (See [[Execution_Environments| PDE's handling]] versus [[Tycho/Execution_E :*Rules of what code changes effect qualifiers are not well documented -- just in b23 KB (3,806 words) - 19:12, 2 May 2016
- This FAQ is about the rules that Eclipse Handly committers follow when developing the project. == Coding ==8 KB (1,260 words) - 11:06, 12 January 2024
- ...ing this you will be able to define a DSE problem including transformation rules and objectives, run it with different built in strategies and use the solut == Transformation rules ==16 KB (2,275 words) - 12:28, 28 November 2016
- == Rules == The following sections describe all of the rules currently available in Orion and ones that we plan to add in the future.35 KB (4,942 words) - 17:38, 8 December 2016
- ...terms of the Eclipse Development Process and the Eclipse IP Due Diligence rules. ...rg/legal/EclipseLegalProcessPoster.pdf intellectual property due diligence rules] from the moment we start the move process.9 KB (1,373 words) - 14:54, 2 November 2016
- ...confusing or outright silliness. In this article we lay down a few ground rules that will help anyone use progress monitors in a way that will work with th ==Eclipse Rich Client Platform: Designing, Coding, and Packaging Java Applications==158 KB (23,992 words) - 11:55, 27 April 2020
- ...confusing or outright silliness. In this article we lay down a few ground rules that will help anyone use progress monitors in a way that will work with th ...ts and relational data. However, not much has been said about how to model rules. This article will define a meta-model in ECore for modeling rule-based sys61 KB (9,332 words) - 10:21, 31 January 2024
- Contribution to an open source project is not only about coding. There are multiple other ways to help this project, which we will describe === Coding & Contribution Rules ===7 KB (1,098 words) - 08:48, 29 November 2016
- ...less than half of the development activities. There are really only a few rules to remember for writing code in ICE: Each of these rules have a purpose:20 KB (3,336 words) - 14:00, 20 January 2017
- In this chapter all rules regarding the code quality are collected. == Coding Conventions ==26 KB (3,957 words) - 09:51, 5 December 2014
- ...project using Oomph. The goal of this wiki page is to help users to set up coding workspace for JDT components using Oomph. Rules and details for Install, Workspace and JRE can be selected based on user ch5 KB (706 words) - 08:16, 22 November 2020
- = Development Rules For Papyrus (DRAFT) = This page is a starting point to discuss about those rules and practices.30 KB (4,639 words) - 09:13, 9 July 2015
- ** Orion continues to push on the Core Coding experience - Orion Editor is on par or better than most desktop editors * Alex: SWT GTK3 and the Endgame Rules27 KB (4,457 words) - 08:46, 29 September 2015
- = Rules = ...tions] should be introduced, which allows tracking user locations, so that rules can compare and relate user and beacon locations.31 KB (4,893 words) - 10:46, 11 April 2016
- Need some help while coding? Activate content assist for code completions, keywords and templates. ...power and speed of [https://github.com/eslint/eslint ESLint], the linting rules in Orion can be configured on a per-rule basis.5 KB (692 words) - 12:29, 18 January 2017
- ...interoperable (both ways) with Java. The Xtend language features simplify coding by getting rid of many verbosities of the Java programming language, but al ...interfaces for provisioning & managing device identity and access control rules.7 KB (1,120 words) - 03:48, 16 November 2016
- * "'''UML RT StateMachines'''" defines stereotypes and rules for state machines to support UML-RT specific semantics; ...ection dialog to move it to the selected item box. We are using C++ as the coding language within the tool to match our C++ runtime service library41 KB (6,454 words) - 15:52, 3 April 2017
- * defines compatibility rules and branding process for implementations of these specifications to ensure * defines compatibility rules and branding process for implementations of these specifications to ensure8 KB (1,212 words) - 15:08, 18 May 2018
- ===Rules about gerrit that will added in rules and charter=== ...bug number, commiter (name not mandatory, but companies), verify dates, ( rules with "," or "-")2 KB (248 words) - 05:16, 3 September 2018
- * Coding Conventions: http://wiki.eclipse.org/Coding_Conventions ...on nor for how it may be assessed. Furthermore, almost all product-related rules (with a few exceptions, like for packages naming) are ''optional'' guidelin9 KB (1,236 words) - 11:11, 6 June 2014
- ...bility...). From the quality improvement stand, they can be interpreted as coding practices and show how conventional good practices are implemented in the p ...ormer. Similarly fix-related commits identification may be impacted by the coding conventions used in the project.7 KB (1,063 words) - 09:55, 10 March 2015
- All the ESF code base follow specific coding rules and standards, mainly based on best practice respect. <br/> ...n of the coding rules can be found in this page: [[ESF coding rules|Coding rules]]4 KB (687 words) - 04:00, 26 August 2015
- == Rules organisation == To ease the rules understanding, a classification has been made to organise them. Thus, each30 KB (4,549 words) - 04:57, 27 April 2015
- * Dani: Rules for exporting packages as outlined in [https://wiki.eclipse.org/Export-Pack ** We need to discuss whether we want to relax those rules.28 KB (4,568 words) - 12:04, 10 March 2021