From jeff at bioinformatics.org Sun Oct 1 00:41:18 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] clarification on Piper vs. .NET Message-ID: <39D6C06E.DEF1D169@bioinformatics.org> A number of people have told me that .NET is another name for Microsoft's future product line, the entire product line. If that is the case, how could Piper ever hope to compete? Piper, after all, is not an operating system, or a word processor, etc. What is Piper trying to achieve? When I say that Piper is a "GNU alternative to .NET", I mean that it is a Free Software alternative to Microsoft's recent adoption of the concept of distributing application components. That's pretty much it. Piper cannot possibly replace Microsoft's entire product line. Also, note that I use the word "alternative" and NOT "equivalent" or "copy". Piper may be used instead of Microsoft's distributed application system, but Piper is NOT a technical or free equivalent. The concept may be the same, but Piper and .NET are taking some very different approaches. If you want to compare Piper with something concrete (as concrete as Micosoft vaporware can ever be), you can compare it to BizTalk. It's probably something like BizTalk mated with AVS and Gnutella. But, since BizTalk forms an integral part of .NET, we can also say that Piper compares to .NET...in some ways. And, please note that we don't want to say that Piper will not be usable until it is a Microsoft Killer. We should get it running ASAP, and then add features from there. Let's try to get Piper running before BizTalk is, which, from recent announcements**, will be early next year. ** http://news.cnet.com/news/0-1003-200-2871745.html?tag=st.ne.1002.srchres.ni Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From jarl at casema.net Sun Oct 1 19:59:35 2000 From: jarl at casema.net (jarl van katwijk) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Status BL Message-ID: <39D7CFE7.FA6F27C3@casema.net> Hi Pipers, Here's another BL status update. I was hoping to bring even better news as what I'm about to summarise, but I think whats left still will be a big step toward some usable code. --- DONE list: 1. Finished C to C++ conversion of BL core. It's running, loading it's plugins, executing the threads, etc. 2. Done C to C++ conversion of the GMS UI. I didn't want to port this at 1st, but testing\debugging the core wont be possible without the old Gms user interface, so I ported this one too and named it "BL_admin". It's compiling and starting, but does not run very long because all the Corba stuff has not yet been done. 3. Wrote a basic Corba server in the BL core using the OMNIorb libraries. Tested it with a Python script, which works fine. 4. Started the BL <-> PL code. --- TODO list: 1. Implement BL <-> BL_admin (former GMS UI) Corba functionality 2. Complete DL <-> BL Corba interface 3. Complete BL <-> PL interface(s) 4. Test & bug fix it all :( My current proffesional project will end october the 4th, after which I still dont have any official followup project, so hopefully I'll have a week extra spare time to spend into this TODO list. bye, jarl From jeff at bioinformatics.org Sun Oct 1 17:05:11 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] The Gnutella paradox Message-ID: <39D7A707.1955D414@bioinformatics.org> This is informative, considering we're thinking about a P2P network like Gnutella for sharing node and network descriptions: ``Mr. Adar hasn't written off Gnutella. He believes a more successful and scalable system is possible but would require trade-offs such as decreased privacy and a few centralized network machines. Future versions of Gnutella could also include a system "default" that forces all users to share, much like Napster. Otherwise, Mr. Adar believes, Gnutella won't be able to hold up under the strain if it is flooded by Napster-like traffic.'' http://www.herring.com/insider/2000/1002/resources/tech-off-salon-gnutella100200-p3.html (It gets interesting only at Part 3.) Jeff From faassen at vet.uu.nl Sun Oct 1 22:31:58 2000 From: faassen at vet.uu.nl (Martijn Faassen) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Narval? Message-ID: <20001002043158.A22823@vet.uu.nl> Hi there, I'm a complete newbie to any of this, but have you guys noticed that there are a lot of synergies between this project and Narval (to which I'm also a complete newbie). I mean, GUI-based programming, XML backend, Python based code, and so on. I mailed a message to the Narval folks with about the same contents. Perhaps working together, if this isn't already happening, would be a good idea. Narval info at: http://www.logilab.org/ Regards, Martijn From jeff at bioinformatics.org Sun Oct 1 22:49:48 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Narval? References: <20001002043158.A22823@vet.uu.nl> Message-ID: <39D7F7CC.539A97BC@bioinformatics.org> Hi Martijn. Thanks for the link to Narval. I was not aware of it. There seem to be many similarities between Narval and Piper, for instance, the use of existing resources on the Internet and a way to graphically connect these resources. However, it seems Narval is primarily an agent system, meaning there is a "software agent" that goes out on the Internet looking for things of interest to the user. Piper, on the other hand, is primarily a data flow system, meaning the user knows what s/he wants, connects the appropriate resources, and then starts the flow of data. It is possible that Piper can use agents in the future, but that is well into the future, since we have some very difficult tasks still to accomplish. I don't know if Narval would like to collaborate on this, but it seems they have their goal already very well defined. Cheers. Jeff Martijn Faassen wrote: > > I'm a complete newbie to any of this, but have you guys noticed that > there are a lot of synergies between this project and Narval (to which > I'm also a complete newbie). I mean, GUI-based programming, XML backend, > Python based code, and so on. I mailed a message to the Narval folks > with about the same contents. Perhaps working together, if this isn't > already happening, would be a good idea. > > Narval info at: > > http://www.logilab.org/ -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From faassen at vet.uu.nl Sun Oct 1 23:32:03 2000 From: faassen at vet.uu.nl (Martijn Faassen) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Narval? In-Reply-To: <39D7F7CC.539A97BC@bioinformatics.org> References: <20001002043158.A22823@vet.uu.nl> <39D7F7CC.539A97BC@bioinformatics.org> Message-ID: <20001002053203.A22877@vet.uu.nl> J.W. Bizzaro wrote: > Thanks for the link to Narval. I was not aware of it. I just was browsing and ran into the two almost simultaneously (I'd seen a few references to Piper before). > There seem to be many similarities between Narval and Piper, for instance, the > use of existing resources on the Internet and a way to graphically connect > these resources. > > However, it seems Narval is primarily an agent system, meaning there is a > "software agent" that goes out on the Internet looking for things of interest > to the user. Piper, on the other hand, is primarily a data flow system, > meaning the user knows what s/he wants, connects the appropriate resources, > and then starts the flow of data. Right, though I don't know enough of either system, I know that there are differences. I don't really know what either are. :) While the focus of Narval seems to be more towards software agent usage than data-transformation, it does seem to be (from a glance through the manual) that a user connects resources in Narval as well. Perhaps take a look at the screenshots. I don't think there's any autonomous agent in Narval that gets transmitted onto the net; it's a 'personal agent' in the sense that it's an assistent, not in the sense that it's a knowbot type thing. To quote from the Narval manual: """ In clear terms, Narval is an original computing engine that can execute user defined tasks. To do this, Narval behaves as a conductor piloting the existing softwares and computer devices in order to perform each of the necessary elementary actions. Therefore, for instance, to download the weather forecast every morning (as the user asked to), Narval will run the Internet connection, get the web site address from the bookmarks, download the correct web page located at this address, save it on the disk and make it available from the browser home page. Thus, Narval philosophy is not to replace the existent but to integrate all its functionalities to ease their execution and their sequencing while hiding their own complexity. """ > It is possible that Piper can use agents in the future, but that is well into > the future, since we have some very difficult tasks still to accomplish. I > don't know if Narval would like to collaborate on this, but it seems they have > their goal already very well defined. The Narval project looks like a pretty new project though. And though there may be a difference in focus, look at the technological similarities -- connecting resources into programs or recipies, use of XML as a backend. Use of Python. Use of a GUI to do this kind of thing. I think there are synergies both in the focus (which is I think still fairly close to Piper), and definitely the technology. Regards, Martijn From jeff at bioinformatics.org Sun Oct 1 23:49:16 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Narval? References: <20001002043158.A22823@vet.uu.nl> <39D7F7CC.539A97BC@bioinformatics.org> <20001002053203.A22877@vet.uu.nl> Message-ID: <39D805BC.2D491929@bioinformatics.org> Martijn Faassen wrote: > > The Narval project looks like a pretty new project though. And though > there may be a difference in focus, look at the technological > similarities -- connecting resources into programs or recipies, use of > XML as a backend. Use of Python. Use of a GUI to do this kind of thing. > I think there are synergies both in the focus (which is I think still > fairly close to Piper), and definitely the technology. I'll be lazy and ask you something I could find out myself: Has Narval developed their infrastructure yet? The reason I ask is because Piper can be used as the infrastructure for other systems. We started an API standards group for just such a thing: DNP-API mailing list http://bioinformatics.org/mailman/listinfo/dnp-api Maybe they'd like to join. (Anyone else?) Who is the person you have been in contact with at Narval? Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From mfp at students.cs.mu.OZ.AU Mon Oct 2 04:25:32 2000 From: mfp at students.cs.mu.OZ.AU (Matthew PATTISON) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] The Gnutella paradox Message-ID: <20001002192532.A23216@holly.cs.mu.OZ.AU> Reply-To: What about the system used by napster, mojonation www.mojohackers.org or iMesh www.imesh.com. I think they're much more scalable than gnutella. Especially Mojonation and iMesh look interesting, although Mojonation may be overkill for what you need, and iMesh is not free software (patent pending). Mojonation is very ambitious though, and written in Python, so there may be some synchronicity. Sorry, I should introduce myself. My name is Matt Pattison, I'm about to graduate as a Software Engineer in about 4 weeks from Melbourne University, Australia. I've just been writing (in a team, for my final year project) a program doing distributed robot simulation in Java, Voyager (transparent Corba & RMI - very cool), Java3D (the buggiest API I've ever used) and a little C++ for collision detection. We're currently 50K lines of code and rising. I'm very interested in distributed computing, linux/free software, and high level languages. I used to be a big Python fan, until I discovered Ruby www.ruby-lang.org. I think this project looks very interesting, and I'd love to get involved (although probably not in the next 4 weeks, for now I'll just lurk). Matt Pattison ----- Original Message ----- From: J.W. Bizzaro To: Sent: Monday, October 02, 2000 7:05 AM Subject: [Pipet Devel] The Gnutella paradox > This is informative, considering we're thinking about a P2P network like > Gnutella for sharing node and network descriptions: > > ``Mr. Adar hasn't written off Gnutella. He believes a more successful and > scalable system is possible but would require trade-offs such as decreased > privacy and a few centralized network machines. Future versions of Gnutella > could also include a system "default" that forces all users to share, much > like Napster. Otherwise, Mr. Adar believes, Gnutella won't be able to hold up > under the strain if it is flooded by Napster-like traffic.'' > > http://www.herring.com/insider/2000/1002/resources/tech-off-salon-gnutella10 0200-p3.html > (It gets interesting only at Part 3.) > > Jeff > > _______________________________________________ > pipet-devel maillist - pipet-devel@bioinformatics.org > http://bioinformatics.org/mailman/listinfo/pipet-devel > > From faassen at vet.uu.nl Mon Oct 2 14:24:40 2000 From: faassen at vet.uu.nl (Martijn Faassen) Date: Fri Feb 10 19:20:34 2006 Subject: [Pipet Devel] Narval? In-Reply-To: <39D805BC.2D491929@bioinformatics.org> References: <20001002043158.A22823@vet.uu.nl> <39D7F7CC.539A97BC@bioinformatics.org> <20001002053203.A22877@vet.uu.nl> <39D805BC.2D491929@bioinformatics.org> Message-ID: <20001002202440.A23311@vet.uu.nl> J.W. Bizzaro wrote: > Martijn Faassen wrote: > > > > The Narval project looks like a pretty new project though. And though > > there may be a difference in focus, look at the technological > > similarities -- connecting resources into programs or recipies, use of > > XML as a backend. Use of Python. Use of a GUI to do this kind of thing. > > I think there are synergies both in the focus (which is I think still > > fairly close to Piper), and definitely the technology. > > I'll be lazy and ask you something I could find out myself: Has Narval > developed their infrastructure yet? I know _nothing_ whatsoever about Narval, so I don't know. :) I just got a reply back from the Narval people (or person, not sure), and he hadn't heard of Piper yet either, and was interested to hear about it (he said he'll get to you when he's studied your system some more). He also pointed out some difference he's observed, so I'll quote from him (with my comments): > * Piper is meant to be a graphical shell + distributed programming. > Narval is meant to be of software agent / personnal assistant. In a sense I think Piper can perform personal assistant style roles, though, right? The Unix pipe idea is a bit like this; you string the components together to do something you like -- I think Narval also has this idea. > * Piper uses FlowCharts. Narval uses something close to Petri Nets. Don't know what Petri Nets are, so I can't comment on this one. > * Piper uses XML as a storage format. Narval uses XML for everything. >From what I've seen in the Narval manual, XPath and XSLT are used, I'm not quite sure how yet though. http://www.digitome.com/pyxie.html > * Piper processes streams. Narval processes XML. Interesting -- XML can represent some structured information better than simple streams, though simple streams can be processed a lot faster. And you can stream XML in various ways; Pyxie may be interesting in that respect to you people too (Pyxie can transform XML to a format that allows standard Unix commandline tools and such to be used with XML). http://www.digitome.com/pyxie.html > The reason I ask is because Piper can be used as the infrastructure for other > systems. We started an API standards group for just such a thing: > > DNP-API mailing list > http://bioinformatics.org/mailman/listinfo/dnp-api > > Maybe they'd like to join. (Anyone else?) > > Who is the person you have been in contact with at Narval? Nicolas Chauvat Anyway, my only goal in all this is to just point each other's existence to each other. To my completely inexpert eyes there seem to be quite a few possible synergies between the projects. Anyway, since I accomplished my goal now I'll step back and see what happens. :) Regards, Martijn From jeff at bioinformatics.org Tue Oct 3 19:18:51 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Infolets - An Open Source Alternative to .NET and Jini Message-ID: <39DA695B.185740FF@bioinformatics.org> ``Cameron Laird and Kathryn Soraiz have pointed me to Piper. Piper has taken the Unix concept of pipes and is attempting to bring it to the Internet at large. Instead of the pipe symbol "|", Piper has developed a simple graphical representation of component relationships that users can easily manipulate. Piper uses simple lines and arrows to connect different components together and then allows users to change and add to these connections at will. Piper is significantly richer than the traditional world of pipes. The goal of Piper is to be a complete XML component language that allows users to construct any program they need from a set of components located anywhere on the Internet. Piper is still in the early stages of development, but it is a project that bears watching.'' http://www.infolets.com/970539595/ Jeff From mangalam at home.com Wed Oct 4 15:24:52 2000 From: mangalam at home.com (Harry Mangalam) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] CORBA-approved, GPL'ed, Python ORB from ATT References: <39DA695B.185740FF@bioinformatics.org> Message-ID: <39DB8404.6DEFB7D@home.com> This is dated yesterday; of interest to this group? http://www.uk.research.att.com/omniORB/omniORBpy/index.html -- Cheers, Harry (the infrequently helpful lurker...) Harry J Mangalam -- (949) 856 2847 (v&f) -- hjm@ncgr.org || mangalam@home.com From jeff at bioinformatics.org Wed Oct 4 17:03:08 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] CORBA-approved, GPL'ed, Python ORB from ATT References: <39DA695B.185740FF@bioinformatics.org> <39DB8404.6DEFB7D@home.com> Message-ID: <39DB9B0C.845A1D5C@bioinformatics.org> Harry Mangalam wrote: > > This is dated yesterday; of interest to this group? > > http://www.uk.research.att.com/omniORB/omniORBpy/index.html We've been using ominORB and omniORBpy with Piper for several months already, but thanks for thinking of us :-) Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From mangalam at home.com Thu Oct 5 10:43:59 2000 From: mangalam at home.com (Harry Mangalam) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] CORBA-approved, GPL'ed, Python ORB from ATT References: <39DA695B.185740FF@bioinformatics.org> <39DB8404.6DEFB7D@home.com> <39DB9B0C.845A1D5C@bioinformatics.org> Message-ID: <39DC93AF.8E19282F@home.com> Blush... Sigh.... I'll go back to lurking... :) hjm "J.W. Bizzaro" wrote: > > Harry Mangalam wrote: > > > > This is dated yesterday; of interest to this group? > > > > http://www.uk.research.att.com/omniORB/omniORBpy/index.html > > We've been using ominORB and omniORBpy with Piper for several months already, > but thanks for thinking of us :-) > > Jeff > -- > J.W. Bizzaro jeff@bioinformatics.org > Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff > "Injustice anywhere is a threat to justice everywhere." > -- Martin Luther King, Jr. > -- > > _______________________________________________ > pipet-devel maillist - pipet-devel@bioinformatics.org > http://bioinformatics.org/mailman/listinfo/pipet-devel -- Cheers, Harry Harry J Mangalam -- (949) 856 2847 (v&f) -- hjm@ncgr.org || mangalam@home.com From SCoffman at CBSINC.com Thu Oct 5 13:36:23 2000 From: SCoffman at CBSINC.com (COFFMAN Steven) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help Message-ID: Hello, I'd like to help out if possible. I'm a commiter on Apache's XML project (FOP mostly), so I know Java, PDF, XML, XSL:T, XSL:FO and other fun acronyms. I don't know python, but I've been meaning to learn it anyway. It's been a while since I used C++. I wrote java stuff using CORBA when the first java bindings were available, but never in C++, and way before GNOME. I'd like to help in whatever way, but I have a an idea for taking two XML files (and DTDs) and using them figure out what a generic XSL:T file would be to translate between the two, so you can edit one and XSL:T it to the other. I've got some scripts that do a half-way decent job of that now. I dunno if that would be helpful to Piper, but I thought I'd offer. So basically "I'm a clueless newbie that should be able to figure things out reasonably fast". :) What would you like me to do? -Steve P.S. The graphical pipe concept is the most fascinating part to me. The distributed network stuff is cool too, but not as exciting. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://bioinformatics.org/pipermail/pipet-devel/attachments/20001005/17163c88/attachment.html From jeff at bioinformatics.org Thu Oct 5 19:13:59 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help References: Message-ID: <39DD0B37.165CB624@bioinformatics.org> Hey Steve. Thanks for writing, and thanks for offering to help. > COFFMAN Steven wrote: > > I'd like to help out if possible. I'm a commiter on Apache's XML project > (FOP mostly), so I know Java, PDF, XML, XSL:T, XSL:FO and other fun > acronyms. I don't know python, but I've been meaning to learn it anyway. > It's been a while since I used C++. I wrote java stuff using CORBA when the > first java bindings were available, but never in C++, and way before GNOME. We'll, we REEEEEEALY need some help in the Definitions Layer of Piper. That's the layer in the Build-Time Subsystem that turns the user-described networks (the "view") into a network description (the "model") that the Run-Time Subsystem can understand. It is in Python, but it uses CORBA and XML more heavily than any other part of Piper. If you're interested, I can have Brad get in touch with you. > I'd like to help in whatever way, but I have a an idea for taking two XML > files (and DTDs) and using them figure out what a generic XSL:T file would > be to translate between the two, so you can edit one and XSL:T it to the > other. I've got some scripts that do a half-way decent job of that now. I > dunno if that would be helpful to Piper, but I thought I'd offer. Actually, XML translations, in fact all kinds of data translation facilities, will be important to Piper. Remember that we are tying together pre-existing programs that were not made to work with each other. For many of these, there may be an intermediate conversion or filtering step. But, those will be nodes or plugins that can be made later. > So basically "I'm a clueless newbie that should be able to figure things out > reasonably fast". :) What would you like me to do? If you can help with the DL, you'd save the day. Python is really easy to pick up, trust me. Otherwise, Jean-Marc and Jarl, if you need Steve's help more than I do, let me know. > P.S. The graphical pipe concept is the most fascinating part to me. The > distributed network stuff is cool too, but not as exciting. Hear that Jarl? My stuff is more exciting than yours :-P Seriously, the DL works closely with all of the user interfaces (UIL), so you'll get to work on graphical piping and on other UI's as well. Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From jarl at casema.net Fri Oct 6 18:22:57 2000 From: jarl at casema.net (Jarl van Katwijk) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help References: <39DD0B37.165CB624@bioinformatics.org> Message-ID: <37FBCBC1.270ED6A3@casema.net> > > If you can help with the DL, you'd save the day. Python is really easy to > pick up, trust me. > > Otherwise, Jean-Marc and Jarl, if you need Steve's help more than I do, let me > know. I think Corba and the BL & PL api sets are a bit out of Steve's interests :) If he will find anything nice to do he'll definitly should have a look at the DL. > > > > P.S. The graphical pipe concept is the most fascinating part to me. The > > distributed network stuff is cool too, but not as exciting. > > Hear that Jarl? My stuff is more exciting than yours :-P hehe, shut up Jeff :) jarl From jarl at casema.net Fri Oct 6 18:23:44 2000 From: jarl at casema.net (Jarl van Katwijk) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] CORBA-approved, GPL'ed, Python ORB from ATT References: <39DA695B.185740FF@bioinformatics.org> <39DB8404.6DEFB7D@home.com> <39DB9B0C.845A1D5C@bioinformatics.org> <39DC93AF.8E19282F@home.com> Message-ID: <37FBCBF0.12EC7969@casema.net> Harry Mangalam wrote: > Blush... Sigh.... I'll go back to lurking... :) > hjm Thnx Harry.. new version of omniORB also. From SCoffman at CBSINC.com Fri Oct 6 14:57:50 2000 From: SCoffman at CBSINC.com (COFFMAN Steven) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help Message-ID: -----Original Message----- From: Jarl van Katwijk [mailto:jarl@casema.net] Sent: Wednesday, October 06, 1999 6:23 PM To: pipet-devel@bioinformatics.org Subject: Re: [Pipet Devel] Offer to help > > If you can help with the DL, you'd save the day. Python is really easy to > pick up, trust me. > > Otherwise, Jean-Marc and Jarl, if you need Steve's help more than I do, let me > know. I think Corba and the BL & PL api sets are a bit out of Steve's interests :) If he will find anything nice to do he'll definitly should have a look at the DL. > > > > P.S. The graphical pipe concept is the most fascinating part to me. The > > distributed network stuff is cool too, but not as exciting. > > Hear that Jarl? My stuff is more exciting than yours :-P hehe, shut up Jeff :) jarl _______________________________________________ pipet-devel maillist - pipet-devel@bioinformatics.org http://bioinformatics.org/mailman/listinfo/pipet-devel From SCoffman at CBSINC.com Fri Oct 6 16:25:11 2000 From: SCoffman at CBSINC.com (COFFMAN Steven) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help Message-ID: Sorry for the blank message. I blame jet lag. I got into python last night, and I'm getting it pretty quick. Are there any python-CORBA documents lying about? I found pygnome GUI articles. What's the info for anonymous checkout from the CVS server? The last item on the DL todo (easier to write XML), looks like a good entry point into piper and python (the auto-"XSL" for now). On a related note, have you ever worked with Conglomerate (www.conglomerate.org)? It's a pretty slick XML editor. -Steve -----Original Message----- From: Jarl van Katwijk [mailto:jarl@casema.net] Sent: Wednesday, October 06, 2000 6:23 PM To: pipet-devel@bioinformatics.org Subject: Re: [Pipet Devel] Offer to help > > If you can help with the DL, you'd save the day. Python is really easy to > pick up, trust me. > > Otherwise, Jean-Marc and Jarl, if you need Steve's help more than I do, let me > know. I think Corba and the BL & PL api sets are a bit out of Steve's interests :) If he will find anything nice to do he'll definitly should have a look at the DL. > > > > P.S. The graphical pipe concept is the most fascinating part to me. The > > distributed network stuff is cool too, but not as exciting. > > Hear that Jarl? My stuff is more exciting than yours :-P hehe, shut up Jeff :) jarl _______________________________________________ pipet-devel maillist - pipet-devel@bioinformatics.org http://bioinformatics.org/mailman/listinfo/pipet-devel From jean-marc.valin at hermes.usherb.ca Fri Oct 6 21:07:32 2000 From: jean-marc.valin at hermes.usherb.ca (jean-marc.valin@hermes.usherb.ca) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help In-Reply-To: References: Message-ID: <200010070107.VAA16628@hermes.usherb.ca> > What's the info for anonymous checkout from the CVS server? > The last item on the DL todo (easier to write XML), looks like a good entry > point into piper and python (the auto-"XSL" for now). On a related note, > have you ever worked with Conglomerate (www.conglomerate.org)? It's a > pretty > slick XML editor. I'm not sure the "easier to write XML" is still pertinent with the changes we have done about a month ago. Even if it still is, it might be too soon for that. ...Or maybe I just didn't understand what Brad meant by that. Brad, what do you think? As for Piper's CVS, I have to say that the last time I tried, I could get access to the anonymous CVS - Jeff, could you create a piper account for me (and give me CVS write access)? JEan-Marc From jeff at bioinformatics.org Fri Oct 6 21:25:59 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help References: <200010070107.VAA16628@hermes.usherb.ca> Message-ID: <39DE7BA7.F3F315CE@bioinformatics.org> jean-marc.valin@hermes.usherb.ca wrote: > > As for Piper's CVS, I have to say that the last time I tried, I could get > access to the anonymous CVS - Jeff, could you create a piper account for me (and > give me CVS write access)? Sure thing. I'll contact both you and Steve about this off of the list. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From jeff at bioinformatics.org Fri Oct 6 22:30:13 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help References: Message-ID: <39DE8AB5.6DFC3384@bioinformatics.org> COFFMAN Steven wrote: > > I got into python last night, and I'm getting it pretty quick. Are there any > python-CORBA documents lying about? I found pygnome GUI articles. We are using omniORB and its Python bindings. There is some documentation on their Web site: http://www.uk.research.att.com/omniORB/omniORBpy/ But I am not aware of any published articles on Python-CORBA. Anyone else? Here is the main omniORB site: http://www.uk.research.att.com/omniORB/ > On a related note, have you ever worked with Conglomerate > (www.conglomerate.org)? It's a pretty slick XML editor. We've mentioned Conglomerate a couple times before and have considered its use in documentation (SGML or DocBook) editing. But, more recently, we have been considering Wiki and LaTeX/LyX for documentation. I'm not sure we all agree on one or the other at this point. Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From raphael.bossek at solutions4linux.de Sat Oct 7 01:19:44 2000 From: raphael.bossek at solutions4linux.de (Raphael Bossek) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Would like to join the project... Message-ID: <20001007071943.A25977@mars> hi, I'm 23 years yound and a official Debian GNU/Linux developer. Have professional expirience in OOAD C++ programming and would like to contribute to PIPER and package PIPER for Debian GNU/Linux of course :) PIPER is a interesting project for me, because it uses techniques that could be interesting in component based software development in the future. I'm intet to use PIPER at work for our future Linux embedded products in conjuction with our OO software design. We are also looking forward to use CORBA as a common way to offer our software interfaces for the outside world. So we will support windows and other unices too in the future and are looking for a forward-looking concept, and PIPER seams to be one! Expirience in C++, PERL. Familiar with CORBA. Learning Pyhton at the moment. No JAVA knowleadge! -- Raphael Bossek [ICQ #40047651] From jeff at bioinformatics.org Sat Oct 7 02:36:26 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Would like to join the project... References: <20001007071943.A25977@mars> Message-ID: <39DEC46A.BF903C98@bioinformatics.org> Hi Raphael. It's great to hear that you'd like to help. Perhaps, with your experience in C++ and CORBA, you'd prefer to work on the Run-Time Subsystem, which includes the Brokering (Generalized Messaging System) and Processing (Overflow) Layers. But if you really want to try some Python, you could work on the Build-Time Subsystem, which includes User Interface and Definition Layers (Loci). In any case, we use (or will use) omniORB CORBA everywhere. It'd also be nice to get some help with packaging. Right now, we don't have someone to make DEB's or RPM's. For anyone interested in helping with Piper and getting CVS commit permission, please register with The Open Lab at Bioinformatics.org. We use a modified version of SourceForge, and the way project contributions are handled is through this system. Once you register (click on "Join The Open Lab" at Bioinformatics.org), contact me, and I can add you as a contributor. You will then get a shell account, CVS access, etc. (If you haven't introduced yourself to this list, please do so first.) As I've mentioned before, a good first step is to download the source code (see the "Download" section on the website), try to compile it (you may need help with that), run it, and take a gander at the source. It's all there (what has been committed anyway), free and open for inspection. If something catches your fancy, ask about it on the list. But, please note that we are still merging 3 code bases: Overflow, GMS and Loci. So, it doesn't do everything we want it to yet. Jarl mentioned that he will have the Brokering Layer operational and communicating with the Processing Layer in a few weeks. After that and some improvements in both the UI Layer and the communication between Build-Time and Run-Time Subsystems, the project should really take off. There are some TODO lists linked to the CVS respository from the "Focus & Goals" section on the website. I'm not sure if they are all up-to-date. If not, I ask the other contributors to update them and/or post a request for help on this list. Cheers. Jeff Raphael Bossek wrote: > > I'm 23 years yound and a official Debian GNU/Linux developer. Have > professional expirience in OOAD C++ programming and would like to > contribute to PIPER and package PIPER for Debian GNU/Linux of course :) > > PIPER is a interesting project for me, because it uses techniques > that could be interesting in component based software development in > the future. > > I'm intet to use PIPER at work for our future Linux embedded products > in conjuction with our OO software design. We are also looking forward > to use CORBA as a common way to offer our software interfaces for the > outside world. So we will support windows and other unices too in the > future and are looking for a forward-looking concept, and PIPER seams > to be one! > > Expirience in C++, PERL. Familiar with CORBA. Learning Pyhton at the > moment. No JAVA knowleadge! -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From chapmanb at arches.uga.edu Mon Oct 9 16:45:46 2000 From: chapmanb at arches.uga.edu (Brad Chapman) Date: Fri Feb 10 19:20:35 2006 Subject: [Pipet Devel] Offer to help In-Reply-To: Message-ID: <200010092045.QAA87552@archa10.cc.uga.edu> Steve wrote: > I got into python last night, and I'm getting it pretty quick. Are > there any python-CORBA documents lying about? There aren't really any all inclusive docs/tutorials for learning CORBA from python but here is how I learned to do it: 1. I didn't know anything about CORBA, so I read a C++ book to get a good foundation for the basic ideas of how it worked. Henning and Vinoski is by far the best -- here's a slashdot review of it: http://slashdot.org/books/99/07/12/1236220.shtml 2. I then took a look at the official mapping, which is pretty readable and a good reference for later: http://cgi.omg.org/cgi-bin/doc?ptc/00-04-08 Be warned though, the only python ORB implementation that currently follows this is omniORBpy (which is used in Piper, of course :-), so you will find some deviations in other ORBs. 3. Then I started playing around with Fnorb (http://www.fnorb.org). This is an almost all python ORB, and has a nice booklet that walks you through a hello world example. 4. Finally, I started working with omniORBpy ( http://www.uk.research.att.com/omniORB/omniORBpy/) and playing around with the examples. There is some documentation for omniORBpy, but last I checked it wasn't very helpful from the "getting started" perspective. However, playing with the examples really helped me get into this a lot. >From there, I think you should be ready to go :-). At least for me, I struggled a bit at first until I suddenly had a moment of clarity where I started to understand what was going on with CORBA, and from there I have had no major problems (especially with python, because it is sooooooo nice for CORBA!). I do not recommend trying to learn by reading the gnome documentation for C programming with CORBA. The C mapping is pretty hard to follow, especially at first, and since CORBA is very OO all the way, python is a better place to start, IMHO. Steve wrote: > > The last item on the DL todo (easier to write XML), looks like a > > good entry point into piper and python (the auto-"XSL" for now). Jean-Marc wrote: > I'm not sure the "easier to write XML" is still pertinent with the > changes we have done about a month ago. Even if it still is, it might be too > soon for that. > ....Or maybe I just didn't understand what Brad meant by that. Brad, > what do you think? Well, the items on the DL to do were generally structured by order of priority and timeframe (at least how it seemed to me at the time :-). In general, I'm not exactly positive if the "easier to write XML" is exactly relevant right now, because that is something that was meant to get into place once a working system was in place. Jean-Marc and I did write a nice perl script to do the work on converting the old Overflow C++ declaration syntax into C++ automatically (including support for comments :-), so I'm not sure if more work needs to be done here right now... Sorry, not to be too discouraging on this! It is definately important, but will probably come into play later down the line. Looking again at the list, I think the most important thing is connecting the DL with the BL, being worked on by Jarl. I got a garbled ICQ message form Jarl yesterday which suggested he was having some luck in this area, so IMO, this is probably the best area to work on, since you will see some results right away (which is always nice). I have already written the skeleton code in the DL for communicating with the BL, but this will probably need some tweaks and error fixes once the BL is up and running with a CORBA server. So, if I were you, I would go after this area first. I can definately be more specific about things, if you want... Brad From SCoffman at CBSINC.com Wed Oct 11 12:59:28 2000 From: SCoffman at CBSINC.com (COFFMAN Steven) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] getting piper built. RPM, deb, etc. Message-ID: A couple of the prerequisites for piper have C++ code. Since RedHat 7.0 uses gcc 2.96, it's best to recompile these rather than installing binaries, as there's some symbol mangling possible, I hear. I found src.rpm's for everything piper needs, except for the omniORB. Would it be useful to provide locations/links or mirrors for those files in src.rpm form so all architectures, versions, and whatnot of RPM based linux distributions are supported? If it's not a waste of time, I can provide that. I noticed that PyXML 0.5.1 and 4Suite 0.9 (which contains 4DOM 0.10 strangely) conflict, but not in the way that the piper INSTALL say they do. The conflict is over __init__.py and __init__.pyc. Should I be worried that no other files were mentioned as conflicting (at least by the RPM install)? For omniORB, I was rather surprised when I did "make export" that it installed into the current directory. /home/gears/junk/deleteme/omni/lib is not where I'd like it. Where's the standard place for it? I contacted the omniORB folks to see if they would like me to make RPMs for it (there are .debs already). Even if they say yes, I was kind of thinking it might be a little premature to build piper RPMs, although I can do this at some point. What do you think? -Steve From jeff at bioinformatics.org Wed Oct 11 16:42:39 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] getting piper built. RPM, deb, etc. References: Message-ID: <39E4D0BF.CA6C0C3@bioinformatics.org> COFFMAN Steven wrote: > > A couple of the prerequisites for piper have C++ code. Since RedHat 7.0 uses > gcc 2.96, it's best to recompile these rather than installing binaries, as > there's some symbol mangling possible, I hear. I heard that as well. > I found src.rpm's for everything piper needs, except for the omniORB. Would > it be useful to provide locations/links or mirrors for those files in > src.rpm form so all architectures, versions, and whatnot of RPM based linux > distributions are supported? If it's not a waste of time, I can provide > that. I managed to find the src.rpm's myself, since I use RPM's, and I was going to list put the URL's in the INSTALL file. But, you're welcomed to do it if you want to :-) We can keep mirrors of the dependencies locally as well, at The Open Lab FTP site. > I noticed that PyXML 0.5.1 and 4Suite 0.9 (which contains 4DOM 0.10 > strangely) conflict, but not in the way that the piper INSTALL say they do. > The conflict is over __init__.py and __init__.pyc. Should I be worried that > no other files were mentioned as conflicting (at least by the RPM install)? That's a good question for Brad. > For omniORB, I was rather surprised when I did "make export" that it > installed into the current directory. /home/gears/junk/deleteme/omni/lib is > not where I'd like it. Where's the standard place for it? I suppose you can put it just about anywhere (I put it in /opt, but some may prefer /usr/local), providing you set the environment variables accordingly: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/opt/omniORB_300/lib/i586_linux_2.0_glibc2.1 export PATH=$PATH:/usr/opt/omniORB_300/bin/i586_linux_2.0_glibc2.1 export PYTHONPATH=$PYTHONPATH:/usr/opt/omniORB_300/lib/python:/usr/opt/omniORB_300/lib/i586_linux_2.0_glibc2.1 > I contacted the > omniORB folks to see if they would like me to make RPMs for it (there are > .debs already). It'd be nice to have those. I suppose no-one ever volunteered to make them for omniORB. > Even if they say yes, I was kind of thinking it might be a little premature > to build piper RPMs, although I can do this at some point. What do you > think? It is a little premature to build RPM's for Piper. Right now, GMS (will be the Brokering Layer) is not in the piper module, although Jarl is working on it. I'd say, give us a few more weeks before considering packaging Piper. But, thanks again for offering. It will be great to have them :-) Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. -- From jarl at casema.net Thu Oct 12 02:11:43 2000 From: jarl at casema.net (jarl van katwijk) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] getting piper built. RPM, deb, etc. References: Message-ID: <39E5561F.A22F88E7@casema.net> > Hi Steven, > > I found src.rpm's for everything piper needs, except for the omniORB. Would > it be useful to provide locations/links or mirrors for those files in > src.rpm form so all architectures, versions, and whatnot of RPM based linux > distributions are supported? If it's not a waste of time, I can provide > that. that would be very nice. > > For omniORB, I was rather surprised when I did "make export" that it > installed into the current directory. /home/gears/junk/deleteme/omni/lib is > not where I'd like it. Where's the standard place for it? I contacted the > omniORB folks to see if they would like me to make RPMs for it (there are > .debs already). OMNIorb is pretty hard to install nicely.. after you compiled it the binairies will be placed ./bin/{platform} directory. I have placed the contents of this in /usr/local, > > Even if they say yes, I was kind of thinking it might be a little premature > to build piper RPMs, although I can do this at some point. What do you > think? It is premature, because there still is no working piper code yet, but if you could already do some preparation work. We'll soon have a piper pilot and than it is nice to have all the packaging already done. thnx & bye, jarl > > > -Steve > > _______________________________________________ > pipet-devel maillist - pipet-devel@bioinformatics.org > http://bioinformatics.org/mailman/listinfo/pipet-devel -- http://sunsite.auc.dk/gms From chapmanb at arches.uga.edu Wed Oct 11 17:41:04 2000 From: chapmanb at arches.uga.edu (Brad Chapman) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] getting piper built. RPM, deb, etc. In-Reply-To: <39E4D0BF.CA6C0C3@bioinformatics.org> Message-ID: <200010112141.RAA68554@archa12.cc.uga.edu> Steve wrote: > > I noticed that PyXML 0.5.1 and 4Suite 0.9 (which contains 4DOM 0.10 > > strangely) conflict, but not in the way that the piper INSTALL say they do. > > The conflict is over __init__.py and __init__.pyc. Should I be worried that > > no other files were mentioned as conflicting (at least by the RPM install)? Jeff wrote: > That's a good question for Brad. Well, I've got a long and a short answer for you. The short answer is: Yes, python XML libraries are a mess right now. But, you don't have to worry about it at all because I removed all dependencies for python XML processing libraries from Piper. Jean-Marc and I extended the XML processing in Overflow, which uses libxml, and then I moved all of the code in the DL to use this XML processing through python wrappers around Overflow C++ code. The INSTALL file probably needs updating to reflect this. The longer answer is: If you ever want to get XML processing in python back into Piper you will be faced with a bit of a mess in the python XML world. As you correctly noted, 4suite is now packaging 4DOM, 4XSLT and 4Xpath (you can guess what all those do from the names :-) together in one bundle (along with some other stuff), so 4DOM alone is now non-existant. However, the most recent PyXML versions (0.6.1 is the most recent, I believe) also ship with the 4DOM library. I'm not sure at all about the versioning differences between the two. To make it even more confusing, python2.0 will also ship with XML processing libraries, including SAX and a new mini-DOM API. So anyways, that's the situation. I can't specifically say anything about your conflict problem with rpms unless you can give more info, because there are __init__.p[y|yc]s in every directory of python code that acts as a module. I hope eventually the XML situation in python will be cleaner -- there are a lot of hard working open-source folks helping with it so once people find time hopefully the conflicts/confusions will begin to resolve themselves here. Brad From jeff at bioinformatics.org Sun Oct 15 08:46:46 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] Compendium: An alternative to .Net, 10/13/00 Message-ID: <39E9A736.AA3FBDD1@bioinformatics.org> There's a mention of Piper at NetworkWorldFusion. (I didn't send this in, honest! ;-)) ------------------------------------------------------------------ Sure, Microsoft wants to turn the Internet into .Net. But there are other proposals to turn the Internet into the world's largest middleware layer. Piper is an effort to develop ways to turn 'Net services and applications into objects, which can be connected through something as simple as drawing lines between them on a client-side GUI. Only the graphical representation of an object resides on a local workstation. Compute-intensive programs and large data sets can reside remotely on high-performance, high-capacity computers. Joining nodes across the Internet can also be used to form world-wide collaboratives ... and provide an almost limitless collection of objects for the user. They've already got some software and documentation for you to download and play with. ------------------------------------------------------------------ http://www.nwfusion.com/columnists/compendium.html?nf Jeff From Alexandre.Fayolle at logilab.fr Thu Oct 19 09:50:27 2000 From: Alexandre.Fayolle at logilab.fr (Alexandre Fayolle) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] Piper and Narval Message-ID: Hi there. My name's Alexandre, and I'm working on the Narval project. There are currently four of us working at full time on Narval, and we should be releasing Narval-1.0rc1 within a few days. Martijn Faassen sent us an email a couple of weeks ago telling us about Piper, and I subscribed to the Piper mailing list shortly afterwards. However, it seems that I missed your discussion on Piper and Narval. I wished to clarify a few points. J.W. Bizzaro seemed to think that Narval was an internet Agent (http://bioinformatics.org/pipermail/pipet-devel/2000-October/001054.html). This is not quite true. Narval _is_ an agent system, but it is not Yet Another Internet Agent, as Martijn Faassen pointed out in his reply. Narval is a personal assistant agent, which means that it focuses on performing tasks. Right now these tasks have to be described manually (by writing recipes), but we intend to implement planning (that is describing a goal and letting Narval sort everything out) in a future version. In order to achieve tasks, Narval executes actions, which can be provided by some external software, provided a wrapper is written. This wrapper is made of two parts: an XML prototype which specifies the inputs and outputs of the action, and a python function which implements the call. The prototype looks like Piper's loci, though the syntax is different, and the python function can act as a proxy to some external ressource (marshalling/unmarshalling of the arguments and doing the actual external call using whatever protocole is available), or implements the action by itself. One of the points you discussed was how the user interacts with Narval. The answer is 'it depends'. A graphical frontend aimed towards recipe programming exists, but this is by no way the only way: right now recipes can listen on network ports (and thus communicate using any standard protocol such as HTTP) or read emails, and we intend to provide facilities for voice communication, with a microphone or a voice modem. There are two main ways of using Narval: the first one is setting it up with a set of recipes to run as a daemon on a server, and then connect to Narval when you need it. The second one is launching it on a per need basis, perhaps write a quick recipe to automate a task and lauch that recipe. This second way is, AFAIU, closer to what you want to do with Piper, but we do not put as much emphasis on visualization as you do. Major differences between Piper and Narval, as far as we've seen, are the following: * Piper seems to put a huge emphasis on distributed objects with corba. Narval can use corba (and DCOM, etc...), but can do otherwise; * the transitions in Narval's recipes can be used to control which part of the recipes are evaluated, and also give some parallelism and synchronisation primitives (this is nothing new, it's only Petri nets semantics); * there has been a lot of effort put in Narval so that the kernel would be able to 'understand' what it is doing, especially when things go wrong (i.e. when an action fails), so that it can report asynchronously to the user or take corrective measures alone; * XML is used everywhere in Narval, which means that is is very easy to serialize the state of the kernel and to restore it in some other place (incidentally, this means that Narval could also be used as a 'knowbot'). Of course this comparison is biased, since I know the Narval project very well, and only know of Piper what can be understood by reading carefully the white papers at http://www.bioinformatics.org/piper/documentation/index.html (which are getting old), so please bear with me if I misunderstood things about your project. I'll be glad to answer any questions you have about Narval and to share experiences with you, so that we could discuss further what both projects can bring to one another. -- Alexandre Fayolle http://www.logilab.com - "Mais o? est donc Ornicar ?" - LOGILAB, Paris (France). From jeff at bioinformatics.org Tue Oct 31 20:04:53 2000 From: jeff at bioinformatics.org (J.W. Bizzaro) Date: Fri Feb 10 19:20:36 2006 Subject: [Pipet Devel] progress Message-ID: <39FF6C35.2DA2340@bioinformatics.org> All quiet on the western front. Although we haven't posted any messages in the last couple weeks, Jarl and I have been making slow progress. Jarl has been working on the BL, getting the original user interface to work using C++ and CORBA. This will help us track the communication between Internet-distributed instances of Piper. I helped Jarl to commit the new code to the Piper module. Anyone with a shell account can check it out, but it compiles separately from the Piper stuff (go into the BL directory). We would appreciate any comments on the new BL code at this time. If you do not have a shell account, and would like get the code, let me know and I can make a tarball. Anonymous CVS won't be working for a couple more weeks. I also have some changes to the Pied/Piper user interface that have yet to be committed. It would be nice if we could get a functional BL and the new Pied/Piper into CVS at about the same time. So, things are still progressing. Anyone wishing to help should try to get Piper installed and running, and contact us about any problems, suggestions, or ideas that they are willing to help with. Cheers. Jeff -- J.W. Bizzaro jeff@bioinformatics.org Director, Bioinformatics.org: The Open Lab http://bioinformatics.org/~jeff "Injustice anywhere is a threat to justice everywhere." -- Martin Luther King, Jr. --