Gregor J. Rothfuss wrote:
Daniel Fagerstrom wrote:
Please cast your votes:
[X ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
i also just noticed that the old JXTemplateGenerator has a dependency on
rhino (which means it does
Le 13 avr. 05, à 16:47, Daniel Fagerstrom a écrit :
[X ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
[ X] Keep JXTG functionality as is and put template development
efforts in CTemplate
[ ] Add new things to JXTG while
Daniel Fagerstrom wrote:
I propose that we (in trunk) remove the current JXTG and replace it
with the refactored JXTG that is part of the Template block. The
refactored JXTG is supposed to be back compatible with the original
JXTG and also add the ability to use JXTG in the same way in a non
Leszek Gawron wrote:
Gregor J. Rothfuss wrote:
Daniel Fagerstrom wrote:
Please cast your votes:
[X ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
i also just noticed that the old JXTemplateGenerator has a dependency
on rhino
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Gregor J. Rothfuss wrote:
Daniel Fagerstrom wrote:
Please cast your votes:
[X ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
i also just noticed that the old JXTemplateGenerator
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
snip/
We have discussed configurable and unified environment (object model)
handling: http://marc.theaimsgroup.com/?t=11096309164r=1w=2,
which would mean that you can decide what you want JXTG to depend on,
e.g. if it should allow the use of
Daniel Fagerstrom wrote:
Leszek Gawron wrote:
Daniel Fagerstrom wrote:
snip/
We have discussed configurable and unified environment (object model)
handling: http://marc.theaimsgroup.com/?t=11096309164r=1w=2,
which would mean that you can decide what you want JXTG to depend on,
e.g. if it
On 13 Apr 2005, at 15:47, Daniel Fagerstrom wrote:
Please cast your votes:
[ X] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
[X ] Keep JXTG functionality as is and put template development
efforts in CTemplate
[ ] Add new
Daniel Fagerstrom wrote:
Please cast your votes:
[X ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ X] Mark the Template block core.
[ ] I suggest ...
i also just noticed that the old JXTemplateGenerator has a dependency on
rhino (which means it does not work in a pure javaflow
Bertrand Delacretaz wrote:
Le 13 avr. 05, à 16:47, Daniel Fagerstrom a écrit :
...There are certainly things left to do in the refactoring but
everything is supposed to work as it is right now...
Before voting, what worries me slightly is the supposed to work bit.
I didn't look into the new
Bertrand Delacretaz wrote:
Le 13 avr. 05, à 16:47, Daniel Fagerstrom a écrit :
...There are certainly things left to do in the refactoring but
everything is supposed to work as it is right now...
Before voting, what worries me slightly is the supposed to work bit.
I didn't look into the new
Le 14 avr. 05, à 08:24, Daniel Fagerstrom a écrit :
Bertrand Delacretaz wrote:
Before voting, what worries me slightly is the supposed to work
bit...
I didn't look into the new stuff yet, are there tests (automated or
not) to help make a more precise assessment?
Of course :)
Bertrand Delacretaz wrote:
Le 14 avr. 05, à 08:24, Daniel Fagerstrom a écrit :
Bertrand Delacretaz wrote:
Before voting, what worries me slightly is the supposed to
work bit...
I didn't look into the new stuff yet, are there tests (automated or
not) to help make a more precise assessment?
Il giorno 13/apr/05, alle 16:47, Daniel Fagerstrom ha scritto:
I propose that we (in trunk) remove the current JXTG and replace it
with the refactored JXTG that is part of the Template block. The
refactored JXTG is supposed to be back compatible with the original
JXTG and also add the ability
Ugo Cei wrote:
Il giorno 13/apr/05, alle 16:47, Daniel Fagerstrom ha scritto:
I propose that we (in trunk) remove the current JXTG and replace it
with the refactored JXTG that is part of the Template block. The
refactored JXTG is supposed to be back compatible with the original
JXTG and also
Daniel Fagerstrom wrote:
[X] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[X] Mark the Template block core.
[ ] I suggest ...
[X] Keep JXTG functionality as is and put template development efforts
in CTemplate
[ ] Add new things to JXTG while keeping it back compatible
[ ] Add
I propose that we (in trunk) remove the current JXTG and replace it with
the refactored JXTG that is part of the Template block. The refactored
JXTG is supposed to be back compatible with the original JXTG and also
add the ability to use JXTG in the same way in a non flow context. The
only
Daniel Fagerstrom wrote:
Please cast your votes:
[ +1 ] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[ +1 ] Mark the Template block core.
[ ] I suggest ...
[ +1 ] Keep JXTG functionality as is and put template development
efforts in CTemplate
[ ] Add new things to JXTG while
Daniel Fagerstrom wrote:
[+1] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[+1] Mark the Template block core.
[ ] I suggest ...
[+1] Keep JXTG functionality as is and put template development efforts
in CTemplate
[ ] Add new things to JXTG while keeping it back compatible
[ ]
Daniel Fagerstrom wrote:
Please cast your votes:
[+1] Let's switch to the refactored JXTG in trunk!
[ ] It can wait.
[+1] Mark the Template block core.
[ ] I suggest ...
[+1] Keep JXTG functionality as is and put template development efforts
in CTemplate
[ ] Add new things to JXTG while keeping
Le 13 avr. 05, à 16:47, Daniel Fagerstrom a écrit :
...There are certainly things left to do in the refactoring but
everything is supposed to work as it is right now...
Before voting, what worries me slightly is the supposed to work bit.
I didn't look into the new stuff yet, are there tests
21 matches
Mail list logo