First of all, thanks for your ideas. Please create RFE's so that the ideas don't get lost!
More inline.... >> - Integrating Jetty into the distribution so that playing with the web >> application becomes easier (Jetty is licensed under APL so there >> doesn't seem to be a problem.) >> I don't know Jetty, so don't expect me to do anything to bring this into the main distribution. Could you write up a patch or show me a demo of how it will look and we can look at it (please sign the contributors agreement if you want to submit your contribution. We cannot apply patches without the agreement in place: http://opensolaris.org/os/about/sun_contributor_agreement/ ) >> - Trying to find a better solution to setting the webapp parameters >> than "unpack the war file, edit web.xml and repack again" (or send the >> configuration to 2424). Maybe it could fall back to a Java system >> properties and environment variables. >> > > I like the sending of configuration, to avoid unpacking the war we've > preset the path to /etc/opengrok/configuration.xml . I plan to change > this to /var/opengrok/configuration.xml so we eventually get rid of it > and it will be just transparently generated by indexer to a known > location (/var/opengrok/log will have rolling logs). > What I'd prefer the most is a web configurator page (in head we have a > status page for developers with listing of config variables). > But there are ideas so the application will be configured remotely > (remote agent is in head, or jmx implementation can be finished too), > or just have an improved cli iface. > In the future the xml file will go away (from the users point of view), and you have to either use: a) the CLI b) the GUI c) a web config page. All of these methods will use JMX to talk to the opengrok server to get / set the configuration. The _only_ configuration property you as a user will have is to specify the URI to the server :) > >> - Some minor tweaks/fixes, for example I've noticed that in 0.7 the >> date shown next to a file in the webapp is the time it was indexed, >> not the time it was last modified. Not sure if this is still the case >> in HEAD. >> > There is a RFE for this. The problem is that to fix this we need to set the filemodification date on the file in the filesystem to the date of the trunk revision. This isn't impossible, but no one implemented it ;) >> What are your thoughts about adding Jetty? >> > > imho ... the web container is out of scope > on the other hand for development/testing purposes this can be neat, > needs investigation on how much effort and how big the size would be > and if it would be worthwhile. > I don't like to see clogged repository with useless stuff. > Right now I am testing the webapp from netbeans+tomcat and it works > quite ok for development/debugging/testing. It might make more sense > to adjust the netbeans project files to include web project by default. > Not sure how the rest of the folks do webapp changes ... Ideas anyone? ;) > We should really have a webapp project for the web pages!!!! It's a PITA right now to do modifications. We should also clean up the JSP files a lot... >> Regarding the Python analyzer, is anyone working on this already and >> if so, anything I can do to help? Otherwise, I will read up on JFlex >> and probably start off with an existing analyzer, maybe the Java or >> Lisp one. What would be the best way to test my changes during >> development without having to run the full stack -- is there a way to >> run the analyzer on a single input file and check its output? >> Create a junit test for it? > >> I might have a few more questions along the way. For example, I don't >> quite understand yet why the analyzers' Xref code is so verbose and >> how it fits together with syntax highlighting. What is the best place >> to ask little questions like that, this list or is there maybe an IRC >> channel? >> The syntax highlighting is done through CSS with the verbose output ;) Cheers, Trond
