Browse Prior Art Database

Auto-completion of a string or char with single or double quotations based on context

IP.com Disclosure Number: IPCOM000250579D
Publication Date: 2017-Aug-04
Document File: 2 page(s) / 14K

Publishing Venue

The IP.com Prior Art Database

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Auto-Completion of a String or Char with Single or Double Quotations Based on Context

When developing code, many of the different IDE's (Integrated Development Environments) provide the ability for auto-completion and auto-correction for variables, methods and functions.

IDE’s also provide quick actions such as creating duplicate and in some cases the reverse characters when it believes they are needed such as ( )," ", ' ', { }, [ ] etc.

However, there is the issue where if a single or double quotations around a string or char is missed it can be tedious to manually insert them. The user would have to go to the first point at which this string started and introduce a quote, then go to the end and introduce another quote which most if not all IDE's would believe a string or char is being started and will duplicate the quotation used adding further frustration.

An automated solution is needed to remove the frustration of this current system and improve productivity of developers.

The idea of this system is to add the ability to an IDE to detect when a user is creating, parsing or assigning a string or char and then to surround the content with either single or double quotations based on the language used. This detection system would occur after a user has either created a new line, terminated the statement with the appropriate character or has used auto-complete function within the IDE.

An extension on this is the ability to determine whether that content contains any special characters that would either break the string/char or cause some other intended behaviour and then insert an escape character prior to that to keep the content intact.

This would make this system more friendly and reactive to what a user types. It would also remove the similar experience to what this disclosure is focusing on removing.

The example below shows the implementation of this idea in Java: 1. The user types in: String str = Hello World 2. The user could then terminate the statement (i.e. with a semicolon), start a

new line or use an auto-complete function 3. This triggers the line to be analysed for a string 4. The string that is being assigned to the str is determined from that line 5. The appropriate quotations are then inserted at either end of said string. This

is then displayed back to the user as: String str = "Hello World"; In step 1, this would also apply to passing a string into a method or function. A

simple Java example of this could be: System.out.println(Hello World); Would automatically correct to: System.out.println("Hello World"); In step 3, an extension of this would be to also determine and insert an escape

character such as " \ " prior to any special characters that requ...