search

tobydragon / metafora-project

Automatically exported from code.google.com/p/metafora-project
1 stars 0 forks source link

Referable objects from eXpresser don't appear in LASAD #123

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Steps to recover things back to normal 

(1) Somehow the XML format has changed and should include receiver 

<user id="Lasad8080" ip="1340279769621" role="receiver"/>

(and maybe originator as well)

(2) There is a need for new mapid (until we resolve the issues of the "default" 
map) as a parameter

i.e. mapid=153

(3)  The info of the user and password also from the resource cards

user=Manu&pw=password

(note: not userID, userpassword as we discussed in skype)

Original issue reported on code.google.com by mavrikis@gmail.com on 21 Jun 2012 at 7:34

GoogleCodeExporter commented 9 years ago 
About (1): the latest commit (but not the release) of eXpresser does that for 
the receiver as we are not sure what the originator should be or if important. 

(3) Also seems to be there already even for resource cards. 

So, assuming that all of this is correct, I pass this to TD as now we are 
waiting for the discussion tool to recover. 

Then we can decide on next steps and whether is worth the effort to just add a 
fixed mapId again or work on the more general solution.

Original comment by mavrikis@gmail.com on 21 Jun 2012 at 7:39

GoogleCodeExporter commented 9 years ago 
It is becoming less important to fix this unless it is trivial. 

In my opinion next steps are: 

(a) get the discussion tool back up and running 
(b) test whether things are working and if not why and re-evaluate next steps

Original comment by mavrikis@gmail.com on 22 Jun 2012 at 7:12

GoogleCodeExporter commented 9 years ago 
Home is adding &mapId=(as agreed) to the eXpresser URL when calling eXpresser 
through tools bar.
Planning Tool adds &collaborate=1 and &mapId=(as agreed) to eXpresser URL when 
opening eXpresser through eXpresser resource card.
"discuss this" in eXpresser resource card sends referable object to mapId=(as 
agreed).

Original comment by kerstinp...@yahoo.de on 22 Jun 2012 at 10:15

GoogleCodeExporter commented 9 years ago 
We are a step closer with that. There were bugs with the old format and other 
conceptual changes as well. LASAD:8080 now accepts proper format and maps IDs 
to last map user is joined into. Change owner to MM to resolve format issues 
with expresser.

Original comment by mavrikis@gmail.com on 28 Jun 2012 at 2:57

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/migen/source/detail?r=11634 resolves part of the 
problems in the released expresser version 270.

Tested sharing and asking help for a model from the following link: 

http://270.web-expresser.appspot.com/?contextKey=U8NyluKFekcPeDmtmaBE6d&metafora
=1&user=LKL1&testServer=true

and worked. 

TD to update lasad 8090. Remove testServer parameter in the link above (and 
change username) and should work. Pass issue back to me to test and close 
hopefully.

Original comment by mavrikis@gmail.com on 28 Jun 2012 at 3:20

GoogleCodeExporter commented 9 years ago 
The test and deployment servers are now updated to handle messages with only 
usernames, and send the object to the last-joined map.  Howver, one needs to be 
sure their last joined map is the correct template.  In this scenario, just be 
sure to choose "expesser" challenge (ID 2) so that resource cards are created 
with the correct template.

There seems some stragen behavior in 2 ways:  1) When sending an object from 
expresser externally (the only way we can right now) it opens a new expresser 
tab in Metafora. 2) It seems to "reload" lasad in some way, resetting to the 
top-right corner of the map rather than the center, whic makes the object not 
visible.Working outside of Metafora has none of these problems.

Original comment by tdragon1...@gmail.com on 28 Jun 2012 at 6:08

GoogleCodeExporter commented 9 years ago 
Also, high interruption feedback is sent to the user if no map is found for 
that user.

Original comment by tdragon1...@gmail.com on 28 Jun 2012 at 6:08

GoogleCodeExporter commented 9 years ago 
Nice one for the feedback ;-) 

Now I think there is another issue up to KK. 

Say the platform opens: 

http://web-expresser.appspot.com/?metafora=1&ptNodeId=UEttYXAueXIxMF9ub2RlXzI%3D
&ptMap=UEttYXAueXIxMA%3D%3D&ptMap=UEttYXAueXIxMA%3D%3D&ptMap=UEttYXAueXIxMA%3D%3
D&ptMap=UEttYXAueXIxMA%3D%3D&token=1340916769817&locale=en&user=LKLMM&pw=00adbcc
42461b689f9790f90868755ed&pwEncrypted=true&ptMap=UEttYXAueXIxMA%3D%3D&groupId=11
.igs.prop.yr10&challengeId=2&challengeName=eXpresser%20Metafora%20Scenario&testS
erver=false

then somehow the view and reference url I think are wrong. 

If my human parsing doesn't full me the view url doesn't have any user info at 
all and the reference url says userkey=new. 

See below:

<action time="1340918607305">
    <actiontype classification="USER_INTERACTION" type="CREATE_ELEMENT" succeeded="UNKNOWN" />
    <user id="eXpresser" role="originator" />
    <user id="Lasad8090" ip="1234567890123" role="receiver" />
    <object id="0" type="element">
        <properties>
            <property name="USERNAME" value="LKLMM" />
            <property name="TOKEN" value="1340916769817" />
            <property name="GROUP_ID" value="11.igs.prop.yr10" />
            <property name="CHALLENGE_ID" value="2" />
            <property name="CHALLENGE_NAME" value="eXpresser Metafora Scenario" />
            <property name="ELEMENT_TYPE" value="MY_MICROWORLD" />
            <property name="TOOL" value="EXPRESSER" />
            <property name="VIEW_URL" value="http://web-expresser.appspot.com/?metafora=1&ptNodeId=UEttYXAueXIxMF9ub2RlXzI%3D&ptMap=UEttYXAueXIxMA%3D%3D&ptMap=UEttYXAueXIxMA%3D%3D&ptMap=UEttYXAueXIxMA%3D%3D&ptMap=UEttYXAueXIxMA%3D%3D&token=1340916769817&locale=en&user=LKLMM&pw=00adbcc42461b689f9790f90868755ed&pwEncrypted=true&ptMap=UEttYXAueXIxMA%3D%3D&groupId=11.igs.prop.yr10&challengeId=2&challengeName=eXpresser%20Metafora%20Scenario&testServer=false&time=1340917208217292478&thumbnail=150x90" />
            <property name="REFERENCE_URL" value="http://web-expresser.appspot.com/?userKey=new&metafora=1&VersionQuery=1&copy=http%3A%2F%2Fweb-expresser.appspot.com%2Fp%2FUEttYXAueXIxMA%3D%3D%2FUEttYXAueXIxMF9ub2RlXzI%3D.xml%3Ftime%3D1340917208217292478" />
            <property name="TEXT" value="" />
        </properties>
    </object>
</action>

Doesn't this confuse the display? I think this happens only when things are 
loaded from the platform. 
So some recent confusion with pknode and map ids etc?

Original comment by mavrikis@gmail.com on 28 Jun 2012 at 9:28

GoogleCodeExporter commented 9 years ago 
Regarding userKey=new -- userKey is deprecated, right?

Metafora has a URL parameter called 'user' -- that's what should be used, right?

Or should there be no user or userKey parameter at all? Maybe the platform 
should add that since it knows what user is opening the referable object and 
eXpresser doesn't.

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 1:44

GoogleCodeExporter commented 9 years ago 
And what about the other launch URL parameters? They should be added as well.

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 1:46

GoogleCodeExporter commented 9 years ago 
YOu are right about reference url. The view url somehow is problematic 

For example. This:

http://web-expresser.appspot.com/?
metafora=1&ptNodeId=ISEh15nXqdeo15DXnCDXnNei15Nfbm9kZV8yOQ%3D%3D&ptMap=ISEh15nXq
deo15DXnCDXnNei15M%3D&token=1340950256113&locale=en

works fine opening a model: 

The corresponding view url (constructed by hand) also works

http://web-expresser.appspot.com/?metafora=1&ptNodeId=ISEh15nXqdeo15DXnCDXnNei15
Nfbm9kZV8yOQ==&ptMap=ISEh15nXqdeo15DXnCDXnNei15M=&token=1340950256113&locale=en&
thumbnail=150x90

One of the exta param somehow confuse it: 

http://web-expresser.appspot.com/?metafora=1&ptNodeId=ISEh15nXqdeo15DXnCDXnNei15
Nfbm9kZV8yOQ==&ptMap=ISEh15nXqdeo15DXnCDXnNei15M=&token=1340950256113&locale=en&
user=LKL1&pw=2d0e3d264d42d63d2a067cccc0b66428&pwEncrypted=true&ptMap=ISEh15nXqde
o15DXnCDXnNei15M=&groupId=100-test&challengeId=2&challengeName=eXpresser%20Metaf
ora%20Scenario&testServer=false&otherUser1=&otherUser2=LKLMM&time=13409476903079
62607&thumbnail=150x90

(and time is not the issue)

Investigating as well so if I figure out anything will post here.

Original comment by mavrikis@gmail.com on 29 Jun 2012 at 5:48

GoogleCodeExporter commented 9 years ago 
Investigating as well but see in the log that somehow creating a button is 
causing the following exception.

2012-06-29 06:29:10.405 /expresser/gwt-log 200 779ms 5kb Mozilla/5.0 
(Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
95.146.167.68 - - [28/Jun/2012:22:29:10 -0700] "POST /expresser/gwt-log 
HTTP/1.1" 200 5799 
"http://web-expresser.appspot.com/?metafora=1&ptNodeId=ISEh15nXqdeo15DXnCDXnNei1
5Nfbm9kZV8yOQ==&ptMap=ISEh15nXqdeo15DXnCDXnNei15M=&token=1340950256113&locale=en
&user=LKL1&pw=2d0e3d264d42d63d2a067cccc0b66428&pwEncrypted=true&ptMap=ISEh15nXqd
eo15DXnCDXnNei15M=&groupId=100-test&challengeId=2&challengeName=eXpresser%20Meta
fora%20Scenario&testServer=false&otherUser1=&otherUser2=LKLMM&time=1340947690307
962607&thumbnail=150x90" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; 
rv:10.0.1) Gecko/20100101 Firefox/10.0.1" "web-expresser.appspot.com" ms=780 
cpu_ms=420 api_cpu_ms=0 cpm_usd=0.012897 
instance=00c61b117c14ce1431a56aea4192eb090c2c1ec7
E 2012-06-29 06:29:10.370
com.allen_sauer.gwt.log.server.ServerLogImplJDK14 log: Uncaught Exception:
com.google.gwt.core.client.JavaScriptException: (TypeError): n is null
 stack: _j()@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A129087.cache.html:4758
gx()@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A129087
.cache.html:1636
U9b([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:3473
Gic([object Object],[object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:4369
vac([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:3919
L$b([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:4713
K$b([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:4285
J$b([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:4604
l_b()@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12908
7.cache.html:4793
YE([object Array],[object 
Array])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A129
087.cache.html:4284
OE([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:3488
aF()@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A129087
.cache.html:4781
UE([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:1736
EE(UE,[object Proxy],[object 
Arguments])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751
A129087.cache.html:2523
HE(UE,[object Proxy],[object 
Arguments])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751
A129087.cache.html:4327
([object 
Object])@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12
9087.cache.html:3402
(239)@http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A12908
7.cache.html:3696

 fileName: http://web-expresser.appspot.com/expresser/C4FBF71A5BD00CD68E15D1751A129087.cache.html
 lineNumber: 4758
    at com.extjs.gxt.ui.client.GXT.init(GXT.java:257)
    at com.extjs.gxt.ui.client.widget.Component.$clinit(Component.java:200)
    at uk.ac.lkl.client.ModelRulesButton.ModelRulesButton(ModelRulesButton.java:30)
    at uk.ac.lkl.client.TotalTilesRulePanel.TotalTilesRulePanel(TotalTilesRulePanel.java:28)
    at uk.ac.lkl.client.MyModelRulesPanel.MyModelRulesPanel(MyModelRulesPanel.java:21)
    at uk.ac.lkl.client.Expresser.$onModuleLoad5(Expresser.java:275)
    at uk.ac.lkl.client.Expresser.$onModuleLoad3(Expresser.java:230)
    at uk.ac.lkl.client.Expresser.$onModuleLoad2(Expresser.java:193)
    at uk.ac.lkl.client.Expresser$1.execute(Expresser.java:187)
    at com.google.gwt.core.client.impl.SchedulerImpl.runScheduledTasks(SchedulerImpl.java:212)
    at com.google.gwt.core.client.impl.SchedulerImpl.$flushPostEventPumpCommands(SchedulerImpl.java:379)
    at com.google.gwt.core.client.impl.SchedulerImpl$Flusher.execute(SchedulerImpl.java:76)
    at com.google.gwt.core.client.impl.SchedulerImpl.execute(SchedulerImpl.java:137)
    at com.google.gwt.core.client.impl.Impl.apply(Impl.java:165)
    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:196)
    at Unknown.anonymous(Unknown Source)
    at Unknown.anonymous(Unknown Source)
    at Unknown.anonymous(Unknown Source)

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 6:14

GoogleCodeExporter commented 9 years ago 
There were two problems:

1. challengeId introduces an activity URL that interferes with thumb nails. 
r11637 fixes that

2. ptMap overrides contextKey. Not clear what to do other than produce a 
warning. A URL  shouldn't do both.

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 7:11

GoogleCodeExporter commented 9 years ago 
But why anything to the thumb nail URL?

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 7:12

GoogleCodeExporter commented 9 years ago 
 If I'm understanding this right, I agree that the view URL probably doesn't need any of the other URL params, all those can be kept with the reference URL, (where we have the actual "context").

Original comment by tdragon1...@gmail.com on 29 Jun 2012 at 7:17

GoogleCodeExporter commented 9 years ago 
The exception in comment 12 remains a mystery. Couldn't reproduce it in the 
development environment.

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 7:18

GoogleCodeExporter commented 9 years ago 
Regarding comment 15 - Yes, that's right.

Original comment by ToonT...@gmail.com on 29 Jun 2012 at 7:22

GoogleCodeExporter commented 9 years ago 
Could you clean a little what should be in the view url? As for the contextkey 
is indeed a leftover from the past in the links from the platform. 

Perhaps (for now at least and until all the platform links change and given 
that expresser code is more flexible)  we could be a bit robust for now and if 
there are both take only the pkmap into account (links outside the platform 
wouldn't have pkmaps anyway).

Original comment by mavrikis@gmail.com on 30 Jun 2012 at 6:41

GoogleCodeExporter commented 9 years ago 
The view URL sent in the referable object XML is complete. Nothing needs to be 
added. Nor should anything. Recall that a view URL could be simply a JPG or the 
like.

Original comment by ToonT...@gmail.com on 1 Jul 2012 at 2:16

GoogleCodeExporter commented 9 years ago 
Should this be closed or given a new owner? The problem is not in eXpresser but 
whatever is adding extra parameters to the VIEW_URL.

Original comment by ToonT...@gmail.com on 7 Jul 2012 at 2:41

GoogleCodeExporter commented 9 years ago 
I don't know. Are you saying that the VIEW_URL that comes from eXpresser is 
clean but something adds it after? I am confused.

Original comment by mavrikis@gmail.com on 7 Jul 2012 at 9:46

GoogleCodeExporter commented 9 years ago 
The VIEW_URL is constructed from the current URL with thumbnail=..., time=..., 
and the like added. See the definition of Utilities.referableObjectProperties

There are lots of parameters that are ignored, but that is OK. But Metafora 
home shouldn't add anything to the VIEW_URL (but it should to the 
REFERENCE_URL).

Original comment by ToonT...@gmail.com on 8 Jul 2012 at 2:17

GoogleCodeExporter commented 9 years ago 
We may be going a little in circles here due to simultaneous changes and other 
issues that are sometimes in the test sometimes in the proper system. Apologies 
this is dragging too long but regardless home is not designed (afaik) to add 
things to REFERENCE_URL. 

We should close this issue and file separate small ones. Until we understand 
them better: 

(a) We need to discuss that when reference url is clicked home needs to add the 
user. This could be a long-term proper way of doing things.

(b) But regardless, first eXpresser should add ptmapid and ptnodeid when these 
are set. Right? It wasn't doing that because the model is accesses with the 
copy url that has the context/model if understand right. But this is 
problematic now with the ptmapid and ptnodeid and somehow also when the model 
is accessed add a contextkey of the current user.

Could you investigate issues related to (b) first? We 'll get there eventually.

Original comment by mavrikis@gmail.com on 9 Jul 2012 at 11:18

GoogleCodeExporter commented 9 years ago 
This particular issue is fixed. Some issues with the viewurl when lasad is in 
Metafora could have to do just with repainting. 

But this work revealed other issues e.g. Issue 147.

Original comment by mavrikis@gmail.com on 9 Jul 2012 at 11:59