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 6
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...

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

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.

Bugs and Issues / Re: Wine effect
« on: October 17, 2016, 07:26:08 am »
The point being, under windows 7, running under VirtualBox, connecting to the Linux host, it works. This is something VB aranges for, Just like under Wine, there's a mapping facility. AFAIK I don't even run samba, I don't share files that way. So I'm not getting the point you're making....sorry

Bugs and Issues / Re: Wine effect
« on: October 14, 2016, 09:29:39 pm »
In both cases it maps to the Linux host, Wine supports drive mappings and Virtualbox does also. It's the same location, but I use mappings because vary long names can cause Windows to barf on occasion. And to even things out, I wanted the path to be equal, in length, drive letter. I tested using Wine Explorer to determine I can see and read the file, using the same path. Notepad under wine opens the files. So I think I can rule out a permission issue. As Wine is not windows, I would not immediately assume that it is something Wine has turned, where Windows 7 hasn't.

It happens to me under Wine and one Windows 7 box (running under VirtualBox). I can take a stab at running it and capturing things, but the UI responds both equally under wine or win7/32, however for some weird reason it does not happen on my win7/64 machine. In all cases, when you define the DSN, the ODBC setup works perfectly, test connection returns successfully. When you access that DSN under EA, it throws a 'invalid DSN or not found' error. It is as if EA can't find the system DSN. So far, defining as an User DSN solves the immediate problem.

I tried to create a log as you suggested, first attempt was opening the DSN defined as a system DSN. I closed the program after getting the error. Then I repeated the test with the same database defined as an user DSN and closed the program after it opened the repository successfully. In both cases the file was empty (0 bytes).

I have noticed this in some situations in EA 13.5 as well, most notably running under Wine, and on a Win7 32bit machine. I cannot replicate it under W7/64 though, which is essentially the same configuration.

However, where it does not work, I have found that defining the database as a User DSN solves the problem, it only appears for me when I define the source as a system DSN. Perhaps that helps you....

Bugs and Issues / Minor but persistent bug
« on: October 13, 2016, 10:32:14 pm »
Somewhere in the 12 series I think, I started noticing that if you set the diagram to be on one page (and I frequently do that), save the diagram and reopen, you have to actually click any element in the diagram before it pushes the page boundaries to show how the diagram would fit on one page.

Personally I'd prefer that it checks for this upon load. In version 13 this is still there. Not a biggie, but one of those in the categorie 'once you notice, you keep noticing it' .

Bugs and Issues / Re: Wine effect
« on: October 13, 2016, 10:27:21 pm »
As both the virtual machine and the wine run use mapped drives, I'd suspect we're firmly in SMB territory. It could well be a wine thing. So, I created the map in Wine to identical to the one VirtualBox and ran both. The Wine import yields nothing much

The Windows import finds the sources, there are 13 of these shots in total to cover all that was imported, I'll just show one

And a shot of the settings, which was the same for Wine as well as VirtualBox. I checked with the Wine Explorer that I can see the .java files before importing. And I can.

(Sorry for the ugly blotches, but I am obligated to blotch out some bits)

One other thing I noticed in Wine, if you detach the projectbrowser, it remains on your screen, even when you change desktops. Which is somewhat odd, and most likely a Wine problem. I run LMDE2, so my wine is a little old: 1.6.2


Bugs and Issues / Re: Wine effect
« on: October 11, 2016, 02:19:20 am »
I would not expect to, all directories are within my home directory, so if windows can, linux should certainly be able to.
**EDIT** the windows machine runs inside Linux, all contained in my home directory, and the location is offered through a permanent share (VirtualBox)

On a side note, I have one W7 32bit machine that also struggles to use System DSN's. W7 64bit has no problems, Linux/Wine, same as the W7 32bit. I suspect it is something in the ODBC setup, but not sure what.  Still looking to what is so different.

Bugs and Issues / Re: Wine effect
« on: October 10, 2016, 10:54:11 pm »
I'll give that a go, but as I've defined the sources as user DSN's, it works well now, just something to watch. When you enter it as a system DSN, it works from the ODBC config (test the connection), but EA says that the DSN isn't there, or not valid. Perhaps it's a Wine and system permissions thingie, I don't use Wine a lot, so could have easily missed things.

For the recurse thing, it does recurse, but doesn't find the same amount of files, so the recurse isn't working as under windows. I can't handover the files and dir structure, without removing stuff.... There's quite a deep nest and quite a lot of empty directories. I'll work on making it handoverable and then post it....

Rgds Chris

Bugs and Issues / Wine effect
« on: October 07, 2016, 11:32:46 pm »
Since 13 came out I was eager to try it under Wine. And it is impressively good. Speed, responsiveness, all much improved. Running EA seemed almost so good, I was about to remove it from the Windows machine that I normally run for mostly EA purposes. However, I noticed when importing some C# code from elsewhere, it failed, whereas windows doesn't. the source code in question resides in various sub directories of a tree I was given, and the first couple are empty. Even so, I had the recurse option set (Import source directory). The source directory was located somewhere in my home directory, let's say ~/Documents/Customer/Project/Source/*.* and below. In my Wine box, this shows as Z:\, on my VPC, the same location would be I:\Project\Source\*.* (so a little shorter).

Under wine, there's no recursion, in the VPC it does. Anyone else ran into this?

And I also noticed that EA 13 cannot pick up system DSN's, only user DSN's. Under windows it works with both. That's not a biggie, but the 'don't recurse' behaviour is a little worrying.

Rgds Chris

General Board / Re: Report strategy question
« on: January 17, 2016, 07:10:51 am »
This sounds an interesting alternative. Perhaps not for this problem, but this might a usefull approach to have in one's arsenal. Any chance of hello world kind of example? :)

General Board / Re: Report strategy question
« on: January 15, 2016, 08:40:45 pm »
Hi Geert,

My scripting experience is limited. But actually I found that one of the fragments from my original attempt was including child elements. When I removed that, it seems to have solved the problem with traversing the elements. Now the main element loop has two fragments, each with specific layout and filtering options and each fragment 'fires' when the correct element is encountered. This is pretty simple, and fits with what I thought should work. I just missed that one check mark. Right now I am almost where I want to be, so I'll explore this further.

Thank you for your suggestions.


General Board / Re: Report strategy question
« on: January 15, 2016, 07:55:54 pm »
Hi Geert,

Yes, possibly that would work, I've used Virtual Documents before. The trouble I'm having is that to report on interesting things I need to be in the element section, but there seems to be no way to tell the report engine to use different sets on different levels. If I leave the child elements section empty, it uses the elements definition, but when I added bespoke items to the child element section, I cannot access links etc.. just the element attributes. The easiest way to fix this allow fragments in the child element section (Virtual documents work great with packages, but tend to be better in reporting on the same hierarchy in different ways, or combining different, non-hierarchical packages to the same template / report section). For that matter, fragments should also be enabled for child packages I guess. Another 'trick' would be to just put all the fragments in the element section and let the filtering produce fragment output or not. That does actually work, but it does not traverse all elements, I notice the first fragment fires, then the second (for the children) and then it just keeps firing the second fragment.

With virtual documents my main issue would be how to get the hierarchical report I want (plateau -> deliverable) without having to set up 2 model documents per plateau. In fact, I'm not even sure you can include elements into model documents, I've so far only added packages.

So I am trying to re-think the project structure, which is almost proving a little hard....... I can of course ask for a change to the report writer, but that doesn't solve my immediate need.

Pages: 1 2 3 [4] 5 6