agilewiki-wiki — General discussion.

[AgileWiki] I'll be working on change name today

[Bill La F. <Wil...@Su...>]

Gordan,

I'll give you another project when you feel you are ready or, better, 
you can suggest one--perhaps one of the projects I've posted as suggestions.

I want to get a release out in 24 hrs that we can use for building real 
content--I'm thinking about programmer docs--and for that, change name 
is really important.

I am glad to see that you are trying to swallow AgileWiki3 whole. Quite 
a feat, actually. And I am looking forward to the time when you can 
start contributing.

All the best to you,

Bill

[AgileWiki] Found it! Fixed it!

[Bill La F. <Wil...@Su...>]

Hopefully now AgileWiki will be significantly more stable.

The bug was a simple one. When a block was split, the new block was not 
being marked dirty. So the larger the database grew, the more likely it 
was that the block was never written out to disk. In this case, it was 
block #12 (the 13th block), where blocks are 34KB long.

So it is time to do a release, methinks.

Bill

Re: [AgileWiki] critical path: change name (gordon) (Bill la Forge)

[Bill la F. <bil...@su...>]

Gordan,

The assignment is intended to be a simple introduction, a first hands-on=20
experience with commands and forms. You crib some code and make a few=20
minor edits, but mostly you get it to work. You learn things like having=20
to do a clean/build after changing commands.txt because the make files=20
don't otherwise update the jar file. And I really don't want any=20
original code at that level. I.E. If your code doesn't look like all the=20
other command/form code, its not good.

As for changing the name itself, the code is something like:
    session.getContext().setName(newName);
which invokes org.agilewiki.ark.rolons.Rolon.setName.

The only fun part of this assignment is determining command=20
applicability, and there's lots of (somewhat confusing) examples.

Now as for timing, I really need to focus on tracking down this db bug I=20
found. So you've got a bit more time. :-)

Bill

gordan milojevic wrote:

> Hi Bill,
> I m still learnig AgileWiki3 all project, and using
> all documentation, and update all new revision, every day.
>
> I have free time and all time try to undersend better AgileWiki3.
> Reading all version of AgileWiki3 alpha 1 to alpha 27 with all fresh=20
> update
> I didnt enought undersend princip of AgileWiki, and AgileWiki 27=20
> become very
> big project, so I was thinking that is for me the best way begin with=20
> AgileWiki3 alpha1
> As you said on February 06 "..but more than half of the architecture=20
> is in place"
> =20
> I was try to undersend  basics princip, and I was found and understend=20
> cmds.txt (from AgileWiki3 alpha1)
> as
> file with context of all classes(which allow class loader from=20
> CmdManager.java)
> all classes from folder cmds represent commands (help, Ct, CcC, CcA,=20
> Attributes, Journal)
> and all extends cmd class(base class for all commands).
> (this is very good way how to read context, parameters and attributes)
> Thats one of constitutive elements of couple, one is ark.java
> which  is knowledge database, its class with represents kind of object=20
> base, its very clever
> way to store the data.
> (I think that searcing and update is faster then using for example=20
> pointbase 4.2re I was using before)
> Whith documentation which explain rolons, ark, drawer, topic,=20
> sections, I have more clearly
> thinking of all project.
> I know for Change Name  command and think about that, and it will
> be implement, I m every day looking, thinking and analysing
> all AgileWiki3 alpha1, and now I think that basics princips of
> AgileWiki3 could be clearly undersending.
> I m every day reading all mail from=20
> com...@li...=20
> <mailto:com...@li...>.
> I was thinking in all projects (including and UML diagrams which can be
> implemented)
> I just need small time, and I will change name
> (I know its class which have to implement QueryCmd(base class on=20
> AgileWiki3 alpha27 AwServer/framework)
> and will have basics methods public final help(), requestDisplay(),=20
> boolean applicable(),
> final void process() plus methods for change name which will have=20
> adequate implement
> (AgileWiki3 alpha1 have basic princips like AgileWiki3 alpha27, but=20
> alpha 27 is very
> biger then alpha1, and this big project make me confused, so now I can=20
> undersend
> and alpha27, but not so clearly.
> So, I will implement change name very soon, at the this  weekend, or=20
> day or two afther.
> =20
> =20
> =20
> best regards
> =20
> gordanmilojevic
>
> */com...@li.../* wrote:
>
>
>
>     Gordon,
>
>     Unless there is some activity on the change name
>     command, I expect to work on it myself this weekend.
>     (Assuming something else more critical doesn't come
>     up.)
>
>     Its been a while since I've heard from you and the
>     agile aspects of agile wiki are starting to become
>     important.
>
>     This week I hope to do an early release and start
>     working on content at agilewiki.org, now that I have
>     rebuild to fall back on. Of course, in the process
>     some bugs may come up--I know they're in there.
>
>     Another command I want to do (unassigned to date) is
>     move, which will allow a topic to be relocated within
>     the same Cabinet.
>
>     I'll note that I only plan to implement very simple
>     forms of these commands--both change name and move
>     should really include refactoring options a la
>     NetBeans, 'cause its supposed to be an AGILE wiki, mm?
>     But for now we're still working of basic wiki
>     capabilities.
>
>     Bill
>
> -----------------------------------------------------------------------=
-
> Ring'em or ping'em. Make PC-to-phone calls as low as 1=A2/min=20
> <http://us.rd.yahoo.com/mail_us/taglines/postman11/*http://us.rd.yahoo.=
com/evt=3D39666/*http://voice.yahoo.com>=20
> with Yahoo! Messenger with Voice.
>
>------------------------------------------------------------------------
>
>Using Tomcat but need to do more? Need to support web services, security=
?
>Get stuff done quickly with pre-integrated technology to make your job e=
asier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni=
mo
>http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> =20
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Compstrm-wiki mailing list
>Com...@li...
>https://lists.sourceforge.net/lists/listinfo/compstrm-wiki
> =20
>

[AgileWiki] new member: Kaim Khairov

[Bill la F. <bil...@su...>]

I'd like to welcome Kaim Khairov:

Among my skills there is GUI development (Swing), 
good knowledge of J2SE, 2 years of Java programming 
experience, some Servlets.

Bill

Re: [AgileWiki] critical path: change name (gordon) (Bill la Forge)

[gordan m. <gor...@ya...>]

Hi Bill, 
  I m still learnig AgileWiki3 all project, and using 
all documentation, and update all new revision, every day.
  
I have free time and all time try to undersend better AgileWiki3.
  Reading all version of AgileWiki3 alpha 1 to alpha 27 with all fresh update
  I didnt enought undersend princip of AgileWiki, and AgileWiki 27 become very
big project, so I was thinking that is for me the best way begin with AgileWiki3 alpha1
  As you said on February 06 "..but more than half of the architecture is in place"
  
I was try to undersend  basics princip, and I was found and understend cmds.txt (from AgileWiki3 alpha1)
  as 
file with context of all classes(which allow class loader from CmdManager.java)
all classes from folder cmds represent commands (help, Ct, CcC, CcA, Attributes, Journal)
and all extends cmd class(base class for all commands). 
(this is very good way how to read context, parameters and attributes)
Thats one of constitutive elements of couple, one is ark.java
which  is knowledge database, its class with represents kind of object base, its very clever
way to store the data.
(I think that searcing and update is faster then using for example pointbase 4.2re I was using before)
  Whith documentation which explain rolons, ark, drawer, topic, sections, I have more clearly
thinking of all project.
  I know for Change Name  command and think about that, and it will
be implement, I m every day looking, thinking and analysing
all AgileWiki3 alpha1, and now I think that basics princips of
AgileWiki3 could be clearly undersending.
  I m every day reading all mail from com...@li....
  I was thinking in all projects (including and UML diagrams which can be
implemented) 
  I just need small time, and I will change name 
(I know its class which have to implement QueryCmd(base class on AgileWiki3 alpha27 AwServer/framework)
and will have basics methods public final help(), requestDisplay(), boolean applicable(), 
final void process() plus methods for change name which will have adequate implement
(AgileWiki3 alpha1 have basic princips like AgileWiki3 alpha27, but alpha 27 is very
biger then alpha1, and this big project make me confused, so now I can undersend 
and alpha27, but not so clearly.
So, I will implement change name very soon, at the this  weekend, or day or two afther.
   
    
   
  best regards
   
  gordanmilojevic

com...@li... wrote:
  

Gordon,

Unless there is some activity on the change name
command, I expect to work on it myself this weekend.
(Assuming something else more critical doesn't come
up.)

Its been a while since I've heard from you and the
agile aspects of agile wiki are starting to become
important.

This week I hope to do an early release and start
working on content at agilewiki.org, now that I have
rebuild to fall back on. Of course, in the process
some bugs may come up--I know they're in there.

Another command I want to do (unassigned to date) is
move, which will allow a topic to be relocated within
the same Cabinet.

I'll note that I only plan to implement very simple
forms of these commands--both change name and move
should really include refactoring options a la
NetBeans, 'cause its supposed to be an AGILE wiki, mm?
But for now we're still working of basic wiki
capabilities.

Bill


 		
---------------------------------
Ring'em or ping'em. Make  PC-to-phone calls as low as 1¢/min with Yahoo! Messenger with Voice.

[AgileWiki] problems and how to fix them

[Bill La F. <Wil...@Su...>]

All svn users,

Because of some changes I made this morning, when you
do a svn up, you will likely have some conflicts which
will prevent you from opening AwServlet.

What you need to do:

1. in AwServlet, delete build.xml

2. in AwServlet/nbproject, delete

build-impl.xml,
project.xml,
genfiles.properties and
project.properties.

3. do "svn up" to restore these files.

4. open the project in the AwServlet folder. It should
now open with the project name "Root".

5. edit the properties of the Root project, resolving
any platform and source-level issues if necessary.

6. do a build/clean.

Sorry 'bout that. I needed to change the war file name
to meet a Tomcat requirement and that caused the mess.
But if you follow the above proceedure, then we should
all be in sync again.

Bill

[AgileWiki] a change of plans!

[Bill la F. <laf...@ya...>]

I was in the process of doing a release this morning,
when the database died with an EOF error.

Using rebuild, I quickly learned that the problem
could be reproduced. So I have a (somewhat large) test
case.

Now by using a binary search, I was able to reduce the
number of transactions such that the database dies
after a rebuild of n trnasactions. (It dies when a
client connects, presumably when a new session is
created.) But everything runs fin if only the first
n-1 transactions are used when rebuilding the
database. 

Of course, there's nothing special about that nth
transacton. So my guess is that it might be a split
operation which is going wrong. But its hard to say at
this point.

So anyway, I've got something to work on. And
considering how much data I had to enter for this
error to occur, I expect that fixing this one bug will
significantly increase database reliability. (No, I'm
not saying that it is the last bug. Only that the next
one will likely be less frequent and subsequently
harder to find.)

This may not be an easy bug to track down. But it is
now reproducable and that is a really big help.

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] new command, addParent

[Bill la F. <laf...@ya...>]

The addParent command applies to Folders and
Pages--it's not just a tree anymore. :-)

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] open assignment: inlining lsecs

[Bill la F. <laf...@ya...>]

All,

It would be nice to have the option of in-lining the
display of LSecs, al la WikiPedia. This could easily
be controled by a DEnt whose value is toggled by a
command.

Any takers?

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] open assignments: ordering

[Bill la F. <laf...@ya...>]

All,

One thing the AgileWiki supports which is not yet very
evident is order. CEnts can be ordered, as well as
DEnts and LEnts. Children can be ordered, and LSecs
too. Even parents can be ordered. (Yes, a Folder or a
Page can have more than one parent.)

So we need commands for all of these. Fortunately, the
API for ordering already exists. And we need a command
for adding a parent to a Folder or Page. (Parent
Topics must all be in the same Cabinet.)

Just let me know if you want to work on any of
these--I can give some pointers on the API and its
good to coordinate projects.

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] critical path: change name (gordon)

[Bill la F. <laf...@ya...>]

Gordon,

Unless there is some activity on the change name
command, I expect to work on it myself this weekend.
(Assuming something else more critical doesn't come
up.)

Its been a while since I've heard from you and the
agile aspects of agile wiki are starting to become
important.

This week I hope to do an early release and start
working on content at agilewiki.org, now that I have
rebuild to fall back on. Of course, in the process
some bugs may come up--I know they're in there.

Another command I want to do (unassigned to date) is
move, which will allow a topic to be relocated within
the same Cabinet.

I'll note that I only plan to implement very simple
forms of these commands--both change name and move
should really include refactoring options a la
NetBeans, 'cause its supposed to be an AGILE wiki, mm?
But for now we're still working of basic wiki
capabilities.

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] a mid-week release?

[Bill la F. <laf...@ya...>]

http://laforge49.blogspot.com/2006/06/mid-week-release.html
 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] rebuild

[Bill la F. <bil...@su...>]

I've now done some additional testing of rebuild (using destroy and 
citations) and I'm not seeing any problems at all.

Now the real testing begins. The rest of this week I'll be trying to use 
AgileWiki to self-host some documentation. Lets see what happens.

Bill

[AgileWiki] The Columns Ledger Section

[Bill la F. <bil...@su...>]

Now every rolon which has a table for its document content has a table 
descriptor unit assigned as its descriptor unit, where all table 
descriptor units have as their assigned descriptor unit, the 
TableDescriptorUnitDescriptorUnit. And there will be a lot of table 
descriptor units, one for every kind of table.

Every table descriptor unit has a Ledger Section rolon named Columns. 
And the descriptor unit assigned to all Column Ledger Sections is always 
the ColumnsDescriptorUnit. (I'm getting a bit dizzy here, methinks.)

Now the Columns Ledger Section is itself a table, so of course the 
descriptor unit assigned to the ColumnsDescriptorUnit is the 
TableDescriptorUnitDescriptorUnit. (Obviously, right?) But enough fun. 
There really is a point I want to make here...

The Columns Ledger Section of every table descriptor unit has two (2) 
columns: ColumnName and BriefDescripton. Hey, that's a start, but I can 
think of two more columns that would be very helpful: Required and 
FieldType.

Now there is a bunch of work to be done here. Sougata has already begun 
work on a table-based single-entry accounting system. And I've suggested 
to Niall that a table sort on a column would be useful. But there's much 
more. For example, we need a command for adding rows to a table. The 
form for this command would be composed using the information in the 
Columns Ledger Section. In addition to sorting on a column, we also need 
to be able to manually reorder rows. And we also need to be able to 
remove a row from a table, or edit the content of a row.

Tables are very important here. They are used in the configuration of 
the AgileWiki, and will likely be central to most applications. And the 
good thing is that there is a very limited API that you need to use to 
work with tables. (Too many things required a very broad-based knowledge 
of the whole of the AgileWiki, but tables is not one of them.)

Bill

[AgileWiki] brief about documents

[Bill la F. <laf...@ya...>]

TKS supports simple properties, tables of key/value pairs and inverted tables of key/value pairs. But AgileWiki only uses one simple property, doc. Note that only simple properties can contain line feeds--the values in TKS tables MUST not contain linefeeds, as linefeeds are used as the delimiter for key/value pairs. So the doc property is the only place where a linefeed can be used.
   
  So, every Rolon can have at most one document, documents being stored in the doc property. The advantage here is that you can pretty much equate documents and rolons, all be it some documents will have no content.
   
  Now there is a DescriptorEntry (DEnt) named MimeType which describes the document content. Currently we support text/plain, text/html and text/csf. But to support an email client application, we will need to support much more.
   
  The text/csf mime type is for application-level tables, but that takes us to my next topic.

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] table descriptor unit

[Bill la F. <laf...@ya...>]

Table Descriptor Unit is somewhat confusing because of the meta recursion. But lets give it a try.
   
  Every Rolon has an assigned descriptor unit, which itself is a rolon in the DescriptorUnits drawer of the same cabinet. (The name of the assigned descriptor unit is displayed in the header of the rolonic view.)
   
  So a Descriptor unit rolon itself has an assigned descriptor unit.
   
  There is one very special descriptor unit, called DescriptorUnitDescriptorUnit. This rolon is special because its assigned descriptor unit is itself.
   
  Now the descriptor unit assigned to most of the descriptor units is this DescriptorUnitDescriptorUnit. But there is a second descriptor unit which is also assigned as the descriptor unit of other descriptor units: TableDescriptorUnitDescriptorUnit.
   
  Now we get to the fun part. When a rolon has a table for its document content, the assigned descriptor unit itself is what we call a table descriptor unit, as it describes the table, including the column headers. And all table descriptor units have, as the descriptor unit assigned to them, the TableDescriptorUnitDescriptorUnit.
   
  Hope I didn't loose anyone there. :-) 
   
  Bill

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] table descriptor unit

[Bill la F. <laf...@ya...>]

Table Descriptor Unit is somewhat confusing because of the meta recursion. But lets give it a try.
   
  Every Rolon has an assigned descriptor unit, which itself is a rolon in the DescriptorUnits drawer of the same cabinet. (The name of the assigned descriptor unit is displayed in the header of the rolonic view.)
   
  So a Descriptor unit rolon itself has an assigned descriptor unit.
   
  There is one very special descriptor unit, called DescriptorUnitDescriptorUnit. This rolon is special because its assigned descriptor unit is itself.
   
  Now the descriptor unit assigned to most of the descriptor units is this DescriptorUnitDescriptorUnit. But there is a second descriptor unit which is also assigned as the descriptor unit of other descriptor units: TableDescriptorUnitDescriptorUnit.
   
  Now we get to the fun part. When a rolon has a table for its document content, the assigned descriptor unit itself is what we call a table descriptor unit, as it describes the table, including the column headers. And all table descriptor units have, as the descriptor unit assigned to them, the TableDescriptorUnitDescriptorUnit.
   
  Hope I didn't loose anyone there. :-) 
   
  Bill

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] brief about documents

[Bill la F. <laf...@ya...>]

TKS supports simple properties, tables of key/value pairs and inverted tables of key/value pairs. But AgileWiki only uses one simple property, doc. Note that only simple properties can contain line feeds--the values in TKS tables MUST not contain linefeeds, as linefeeds are used as the delimiter for key/value pairs. So the doc property is the only place where a linefeed can be used.
   
  So, every Rolon can have at most one document, documents being stored in the doc property. The advantage here is that you can pretty much equate documents and rolons, all be it some documents will have no content.
   
  Now there is a DescriptorEntry (DEnt) named MimeType which describes the document content. Currently we support text/plain, text/html and text/csf. But to support an email client application, we will need to support much more.
   
  The text/csf mime type is for application-level tables, but that takes us to my next topic.

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] AgileWiki tables

[Bill la F. <laf...@ya...>]

We've got 2 kinds of tables, so we've got to be careful to distinguish between them. TKS supports tables of key/value pairs. And at a higher level, one type of document content, with a mime type of text/csf, is a multi-column table. Here I'm speaking about the latter.
   
  Now we have different types of rolons, as defined both by their descriptor unit and by the DescriptorEntry, Type. The former is used to set the latter when a rolon is created.
   
  Now the values of the Type DEnt are used to determine the class used to instantiate the Rolon Data Proxy object, with the table of types/classes found in the rolons.txt file.
   
  All rolons with tables use either the TableRolon class or a subclass of same. So when defining a table operation/command, we can simply attach it to the TableRolon class, thus defining the scope of the command to apply to all tables.
   
  The content of a table is very simple. Each line is a row. Cells are separated by commas. And the first row is the header row.
   
  Every application table can have its own subclass of TableRolon, though this is not always necessary. However, every application table should has a Descriptor Unit rolon, for it is here that we put the information describing the table.

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] Niall's changes to register and swing client

[Bill la F. <laf...@ya...>]

Niall,
   
  I've reviewed your code and it all looks good. The only thing I've done is to have NetBeans do a reformat on AwSwingClient Main.
   
  Now it turns out the problem I was asking you to fix in Portal is perhaps unfixible--it looks like the registry bind is done in UnicastRemoteObject.
   
  As for the change to register, I do like what you did. And it works equally well for both the swing client and the servlet.
   
  Bill

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

Re: [AgileWiki] things are getting exciting: sharing

[Bill La F. <Wil...@Su...>]

Norm,

Well, for sure, synchronization doesn't work at web-scale. :-)

Actually, I was premature on much of what I wrote. Rebuild is a bit 
simpler than what is needed for sharing, though not that much. Rebuild 
processes everything at the time of occurence, not at the time the log 
file was received from another system--an important distinction.  Also, 
a create should be ignored if its parent has been deleted on the system 
where the log file is being loaded. So sharing is a bit more complicated.

Oh, and I've done a very superficial test of rebuild with the latest 
changes and it seems to run OK. Which is probably good enough for 
checkin right now, but fer sure it needs more testing before the weekend 
release.

Now, are you ready to start entering content? (I should know more by 
next weekend!)

Bill

Norm Kashdan wrote:

>Bill, you should be sure to emphasize that sharing is NOT synchronization.
>The Rolonic position on synchronization is simply that it does not work.
>Many systems have died trying.
>
>;-n
>
>-----Original Message-----
>From: com...@li...
>[mailto:com...@li...] On Behalf Of Bill la
>Forge
>Sent: Monday, June 19, 2006 2:07 AM
>To: com...@li...
>Subject: [AgileWiki] things are getting exciting: sharing
>
>I've just made a bunch of changes to TKS and Rebuild,
>though it will perhaps take a day for me to catch up
>on testing.  :-(
>
>But I wanted to let you know that we are very close to
>something quite exciting: sharing.
>
>What is sharing? Sharing is the exchange of selected
>log file entries between arks, where selection is
>based on Cabinet. It allows you to work locally in
>your own ark, but share the changes you make with arks
>on other systems, via RMI, svn or email.
>
>For sharing to work, we need to enhance the way
>rebuild handles destroys--it needs to destroy child
>rolons present in an ark which are not present in the
>ark which performed the destroy. That's not too
>difficult.
>
>We'll also want to tag the actions in the log file by
>cabinet, so we can just share the changes made to the
>cabinets which are being shared.
>
>Another change that we'll want is to have an
>incrimental version of rebuild which adds a log file
>from another ark to the existing ark without having to
>rebuild the entire ark.
>
>Sharing has been "in the works" for several years
>now--some prior versions of AgileWiki already
>supported this, so I'm quite familiar with the issues
>involved.
>
>The advantage of sharing is that you can work off-line
>(think laptop) and then share your changes when you
>come back on-line. And even when you are on-line, if
>you are making a lot of updates (think power user),
>things will go a whole lot quicker if you make the
>changes locally and then batch the updates to remote
>systems. Sharing is one of the major features targeted
>for AgileWiki3.
>
>Bill
>
>  
>

Re: [AgileWiki] things are getting exciting: sharing

[Norm K. <nr...@cm...>]

Bill, you should be sure to emphasize that sharing is NOT synchronization.
The Rolonic position on synchronization is simply that it does not work.
Many systems have died trying.

;-n

-----Original Message-----
From: com...@li...
[mailto:com...@li...] On Behalf Of Bill la
Forge
Sent: Monday, June 19, 2006 2:07 AM
To: com...@li...
Subject: [AgileWiki] things are getting exciting: sharing

I've just made a bunch of changes to TKS and Rebuild,
though it will perhaps take a day for me to catch up
on testing.  :-(

But I wanted to let you know that we are very close to
something quite exciting: sharing.

What is sharing? Sharing is the exchange of selected
log file entries between arks, where selection is
based on Cabinet. It allows you to work locally in
your own ark, but share the changes you make with arks
on other systems, via RMI, svn or email.

For sharing to work, we need to enhance the way
rebuild handles destroys--it needs to destroy child
rolons present in an ark which are not present in the
ark which performed the destroy. That's not too
difficult.

We'll also want to tag the actions in the log file by
cabinet, so we can just share the changes made to the
cabinets which are being shared.

Another change that we'll want is to have an
incrimental version of rebuild which adds a log file
from another ark to the existing ark without having to
rebuild the entire ark.

Sharing has been "in the works" for several years
now--some prior versions of AgileWiki already
supported this, so I'm quite familiar with the issues
involved.

The advantage of sharing is that you can work off-line
(think laptop) and then share your changes when you
come back on-line. And even when you are on-line, if
you are making a lot of updates (think power user),
things will go a whole lot quicker if you make the
changes locally and then batch the updates to remote
systems. Sharing is one of the major features targeted
for AgileWiki3.

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/


_______________________________________________
Compstrm-wiki mailing list
Com...@li...
https://lists.sourceforge.net/lists/listinfo/compstrm-wiki

[AgileWiki] things are getting exciting: sharing

[Bill la F. <laf...@ya...>]

I've just made a bunch of changes to TKS and Rebuild,
though it will perhaps take a day for me to catch up
on testing.  :-(

But I wanted to let you know that we are very close to
something quite exciting: sharing.

What is sharing? Sharing is the exchange of selected
log file entries between arks, where selection is
based on Cabinet. It allows you to work locally in
your own ark, but share the changes you make with arks
on other systems, via RMI, svn or email.

For sharing to work, we need to enhance the way
rebuild handles destroys--it needs to destroy child
rolons present in an ark which are not present in the
ark which performed the destroy. That's not too
difficult.

We'll also want to tag the actions in the log file by
cabinet, so we can just share the changes made to the
cabinets which are being shared.

Another change that we'll want is to have an
incrimental version of rebuild which adds a log file
from another ark to the existing ark without having to
rebuild the entire ark.

Sharing has been "in the works" for several years
now--some prior versions of AgileWiki already
supported this, so I'm quite familiar with the issues
involved.

The advantage of sharing is that you can work off-line
(think laptop) and then share your changes when you
come back on-line. And even when you are on-line, if
you are making a lot of updates (think power user),
things will go a whole lot quicker if you make the
changes locally and then batch the updates to remote
systems. Sharing is one of the major features targeted
for AgileWiki3.

Bill


		
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

[AgileWiki] woops!

[Bill la F. <laf...@ya...>]

Found a design flaw.
   
  When a key/value pair is removed from an inverted table, this is NOT noted in the log file. Consequently the item is not removed from the inverted table during the rebuild process.
   
  Easily fixed, I suspect. But right now I'm on a mini-holiday--going shopping for a recreational book (SciFi). I figure I need the break. Its still been a great weekend.
   
  Bill

 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now

[AgileWiki] fyi

[Bill la F. <laf...@ya...>]

http://laforge49.blogspot.com/2006/06/rebuild-facility-is-now-complete-next.html
 				
---------------------------------
  Yahoo! India Answers: Share what you know. Learn something new Click here
 Send free SMS to your Friends on Mobile from your Yahoo! Messenger Download now