xmlwiki-developers Mailing List for xmlWiki (Page 3)
Brought to you by:
elhugo
Menu
▾
▴
xmlwiki-developers — xmlWiki developers list
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(77) |
Nov
(48) |
Dec
(50) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(16) |
Feb
(10) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: naime <na...@st...> - 2001-12-06 14:56:55
|
Bola and Deb, The online site looks really good. There are several links that do not work yet. Is that correct? Maybe a menu option showing known problems would be good as well. Regards, Abe >===== Original Message From "Bolade Olaniyi" <bo...@ho...> ===== >There's an XMLWiki web site currently on http://24.60.157.224:85/index.htm >which integrates most of the artifacts and other information about the >project. > >Let's have your comments. > >Bola > > > >_________________________________________________________________ >Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > >_______________________________________________ >xmlWiki-developers mailing list >xml...@li... >https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers _______________________________________________ xmlWiki-developers mailing list xml...@li... https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers |
|
From: naime <na...@st...> - 2001-12-06 14:55:19
|
Jim, Here is the ORO info, from a previous email on the Transformer. In order to be able to compile this code, you should have ORO 1.1.0a added to your class path. Note that ORO does not provide a jar file. To download this beautiful piece of technology, please go to http://www.savarese.org/oro/software/OROMatcher1.1.html. We can move to the newer version by Jakarta in the next iteration. I do not want to take the risk of dealing with a new version at this point. Regards, Abe >===== Original Message From "Jim Kalafut" <ka...@ie...> ===== >Good job Radu. I got it to run on Windows, haven't tried it in linux yet. >One thing... the oro package you are using isn't from Jakarta, and I wasn't >even able to connect to the author's site. A google.com cached page had >something about custodianship being turned over to Apache. When I changed >the package reference to org.apache.... everything worked fine. Do we want >to go with the Apache version, which will probably be maintained and more >accessible? (Or, where can we get the oroinc package directly?) > >Regards, >Jim > > >_______________________________________________ >xmlWiki-developers mailing list >xml...@li... >https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers |
|
From: naime <na...@st...> - 2001-12-06 14:50:03
|
Bola and Deb, The online site looks really good. There are several links that do not work yet. Is that correct? Regards, Abe >===== Original Message From "Bolade Olaniyi" <bo...@ho...> ===== >There's an XMLWiki web site currently on http://24.60.157.224:85/index.htm >which integrates most of the artifacts and other information about the >project. > >Let's have your comments. > >Bola > > > >_________________________________________________________________ >Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > >_______________________________________________ >xmlWiki-developers mailing list >xml...@li... >https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers |
|
From: Bolade O. <bo...@ho...> - 2001-12-06 13:55:04
|
There's an XMLWiki web site currently on http://24.60.157.224:85/index.htm which integrates most of the artifacts and other information about the project. Let's have your comments. Bola _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
|
From: Jim K. <ka...@ie...> - 2001-12-06 13:08:24
|
Good job Radu. I got it to run on Windows, haven't tried it in linux yet. One thing... the oro package you are using isn't from Jakarta, and I wasn't even able to connect to the author's site. A google.com cached page had something about custodianship being turned over to Apache. When I changed the package reference to org.apache.... everything worked fine. Do we want to go with the Apache version, which will probably be maintained and more accessible? (Or, where can we get the oroinc package directly?) Regards, Jim |
|
From: Radu D. <rd...@ly...> - 2001-12-06 06:22:52
|
Jim, I finally finished the integration. Now our project has a main page where you can see the available pages,then one could edit,preview,browse and delete a page. I committed all sources in the CVS. Please get all the sources again and deploy them on your box.I hope that the deployment will be much easier. Be aware that web.xml changed. An example of working wiki page would be: ---- This is a text in the first paragraph. This is a text in the second paragraph. External link: [https://www-courses.cs.uiuc.edu/~cs327/] Internal link: [RUP] An excellent RUP website [http://doc.ic.tsu.ru/dox/analysis+design/rup/index.htm] ---- This is a text in the first paragraph. This is a text in the second paragraph. External link: [https://www-courses.cs.uiuc.edu/~cs327/] Internal link: [RUP] An excellent RUP website [http://doc.ic.tsu.ru/dox/analysis+design/rup/index.htm] another test [abe] --- After creating a page, you have to refresh the main page to see the new one. Of course, this is a basic framework that will be refactored.And in the next release, after we implement more wiki features, the main page will be a WIKI page. If you have any question, please let me know. Thank you. Radu PS. Could you guys figure out why the unit tests fail? On Wed, 5 Dec 2001 20:25:58 Jim Kalafut wrote: >I've made the necessary changes to the linux box and our Wiki now works on >it. The intent is that we could point the TA/grader to that site for a >little system demo. The address is the same as the Jabber but with the >xmlWiki path: http://24.178.71.65:8080/xmlWiki . I've also modified >build.xml so anyone can deploy the system on the linux box. It may not be >essential just for one demo, but I thought it would be a handy feature to >have in general. Just log into my system and copy over the CVS tree to your >directory. The same 'ant deploy' will now detect the OS and move things >around a little differently to get it to work. Lastly, do we want to put >anything else on that system for the demo? I guess it really doesn't offer >much over the sourceforge site for static pages. Once we finalize the >version, we should at least create a few nice xml pages and add them to the >database with meaningful names. The TAs can then pull those up to see how >our transformer is working... > >Later, >Jim > > > >_______________________________________________ >xmlWiki-developers mailing list >xml...@li... >https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers > |
|
From: naime <na...@st...> - 2001-12-06 05:39:09
|
First pass of the UML Diagrams. Reflects the code checked-in this evening. (You should download the new code and check out the navigation facities that have been added. A+ with lots of stars.) The file is in PostScritp format (so ghost script can read it) I will spend sometime analyzing the relationship diagram tomorrow. Regards, Abe |
|
From: Jim K. <ka...@ie...> - 2001-12-06 02:25:43
|
I've made the necessary changes to the linux box and our Wiki now works on it. The intent is that we could point the TA/grader to that site for a little system demo. The address is the same as the Jabber but with the xmlWiki path: http://24.178.71.65:8080/xmlWiki . I've also modified build.xml so anyone can deploy the system on the linux box. It may not be essential just for one demo, but I thought it would be a handy feature to have in general. Just log into my system and copy over the CVS tree to your directory. The same 'ant deploy' will now detect the OS and move things around a little differently to get it to work. Lastly, do we want to put anything else on that system for the demo? I guess it really doesn't offer much over the sourceforge site for static pages. Once we finalize the version, we should at least create a few nice xml pages and add them to the database with meaningful names. The TAs can then pull those up to see how our transformer is working... Later, Jim |
|
From: Jim K. <ka...@ie...> - 2001-12-05 21:45:55
|
I've added the tool setup input Arnaldo requested. It is integrated right into the document in a red font. I've decided that a CVS log appendix doesn't fit in well with this document and have instead provided a link to our SourceForge page. The graders can get a better idea how things are organized using the CVS viewer anyway. Regards, Jim Kalafut |
|
From: Arnaldo C. <ar...@mi...> - 2001-12-05 19:26:36
|
Hey, if anyone has already watched yesterday's lecture (though I know = that it's catch up time for many) He specifically references our group's plight at around 53 minutes, 30 = seconds into the lecture. Just fyi. |
|
From: naime <na...@st...> - 2001-12-04 22:48:05
|
Team, Find below two comments related to the deliverables. On UML diagram: The course staff wants some content that explains the diagram. Something like: a user requests a page, the web server instantiates the wikiPage object, which in turn calls the wikiDB ... A sequence diagram might also be extremely valuable. On Online index: Bola and Deb for HW6 I sent two emails to the team that was supposed to review our project, the two emails contained most of the links mentioned by Arnaldo. I still have those documents available. If you need a starting point please let me know and I will forward it to you. Arnaldo, I might need an extension until Thursday night to provide my feedback. :( Regards, Abe >===== Original Message From "Arnaldo Cavazos" <ar...@mi...> ===== >First, quick administrative decisions made: > -No meeting this Thursday. Instead, we'll meet on Sunday at 2PM CST to sign off on all project deliverables. > -Please have suggested changes to synopsis document and UML diagram by Wed. night Send them to the entire group so that people can disagree or concur if they want to. > -"Chat standard" - 'Away' in our chat room means "I'm working on something to do with our project, and the window to the chat room is in the background." 'Ext. Away' means "I'm not in the room right now." > >-->Project deliverables<-- >-Online index- > POCs: Deb and Bola > Description: A whole lot of our project is either online or getting there. This will be an index of links to different items (on the Wiki, on SourceForge, on the xmlwiki site, etc.) > Will include links to: release plan, iteration plans, estimates, source code, log of code versions, meeting minutes, actual meeting scripts, and of course a running version of the "first release version" of our actual Wiki. > Note: This means that if any of the UML diagram, synopsis document, >online index to... >-Synopsis Document- > POC: Arnaldo >-UML Diagram- > POC: Radu > >Let me know if I missed anything here. Almost there! >--Arnaldo |
|
From: HEISTAD,CHRIS (A-USA,ex2) <chr...@ag...> - 2001-12-04 20:57:08
|
Also: We're really working on one PC for distributed xp. Except this PC is not in a physically accessable place for one half of the pair. We had the problem that my pair wanted to see what we had done earlier, but couldn't because it was not finished and we could not check it in. The only solutions are bad: check in bad stuff, leave computer available (hacking threat), or else remember to always copy the source before quitting work. My pair had to wait for me to email the code to him and that is not efficient. -> -----Original Message----- -> From: Arnaldo Cavazos [mailto:ar...@mi...] -> Sent: Tuesday, December 04, 2001 2:51 PM -> To: xml...@li... -> Subject: Re: [xmlWiki-developers] meeting minutes from 3 Dec -> - project -> deliverables -> -> -> Chris, -> This is a really terrific analysis. I've had some of -> the exact same -> problems. I think that this is precisely the kind of stuff -> that Johnson -> will be interested to see. -> --Arnaldo -> ----- Original Message ----- -> From: "HEISTAD,CHRIS (A-USA,ex2)" <chr...@ag...> -> To: <xml...@li...> -> Sent: Tuesday, December 04, 2001 12:25 PM -> Subject: RE: [xmlWiki-developers] meeting minutes from 3 Dec -> - project -> deliverables -> -> -> > Of possible use in the summary: -> > -> > Please note I was really trying hard to find negative -> things. I had a -> really -> > good -> > experience with Hugo and everybody else I worked with. -> > -> > Things that made distributed xp hard for me. -> > -> > I can't gauge my pair. Normally I'd be in the office and talk with -> someone. -> > Take them -> > out for coffee and learn about their experience. Doing -> this over the phone -> > won't work. -> > I don't know the strengths and weaknesses of my teammates -> and my pair. -> > -> > It is hard to explain why you're frustrated over the -> phone. You can't -> gauge -> > how your -> > pair is going to react. Or if they are annoyed or not. -> > -> > The whole process kind of goes to hell when you get -> interrupted. I.e. -> > bathroom. -> > Laying down a phone just feels different than taking a -> walk in an office. -> > You feel -> > guilty, like someone is constantly waiting for you. And -> even if you have a -> > cordless, taking -> > it into the bathroom definently violates some protocol. -> > -> > Plus your wife(spouse) thinks you're not really -> > doing anything 'up there by yourself' and tends to interrupt. This -> wouldn't -> > happen if my -> > wife(spouse) knew someone else was physically in the -> house. Or out in -> public -> > people would -> > tend not to interrupt when two people are sitting together -> and obviously -> > working. But here -> > you're by yourself and nobody can really see that you are -> working with -> > someone else. -> > -> > The whole desktop sharing thing really bothered me. We constantly -> interupted -> > each other. -> > It would have been much simpler to hand the keyboard back -> and forth. Then -> > you would -> > know exactly who was driving. It can be very frustrating -> trying to move -> the -> > pointer -> > while someone else is trying to do the same. Even when you -> have a lock, -> its -> > a pain to -> > constantly relase the lock. In person you can see the -> hands before the -> keys -> > are hit. You -> > don't have this with a screen sharing program. -> > -> > It is really hard to learn something while in the -> distributed xp process. -> I -> > either found myself -> > wondering why my partner was doing something. And asking -> made me feel like -> I -> > was inhibiting -> > progress, again the impersonal phone. Or else I was -> driving with the pair -> > telling me -> > what to do. This isn't good either because I can't -> concentrate on what -> > exactly why the -> > pair is telling me to do something. -> > -> > It is a real pain to set up a call. In an office you can -> look over and see -> > that someone is -> > not busy. But with the phone, you call and maybe your pair -> is working on -> > something and can't -> > work immediately. Then you're supposed to call back. But -> you still don't -> > know if they're -> > ready. Definently the protocol should be that the busy -> pair has to call -> > back. -> > -> > Everything seems more blunt when working through the -> phone. Just like -> people -> > are more terse in -> > email, they seem more terse while working on the phone, -> but not as bad as -> > email. Seems like the bluntness goes: -> > -> > in person (least blunt) -> > phone -> > email -> > text chat -> > -> > Text chat does not really work for technical discussion. Technical -> > discussion needs elaboration not tersness. Nobody wants to -> type alot. And -> > the abbreviations are annoying. You never are sure what they mean. -> > -> > Its an effort to discuss ideas with teammates who are -> nonpairs. You have -> to -> > arrange it. -> > You just can't see they are not busy and walk up and start -> talking. It is -> > more of an -> > effort to communicate with team members in distributed xp. -> > -> > It seems that there is the drive to make oneself available -> too much. -> Because -> > there is the idea -> > that all you need is time and access to the internet. But -> it is probably -> not -> > appropriate to think that you can pair program at -> grandma's house over -> > Thanksgiving. Even though grandma has a 1Ghz pc and a -> cable modem. Pair -> > programming is best done at regular scheduled intervals. I -> > had the opposite problem. We had people over for -> thanksgiving and I was -> > tempted too much to -> > try to set something up. It just didn't work. We had -> people over and I was -> > pre-occupied. Its better to just forget about it. -> > -> > There is also the temptation to read documentation or -> something while your -> > pair is writing code or doing something else. The pair -> that is hosting the -> > shared session can't see what you are doing anyhow. This -> kind of destroys -> > the whole motiviation for pair programming. So unless -> there is some kind -> of -> > technology to share both desktops or lock the screens -> together in some -> type -> > of bidirectional way, you really don't know if you're pair -> programming or -> > not. -> > -> > Having a phone headset as opposed to using the handset is -> mandatory for -> any -> > distributed XP'r. -> > I used a handset and it really made my neck sore. No the -> speaker phone -> > doesn't work well either. Don't even try a cellphone -> without a headset. My -> > pair had to set the cellphone down when typing. It -> inhibits the work flow, -> > you can't talk and type at the same time. And when you are -> typing you get -> > the best ideas. But we did the best with what we had and -> did make alot of -> > progress. It just wasn't as good as it could have been. -> > -> > Since you're using a phone you really cannot listen to music as it -> > interferes with the phone and annoys your pair. This is a -> big deal for me. -> > Phone resolution is much lower than cd resolution. So even -> if your pair -> > likes the same type of music, it just doesn't work. -> > -> > -> > -> > -> > _______________________________________________ -> > xmlWiki-developers mailing list -> > xml...@li... -> > https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers -> -> -> _______________________________________________ -> xmlWiki-developers mailing list -> xml...@li... -> https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers -> |
|
From: Arnaldo C. <ar...@mi...> - 2001-12-04 20:50:29
|
Chris,
This is a really terrific analysis. I've had some of the exact same
problems. I think that this is precisely the kind of stuff that Johnson
will be interested to see.
--Arnaldo
----- Original Message -----
From: "HEISTAD,CHRIS (A-USA,ex2)" <chr...@ag...>
To: <xml...@li...>
Sent: Tuesday, December 04, 2001 12:25 PM
Subject: RE: [xmlWiki-developers] meeting minutes from 3 Dec - project
deliverables
> Of possible use in the summary:
>
> Please note I was really trying hard to find negative things. I had a
really
> good
> experience with Hugo and everybody else I worked with.
>
> Things that made distributed xp hard for me.
>
> I can't gauge my pair. Normally I'd be in the office and talk with
someone.
> Take them
> out for coffee and learn about their experience. Doing this over the phone
> won't work.
> I don't know the strengths and weaknesses of my teammates and my pair.
>
> It is hard to explain why you're frustrated over the phone. You can't
gauge
> how your
> pair is going to react. Or if they are annoyed or not.
>
> The whole process kind of goes to hell when you get interrupted. I.e.
> bathroom.
> Laying down a phone just feels different than taking a walk in an office.
> You feel
> guilty, like someone is constantly waiting for you. And even if you have a
> cordless, taking
> it into the bathroom definently violates some protocol.
>
> Plus your wife(spouse) thinks you're not really
> doing anything 'up there by yourself' and tends to interrupt. This
wouldn't
> happen if my
> wife(spouse) knew someone else was physically in the house. Or out in
public
> people would
> tend not to interrupt when two people are sitting together and obviously
> working. But here
> you're by yourself and nobody can really see that you are working with
> someone else.
>
> The whole desktop sharing thing really bothered me. We constantly
interupted
> each other.
> It would have been much simpler to hand the keyboard back and forth. Then
> you would
> know exactly who was driving. It can be very frustrating trying to move
the
> pointer
> while someone else is trying to do the same. Even when you have a lock,
its
> a pain to
> constantly relase the lock. In person you can see the hands before the
keys
> are hit. You
> don't have this with a screen sharing program.
>
> It is really hard to learn something while in the distributed xp process.
I
> either found myself
> wondering why my partner was doing something. And asking made me feel like
I
> was inhibiting
> progress, again the impersonal phone. Or else I was driving with the pair
> telling me
> what to do. This isn't good either because I can't concentrate on what
> exactly why the
> pair is telling me to do something.
>
> It is a real pain to set up a call. In an office you can look over and see
> that someone is
> not busy. But with the phone, you call and maybe your pair is working on
> something and can't
> work immediately. Then you're supposed to call back. But you still don't
> know if they're
> ready. Definently the protocol should be that the busy pair has to call
> back.
>
> Everything seems more blunt when working through the phone. Just like
people
> are more terse in
> email, they seem more terse while working on the phone, but not as bad as
> email. Seems like the bluntness goes:
>
> in person (least blunt)
> phone
> email
> text chat
>
> Text chat does not really work for technical discussion. Technical
> discussion needs elaboration not tersness. Nobody wants to type alot. And
> the abbreviations are annoying. You never are sure what they mean.
>
> Its an effort to discuss ideas with teammates who are nonpairs. You have
to
> arrange it.
> You just can't see they are not busy and walk up and start talking. It is
> more of an
> effort to communicate with team members in distributed xp.
>
> It seems that there is the drive to make oneself available too much.
Because
> there is the idea
> that all you need is time and access to the internet. But it is probably
not
> appropriate to think that you can pair program at grandma's house over
> Thanksgiving. Even though grandma has a 1Ghz pc and a cable modem. Pair
> programming is best done at regular scheduled intervals. I
> had the opposite problem. We had people over for thanksgiving and I was
> tempted too much to
> try to set something up. It just didn't work. We had people over and I was
> pre-occupied. Its better to just forget about it.
>
> There is also the temptation to read documentation or something while your
> pair is writing code or doing something else. The pair that is hosting the
> shared session can't see what you are doing anyhow. This kind of destroys
> the whole motiviation for pair programming. So unless there is some kind
of
> technology to share both desktops or lock the screens together in some
type
> of bidirectional way, you really don't know if you're pair programming or
> not.
>
> Having a phone headset as opposed to using the handset is mandatory for
any
> distributed XP'r.
> I used a handset and it really made my neck sore. No the speaker phone
> doesn't work well either. Don't even try a cellphone without a headset. My
> pair had to set the cellphone down when typing. It inhibits the work flow,
> you can't talk and type at the same time. And when you are typing you get
> the best ideas. But we did the best with what we had and did make alot of
> progress. It just wasn't as good as it could have been.
>
> Since you're using a phone you really cannot listen to music as it
> interferes with the phone and annoys your pair. This is a big deal for me.
> Phone resolution is much lower than cd resolution. So even if your pair
> likes the same type of music, it just doesn't work.
>
>
>
>
> _______________________________________________
> xmlWiki-developers mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers
|
|
From: HEISTAD,CHRIS (A-USA,ex2) <chr...@ag...> - 2001-12-04 19:25:58
|
Of possible use in the summary: Please note I was really trying hard to find negative things. I had a really good experience with Hugo and everybody else I worked with. Things that made distributed xp hard for me. I can't gauge my pair. Normally I'd be in the office and talk with someone. Take them out for coffee and learn about their experience. Doing this over the phone won't work. I don't know the strengths and weaknesses of my teammates and my pair. It is hard to explain why you're frustrated over the phone. You can't gauge how your pair is going to react. Or if they are annoyed or not. The whole process kind of goes to hell when you get interrupted. I.e. bathroom. Laying down a phone just feels different than taking a walk in an office. You feel guilty, like someone is constantly waiting for you. And even if you have a cordless, taking it into the bathroom definently violates some protocol. Plus your wife(spouse) thinks you're not really doing anything 'up there by yourself' and tends to interrupt. This wouldn't happen if my wife(spouse) knew someone else was physically in the house. Or out in public people would tend not to interrupt when two people are sitting together and obviously working. But here you're by yourself and nobody can really see that you are working with someone else. The whole desktop sharing thing really bothered me. We constantly interupted each other. It would have been much simpler to hand the keyboard back and forth. Then you would know exactly who was driving. It can be very frustrating trying to move the pointer while someone else is trying to do the same. Even when you have a lock, its a pain to constantly relase the lock. In person you can see the hands before the keys are hit. You don't have this with a screen sharing program. It is really hard to learn something while in the distributed xp process. I either found myself wondering why my partner was doing something. And asking made me feel like I was inhibiting progress, again the impersonal phone. Or else I was driving with the pair telling me what to do. This isn't good either because I can't concentrate on what exactly why the pair is telling me to do something. It is a real pain to set up a call. In an office you can look over and see that someone is not busy. But with the phone, you call and maybe your pair is working on something and can't work immediately. Then you're supposed to call back. But you still don't know if they're ready. Definently the protocol should be that the busy pair has to call back. Everything seems more blunt when working through the phone. Just like people are more terse in email, they seem more terse while working on the phone, but not as bad as email. Seems like the bluntness goes: in person (least blunt) phone email text chat Text chat does not really work for technical discussion. Technical discussion needs elaboration not tersness. Nobody wants to type alot. And the abbreviations are annoying. You never are sure what they mean. Its an effort to discuss ideas with teammates who are nonpairs. You have to arrange it. You just can't see they are not busy and walk up and start talking. It is more of an effort to communicate with team members in distributed xp. It seems that there is the drive to make oneself available too much. Because there is the idea that all you need is time and access to the internet. But it is probably not appropriate to think that you can pair program at grandma's house over Thanksgiving. Even though grandma has a 1Ghz pc and a cable modem. Pair programming is best done at regular scheduled intervals. I had the opposite problem. We had people over for thanksgiving and I was tempted too much to try to set something up. It just didn't work. We had people over and I was pre-occupied. Its better to just forget about it. There is also the temptation to read documentation or something while your pair is writing code or doing something else. The pair that is hosting the shared session can't see what you are doing anyhow. This kind of destroys the whole motiviation for pair programming. So unless there is some kind of technology to share both desktops or lock the screens together in some type of bidirectional way, you really don't know if you're pair programming or not. Having a phone headset as opposed to using the handset is mandatory for any distributed XP'r. I used a handset and it really made my neck sore. No the speaker phone doesn't work well either. Don't even try a cellphone without a headset. My pair had to set the cellphone down when typing. It inhibits the work flow, you can't talk and type at the same time. And when you are typing you get the best ideas. But we did the best with what we had and did make alot of progress. It just wasn't as good as it could have been. Since you're using a phone you really cannot listen to music as it interferes with the phone and annoys your pair. This is a big deal for me. Phone resolution is much lower than cd resolution. So even if your pair likes the same type of music, it just doesn't work. |
|
From: Arnaldo C. <ar...@mi...> - 2001-12-04 18:50:07
|
Way to go Radu and Abe! My personal take is that any extra time should go into polishing, rather than adding to, the deliverables that we already plan to submit. Deb and Bola, perhaps, may be able to use some help with the online index. Plus, Radu's got his hands full (at least I would) with the final and the UML diagram and his wife expecting to deliver any day now! ----- Original Message ----- From: "naime" <na...@st...> To: <xml...@li...> Sent: Monday, December 03, 2001 10:29 PM Subject: [xmlWiki-developers] Edit Status > Team, > Daddy Radu has some exciting news. No the baby is not born yet :-). But the > other baby, the Edit Story, works for a simple test case, after integration. > Therefore, we have a basic Edit User Story completed. Ahead of calendar > schedule, but very behind the time effort to complete the iteration. We might > enhance the wiki2XMLTransformer class, since we have some extra time. > Warmest regards, > Radu and Abe > > > > _______________________________________________ > xmlWiki-developers mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlwiki-developers |
|
From: Arnaldo C. <ar...@mi...> - 2001-12-04 18:40:05
|
First, quick administrative decisions made:
-No meeting this Thursday. Instead, we'll meet on Sunday at 2PM CST =
to sign off on all project deliverables.
-Please have suggested changes to synopsis document and UML diagram =
by Wed. night Send them to the entire group so that people can disagree =
or concur if they want to.
-"Chat standard" - 'Away' in our chat room means "I'm working on =
something to do with our project, and the window to the chat room is in =
the background." 'Ext. Away' means "I'm not in the room right now."
-->Project deliverables<--
-Online index-
POCs: Deb and Bola
Description: A whole lot of our project is either online or getting =
there. This will be an index of links to different items (on the Wiki, =
on SourceForge, on the xmlwiki site, etc.)
Will include links to: release plan, iteration plans, estimates, =
source code, log of code versions, meeting minutes, actual meeting =
scripts, and of course a running version of the "first release version" =
of our actual Wiki.
Note: This means that if any of the UML diagram, synopsis document, =
=20
online index to...
-Synopsis Document-
POC: Arnaldo
-UML Diagram-
POC: Radu
Let me know if I missed anything here. Almost there!
--Arnaldo
|
|
From: naime <na...@st...> - 2001-12-04 05:29:53
|
Team, Daddy Radu has some exciting news. No the baby is not born yet :-). But the other baby, the Edit Story, works for a simple test case, after integration. Therefore, we have a basic Edit User Story completed. Ahead of calendar schedule, but very behind the time effort to complete the iteration. We might enhance the wiki2XMLTransformer class, since we have some extra time. Warmest regards, Radu and Abe |
|
From: Arnaldo C. <ar...@mi...> - 2001-12-03 23:56:47
|
Tonight's topics are rather intuitive. :) -What will our final deliverables be? (A suggested list: working = version of 1st release, UML diagram, synopsis document, meeting minutes. = Peer reviews we'll handle on our own.) -How close are we to having the final deliverables ready? (I know that a = lot of work has been done since Thursday. Where are we exactly? How = close is the code to being integrated? Is the Edit story done?) -Thursday will hopefully be just a "wrap-up" meeting. --Arnaldo |
|
From: Radu D. <rd...@ly...> - 2001-12-03 07:54:49
|
Hi, gang. I attach the latest java sources for our xmlWiki project. I and Abe worked to integrate the Edit story. There are still some issues we can discuss tomorrow in out meeting. I could not check in the files in CVS. That is why I send the java files as a ZIP archive. Somebody please try to check them in before tomorrow meeting. If you have problems accessing the sources, please let me know. Thank you. Radu |
|
From: naime <na...@st...> - 2001-12-02 00:55:44
|
Team, Find attached a first version of the Wiki2XMLTransformer and XML2WikiTransformer. I am also attaching a Tester class and a test file. The code currently compiles and passes the unit test. In order to minimize size, I have zipped the files using WinZip 8.0 (for an evaluation copy, please go to http://www.winzip.com/ddchomea.htm). After integration the same source will be in CVS, so if you cannot unzip the file, please hold your horses, you will get it pretty soon. In order to be able to compile this code, you should have ORO 1.1.0a added to your class path. Note that ORO does not provide a jar file. To download this beautiful piece of technology, please go to http://www.savarese.org/oro/software/OROMatcher1.1.html. The two classes (Wiki2XMLTransformer and XML2WikiTransformer ) provide a basic framework to support the Wiki syntax. Currently, the set of wiki features is limited to Sections, Paragraphs and Links. Only external and internal links are supported, ISBN links are not supported yet, but can be easily added on. Radu and I plan to integrate the two classes on Sunday Dec 02, 2001. Abe will work mostly in the Pacific Coast morning. Abe plans to get started around 8:00 AM PST done by 12:00 PM PST. Abe won=92t be available during the Pacific Coast afternoon. Radu is still working on his schedule. After integration work, we should meet Andrew=92s requirement on providing a basic Edit Functionality, not as robust or intelligent as I would like, however time is precious these days. In our view, we should refactor this code with the current set of features, in order to expand code flexibility and robustness before expanding the syntax. Especially by encapsulating some of the logic to reduce complexity. Warmest regards, Abe and Radu |
|
From: Arnaldo C. <ar...@mi...> - 2001-11-30 00:18:37
|
First, last time we covered:
-Our approach to the "home page" is the simple one - just have a main =
page, that for all practical purposes, is no different than any other =
page.
-As in most Wikis, every page name will be unique.
-How will the URL identify whether or not the Wiki is in Edit mode? We =
went with Radu's solution for now: "/wikiURL/edit?pagename"
Tonight's topic:
-Where are we on the Edit Story? Who's planning to do what?
I really think this should be about a 10 minute meeting where people who =
want to can stick around and discuss different issues afterwards for an =
indefinite amount of time.
--Arnaldo
|
|
From: Radu D. <rd...@ly...> - 2001-11-27 06:07:35
|
Hi, guys. The attachement is the latest version for the PreviewPage. Now , in PreviewPage, we have the whole functionality: Create, Save, Retrieve,Preview and Browse. Since I am having problems merging this page in CVS, please let me know what are the steps to merge a file(maybe I am doing something wrong, though for the other pages it worked). Thanks. Radu |
|
From: Arnaldo C. <ar...@mi...> - 2001-11-27 00:05:49
|
All, =20
Hope everyone had a terrific Turkey week.
Items for tonight:
-coming up with a graphical framework for a wikipage(with some kind =
of links, a list of available wiki pages etc.)
-otherwise, just a typical "stand-up meeting" - reviewing where we =
are on the Edit story relative to our last meeting
...should be a quick one tonight, unless there's something big I'm =
forgetting.
--Arnaldo
|
|
From: Radu D. <rd...@ly...> - 2001-11-26 20:23:01
|
Hi, gang. This is list of changes I made to the sources since our last meeting: - added a unit test for the XML->HTML transformation( for now, it uses the full path to open a file and not the servlet context to get the real path from a virtual path) - fixed the BrowsePage so that it works with the XML->HTML transformation - fixed some stuff in the PreviewPage - change the web.xml so that the address for the BrowsePage is: localhost/xmlWiki/BrowsePage?pageName=foo - fixed the xsl and xml files. I had a problem where commiting the source in CVS: the message for the new version is empty and I could not merge in PreviewPage.java. I will try again in the evening before our meeting. My bullet for today meeting: - come up with a graphical framework for a wikipage(with some kind of links, a list of available wiki pages etc.) If you have any questions, please let me know. Thanks. Radu |
|
From: <xm...@ne...> - 2001-11-23 16:19:22
|
two steps 1 remove jaxp.jar and parse.jar from the $TOMCAT_HOME/lib directory. 2 Install the following jars into the $TOMCAT_HOME/lib directory: jaxp.jar (version 1.1), crimson.jar and xalan.jar. -H -- __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ |
15 messages has been excluded from this view by a project administrator.
