Re: [xwt-users] xvt and jikes and shoehorn
Jeff Buhrt <[email protected]> Fri, 10 Oct 2003 15:23:57 -0500
| Newsgroups | gmane.comp.java.xwt.users |
|---|---|
| Message-ID | <[email protected]> |
Hi. I am a relative newbie myself. I can answer a lot of these. See below. -Jeff Jeff Buhrt Achievement Focused Technology, Inc. [email protected] http://aftinc.net Nazario Irizarry wrote: > I spent the last few days playing with XVT to see if it was of > potential use on a project I am working on. I like what you guys are > doing and hope you guys can keep going. A few questions: > > - Where is the source for shoehorn? No clue. I assume also in CVS. > > - You seem to be working hard to implement native XVT but I think a > true applet based XVT would be great for many "real-world" > applications. Even if the applet was limited to RPC to the source > host that would be ok. Many times the reason to use applets on an > intranet is that the organization does not want to download things > into peoples desktops. In fact the project I am working on only wants > servlets - hence i have been looking for thin servlet technology. The idea is nothing has to be INSTALLED. The shoehorn checks the local cache for a copy though. Note that this method also makes it browser independent. You *can* run off a network 'drive' if you would like though... (see later). > > - I tried a make and discovered the attempt to build and use jikes > when all i wanted was the xvt.jar (make JVM). Why not use javac? I had someone helping me review XWT initially, he got hung up compiling at first. The idea is to *not* change the compiled code. That is why there are widgets vs built-in compiled functions, etc.. > > - It would be helpful for debug and development to be able to include > multiple .xwar files so that a target app could build on "standard" > widgets. Also would be cool to be able to not have to package things > up in a .xwar at all when running locally, ie, leave the .xwt template > files under development in a directory and pass the directory in > instead of the .xwar. > You can. For development using a directory vs xwar see http://www.xwt.org/reference.html, Appendix E. As for runtime you will be able to use multiple cached xwars AND the discussion is that even single files on a website would be allowed. > BTW I like the whole trap on read and trap on write concept. Very cool. > > Naz Irizarry > > > > _______________________________________________ > users mailing list > [email protected] > http://lists.xwt.org/listinfo/users >