.
FRDCSA | internal codebases | FWeb

FWeb

Jump to: Project Description | Capabilities

Project Description

The FRDCSA project website has unique needs and therefore we have written its own CMS, which provides users with a custom view of the FRDCSA content. Currently, it provides references to most focal areas of development: theory, projects, internal and external codebases, and packages.

Capabilities

• Increase the fweb decay halflife.
• Alter fweb to display what has been accomplished.
• /var/lib/myfrdcsa/codebases/internal/boss/scripts/stat.pl can be used in fweb.
• fweb should use a code difference metric to prevent building a digram for code that has undergone practically no change.
• Fix all the contact information in fweb and do a rebuild.
• Get rid of :Use of uninitialized value in concatenation (.) or string at /usr/local/share/perl/5.8.8/fweb/Project.pm line 268. : Use of uninitialized value in pattern match (m//) at /usr/local/share/perl/5.8.8/fweb/Project.pm line 269. problems
• fweb should be more stable.
• Fix fweb which just screwed up my webpage.
• Use the template system on fweb to generate better linked documentation.
• Setup a version sort for fweb, or in general a function to sort software, since I notice that roadnav-0.12.0 is coming in front of roadnav-0.4.0
• That is an encouraging start. Now we can probably build the fweb stuff again.
• fweb should include links to projects like "vampire" using markup
• seeker obviously incorporates some of critics abilities to remember what the user has already seen. In fact, that part of fweb that records sentences could be generalized to serve as the backend for clear, seeker, critic and fweb.
• When displayed with fweb.
• Later to make the fweb service better, we can have it realize just the words in a sentence, so that it is invariant to reformattings.
• Get timing information on fweb.
• Why is fweb running twice?
• Sometimes subtasking will not be a true dependency. E.g. we don't really need the above to be true to get the current task (fweb incidentally) to work, but it would be nice
• fweb capability listings (boss too) should be organized based on importance.
• fweb should be more differential.
• Create a publications section of fweb, from coauthor.
• Keep some database of solutions. I guess this is what architect does? But we need something more general. Example, if I can't program, and need help getting started, a good thing to do is to rebuild the fweb stuff.
• fweb should detect archaic system names (like Predator)
• fweb in dynamic content generation should do coloring dynamic to user.
• diamond demos should be accessible from fweb.
• Ultimately change fweb to a dynamic web application (ruby?)
• Replace fweb with a ruby on rails database interface...
• On fweb, that is.
• As well as the various fweb classes.
• Make sure fweb intropage has project statistics on it.
• Rewrite fweb using proper URL objects, so that all the conversions becomes easier.
• It would be at least possible, perhaps not desirable, to actually use fweb project pages to display output information - for instance, pse, could display public goals through fweb.
• Add a notes section to each fweb class
• fweb should have the ability to rebuild specific projects only
• To aid in debugging fweb, could add debug mode where it only does three of each project.
• Use DrJones to extract "how old" fweb stuff
• boss and fweb should use http://readyset.tigris.org/
• fweb can keep a database of which sentences were entered when for which documents.
• Add search this site with google to fweb.
• With fweb, be sure to sort projects by case-insensitive alphabetic order, add borders to wikilike name substitutions, and add coloration based on project activity or perhaps size.
• use the output of ls on /var/lib/myfrdcsa/sandbox and /var/lib/myfrdcsa/codebases/external and internal as an "overview" of the FRDCSA project on fweb.
• fweb must see ontowebber