Re: [vqwiki-dev] Current Status, Task Requests and Project Direction
Status: Abandoned
Brought to you by:
mteodori
From: Andreas S. <st...@gm...> - 2006-06-08 22:33:45
|
Hello Martijn GraphViz is a command line tool available on Windows, Mac OS and Linux. It's the easiest way I know to get Graph's from dependencies ;-) So since it's not java, I don't think it's something to add into the repository. Cheers Andreas. Martijn van der Kleijn wrote: >Andreas, > >Looks like an interesting tool... we can certainly "trial run" it? :-) >GraphViz isn't a kind of tool we can put in the repository I assume? > >Gr. Martijn >----- >Project Lead for the VQWiki Open Source project > >----- Original Message ----- >From: "Andreas Studer" <st...@gm...> >To: "A mailing list for the developers of VQWiki." ><ver...@li...> >Sent: Wednesday, June 07, 2006 6:47 PM >Subject: Re: [vqwiki-dev] Current Status, Task Requests and Project >Direction > > > > >>Hello Martijn >> >>As for the point UML documentation in classes, I prefer UMLGraph for that >>http://www.spinellis.gr/sw/umlgraph/ >>(declarative drawing of UML Diagrams) >> >>Advantage: >>- We don't use MDA here, so this will document our work while we coding. >>- can use JavaDoc tags for dependencies and documentation of the >>dependencies (in fact, the tool is a Doclet) >>- Can be generated in a ant (or maven) task on the fly (canon, dia, fig, >>gd, gd2, gif, hpgl, jpg, mif, mp, pcl, pic, png, ps, ps2, svg, svgz, >>vrml, vtx, wbmp). >>- Can generate multiple diagram views. >>- Can be integrated in eclipse ;-) >> >>Disadvantage: >>- you need GraphViz installed for it. >>- you can't control the positions of the classes and the routing of the >>dependencies (GraphViz will do that for you) >> >>What do the other think about that? >> >>Cheers >> >>Andreas >> >> >>Martijn van der Kleijn wrote: >> >> >> >>>Hi Gentlemen, >>> >>>Three things: current status of 3.0, how you can help and direction of the >>>project >>> >>>One word of warning... compiling is broken and VERY broken at that... just >>>read on ;-) >>> >>>1) Current Status; >>> >>>- Everything has been moved to org.vqwiki and the file and db packages >>>have >>>been moved to a org.vqwiki.persistency.file and org.vqwiki.persistency.db >>>structure. >>>- File structure layout has also significantly changed and as such I have >>>been revamping the build.xml file. I'm still not happy with the file >>>layout >>>and I'd like your input on it. >>>- All readme's etc have been moved deeper into the structure, into a >>>./src/resources/doc directory >>>- Only two readme-like files remain in the root: README_FIRST.txt and >>>CHANGELOG.txt... see the files to give you an idea of what they should be >>>in >>>my opinion >>>- Introduced a build.properties file >>>- Added a org.vqwiki.web package containing the Spring controllers >>>- Made some stubs for various items and created a full controller for the >>>view action named ViewTopicController >>>- Cleaned up WikiBase a little and introduced two new methods for use with >>>new framework. (see bottom of file) >>>- Added some methods to Topic class (see bottom of file) >>>- Introduced two methods into Topic class for getting the contents >>> public String getRenderedContent(String parsername) >>> public String getRenderedContent() >>>- JSP files have been moved to ./src/webapp/WEB-INF/jsp >>>- Moved core VQWiki lexers to ./src/lex and moved non-core lexers to >>>./src/lex/alt >>>- Lexers are always recompiled >>>- A default.properties file was introduced with the intention of removing >>>hard-coded default values. >>>- Major changes in Environment class to match introduction of >>>default.properties.... THIS IS CURRENTLY VERY BROKEN >>> >>>Hope I haven't left anything out.... >>> >>>2) Task Request (i.e. how can you help / could you please do this?) ;-) >>> >>>RYAN, I'd like you to: >>> >>>- Remove any libraries which are no longer being used. >>>- Verify that all libraries needed to build the project are included in >>>the >>>repository. >>>- Move all content retrieval methods in WikiBase to the Topic class. >>> The Topic class should have methods like getRenderedContent (see >>>above) >>>and getRawContent. >>> No methods should remain in WikiBase which have to do with content >>>retrieval or manipulation. >>> Make sure it all works nicely with the NEW parser system. We drop the >>>old system in release 3.0. >>>- Please make sure you document your methods etc for Javadoc generation >>>purposes. >>>- Form an opinion about: how to document, should we use PNG/GIF/JPG to >>>produce UML class diagrams or shouldn't we bother? >>> >>>ANDREAS, I'd like you to: >>>- Look at what I've done to the Environment class and go with that >>>intention/direction please... work on the Environment class with the >>>intent >>>that it should be generalistic and contain only information about the >>>GENERAL environment. No parser or plugin specific stuff. >>>- Think about / create a simple conversion tool... can be command-line or >>>in-wiki-system. >>> Goal: simple to do conversion of ParserA type content to ParserB type >>>content with fail proof backup mechanism. Should work with file and db >>>persistency. Start with file based persistency. >>> Mainly to be used for 2.7.x -> 3.0 conversion. Should be easily >>>changeable / configurable to also be able to handle 3.0 -> 3.x or 4.x >>>conversions for example. >>>- Please make sure you document your methods etc for Javadoc generation >>>purposes. >>>- Form an opinion about: how to document, should we use PNG/GIF/JPG to >>>produce UML class diagrams or shouldn't we bother? >>> >>>AS FOR MYSELF, I'll be: >>>- Continuing to work on the Spring controller stuff. >>>- Finalize the file system structure and build.xml file with your input >>>- Cleaning up WikiBase and other classes where necessary >>>- Working Wiki ML 3 into the new parser system >>>- Working on the new ACL system, figure out appropriate hooks etc. >>>- Alter the build.xml (in as far as that hasn't been done yet) to build >>>two >>>packages: one src package and one binary-only package. >>>- Form an opinion about: how to document, should we use PNG/GIF/JPG to >>>produce UML class diagrams or shouldn't we bother? >>> >>> >>>If either of you have any objections / comments / requests / "did you >>>think >>>about.." comments / "I want to work on..." comments or simply don't have >>>time to work on the project, please say so. When you are finished with the >>>things I'm asking of you here, I've got more stuff for you to do and I'd >>>also like to recheck our position and direction again at that moment in >>>time. >>> >>> >>>3) Project Direction; >>> >>>First off all... I'm thinking about introducing the XStream project for >>>revamping the file persistency things... not for actual content files, but >>>for meta data, revisions, ACLs and such. I like it a lot, it's fast, has a >>>lot of potential and makes for easily read XML output. I've made some >>>trial >>>runs with the software and it looks to be of good quality and easy to use. >>>What's your opinions? >>> >>>Now for the rest... >>> >>>Release 3.0 alpha >>>- We've got a new logo >>>- I'm having someone work on a new look-and-feel for the site >>>- My intention is to keep the new structure as clean, lean and clear as >>>possible. >>>- The Spring Framework will be introduced >>>- A new parser system will be introduced >>>- A new ACL system will be introduced >>>- The file persistency system will be revamped >>> >>>Release 3.0 beta >>>- JSPs will be revamped >>>- The database persistency system will be revamped >>>- A new module system will be introduced which is a variation on the new >>>parser system >>> >>>Release 3.0 RC1 >>>- A theme-ing system will be introduced >>>- Bug squasing >>> >>>Releases 3.0 RC2 - RC4 >>>- Bug squasing >>> >>>Release 3.5 >>>- The database persistency system will be revamped to use Hibernate(?) >>> >>> >>>I hope this makes it a little bit more clear what I want to do with the >>>project in the coming period.... >>> >>>Sincerely, Martijn >>>----- >>>Project Lead for the VQWiki Open Source project >>> >>>----- Original Message ----- >>>From: "Ryan Holliday" <rya...@gm...> >>>To: <ver...@li...> >>>Sent: Monday, June 05, 2006 6:53 PM >>>Subject: [vqwiki-dev] Spring Framework Transition >>> >>> >>> >>> >>> >>> >>>>Hi Martijn, >>>> >>>>Is there any chance of getting an update on the status of the transition >>>>to the Spring Framework? I realize you're still in the process of >>>>getting the /trunk/vqwiki project ready, but if there's anything I can >>>>do to help move the process along please let me know. >>>> >>>>Cheers, >>>> >>>>Ryan >>>> >>>> >>>>_______________________________________________ >>>>veryquickwiki-develop mailing list >>>>ver...@li... >>>>https://lists.sourceforge.net/lists/listinfo/veryquickwiki-develop >>>> >>>> >>>> >>>> >>>> >>> >>>_______________________________________________ >>>veryquickwiki-develop mailing list >>>ver...@li... >>>https://lists.sourceforge.net/lists/listinfo/veryquickwiki-develop >>> >>> >>> >>> >>> >>> >>_______________________________________________ >>veryquickwiki-develop mailing list >>ver...@li... >>https://lists.sourceforge.net/lists/listinfo/veryquickwiki-develop >> >> >> > > > >_______________________________________________ >veryquickwiki-develop mailing list >ver...@li... >https://lists.sourceforge.net/lists/listinfo/veryquickwiki-develop > > > > |