If this is your first visit to the new VUE forums, you can login using the same username and password you currently use on VUE's website. If you need an account, please create one through VUE's website. If you have problems, please contact us via the contact form on http://vue.tufts.edu

I updated sourceforge with the lastest code as of 2/25, you had mentioned in your previous post you had interest in the layouts package and Anoop has done a lot of work on improving the layouts lately so I thought you may want to check out the very latest.

Hello,
again I have problems. I updated the VUE code and I ran the ant all. It is successful, but I get the following compilation errors:
- edu.tufts.vue.mbs.OpenCalaisAnalyzer (the package com.clearforest.* cannot be resolved)
- tufts.vue.LWIcon (PdfGraphics2D.HyperLinkKey cannot be resolved)
Can you help me to solve that problem?

We updated Itext in the latest release, so in your eclipse project you need to remove the lib itext-2.0.4.jar and add /lib/itext-2.1.4.jar, and we're using Open Calais for some analysis so you need to to add /lib/calais.jar to your build path in eclipse.

I need clarification about the policy and practices that we should follow in order to start committing new functionality to the VUE sourceforge project. It will be useful to us to read the open source license of VUE. We also have some concrete technical questions.

1) We have developed a functionality for loading XML documents in a concept/ content map view. The visualization is configured in an external for VUE XML document, which has to be selected from the local file system when an XML document is aimed to be loaded as a concept/ content map. I will prepare a document where is described the schema for visualization and implementation details and I will send it to you. We added new functionality in a new package in VUE code. Is it suitable to commit a new package? What are the practices you follow and recommend?

2) We have been working on exceeding the expressivity of the visualization schema document. Our aims are as follows:
- to visualize for particular nodes an extracted by Xpath expression content as rich text format notes (as a tool tip)
- to be possible to specify the shape of the nodes (oval, rectangle, ...) in the visualization schema document. Here we have problems with creating different Shape instances.
- to be possible to define modification rules for a particular XSD/DTD.
Example:
This is part of a DTD:
<!ELEMENT paragraph (sentence+)>
<!ELEMENT sentence (#PCDATA)>

According to it, it is not allowed to nest paragraphs in paragraphs.
In the visualization schema we define that we want to have separate nodes for the paragraphs and sentences available in XML documents validated by the DTD. We define that there should exist a link starting from a sentence node and ending in a paragraph node with a label “part_of”. It should not be possible to nest paragraph nodes and to modify the links in the concept/ content mapping view.
We have problems with implementation of that functionality. It is not clear to us which are the map modification events and which are the handler and listener classes. Is it better to create subclasses of LWNode i LWLink in which the modification constraints have to be defined? It will be very useful to us to receive some advice from you.
- to be possible to specify resources which have to be attached to map nodes; to be possible to configure an external program which can be used for loading/ opening/ editing these resources. Can you navigate us to the code which deals with these features?
- to be developed a GUI for definition of visualization schema according to an XSD/ DTD.

Our development effort will be decreased drastically if we get some advice from you for the location of the objects which we should use in order to implement the aimed functionality.

3) We have started extending VUE in order to comply with requirements specified for the LTfLL project. There is a project in sourceforge created for the LTfLL system (http://sourceforge.net/projects/ltfll/ ). We should commit our code there. I’m interested to read the open source license of the VUE project. I could not find it. Are there any clauses in it that forbid the committing of all the VUE code to the LTfLL sourceforge project?

It will be very useful to us if you can answer our questions and give us some advice.

We'd be happy to have you submit a new package, the way we've currently have our public and private sourcecode systems configured it'd be a bit difficult for us to take it at the moment. Anoop and I are going to work on this in May and provide a means for you to get regular updates from our repository as well as work on your own branch within that repository.

You can put the VUE code in your project on sf, here's our license also at the top of the source files:

Hi to Aneliya and everyone else--
I have had rather mixed results with the "layout" function. Half the time it puts things in more or less random order. Was it designed as a fun gadget, or to enhance usefulness? (See my post at https://vue-forums.uit.tufts.edu/posts/list/409.page). Above, you refer to "edu.tufts.vue.dataset". Is this a depot where I can get other layouts? How would I go about using them>