wwu-pi / md2-framework Goto Github PK

The wizard should gather additional information on the to-be-created project to be able to generate the main block in the controller part. This requires input of the app name, version, etc (see required elements of main block).

The Xtext help provides info on extending the wizard.

The preprocessing runs into an infinite loop if the model contains an AutoGenerator for an entity as follows.

entity A {
  ref1 : B
}
entity B{
  ref2 : A
}

Excluding the reference from the Autogenerator will help. The problem will likely also occur with recursive structures.
The relevant line is line 884 of PreprocessModel.xtend

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for de.wwu.md2.framework:de.wwu.md2.framework:[unknown-version]: Failure to find de.wwu.md2.framework:de.wwu.md2.framework.parent:pom:0.3.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 74, column 10
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project de.wwu.md2.framework:de.wwu.md2.framework:[unknown-version] (C:\Users\Ali-Haouari\Desktop\Eclipse Noen2\MD2\md2-framework\de.wwu.md2.framework\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for de.wwu.md2.framework:de.wwu.md2.framework:[unknown-version]: Failure to find de.wwu.md2.framework:de.wwu.md2.framework.parent:pom:0.3.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 74, column 10 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Attribute values etc that have been changed since loading are not reset to their persistent values.

NSManagedObjectContext executeFetchRequest does not overwrite changes. According to http://lists.apple.com/archives/cocoa-dev/2012/Jan/msg00173.html, this might not be so easy. Possible solution: manual undo - http://stackoverflow.com/questions/2214343/core-data-reset-to-the-initial-state

This causes an error in Eclipse.

While Activities are recreated when an app is restarted, Android keeps some things in memory, for example, MD2Application.
MD2Application, however, contains references to UI elements (via mappings, possibly also validators) that are specific to one lifecycle. When an activity (but not MD2Application) is created again, the mappings point to stale UI elements and do not have any effect.
The global context should not hold references to objects that will be recreated when the apps is newly started.

To see this effect in action, look at the simple app in wwu-pi/md2-testApps@85c2e8a

• close it (via back button)
• open it again => mappings not working
• close it and remove it from cache (Running Services -> Show cached processes)
• open it again => mappings working again, because context has been created anew

This might be expected by clients of /first, but the Android ManyContentProvider is surprised and cannot parse the result, for example
{"contact":{"__internalId":"1","familyName":"Mustermann","givenName":"Max","phone":{"__internalId":"2","number":"012345-45321","kind":"0"},"dateOfBirth":"1985-01-01T00:00:00+01:00"}}
A client expecting a multi-valued return type (with an arbitrary number of entries, possibly also one), would expect the following:
{"contact":[{"__internalId":"1","familyName":"Mustermann","givenName":"Max","phone":{"__internalId":"2","number":"012345-45321","kind":"0"},"dateOfBirth":"1985-01-01T00:00:00+01:00"}]}

A read operation should not issue a write operation in the background.

See ContentProvider.m, line 118 (4c98d04)

See simple app in wwu-pi/md2-testApps@85c2e8a

The required Android layout attributes layout_width and layout_height are not being set for a FlowLayoutPane with a Spacer during generation. Example:

package com.example.md2.sessiontest.views 
    FlowLayoutPane sessionListPane (vertical ) { 
        Label titleAbbreviation { text "Abbreviation" } 
        TextInput abbreviation 
        Label titleLabel { text "Title" } 
        TextInput title 
        Spacer
     }

The generated code for the Spacer is:
<TextView />
The app crashes with:

10-11 16:40:37.401: E/AndroidRuntime(429): FATAL EXCEPTION: main
10-11 16:40:37.401: E/AndroidRuntime(429): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.example.md2.sessiontest.android/com.activenetwork.md2.sessiontest.android.controller.SessionListPaneActivity}: java.lang.RuntimeException: Binary XML file line #38: You must supply a layout_width attribute.

This requires manual fixing the generated code in order for the Android application to build and run.

Also, the graphical layout editor in Eclipse complains that

"sessionListPane" does not set the required layout_height attribute:
 (1) Set to "wrap_content"
 (2) Set to "match_parent"

(but the app builds and runs)

Similar to Android, the static, generic parts of an iOS app should be included as a library. This would enable a clear structural separation between generated parts and target platform in the resulting app.

The state of the qualified name provider etc. should be reset on each new generation. Thus, its methods would best not be static.
Otherwise, state (wrt names) from the previous generation might leak into the next generation.

Example: first version of an app contains a button named "reset" and an action named reset. Then, the generated Android code contains errors, because the class .actions.Reset.javacontains a class Reset1 (related to a different bug: line 160 of AndroidGenerator.xtend should use getName as well).
Renaming the button to, e.g., "resetBtn" does not help directly, presumably because the old name mapping is still in the cache. Restarting the MD2-Eclipse instance and regenerating again resolves the error.