Re: [tools-dev] Code analysis tool
From: Mohammed Mamdouh [EMAIL PROTECTED] Date: Wed, 07 Sep 2005 21:30:07 + Hi, I am Mohammed Mamdouh , working with Ramez on the OOQ project, we are still waiting for your support and comments, as filling for ramez, The tool will produce xmi file from the code also which is readable by ARGOUML and possibly Borland Together or Rational rose can you ask that question again? Please do not send private mails. Use this list. -- Pavel Janík With some developers it is not needed to run the code through obfuscator... I have inherited code which only the compiler could understand. -- someone in LKML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] Code analysis tool
Dear sir we are asking for the developers comments and Ideas on our tool, is it useful, what did we miss..etc, the tool reads the code files idependent from the language it is written in, produces xmi file readable by ARGOUML mainly and we are working on compatibility with other UML tools as BTogether or rational rose, the tool produces a report of flaws in the design these Ramez mentioned and I pasted them again here... these metrics are the first release (design checking) there will be - as planned- automated checklist tool, Style and convention checking tool and also an optimization techniques cheking tool.. Class size: The number of attributes in a class. The number of operations in a class. The number of public operations in a class. For inner classes, nesting level of the inner class Class Inheritance: The number of interfaces the class implements (UML Abstraction). The number of children of the class (UML Generalization). The number of descendants of the class (UML Generalization). The number of ancestors of the class. The depth of the class in the inheritance hierarchy. Class to leaf depth. The number of inherited operations. The number of inherited attributes. Class Coupling: The number of dependencies where the class is the client. The number of dependencies where the class is the supplier. The number of associated classes in the same scope. The number of associated classes in the same scope branch. The number of associated classes not in the same scope branch. The number of times the class is externally used as attribute type. The number of attributes in the class having an interface or class as their type. The number of object instances of the class in the model. The number of classifier roles where the class is the base. Package Size: The number of classes in the package. The number of interfaces in the package. Nesting level of the package in the package hierarchy. Package Coupling: The number of packages on which classes of this package depend. The number of elements outside the package having an association with a class inside the package. Interface Metrics: The number of operations in the interface. The number of times the interface is used as attribute type. The number of associations the interface participates in. The number of classes directly implementing the interface (UML Abstraction). The number of classes implementing a descendent of the interface. The number of ancestors of the interface. The number of descendants of the interface. Diagram-specific Metrics: The number of classes on the diagram. The number of interfaces on the diagram. The number of packages on the diagram. The number of associations on the diagram. The number of generalizations on the diagram. The number of abstractions on the diagram. thanks for your interest waiting for the support of everyone interested Best Regards Mohammed Mamdouh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] Code analysis tool
From: Mohammed Mamdouh [EMAIL PROTECTED] Date: Thu, 08 Sep 2005 11:07:20 + Hi, we are asking for the developers comments and Ideas on our tool yes, it could be useful. Now please show us some real results or the tool itself. Do not repeat what you wrote already three times. -- Pavel Janík Q: Or are you waiting for GNU Emacs 21 release with it? A: Unfortunately, I'm not sure I'll live that long. -- One of GNU Emacs's developers in private e-mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] build tool with html build status page
Vladimir Glazounov wrote: Hi all, from now on the the new feature in build tool is available. You can see the status of the build in Technicolor on a generated html page. Just resync your solenv/bin/build.pl to the version of SRC680 m128 and enjoy! (Trigger with '--html', help available) Best regards, Vladimir PS: I'm looking for enhancement proposals comments. OK I'm actually trying it out now and it really is fantastic! Some feedback: - make it automatically display the current job in the Jobs pane (maybe a current project link that autorefreshes so you can always see the detail for the current project) - clicking Total Progress sometimes caused an error and wrote javascript into the document (not serious as you can reload) What would be really nice as an enhancement is to be able to log all the output of build to a file, and be able to click on the link for a project / section but especially for an error, and see the actual output for that section. But you can usually do this manually anyway... I also thought in the past when doing my builds, it would be nice to somehow record the average amount of time to do an initial build or a rebuild for a given project, and use that information to work out the overall progress (e.g. on Windows binfilter takes a long time to build but some projects are very quick) Thanks for a great tool, already making my life easier today David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] build tool with html build status page
Vladimir Glazounov wrote: Hi David, the feature is just released, so now I'm collecting all comments for next release's features. See my comments inline... OK I'm actually trying it out now and it really is fantastic! thanks a lot :) Some feedback: - make it automatically display the current job in the Jobs pane (maybe a current project link that autorefreshes so you can always see the detail for the current project) If you're building with multiprocessing, than there can be more than 1 module in build. What should I pick as the best candidate? OK I'm not building with multiprocessing so I haven't had that AFAIK. could make another subframe and split it up between the current building projects but that might look a bit crazy! - clicking Total Progress sometimes caused an error and wrote javascript into the document (not serious as you can reload) Unfortunately I cannot syncronize write (in perl) and reload (in browser) operations - that's why sometimes there are errors. OK makes sense, I'm impressed that this works the way it does. What would be really nice as an enhancement is to be able to log all the output of build to a file, and be able to click on the link for a project / section but especially for an error, and see the actual output for that section. I'm thinking about it. Maybe, in next vesion there will be something like that. So far I do not have a clear vision of how to handle these logs. I mean where to write and when to remove. I always keep lots of log files as they're much smaller than the generated builds. But different people probably have different styles here. I also thought in the past when doing my builds, it would be nice to somehow record the average amount of time to do an initial build or a rebuild for a given project, and use that information to work out the overall progress (e.g. on Windows binfilter takes a long time to build but some projects are very quick) I think, this information is already there. You can see total build time, CPU time (is different in multiprocessing mode) and times for each directory (dmake times). Isn't it that what you mean? Yes, but if it could remember the time for each project from the last build then it could update the progress bar to reflect percentage of time rather than just percentage of projects. But having the times there is very helpful already Thanks again David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[tools-dev] after m79 build, setup don't exist, oo won't launch
hi Sorry, I try to find by myself, but... I finish compile the m79... by build --all in instsetoo_native then in unxlngi4.pro/OpenOffice/install/en-US/RPMS/ I got 21 nice RPMS (core01, writer...), about 101Mb, but no setup file??? I don't know what goes wrong, and I can't even install OO now (well, I installed all rpms with rpm -i --nodeps *, but when I launch soffice, it complains with a document recovery screen and a sh: line 1:crash_report: command not found, then if I uncheck Launch OpenOffice automatically in that screen, it ends up) I'm under mandrake 10.0 thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] after m79 build, setup don't exist, oo won't launch
On Thu, Sep 08, 2005 at 03:56:30PM +, Etienne de Boissezon wrote: hi Sorry, I try to find by myself, but... I finish compile the m79... by build --all in instsetoo_native are you really building m79?? ;-) this milestone is antique now, the latest source can be found at mirrors and http://ftp.stardiv.de/pub/OpenOffice.org/stable/2.0beta2/OOo_2.0beta2_src.tar.gz Max - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
