Hi again,
if you do end up having to patch the Generator, it shouldn't be too
hard. misc.textutil already has the necessary conversion function, so
it's just a matter of modifying Generator.runFix so that it calls
textutil.any2Dos instead of textutil.any2Unix.
Regards,
Daniel
Peter Schneider schrieb:
> Hi Daniel,
>
> thank you for the information. I had expected that answer.
>
> And to answer your question with an answer:
> No I don't use 'edlin' or 'notepad' for editing ;)
>
> DOS-EOL was -as I said- just a convention on our side.
> And so we currently ended up in having two different endings: UNIX in
> qooxdoo-framework and DOS in application :-/
>
> Nevertheless, no need for any action on your side!
>
> I might be able to change the EOL-rule for this project on our side,
> or get the time to patch the frameworks Generator
> (...and hoping for the first option...)
>
>
> Thanks again,
> Peter
>
> -------- Original --------
> From: Daniel Wagner
> Date: 30.03.2010 16:35
>
>> Hi Peter,
>>
>> I asked some of the other core devs but nobody knew a reason other than
>> "we had to decide one way or the other so we just went with Unix-style
>> line endings". It's just a convention, like the "two spaces for
>> indentation" rule.
>>
>> To answer your question with another, why would you want to punish
>> yourself by using an editor that can't even deal with different kinds of
>> line endings? ;)
>>
>>
>> Regards,
>> Daniel
>>
>> Peter Schneider schrieb:
>>> Hi there,
>>>
>>> in the current version (1.0.1) the "fix" job ("fix-files") normalizes all
>>> files
>>> to have *nix type end-of-line (EOL) characters.
>>>
>>> Is there a reason for that - apart from being just 1 byte in size (instead
>>> of 2
>>> bytes for Windows EOLs)?
>>>
>>> I think it should at least be possible to configure the EOL-character ("CR",
>>> "LF" or "CRLF"), unless there is a good reason to stick with the *nix style.
>>>
>>> This question just came up, 'cause we are developing and running the
>>> application on Windows machines and it is our current "company-rule" to
>>> store
>>> (source-)files with windows-style EOLs.
>>> Which makes kind of sense, 'cause you can open and view the file even with
>>> the
>>> dumbest editor ;)
>>>
>>> Again, this is no "request for a change", but rather a "request for
>>> knowledge".
>>> So if there's a striking reason for *unix EOL, I might be able to argue for
>>> that here in the company :-D
>>>
>>> Regards,
>>> (curious) Peter
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
