AW: Re: [Uml-devel] UML FUTURE UPDATE

[Luis De la Parra]

> I've put that into CVS.  It didn't seem to be able to find the code
> generation library but maybe Luis' newer version will fix that.  Look good
> but.

yes, the zip file paul put up is broken. it doesnt find code generation
automatically (you have to copy the libcodegenerator.la file to
(kdedir)/share/apps/uml/codegenerators/ and restart uml.  In the new file I sent to paul
yesterday that is already fixed. I also fixed some other problems that seem only
to affect SuSE.. or at least me, so I suggested to paul to check it out (I
think he's using RH) and if it works ok for him too then to put in cvs the
complete program as I sent him.  (problems with line terminators and a QPtrList
!=)

maybe you can get in touch with paul and he can send you the new
uml-luis.tar.bz2 file so you can put in cvs instead of the old one.


> Well I would gladly do it.  I havn't done that much on the programme but
> if I was the chosen one I'd almost certainly make it my final year
> university project and could dedicate myself to it basicly full time.

great to see a volunteer... but, please check before if that would be ok
with your university, I mean, that other people contribute code to the program
as well or if you would have to do it all on your own. If that were the case
then I'd sugest forking so that your professors accept your work as your final
project and other people can still contribute to the project at the same
time.


ohh!!, by the way!, last night I fixed the UMLView->setCursor problem . not
sure why I was not getting a pointer to the view.. I was doing a bunch of
castings dont remember now but something like
UMLView *view = ((UMLApp*)
(kApplication()->mainWidget()))->getDocument()->getView()
view->setCursor()
and now I'm doing parent()->parent() to get a ponter to UMLApp and works
fine. the problem seems to be with KApplication, not sure why, I can only
imagine because it inherits KInstance AND QApplication and the casting I was doing
was wrong.. 

anyways, now it *almost* works. the only problem is that when inserting
classes (concepts) after the first class the cursor changes back to the default
arrow. the "concept tool" is still selected, only the cursor changes.
inserting other stuff, text, asociations, actors, states, etc, works fine, it's only
with inserting Concept. seems as if the view did a "reset" before redrawing
itself and then it takes the cursor from its parent widget, which is set to
the default... I'll send the files later. I'll also try to work on the java
generator. till now I'v only worked on cpp and the java generator is still based
on the first implementation of my generators, so it is not really usefull.

regards,

luis.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net