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 - Glassboy

Pages: 1 ... 5 6 [7] 8 9 ... 68
General Board / Re: EA14 Beta - HiDpi Disastar
« on: March 27, 2018, 09:49:28 am »
Yes, one can report bugs. And sometimes they get fixed. Somewhen. But from my statics reported bugs simply get buried. Or lost. Or they print them on paper and use that for something like an Easter fire (German rite to light a huge fire on Easter) or the Burning Man.

I'm pretty certain I've had responses and acceptance of all the bugs I've logged.  And sometimes even a follow up email to tell me what version the fix will be in.  The bigger problem I have had is being out of maintenance by the time the new version comes out.

The point really is this is the General Board, not the temper tantrum board :-)

I need prevent a table will be splitted when content cannot end in the page and need to send to the next page, I've insert page break, but each table is showed in one page, and that is incorrect too, I want prevent split a table and I wan't prevent that exist one table by page.

This is not something you can achieve in a word processor so I very much doubt you can force EA to do it in the documentation generation.  Generally if you want a table to be one page only you change the font size until you shrink it enough.  That or generate an image that you scale to one page.

General Board / Re: EA14 Beta - HiDpi Disastar
« on: March 27, 2018, 07:38:08 am »
Yep that's another one. Not hard to find examples all over the place. Like I said, it's a mess and I for one am fed up of sparx not bothering to fix these basic things but then go on to add additional bloat of limited use.

Unless you log bug reports for these problems when you find them they are unlikely to be fixed.  The developers aren't psychic and actual logged bugs will get priority over all the things you are bitching about.  The link to report a bug is in the description of the Bugs and Issues board (you know the board that's not General for discussing Bugs and Issues).

General Board / Re: Learning the document generator
« on: March 26, 2018, 08:27:06 am »
If I understand what you are saying, my comment would be it is easier to document a package and include a diagram rather than document a diagram.

Every single project (operational project 1, operational project 2...) could be assigned to a sub-node of the root node (operational projects). Do you know if these s

A standard package should be fine.  I also give everyone a sandpit area so they can play in a space easy to clean out.  Rather than having them trying different things inside a project where it can be very confusing to someone else later.

As far as 1..1 (1) relationships, they need to be confirmed but aren't, prima facie, wrong.  Incorrect 1..1 associations are a common newbie, mistake, but we are usually cured of that pretty quickly.

I try to tell my wife that, but will she listen?

Until v14's row-level access has been confirmed as viable.  Then maybe you can "hide" those confidential portions of the repository using that.

I still wouldn't use the same repository in that instance.  I've seen several instances of personal grievances claims made against an employer when staff felt they were not being consulted about restructuring.  If you keep the "pie in the sky" "what if" process modelling in a separate database to the "production" repository it is completely clear that the models are not in any official or approved.

In almost all cases I've seen the single repository setup was to be preferred.

The case where it is not is if your organisation is going to perform a significant process re-engineering which might result in job losses.  In this case it is best to clone your process models into a new repository with access only given to those staff working on the re-engineering.  This also allows the what-if models to be flushed away when the modelling is over.

General Board / Re: EA v14 Beta Crashes when opening
« on: March 09, 2018, 12:17:56 pm »
The error message looks to me like our code threw an exception. (Which could be intentional)

Three developers trying to claim responsibility for a crash, I think I may need a lie down.

General Board / Re: Replica conflict resolution help
« on: March 07, 2018, 12:07:19 pm »
Oh, and even in these days of gender neutrality, Athena was a Goddess, not a God.  ;)

True but the operative word was patron and she wasn't above disguising herself as a man.

General Board / Re: Replica conflict resolution help
« on: March 07, 2018, 08:28:13 am »
I thought this advice would be like carrying owls to Athens (German proverb).
Wear thick gloves?

The patron god of Athens is Athena, and Athena's sacred animal is an owl. 

I don't know Archimate well, but your wording is a bit suspect. Modifying a language is usually not a good idea. But extending it should well be possible by creating your own MDG based on Archimate.

Adding attributes and specialising elements is kosher according to Archimate .  But you're right, functionally a MDG that specialises the whole thing is probably best.  You could go as far as some people (Sunshine?) and create your own Archimate 3 MDG.

General Board / Re: Set the Default Diagram in EA13
« on: March 06, 2018, 07:44:42 am »
I didn't find where I can set my Default Diagram in EA13 the first open.

Right click on a diagram and choose set as user default diagram.

Model default is a bit hidden.  Lay out ribbon | Manage | Set as Model Default.  User Default is also there as well.

General Board / Re: Document a whole Solution
« on: March 05, 2018, 07:38:31 am »
Geert, if you use UML for everything you will have a fully integrated model, with consistent elements and artifacts from contextual down to physical and out of context... easier, more efficient and effective than mixing multiple notations.  IMHO UML works even better at contextual-conceptual-logical than at physical level (UML was originally developed to talk to people, and a failed attempt to shoehorn it into a programming language has damaged it quite a lot...)

I really should put my doing Archimate better with UML MDG together one of these days :-)

General Board / Re: Document a whole Solution
« on: March 02, 2018, 10:02:24 am »
As for the model organisation, I prefer abstraction layer before domain

The TOGAF content meta-model is by far the best part of TOGAF and is very useful for structuring "content".

Pages: 1 ... 5 6 [7] 8 9 ... 68