Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
VIATRA/DeveloperMeetingMinutes/Meeting20171214
< VIATRA | DeveloperMeetingMinutes
Revision as of 15:36, 10 January 2018 by Unnamed Poltroon (Talk) (Created page with "= Topics = * {{VIATRA-Status}} * VIATRA 1.7 released * VIATRA 1.7.1 seems necessary ** Query results view issue with LS https://bugs.eclipse.org/bugs/show_bug.cgi?id=528378 *...")
Topics
- Current status: Bugzilla Gerrit AERI
- VIATRA 1.7 released
- VIATRA 1.7.1 seems necessary
- Query results view issue with LS https://bugs.eclipse.org/bugs/show_bug.cgi?id=528378
- Query registry issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=528436
- Suggested date: first half of January
- VIATRA 2.0 status
- Query runtime uses unchecked exceptions
- Query explorer removed
- First milestone build
- Open questions:
- Language design: multiple languages vs. pluggable scope dialects
- Pluggable superlanguage version is much more flexible; would offer many benefits:
- “Match this pattern over this EMF model, plus this DOORS/etc model, plus this traceability table between them” → easy with hybrid scopes
- “Template patterns”, restrict certain patterns (both in the incremental and the stateless case) to a few user-supplied starting points (objects or identifiers) at runtime → this can be a use case for a user-supplied (unary) table
- Pluggable superlanguage may take more initial effort
- Runtime-level plus language-level composition
- Solve editor content assist etc. issues…
- import <<IVQLImportable on classpath>> <<details>>
- Example importables: epackage, java, user-table etc. ← list should be extensible; also probably deprecate / remove the default case
- “Details” could be Java package name, EPackage nsURI, user table name/class etc.
- Give +1000% time budget to Zoltán :)
- Timeframe? Is it meaningful to release 2.0 with language issues postponed?
- Pluggable superlanguage version is much more flexible; would offer many benefits:
- Language design: multiple languages vs. pluggable scope dialects
- Feature plans: https://docs.google.com/document/d/125Le7ejjXtLf1Xcz2Opra7Afs6_mm9-ciNXRGDJmmts/edit?usp=sharing
Minutes
- 1.7.0 released, some bugs only identified in the last minute
- 1.7.1 will be necessary
- 2.0.0
- M1 released
- VIATRA runtime exceptions are unchecked
- Query Explorer removed
- Query language question
- Deep question, will discuss later with leadership
- Indexes and zipping elements in queries
- Tamás Szabó would be happy to help with this if it is selected for inclusion in 2.0.0