agilewiki-wiki — General discussion.

[AgileWiki] Something wonderful

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

I am now taking full advantage of column types when displaying tables 
and rows. CabinetNames, Pathnames and userNames are all clickable. But 
of greater interest are untyped columns. These can have wiki text. Full 
brace notation and html fragments are supported.

So now, for example, you can include the document of another Rolon in 
the content of a table.

I think it is just about time for a release.

;-)

Bill

[AgileWiki] new table display, misc items

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

The new table display now contains the names of the rows, and these are 
clickable--taking you directly to the row rolon.

No other columns in the display are clickable. This needs to be worked 
on--the question is, how best to handle references/citations. these 
would be references by the rows and, as a row has no document content, 
we can use the _ref- table to implement this. Note though that it would 
be dependent on the column type. I expect only the cabinetName, pathname 
and userName types would be clickable. (I think this is next on my list.)

Also, I've dropped some redundent displays. The LSecs of a table are not 
displayed. And the LEnts of a row are not displayed.

Bill

[AgileWiki] misc items

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

I had to restart agilewiki.org again. And again, it looks like an 
ISP-related problem.

Now some good news: I can again access blogspot, so I can resume the 
blog at http://laforge49.blogspot.com/

The editRow command now validates the content, both for required fields 
and by type.

Next on my list is table display--this code has become a bit dated.

Bill

[AgileWiki] new account command dropped

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

The generic crRow is powerful enough that the newAccount command in 
SimpleAccounting was simply redundent. So it was dropped.

Bill

[AgileWiki] crRow now validates, initializes

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

I've now added InitialValue to the Columns tables as well.

And crRow now checks for required columns, validates AND provides 
initial values. :-)

And that's a wrap. Tomorrow I suspect editRow will be similarly updated.

Bill

[AgileWiki] Updated all Columns tables, more types of structures

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

I've now updated the Columns table in the following descriptor units:

    * SimpleAccountingDescriptorUnit,
    * UsersDescriptorUnit and
    * ColumnsDescriptorUnit.

For each row in the Columns table, there is now an optional field type 
name and an optional required flag. And I think the next step is na 
obvious one: update the crRow and editRow commands to validate based on 
this additional information.

Now it occurs to me that while the LEnts of a Rolon can be described as 
a structure, the same is always true of DEnts and CEnts. So perhaps 
every descriptor unit should have a DStruct and a CStruct table to 
define these structures? With this addition, suddenly AgileWiki becomes 
a strongly typed system.

Bill

[AgileWiki] 13 field types now defined

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

I thought I would work on row validation and immediately came up with 
two more field types: flag and entryName.

Bill

We now have the following field types:

>    1. amount,
>    2. cabinetName,
>    3. fieldType,
>    4. fileRegex,
>    5. groupName,
>    6. name,
>    7. number,
>    8. pathname,
>    9. rolonType,
>   10. userGroupName and
>   11. userName.
>

[AgileWiki] refresh on destroy

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

OK, I've now added a bit of cleverness to the de command. Normally I 
dislike cleaverness. Too much makes a system quite incomprehendable very 
quickly. Perhaps I'm just being lazy today.

The de command now has a special case for the DescriptorUnits Drawer. If 
you destroy a DescriptorUnits Drawer, the de command immediately 
recreates it, 'cause you gotta have one. By this means then you can 
easily replace an out dated DescriptorUnits Drawer. Saves a whole lot of 
manual tweeking, mm?

Bill

[AgileWiki] 11 field types now defined

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

We now have the following field types:

   1. amount,
   2. cabinetName,
   3. fieldType,
   4. fileRegex,
   5. groupName,
   6. name,
   7. number,
   8. pathname,
   9. rolonType,
  10. userGroupName and
  11. userName.

Not exhaustive, but better than before, mm?

:-)

Bill

[AgileWiki] some misc thoughts

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

1. With a delay of agility, there needs to be a way to update the 
various DescriptorUnits Drawers. Perhaps a refresh command that AdMin 
can run? This is currently a problem at agilewiki.org and will only get 
worse as we add structures and validation.

2. DescriptorUnits are themselves structures. Recongnizing this will 
give us a way to validate the Rolon Type which every DU carries.

3. We need several types. Reference would be handy--then a column of 
references in a table could be clickable, and add to the citations as well.

Rolon Type, as I mentioned above, will also be needed.

We should probably also define a double type for SimpleAccounting.

Anything else?

Bill

[AgileWiki] agilewiki.org, priorities

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

I found agilewiki.org down this morning. Its back up now. Our ISP had 
warned me that he was having UPS problems and to expect some outages.

Now I've been looking over the open issues and have a thought. Lets put 
off agility for now and focus instead on the API, including validation. 
And we can add structures too. We'd then focus on agility after the 
release of 3.2 and classifiers after the release of 3.3. This gives a 
more cohesive focus to the 3.2 release, though even so I think it is a 
few weeks off.

Bill

[AgileWiki] table display

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

Naill,

You've been quiet for a while now. At this point table displays need a 
lot of work, so I'm taking your name off that issue.

Meanwhile, you're still on for swing field length.

Bill

[AgileWiki] editRow, structures

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

OK, the editRow command is checked in.

I've also been thinking about structures this morning. A structure is 
like a row, except that it is not in a table. And, unlike a row where 
the Columns table is in the row's table's descriptor unit, a structure's 
descriptor unit would itself have a Structure table.

I expect that, like tables and rows, structures will be very helpful 
when implementing an application.

Bill

[AgileWiki] crRow command, some thoughts about 3.2

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

When in the context of a table, the crLSec command no longer functions. 
However a new command, crRow is then available.

The new crRow command requests entry of the row name, headline, and 
column values for the row. (Row names must be unique.)

I think the editRow command will be close behind.

I'll note that I have not been quite so productive lately as I have been 
programming for my day job. And for the moment I've set documentation of 
the application interface aside for now. Still, I believe progress has 
been steady. But please let me know if you have any questions. And if 
there is any area you would like to work on, by all means, speak up!

I also expect that we will not reach 3.2, when we start of classifiers, 
for some time yet. We need to wrap up tables, finish access delegation 
and make some progress on agility first. By the time we do the 3.2 
release, AgileWiki should be a pretty powerful wiki. Then we can spend 
some time on the knowledge management aspects, which is where Rolonics 
really adds value. (In 3.2, we also need to work on validation--that's 
vital for a real application platform. But we need a good handle on 
tables first, as tables will be used extensively for validation.)

Bill

[AgileWiki] RowRolon now has a custom display

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

This morning I did a bit of refactoring of TableRolon.docEvent, breaking 
out a getColumns method.

I then added a getTable method on RowRolon.

Finally, I wrote a docEvent method on RowRolon. This custom display 
produces a 3-column table:
Column name,
value and
description.

I must say, it is a lot nicer than just a blank display. I want to 
continue to work on rows a bit, adding a command to add a row to a table 
and also a command to edit a row. After that it would be nice to add 
commands for creating descriptor units and table descriptor units.

Meanwhile, on my day job I've been having fun writing an xml-driven 
GUI-independent wizard engine. Its nearly done. The next step would be 
to wrap a GUI around it, but the trick there is to make it look like the 
product it is replacing. :-( At some point I also want to add wizards to 
AgileWiki, though right now it has enough half-finished (and 
half-baked?) features. I'd rather work on closure.

Bill

Re: [AgileWiki] java Developver

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

Anil,

You are most welcome. Only you should ask a lot of questions--there is 
much to learn and the documentation is incomplete.

(And questions help me write better documentation!)

Bill

anil kumar wrote:

>Hi all
>        i am engg graduate , i hav 1+ java exp, i
>desparatly like to be a member of this project ,
>                                     Anil
>

[AgileWiki] java Developver

[anil k. <mp...@ya...>]

Hi all
        i am engg graduate , i hav 1+ java exp, i
desparatly like to be a member of this project ,
                                     Anil

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[AgileWiki] new editable method on rolons

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

The edit command now only applies to rolons whose editable method 
returns true, which is the default.

Comments are editable, but JSecs are not.
Tables and rows are not.

[AgileWiki] 3.1.2.0 released, what's next?

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

Release 3.1.2.0 is installed at agilewiki.org and has been released: 
https://sourceforge.net/forum/message.php?msg_id=3829420

So what's next? There are 3 areas where AW is especially weak:

   1. agility
   2. tables
   3. classifiers

Now with the addition of tags and tagSearch, we now have some 
classifiers, though no classifier sections. Its a start anyway. I expect 
classifiers and classifier sections will be the focus of 3.2, while 
tables and agility are the focus of 3.1.

I find the lack of agility quite anoying, especially as I use AW as a 
wiki. On the other hand when it comes to tables, AW is almost completely 
non-functional. So I want to focus on tables and rows for a while. 
Creating rows right now is so bad that I don't want to document it.

Bill

[AgileWiki] automatic creation?

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

I've been thinking of a wiki behavior which is lacking in 
AgileWiki--automatic creation when clicking on a WikiWord which can not 
be resolved.

This is a complicated matter because of the different brace notations 
available and the possible use of pathnames.

If the notation is {+some text}, then we probably want to create an LSec 
named "some text".

If the notation is {some text} or SomeText, then we probably want to 
create a sibling to the rolon, but to which rolon? The notation may be 
in an included LSec and I'm thinking we should not be creating an LSec, 
but rather a sibling to the closest topic ancestor. (Unless that 
ancestor is a JSec, mm? Then we want an LSec under the JSec.)

There are, methinks, easier fish to fry. I've been thinking about this 
since last I talked with Norm, and I'm ready to toss this one back in 
the lake.

Bill

[AgileWiki] spaces now allowed in most topic names

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

Cabinet names are still restricted, but other topic names (for Drawers, 
Folders and Pages) are now validated the same as LSec names. So you can 
now have spaces in most topic names.

The restriction on Topic names was a carryover from AW2, but the 
justification for the restriction does not apply to AW3. And I'll give 
credit to Norm for raising this issue.

Now the catch is that names with spaces are not recognized as names 
automaticly--you need to enclose such names {in curly braces} when 
entering/editing document content.

Bill

[AgileWiki] the good and the strange

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

The good news is that I'm about to deploy AgileWiki as an internal 
application at work. It will be  used (as is, but the unreleased 
version) as a means of collecting and managing comments on a complex 
document. Now I had previously exposed many of my coworkers to 
AgileWiki2 and it never made a good impression. But, for all its lacks, 
the 3 coworkers who have seen it so far are reasonably impressed. (Of 
course, Norm and I are greatly unimpressed by AW3--we both badly miss 
the features still lacking in Aw3!)

One of the advantages of AW3 is its support for html as document 
content. It means you can put together nice looking content, and in the 
end, it is the content that counts, not the tool.

As for the strange, agilewiki.org got into a funky state and was not 
accepting logins. Restarting it seemed to do the job. And that's the 
first time this has happened.

Bill

[AgileWiki] tags are now displayed

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

Tags, when present, are now displayed in a lot of places, but in 
particular, they are displayed in the results of a tagSearch.

Bill

[AgileWiki] Some cleanup, some complications

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

I've simplified the titles used with comments and JSecs--the timestamp 
is no longer included.

When comments are listed, the author and status are now listed. This is 
hempful when comments are used as a light-weight issue management 
system. Also, when all the comments for the day are listed, the context 
where the comment was created is also given.

Bill

Re: [AgileWiki] Build next generation applications

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

Paul,

In the download, there are two applications listed in the top-level directory, GuessNumber and SimpleAccounting. There is no documentation for GuessNumber, but it occurs as a Game when you go to http://agilewiki.org/aw3/AwServlet

I've also just started the documentation for the application programmer interface at http://agilewiki.org/aw3/AwServlet?cmd=rid%209f6e87509884a713b50a182d537da6e9 and that includes some material on SimpleAccounting.

Simple, I have learned, only comes with a lot of hard work. It is also a bit of "in the eye of the beholder". Note that these two applications have no GUI code, yet run both as web applications and within a Swing client. Todate only simple forms are supported, but in the office I've been doing a lot of work on wizards, and that is a natural addition.

And to much of application code these days is devoted to GUI code.

Now for the core functionality of an accounting system, you will find that SimpleAccounting is very very small, and most of that code is simply boiler plate copied from other rolons, commands and forms. This is possible because the database and application framework do all the heavy lifting, especially in the area of journals.

On the flip side, please keep in mind that everything in AgileWiki3 is pretty rude and crude. Just got some (SOME!) of the core pieces working and little time for polish. Also, AgileWiki2 was not an application server--it dealt mostly with knowledge management. I've been doing one application for the office and running into issues of providing a more application-focused display.

I hope this helps somewhat. Please keep commenting on what you find, like and dislike. And what you find confusing.

Bill

. . . . . . . . . . . . . . .

Okay, I've created the accounts.  agilewiki.org is a mailing list right?

agilewiki.dev.java.net I signed up as pdemarco I've requested observer.

Is there a Hello World introduction example ?

I've read a some of the stuff but the simplicity still eludes me.

	--Paul