[kepler-users] Bug with saving actors to library

[Chad Berkley]

The functionality is a bit different in the SVN head (soon to be 2.0). 
To put an actor/workflow/kar in the library, you just right click on it, 
say "save as kar" then save it in the kepler/workflows directory.  This 
directory will probably be moved to the ~/KeplerData directory, but the 
functionality will be the same.

Once you save it in that directory, the actor/workflow/kar shows up in 
the library automatically.  To test this, I did the following:

1) drag any actor to the canvas
2) change it's name
3) rt. click and "save as kar"
4) save it in the workflows directory
5) search the library for the new name

chad


Christopher Brooks wrote:
> Hi Michal,
> Ok, the "Save in Library" menu choice is present in
> Kepler-1.0.0 and I can reproduce the bug in Kepler-1.0.0.
> 
> There have been many changes since Kepler-1.0.0 came out.
> I'm guessing that some of these changes may fix the problem in the svn 
> head.
> I can't replicate this problem in the svn head.   I don't have a
> "Save in Library" menu choice in the svn head.
> 
> Does anyone else have "Save in Library" in the svn head?
> This is all a bit mysterious.
> 
> _Christopher
> 
> On 2/2/10 1:18 AM, Michal Owsiak wrote:
>> Hello Christopher,
>>
>> I can confirm the same bug in Mac OS's version of Kepler-1.0.0
>>
>> As you can see, "Save in Library" is available to me.
>>
>> I have used regular installation package from the following location:
>>
>> http://kepler-project.org/dist/Kepler-1.0.0/kepler-mac-1.0.0.jar
>> (without R).
>>
>> After installing this version (into both "/Applications/Kepler-1.0.0"
>> and /Users/.../Applications/Kepler-1.0.0) I am able to reproduce Tomek's
>> error.
>>
>> Cheers
>>
>> Michal
>>
>>
>>> Hi Christopher,
>>>
>>> I am using Kepler on Linux. The "Save in Library" position in menu is
>>> in both
>>> 1.0.0 version and with the newest one from svn. Please see the 
>>> screenshot
>>> attached. I will have a possibility to check the bug existence in a
>>> clean tree
>>> on Thursday.
>>>
>>> Also, please note, that this error occurs not only with such simple
>>> example. I
>>> found it out in one of my complex composites, and just prepared a 
>>> minimal
>>> reproducible example to send it here on list :)
>>>
>>> In the real use case I introduced such relation<->relation links to
>>> improve
>>> readability of workflow. And this real use case for sure has other
>>> actors, ports,
>>> etc.
>>>
>>> Regards,
>>> Tomek
>>>
>>> On poniedzia�ek 01 luty 2010 at 18:00:38 Christopher Brooks wrote:
>>>> Hi Tomasz,
>>>> Strange, I don't have "Save in Library" in my Kepler configuration
>>>> (see attached).
>>>>
>>>> Are you running with a regular configuration? My tree is fairly recent
>>>> and updated today. I did "ant switch-to -Dsuite=kepler" to create the
>>>> tree. I have a slow connection today and tomorrow, so I can't check
>>>> out a
>>>> clean tree. Would you have the opportunity to check out a clean tree 
>>>> and
>>>> replicate the bug?
>>>>
>>>> I do have "Save in Library" in Vergil when running in a Ptolemy tree
>>>> outside of Kepler.
>>>>
>>>> I can't replicate the problem there either.
>>>>
>>>> There could easily be a bug here, there have been issues with 
>>>> composites
>>>> that contain no actors.
>>>>
>>>> _Christopher
>>>>
>>>> On 2/1/10 8:41 AM, Tomasz Ĺťok wrote:
>>>>> Hi Christopher,
>>>>>
>>>>> The problem occurred when composite actor was saved in a library,
>>>>> not in
>>>>> a KAR file. I selected the actor, clicked right button and chose
>>>>> "Save in
>>>>> library..." in the popup menu.
>>>>>
>>>>> Regards,
>>>>> Tomek
>>>>>
>>>>> On poniedzia�ek 01 luty 2010 at 15:49:31 Christopher Brooks wrote:
>>>>>> Hi Tomasz,
>>>>>> I can't seem to reproduce this. I'm using the Kepler head under Mac
>>>>>> OS.
>>>>>> I used "Save As (KAR)..." to save the composite and it has the
>>>>>> two relations and the link between them.
>>>>>>
>>>>>> I'm probably doing something wrong?
>>>>>>
>>>>>> _Christopher
>>>>>>
>>>>>> On 2/1/10 6:24 AM, Tomasz Ĺťok wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I've just discovered a bug with actor exporting. The process of
>>>>>>> saving
>>>>>>> an actor to library does not export connections between relations.
>>>>>>> Everything else is saved correctly (eg. port<-> relation, 
>>>>>>> constant<->
>>>>>>> relation), but relation<-> relation is not exported
>>>>>>>
>>>>>>> To reproduce:
>>>>>>> 1. Create a composite actor
>>>>>>> 2. Inside it, create two relations (control+click)
>>>>>>> 3. Connect them and save this actor in the library
>>>>>>> 4. The connection between relations was not saved. When you put the
>>>>>>> actor from library, it is missing.
>>>>>>>
>>>>>>> I have tested in on Kepler 1.0.0 and on the HEAD update from svn
>>>>>>> repository
>>>>>>>
>>>>>>> In the attachment there is a workflow with only one such composite
>>>>>>> actor, containing only connection between relations. Please try to
>>>>>>> save
>>>>>>> this actor in the library and reuse it from there to observe the
>>>>>>> incorrect behaviour.
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Tomek
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Kepler-users mailing list
>>>> Kepler-users at kepler-project.org
>>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>
>>
>>
>>
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>