> ``the concept of a TCP session not "letting go" could be really distressing to some TCP stacks and

later 18:56 <Chami1> ok 18:56 <+tmortagne> for now what's important is the general concept of providing

the design of workspaces) 17:27 <JuanDaugherty> I meant the concept with the URL I just gave, not

proof of concept 11:43 <vmassol> ok good 11:43 <vmassol> thanks 11:46 <pturcotte> has quit 12:11

the administration app) just for the proof of concept 11:43 <vmassol> ok good 11:43 <vmassol> thanks

() gets the "selected object" from the document (which is a bad concept IMO) 19:05 <@cjdelisle> getObject

() gets the "selected object" from the document (which is a bad concept IMO) 19:05 <@cjdelisle> getObject

<jstoldt> proof of concept? 10:16 <@cjdelisle> Because mine doesn't rely on asking verisign who owns a

<jstoldt> proof of concept? 10:16 <@cjdelisle> Because mine doesn't rely on asking verisign who owns a

"page renamed" event 11:51 <jstoldt> to be honest, i don't like the concept of add new, remove old to

"page renamed" event 11:51 <jstoldt> to be honest, i don't like the concept of add new, remove old to

/expansable/expendable/ 22:16 <mar3lis> i'm not sure i understand the concept of this method 22:16 <+Denis> if

/expansable/expendable/ 22:16 <mar3lis> i'm not sure i understand the concept of this method 22:16 <+Denis> if

commons sense, when a project contains too much concept you separate it is several like we do all the time

commons sense, when a project contains too much concept you separate it is several like we do all the time

<+tmortagne> we could find a way to make include macro a bit less dependent on wiki concept, like some API to