GithubHelp home page GithubHelp logo

obeonetwork / capella-extensions Goto Github PK

View Code? Open in Web Editor NEW
5.0 9.0 10.0 274.41 MB

Collection of plugins adding features to Capella (http://polarsys.org/capella/)

License: Eclipse Public License 1.0

Java 99.81% HTML 0.02% Shell 0.17%

capella-extensions's Introduction

Capella-Extensions

Collection of plugins adding features to Capella

Download

An update site is built and published for every commit:

Nightly

Nightly Capella 6.0.x

6.0.0

Nightly Capella 5.2.x

5.2.0

Nightly Capella 5.1.x

5.1.0

Nightly Capella 5.0.x

5.0.0

Nightly Capella 1.4.x

1.4.2

1.4.1

1.4.0

Nightly Capella 1.3.x

1.3.1

1.3.0

Nightly Capella 1.2.x

1.2.1

1.2.0

Nightly Capella 1.1.x

1.1.0

Prerequisites

  • Capella

#Continuous Integration

Current status for branch master

Current status for branch capella-1.3.x

Current status for branch capella-1.2.x

Current status for branch capella-1.1.x

Travis is used to build this project:

https://travis-ci.org/ObeoNetwork/Capella-Extensions

capella-extensions's People

Contributors

cboudjennah avatar cbrun avatar dependabot[bot] avatar mporhel avatar ylussaud avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

capella-extensions's Issues

Release 1.2.0

Tests extensions against Capella 1.2.0 and tag the master branche.

Add the LDFB CTX diagram for each functions

In LA-Complete generator, add in chapter "3.1 Logical Function : " a service to show the contextual diagram of each function:
f.asImageByRepresentationDescriptionName('LDFB CTX ' + f.name)

It should improve the result with more diagram in the generated document and an example of service call with a computed diagram name.

M2Doc for Capella should support the "Visible in documentation" field for diagrams

This issue has been moved from ObeoNetwork/M2Doc#289

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please have a look to the support pages of our website : http://m2doc.org/support/

Current behavior

Currently all diagrams are exported during M2Doc generation

Expected behavior

In Capella, some diagrams can be done only to work on the model. They are not supposed to be exported for documentation. The field "Visible in documentation" could be used in order to identify such kind of diagrams by setting its value to false.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Remove from documentation diagrams created only to work on the model

Environment


M2Doc version: X.Y.Z
Eclipse version: X.Y.Z
Platform version:   X.Y.Z

Others:

NPY in command line when the genconf URI is invalid

!ENTRY org.eclipse.osgi 4 0 2021-04-26 16:51:02.165
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException
at org.obeonetwork.capella.m2doc.commandline.M2DocCommandLine.execute(M2DocCommandLine.java:120)
at org.polarsys.capella.core.commandline.core.CommandLineApp.launchApp(CommandLineApp.java:138)

Maybe, the stack trace tells you something.

(M2doc3.1.0)

This NPE is produced when the line 200 of M2DocCommandLine throws an Exception. This add a null to the list of genconf URI.

Promote archived update sites

Update sites for:

  • Capella Extensions
  • Capella Extensions and dependencies

are promoted on the s3 amazon server. It can be very useful to upload an archived version of those update sites for people who can't install features from a remote update site.

ReplaceLink service does not handle Team for Capella session with representation lazy loading enabled

In some situations DRepresentation elements will not be contained in the main Sirius session resource or even not be loaded at at all yet. For example with Team for Capella connected projects, the main session resource will contain only the local representations but the shared ones are hosted on the server. Furthermore by default the lazy loading of representation is enabled : the aird is split and every DRepresentation is stored in its own .srm resource.

The replaceLink service does not handle those cases as it looks for an object with the given id/uid only in the main .aird.

See https://github.com/ObeoNetwork/Capella-Extensions/blob/master/plugins/org.obeonetwork.capella.m2doc.aql.queries/src/org/obeonetwork/capella/m2doc/aql/queries/M2DocGenServices.java#:~:text=private%20MHyperLink-,internalReplaceLink,-(MHyperLink%20link

Add a service to get extensions

Add a service to get an extension using its EClass and returning the instance of the extension. It should properly validate to the requested type.

Enable tests in the build

For the moment tests can't be ran during build. It would be great to fix that and add the "verify" directive to the maven command line.

This is for master branch only.

M2Doc does not export images that were created with "Add Image" function in the editor

This is an issue following the forum post here: https://forum.mbse-capella.org/t/embedded-images-have-133-size/5004
This is for capella 1.4.2 and M2Doc 3.1.1.

There are two ways of adding an image to the description of an object

  • By copy-pasting
  • By using the "Add image" function in the top right corner of the editor

Copy-pasting creates an image URI of style: data:image/png;base64,AAAAAAAAAAAAAAAAAAAA...
Adding images creates an image URI of style: img/test_image.png
The latter one corresponds to the relative file path.

Both images are displayed correctly in the editor. When exporting the description to a document with m:object.description.fromHTMLBodyString(), only the copy-pasted image is displayed. For the other image, the following error message is written in the document:

An I/O Problem occured while reading platform:/resource/ExampleProject/doc/img/test_image.png: Resource '/ExampleProject/doc/img/test_image.png' does not exist..

I created and attached a simple test case.
ExampleProject.zip

Split the extension services from the IFE example

Split the extension services from the IFE example. This will allows to provide one plugin for the extension and several for the IFE example (one by Capella version).
Also add one optional feature for each version of the example

Typo in LA template

There is a small typo in the LA template provided with Capella.

Section "2.1 Logical components", additional spaces prevents diagrams generation.
m:if lc.isRepresentationDescriptionName(' Logical Component Breakdown ')'-> m:if lc.isRepresentationDescriptionName('Logical Component Breakdown')

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.