Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ChrisMW

Pages: 1 [2] 3 4 5
16
General Board / Re: Jumping line angles
« on: November 04, 2016, 09:31:44 pm »
My question also, it was not done deliberately. And I cannot find a global setting, so it should be a setting inside the project. That begs the question, why does one apply it and the other not? There seems to be more than one thing going on here.....

17
General Board / Re: Jumping line angles
« on: November 04, 2016, 08:00:40 pm »
That option is set on all machines, I think it is a default with EA13, still things are not calm visually.

So I took the same diagram, from the same project, simply loaded the file, opened the diagram and did a publish to file. I choose WMF as the format. Now it gets interesting, as the result is not equal, why?

From the Wine EA 13, the wmf info is:


From the Win 7 running under virtualbox the info is:


As this is the same diagram, from the same file, I'd expect this to be the same. The Wine image looks clean, but the Win7 VB client looks like the aspect ratio is stuffed. Something which the file is reflecting (1:12 vs. 1:57). Also the colour count is different, file size etc... The Diagram is set to always be on one page, A4 portrait in this case.

But there's something else, the sequence of the attributes differs also, look at the example from wine:


Notice how under windows the field Type on the right is now in a different spot:


Is there a global setting that affects this? I assumed that this setting would be per project and therefore stored in the project file.

However, the different interpretation of the diagram size affects the display also, here's a part frrom the Wine EA:


And the similar part from the Windows VB client EA:


Now given that A4 is a standard size, this is the same EAP file and the DPI setting is equal, something else is going on, the font resize into element option is on, I was expecting the wmf of the same diagram to come up with the same numbers. Default element font is Arial 8 on both environments, as are the other settings.

18
General Board / Re: Jumping line angles
« on: November 02, 2016, 08:19:18 pm »
Hi, perhaps I'm not getting you, but isn't the zoom level saved with the diagram? I.e. if I save in one, and open in the other, it should display the same. All other things being equal. Or are you referring to a setting somewhere, I can check that....


19
I can read the tags that EA created, but not the ones I add manually. Is there a list of TAGS that is maintained somewhere?

20
After some further exploration, it seems if I manually add a tag to an element with the table stereotype, you cannot read that tag in the DDL script. Why?

My plan was to manually tag the materialized views and then when I generate the DDL, skip those tables with that tag. But neither DDL_TABLE_TAGVALUE  or tableProperty:"propertyName" return the tag value. I defined a new tag value 'MaterializedView' and set it to Yes. In the DDL script I simply try to read the value and print it in the DDL. It comes up empty. Suggestions appreciated.....

21
General Board / Re: Jumping line angles
« on: November 02, 2016, 06:20:12 pm »
Whilst the renderer does make some impact on the visibility of the lines, the fonts seems to have a bigger influence. But those we've synced and the problem is still there. What seems to happen is that the boxes (it's a logical datamodel in this case) alter position a little and this causes some parts of the line to jump (mostly those that connect to an ellement) and some not (where I've bent the line). Personally I'd rather have the element stay where I've put it and have the font become less readable, or have the font resized to fit the space it gets on the system. Then nothing would have to change. Seems less of a problem than having to look at a messy diagram. Perhaps an option to consider?

All the systems are using Enh-1, with the GDIPlus checkmark set. Basic works but yields thin lines on some machines and Enh-2 doesn't play well with others.

22
General Board / Jumping line angles
« on: November 02, 2016, 01:22:05 am »
Hi,

I think I've seen this one dealt with before, but can't seem to find it. I share a repository with several co-workers, but on each machine, the line angles jump. Normally we tend to use custom lines, but they seem to easily decide to alter my carefully created route (straight angles, but not always the shortest) in one with weird angles. So when I save it, it looks good, when someone else loads it, it looks bad.

We all have 96dpi displays, we all have the same font config in EA. What else can be done to ensure the diagrams look consistently neat across our screens? Stop using custom lines? I like custom lines, and use virtualisation of ends quite frequently. But the diagram should display correctly across the machines.

I even have it on one computer, that runs Wine + EA and a virtualised windows 7 and EA. What causes the lines to jump around? Fonts seem to matter.

Rgds Chris

23
Hi,

As EA doesn't process Oracle's materialized views the way I'd like, I'm looking to adjust the DDL scripts, bascially skip dropping / creating tables that contain a tag. But not really finding a good example. I found DDL_TABLE_TAGVALUE ([tagName]) mentioned, and in the DDL Template editor I see the script create table.

Simply adding an
%if DDL_TABLE_TAGVALUE("mytag") != ""%
%endTemplate%

To the create table did not alter a single thing. Ideally I want to skip the tables I tag and add a comment to the DDL saying it was skipped for some reason.

Not having much luck in finding a good starting point on how to do it, but then, this is a part of EA I've not really explored a lot before, I'd appreciate some example, or links to where to look for the howto kind of information.

TIA

Chris

24
Bugs and Issues / Re: Wine effect
« on: October 20, 2016, 07:30:46 am »
Thanks Simon,

After trying Play On Linux, and more recent wine, I've decided to stick with the stable wine release from the jessie backports and q4wine + winetricks. It is faster, and it seems easier to tweak than the other option. EA is now running even better on Linux, thanks to your feedback/comments/suggestions and one more bug squashed. All good. Thanks again......

25
Bugs and Issues / Re: Wine effect
« on: October 18, 2016, 06:16:41 pm »
Simon,

I tried EA13 and W10/32bit, straight from the install it doesn't work. It had a EA11.13 on it and some old ODBC links, a few that still work (as they point to the PostgreSQL on the Linux host). So I simply upgraded 13, rebooted (because when in doubt, with windows, reboot  ;) ) and tried to connect. 11.13 connected fine, 13.05 throws the error. So for me it seems predictable, a 32bit windows requires an user DSN, a 64bit windows does work with a 32bit system DSN.

I'd love to try the latest Wine, but 1.8.4 is not happy with a 64/32 wineprefix, although EA 13 runs fine, the ODBC is messed up. Not sure I'm going to go with 1.9, I quite like the way EA works with wine now, and 1.8.4 is almost the latest stable version (1.8.5 currently), and available as a back-port for my system. Giving the time it would take, a roll your own 1.9.x on a Debian based 64/32 system is probably interesting, not sensible from a production POV. I might have a old Linux laptop lying around that I could try, not sure if it still works... I'll see what I can do, testing with Wine is easier, as setting up a new prefix is quite quick.

26
Bugs and Issues / Re: Wine effect
« on: October 18, 2016, 05:57:52 pm »
Hi Simon,

Well Wine 1.8.4 seems to work better, but Debian and Wine are not a trivial match. I had to sequence the backports carefully to get it installed, and resort to the command line, Synaptic wasn't coping well.

About the import, the thing is, it does create diagrams, loads, within the spot you do the 'import source dir' , but they are all empty. If the assumption is that the existing classes are already on the diagrams, then why create loads of new empty ones. Also, if I switch on overwrite, it will remove the existing classes leaving the original diagrams empty.

I personally think this is confusing, wouldn't it be more straightforward to simply check during import, and if there's an existing structure, ask if the user wants to import a copy here, or update the existing branch in the repository? Because the package structure can be altered, trying to update a previous import can be a little hard. It seems a little hard to predict the end result, and I do use the import source dir to close the feedback loop. I'm good with cloning, I'm good with rewriting the original import, but I'm struggling with creating loads of empty diagrams (because the previously imported ones were synced and remain on those diagrams) and not knowing where the classes did end up (multiple people working on the same repo), or re-creating the package/diagram/classes in my part of the repo, but then affecting other parts of the repo. I now know sort of what to expect, but not sure I'll remember.....

As for the ODBC, I installed both. In the list you see both, I was careful to select the 32bit version in EA.

As for the system DSN issue, as I had to create a wineprefix from scratch, and it happens there, that might be easiest route to reproduction. My W7/64 doesn't have any issues using the system DSN. The 32bit W7 I was testing is an old VM and I'm not sure the installation is clean enough (having installed/removed lots of software over time, it might be a 'dirty' windows. I'll give my only other 32bit machine a go, but that's W10. But it's a cleaner environment. Any plans to go 64bit with EA?

27
Bugs and Issues / Re: Wine effect
« on: October 18, 2016, 01:45:07 am »
Ok, it took a little time, but I moved Wine from 1.6.2 to 1.8.4, I found on the Debian Jessie backports. I found another link, but those debs stuffed my installation in a very profound way, so I had to fix that first. I then made the mistake of creating a 64 bit prefix, which caused a host of problems for ODBC. So now I have the 32bit prefix, 1.8.4 and EA13. Needed to update winetricks to get the fonts to install properly, but that's easy.

The good news is that the black bars are completely gone, so the screen looks better.  The import does work better, although there are still a few things that work differently from what I'd expect.

I also tried running EA under wine, as in wine ea.exe > ea.log and this yielded a log file of zero bytes. So I then tried wine ea.exe > ea.log 2>&1 and now I'm seeing lots of

err:ole:CoGetClassObject no class object {88d96a05-f192-11d4-a65f-0040963251e5} could be created for context 0x17
err:ole:apartment_getclassobject DllGetClassObject returned error 0x80040111
err:ole:create_server class {88d96a05-f192-11d4-a65f-0040963251e5} not registered


So I reran and these messages all appear whilst loading.

I then used the 'overwrite' options and all loaded perfectly. So I checked and yes, the old import was in the same repo....  :-[

However, that made me wonder, if I import and have the classes synced, shouldn't they have appeared on the diagram, but referencing the existing class location. Which would have helped, as I would have seen the diagrams having classes, but the classes not being in the same location, it's trivial to find where they are once you see something on the diagrams. However, the diagrams were empty.

So going back is probably not worthwhile, and probably has something to do with it (remember my first import was using Wine 1.6.2 and EA 13 and the sync option with no previous code elements present, which failed, which was the reason I tried under windows). But using Wine 1.8.4, EA 13 and the overwrite option works properly, and displays properly as well. You must however create a 32bit prefix, because a 64bit prefix creates a problem with ODBC. Under wine it doesn't matter if you start the 32 or 64 ODBC manager, because it seems the same, you see 32+64 sources in the same list, regardsless of which one you start. EA throws a 193 error, which others report is a stack problem when using the 64 bit ODBC manager. The windows work around does not work under wine.

Also, using this setup still has the system DSN problem, at least for PostgreSQL. They all must configured as user DSN's.



28
Bugs and Issues / Re: Wine effect
« on: October 17, 2016, 07:24:39 pm »
Under EA10, much the same as under 12.1. The progress window does mention that it is processing classes, and it even mentions layouting the diagrams, but nothing is added to the project, only packages and diagrams.

As to check the recursion, I went for the packager per directory option, and that does display the folder tree correctly, so it seems it's the java classes, having the extension .java

Going back to 13, the black bar only appears for items that do not have sub items. During the import it actually lists the classes (I kept using the package per directory option), but non of them make it into the project. So it doesn't seem a problem with the recursion, more with either reading the file (but it knows the class name, rather than the filename, so it seems unlikely) or adding the result to the project.

I'll start exploring the wine upgrade option...

29
Bugs and Issues / Re: Wine effect
« on: October 17, 2016, 07:07:51 pm »
Under 12.1 I still get the black bars to the left of the icons and the import seems to be processing more files, but the net effect is the same as with 13, no classes...

Trying EA 10


30
Bugs and Issues / Re: Wine effect
« on: October 17, 2016, 05:23:15 pm »
I'll check with an older version, would 12.1 be ok? or older?

I run LMDE, which is Debian+, I would have to see how to build it from scratch. I run a 64bit Linux, and wine is a little tricky to setup in that environment, so it might take time.

I've set Wine to be Win7 as a default standard. it made little difference, although I did have it still at XP when I installed. AFAIK the main difference is that the black lines started to show up further down the tree, but I could very well be mistaken. I've also noticed that sometimes you need to drag elements using the black bar, if you want them on a diagram. Hadn't paid too much attention to it, the workaround is pretty easy.

Will let you know.

Pages: 1 [2] 3 4 5