of
character classes inside Lyx, Therefore I modified my proposal, and
the whole procedure is now simpler.
On Wed, May 1, 2013 at 4:14 AM, Tommaso Cucinotta tomm...@lyx.org wrote:
On 30/04/13 03:11, Albus X wrote:
My proposal is updated. I removed the mentioning of Prolog, made the
algorithm
of
character classes inside Lyx, Therefore I modified my proposal, and
the whole procedure is now simpler.
On Wed, May 1, 2013 at 4:14 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote:
> On 30/04/13 03:11, Albus X wrote:
>> My proposal is updated. I removed the mentioning
Hello. In my opinion, cooperative editing the same paragraph does not
make sense. I will be annoyed if the paragraph I am editing change
from time to time making the structure and meaning and everything a
mess. I suggest that we could simply lock that paragraph while others
can commenting on it,
Hello. In my opinion, cooperative editing the same paragraph does not
make sense. I will be annoyed if the paragraph I am editing change
from time to time making the structure and meaning and everything a
mess. I suggest that we could simply lock that paragraph while others
can commenting on it,
I have officially submitted my proposal at
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/albuseer/1
Please have a review.
On Mon, Apr 29, 2013 at 10:18 AM, Albus X albus...@gmail.com wrote:
I am not very familiar with git, what is the meaning of
[712e1871/lyxgit]? I
see that you mention Prolog
in your proposal. Are you planning on using Prolog? Do you have any ideas in
how a similar algorithm could be implemented in C or C++ instead? (It would
be good if a LyX user did not have to install Prolog as LyX currently does
not depend on it.)
Albus X wrote:
I
It seems that there is another person interested in this project?
OK, here is my opinion:
I understand there will be plenty of classes modified this way, but to
most of them, the change is minor, and share a common pattern.
What we need for an inset class is (1) its type and (2) its child
My proposal is updated. I removed the mentioning of Prolog, made the
algorithm description clearer, and added more explanation.
On Tue, Apr 30, 2013 at 8:58 AM, Albus X albus...@gmail.com wrote:
No. I am indeed not familiar with programming in Prolog. I mentioned
it because the pattern matching
I have officially submitted my proposal at
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/albuseer/1
Please have a review.
On Mon, Apr 29, 2013 at 10:18 AM, Albus X <albus...@gmail.com> wrote:
>> I am not very familiar with git, what is the meaning of
>>
depend on it.)
>
>
> Albus X wrote:
>>
>> I have officially submitted my proposal at
>>
>> https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/albuseer/1
>>
>> Please have a review.
>>
>> On Mon, Apr 29, 2013 at 10:18 AM,
It seems that there is another person interested in this project?
OK, here is my opinion:
I understand there will be plenty of classes modified this way, but to
most of them, the change is minor, and share a common pattern.
What we need for an inset class is (1) its type and (2) its child
My proposal is updated. I removed the mentioning of Prolog, made the
algorithm description clearer, and added more explanation.
On Tue, Apr 30, 2013 at 8:58 AM, Albus X <albus...@gmail.com> wrote:
> No. I am indeed not familiar with programming in Prolog. I mentioned
> it because
Hello everyone, I am interested in GSoC 2013 and particularly the
Advanced find and replace project.
Before I start, I had a try with the current version, and want to ask
some questions.
I read the corresponding sections in the user guide, and tried to find
some math using regular expressions. I
Hello everyone, I am interested in GSoC 2013 and particularly the
"Advanced find and replace" project.
Before I start, I had a try with the current version, and want to ask
some questions.
I read the corresponding sections in the user guide, and tried to find
some math using regular expressions.
14 matches
Mail list logo
