@Maxim OK! I will update the demo by tomorrow, if you have some
additionally commits later, its okay to test them locally and not on a
public instance. But we should have a public instance running with the new
red5 code for a certain period of time.

@German & Timur
I've fixed the first Reference issue in r4592, I also started to rename
some of the duplicated lzx-Classes now. Some of the SWF10 lzx classes seem
to have no reference in the application at all. We should try to clean up
those that are not referenced and avoid duplicate classnames.
I will start looking at the other AS3 reference errors now.

Sebastian

2011/11/19 Maxim Solodovnik <[email protected]>

> Hello Sebastian,
>
> I would like to finish room polls (today or tomorrow)
> and "default language" feature (hopefully tomorrow)
> After that we can start testing the trunk.
>
> 2011/11/19 [email protected] <[email protected]>
>
> Hi,
>>
>> the a/v integration has some problem on OSX. At least on my MAC device.
>> The effect is that the window to select your device does never close.
>> I think the problem is that my Mac has some issues with the Camera, and
>> Line 136 in the new editRecordStream.lzx (AS3)
>> var _camera = Camera.getCamera(valCam);
>> does return null, I can see sth like:
>> Error @swf10/video/editRecordStream.lzx~124 TypeError: Error #1009
>>
>> Other issues:
>> 1) The green dot is little bit fuzzy, it does not flash when it should
>> and sometimes stays forever green. I think I have fixed something in this
>> activity-meter, also the video views in trunk look different, they have a
>> full activity meter in each video view. We will need to bring those changes
>> into your branch.
>>
>> 2) If you choose "audio-only" the video-view gets smaller, if you then
>> re-sync and choose "audio And video" the video-view doesn't enlarge anymore
>> and you cannot see your video.
>>
>> 3) I did not start yet to modify the ScopeApplicationAdapter to modify
>> the RoomClient session handling. This is propably sth that I will be able
>> to fix by this weekend.
>>
>> 4) There are reference errors in the video view dialog:
>> ERROR @swf10/base/remote/baseVideoStreamDevice.lzx≈57: ReferenceError:
>> Error #1069
>> ERROR @swf10/base/remote/baseVideoStreamDevice.lzx≈73: ReferenceError:
>> Error #1069
>> I guess stats.info is null or sth like that.
>>
>> 5) Other Issues in AS3:
>> ERROR @swf10/base/remote/baseVideoStream.lzx≈52: ArgumentError: Error
>> #2126
>> ERROR @swf10/base/remote/baseVideoStream.lzx≈88: TypeError: Error #1009
>> => errors in the methods: createStream and playStream
>>
>> Those NullPointer and Reference Errors in AS3 will stop executing the
>> code at those methods/classes. Different from AS2 where the execution
>> throws the error but still continues. So ... as it was possible to ignore
>> some of the debugger exceptions in the Laszlo Debugger previously, doing
>> that now in AS3 can lead to unexpected side effects.
>>
>> About the Roadmap to merge this to trunk:
>> We will release current trunk and then merge the video components to it.
>> I will start testing trunk by tomorrow and update the demo platform.
>> Demo has to run for some days, so that we can be sure that there is no
>> issue with the new Red5 code.
>>
>> During this period those Issues in the video-components branch should be
>> fixed so that we can start thinking about the merging process.
>> I will try to fix the Session handling issues in the
>> ScopeApplicationAdapter.
>>
>> What do you think Maxim? You have been lately doing lot of changes to
>> trunk, you think its ready for testing or are there issues you would like
>> to fix beforehand?
>>
>> Sebastian
>>
>>
>> 2011/11/18 [email protected] <[email protected]>
>>
>>> Hi,
>>>
>>> your modifications look quite good, I have been able to run the code et
>>> cetera.
>>>
>>> I don't see any big blockers for now.
>>> But actually from my point of view the goal should be the transform the
>>> whole codebase to AS3 then.
>>> I will continue testing this weekend, if things work out well we might
>>> be able to merge this to trunk by next week.
>>>
>>> Sebastian
>>>
>>> 2011/11/18 [email protected] <[email protected]>
>>>
>>> No not yet,
>>>> I will have some time by tomorrow and give you feedback.
>>>>
>>>> Sebastian
>>>>
>>>>
>>>> 2011/11/18 German Grekhov <[email protected]>
>>>>
>>>>> Hello, Sebastian.
>>>>>
>>>>> So, have you already seen and tested our branch? What is your opinion
>>>>> about it?
>>>>>
>>>>> German.
>>>>>
>>>>>
>>>>> 17 ноября 2011 г. 14:44 пользователь [email protected] <
>>>>> [email protected]> написал:
>>>>>
>>>>> okay,
>>>>>>
>>>>>> well I can live with that one. The thing is that actually in AS3 the
>>>>>> flash player can freeze if you have a nullpointer exception. So you might
>>>>>> notice that something is wrong quite fast :)
>>>>>>
>>>>>> Btw: We should also try to use other codecs then using the new Video
>>>>>> components. For example Speex for the Audio. I think it might get easier 
>>>>>> to
>>>>>> encode and do some integration using speex then nellymoser.
>>>>>>
>>>>>> Sebastian
>>>>>>
>>>>>>
>>>>>> 2011/11/17 German Grekhov <[email protected]>
>>>>>>
>>>>>>> Hello, Sebastian. Sorry for long response.
>>>>>>> No, we haven't done any performance tests.
>>>>>>>
>>>>>>> Yes, OpenLaszlo Debugger still works. There are two debuggers now.
>>>>>>> One is for main swf8 and another one is for video component swf10.
>>>>>>>
>>>>>>> But there is one problem of swf10. Using action script 3 doesn't
>>>>>>> allow to see errors like NullPointerException and others direclty. It 
>>>>>>> means
>>>>>>> that you could see only a method that contains a error and what the 
>>>>>>> error
>>>>>>> it is, but not the code line number with this error. It is only about
>>>>>>> swf10. Swf8 is still ok.
>>>>>>>
>>>>>>> German.
>>>>>>>
>>>>>>>
>>>>>>> 14 ноября 2011 г. 18:42 пользователь [email protected] <
>>>>>>> [email protected]> написал:
>>>>>>>
>>>>>>> Ok,
>>>>>>>>
>>>>>>>> I hope to find some time by the end of this week to work on this.
>>>>>>>>
>>>>>>>> Have you tried to run some test with the application in terms of
>>>>>>>> performance ( I mean for example the whiteboard performance ).
>>>>>>>> Does the OpenLaszlo Debugger still work? I would like to have its
>>>>>>>> ability to show NullPointerException in the JavaScript code.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Sebastian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2011/11/10 Тимур Тлеукенов <[email protected]>
>>>>>>>>
>>>>>>>>> Hello Sebastian,
>>>>>>>>>
>>>>>>>>> Yes, all the RPC calls go through SWF8. NetConnection of AS3
>>>>>>>>> component
>>>>>>>>> used only for transfering video and audio.
>>>>>>>>> This was done to temporary avoid changes in the server side of
>>>>>>>>> application, because in most cases the server identifies the
>>>>>>>>> client by
>>>>>>>>> connection\stream ID.
>>>>>>>>> Problem with the "registerMethods" isn't solved, so we use this
>>>>>>>>> workaround with SWF8.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Timur
>>>>>>>>>
>>>>>>>>> 2011/11/9 German Grekhov <[email protected]>:
>>>>>>>>> > Тимур, ответь Себастьяну.
>>>>>>>>> > про setMicMuted: я его убрал уже оттуда
>>>>>>>>> >
>>>>>>>>> > ---------- Forwarded message ----------
>>>>>>>>> > From: [email protected] <[email protected]>
>>>>>>>>> > Date: 2011/11/9
>>>>>>>>> > Subject: Re: Separate video component
>>>>>>>>> > To: German Grekhov <[email protected]>
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > btw:
>>>>>>>>> >
>>>>>>>>> > I had no chance to look at it yet just for my understanding:
>>>>>>>>> >
>>>>>>>>> > You did refactor the current rtmpConnection to work with AS3
>>>>>>>>> right?
>>>>>>>>> > When I was doing that my problem was that the "registerMethods"
>>>>>>>>> call did not
>>>>>>>>> > work, so when the server did call a method in the client that
>>>>>>>>> failed
>>>>>>>>> > constantly.
>>>>>>>>> >
>>>>>>>>> > Did you solve that one? As far as I do understand you don't use
>>>>>>>>> the
>>>>>>>>> > NetConnection of the AS3 component for receiving messages. There
>>>>>>>>> is just a
>>>>>>>>> > single call in the AS3 version of the hibRtmpConnection
>>>>>>>>> "switchMicMuted" and
>>>>>>>>> > this one seems having a problem according to the Debug logs in
>>>>>>>>> the
>>>>>>>>> > Return-Body of the method.
>>>>>>>>> >
>>>>>>>>> > So all RPC calls of Openmeetings go through the SWF8 version
>>>>>>>>> that gets
>>>>>>>>> > loaded into the SWF10 application. The SWF8 application that
>>>>>>>>> uses a
>>>>>>>>> > LocalConnection to forward the events to the SWF10 app.
>>>>>>>>> >
>>>>>>>>> > I think this workaround is okay to get started, however it
>>>>>>>>> should be our
>>>>>>>>> > goal to for the future roadmap to get the rtmp-messaging working
>>>>>>>>> in the
>>>>>>>>> > SWF10 runtime.
>>>>>>>>> >
>>>>>>>>> > Sebastian
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sebastian Wagner
>>>>>>>> http://www.openmeetings.de
>>>>>>>> http://www.webbase-design.de
>>>>>>>> http://www.wagner-sebastian.com
>>>>>>>> [email protected]
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sebastian Wagner
>>>>>> http://www.openmeetings.de
>>>>>> http://www.webbase-design.de
>>>>>> http://www.wagner-sebastian.com
>>>>>> [email protected]
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sebastian Wagner
>>>> http://www.openmeetings.de
>>>> http://www.webbase-design.de
>>>> http://www.wagner-sebastian.com
>>>> [email protected]
>>>>
>>>
>>>
>>>
>>> --
>>> Sebastian Wagner
>>> http://www.openmeetings.de
>>> http://www.webbase-design.de
>>> http://www.wagner-sebastian.com
>>> [email protected]
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> [email protected]
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"OpenMeetings developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/openmeetings-dev?hl=en.

Reply via email to