On 23 Jan 2013, at 5:40 AM, Jean Suisse wrote:
>>
>> Hmm. Maybe not. I want to keep the generated variable name legible.
>
>> I think I will have to introduce an intermediate NSTextView that filters and
>> displays the natural language input.
>> The user can then modify the variable name if ne
On 23 Jan 2013, at 13:07, Uli Kusterer wrote:
> On Jan 23, 2013, at 2:18 AM, jonat...@mugginsoft.com wrote:
>> Hmm. Maybe not. I want to keep the generated variable name legible.
>
> You need to nail down the languages you want to deploy to, and then find out
> what their criteria for identif
On Jan 23, 2013, at 2:18 AM, jonat...@mugginsoft.com wrote:
> Hmm. Maybe not. I want to keep the generated variable name legible.
You need to nail down the languages you want to deploy to, and then find out
what their criteria for identifiers are. Then you can decide to either generate
identical
On 23 Jan 2013, at 11:40, Jean Suisse wrote:
> On 23 janv. 2013, at 02:18, "jonat...@mugginsoft.com"
> wrote:
>
My current thinking is, regardless of the language, is to exclude all
characters that are not members of NSCharacterSet + (id)letterCharacterSet.
Is +
On 23 janv. 2013, at 02:18, "jonat...@mugginsoft.com"
wrote:
>>>
>>> My current thinking is, regardless of the language, is to exclude all
>>> characters that are not members of NSCharacterSet + (id)letterCharacterSet.
>>>
>>> Is + (id)letterCharacterSet the best choice here?
>>
>> I don't
On 23 Jan 2013, at 01:32, Keary Suska wrote:
> On Jan 22, 2013, at 6:18 PM, Jens Alfke wrote:
>
>> On Jan 22, 2013, at 3:28 PM, jonat...@mugginsoft.com wrote:
>>
>>> Is + (id)letterCharacterSet the best choice here?
>>
>> The API docs say "Informally, this set is the set of all characters us
On 23 Jan 2013, at 00:05, Jean Suisse wrote:
>>
>> Dealing with English seems not too troublesome but titles composed in other
>> languages might be a different matter.
>
> Do you want to deal with other languages ? For instance Japanese, Chinese,
> Korean, Arabic, etc. ?
The user can enter
On Jan 22, 2013, at 6:18 PM, Jens Alfke wrote:
> On Jan 22, 2013, at 3:28 PM, jonat...@mugginsoft.com wrote:
>
>> Is + (id)letterCharacterSet the best choice here?
>
> The API docs say "Informally, this set is the set of all characters used as
> letters of alphabets and ideographs.”
> Which ve
On Jan 22, 2013, at 4:28 PM, jonat...@mugginsoft.com wrote:
> I have a generic descriptive title of a parameter and want to express it as a
> variable name within a script.
>
> So if my title is "No more awesome today, please!" I will likely render this
> as "no-more-awesome-today-please" ( I c
On Jan 22, 2013, at 3:28 PM, jonat...@mugginsoft.com wrote:
> Is + (id)letterCharacterSet the best choice here?
The API docs say "Informally, this set is the set of all characters used as
letters of alphabets and ideographs.”
Which very strongly implies it is not just ASCII, but covers all Uni
On 23 janv. 2013, at 00:28, "jonat...@mugginsoft.com"
wrote:
> I have a generic descriptive title of a parameter and want to express it as a
> variable name within a script.
>
> So if my title is "No more awesome today, please!" I will likely render this
> as "no-more-awesome-today-please" (
I have a generic descriptive title of a parameter and want to express it as a
variable name within a script.
So if my title is "No more awesome today, please!" I will likely render this as
"no-more-awesome-today-please" ( I can define the separator style).
I am targeting about 20 or so scriptin
12 matches
Mail list logo