[clam-devel] annotator, songbird and the playlist
Jun Wang
wangjun at icst.pku.edu.cn
Sun Jul 4 22:10:58 PDT 2010
Hola, Xavier Serra,
I'm Jun. I used to work on a project about annotator. I was told that you're a student currently working on a better python integration of the annotator, are you?
Recently I played with Songbird and found it very interesting as it supports the metadata annotation by listener as well as the web. If you're also interested, we may talk about it sometime (I mean the open source part).
Saludos da Peking ! Ciaooo !
Jun
----- Original Message -----
From: <clam-devel-request at lists.clam-project.org>
To: <clam-devel at lists.clam-project.org>
Sent: Friday, July 02, 2010 12:12 AM
Subject: clam-devel Digest, Vol 44, Issue 1
> Send clam-devel mailing list submissions to
> clam-devel at lists.clam-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org
>
> or, via email, send a message with subject or body 'help' to
> clam-devel-request at lists.clam-project.org
>
> You can reach the person managing the list at
> clam-devel-owner at lists.clam-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of clam-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: Changes to NetworkEditor (Xavier Serra)
> 2. Re: Changes to NetworkEditor (Natanael Olaiz)
> 3. Re: Changes to NetworkEditor (Xavier Serra)
> 4. Re: Changes to NetworkEditor (David Garc?a Garz?n)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Jun 2010 21:13:03 +0200
> From: Xavier Serra <xvr.serra at gmail.com>
> To: CLAM development list <clam-devel at lists.clam-project.org>
> Subject: Re: [clam-devel] Changes to NetworkEditor
> Message-ID: <1A54F788-A95A-41BD-8D8E-5EFB60498596 at gmail.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
> On Jun 30, 2010, at 5:01 PM, David Garc?a Garz?n wrote:
>
>> On Monday 21 June 2010 17:14:57 Xavier Serra wrote:
>>> Hi guys,
>>> I'm Xavi Serra, an student at UPF doing his final project for CLAM with
>>> David.
>>>
>>> We intend to extend the funcionality of the NetworkEditor. The first
>>> thing we are doing is to detect when a network file is outdated and
>>> automatically throw clamRefactor (asking permission to the user to do
>>> so).
>>>
>>> I'm sending the first patch with some modifications, nothing serious
>>> yet. It only checks the network file version and asks the user if he
>>> wants to update the file (without actually doing so). Files without the
>>> attribute @clamVersion are treated as old.
>>>
>>> Bye!
>>>
>>> Xavier Serra
>>
>> Committed after some refactorings we did yesterday together. Now a dialog is
>> shown on version mismatch and in the case of a network of an older version it
>> gives you the option to upgrade the network by using clamrefactor before
>> loading it. The upgrade is still dummy, but Xavi is already working on it.
>>
>> Xavi, some screenshots would be helpful so that other developers can do
>> comments on usability aspects. Could you put them on the wiki?
>>
> Done.
>
> It would be great too if you guys could give some feedback about usability issues. I think the messages are now, after David's modification, more clear but I'd prefer more opinions.
>
> Xavi Serra
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 30 Jun 2010 23:18:53 +0200
> From: Natanael Olaiz <nolaiz at gmail.com>
> To: CLAM development list <clam-devel at lists.clam-project.org>
> Subject: Re: [clam-devel] Changes to NetworkEditor
> Message-ID: <4C2BB4BD.4090307 at gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Hi,
>
> El 06/30/2010 09:13 PM, Xavier Serra escribi?:
>> On Jun 30, 2010, at 5:01 PM, David Garc?a Garz?n wrote:
>>
>>> On Monday 21 June 2010 17:14:57 Xavier Serra wrote:
>>>
>>>> Hi guys,
>>>> I'm Xavi Serra, an student at UPF doing his final project for CLAM with
>>>> David.
>>>>
>>>> We intend to extend the funcionality of the NetworkEditor. The first
>>>> thing we are doing is to detect when a network file is outdated and
>>>> automatically throw clamRefactor (asking permission to the user to do
>>>> so).
>>>>
>>>> [snip]
>>>>
>>>> Xavier Serra
>>>>
>>> Committed after some refactorings we did yesterday together. Now a dialog is
>>> shown on version mismatch and in the case of a network of an older version it
>>> gives you the option to upgrade the network by using clamrefactor before
>>> loading it. The upgrade is still dummy, but Xavi is already working on it.
>>>
>>> Xavi, some screenshots would be helpful so that other developers can do
>>> comments on usability aspects. Could you put them on the wiki?
>>>
>>>
>> Done.
>>
>> It would be great too if you guys could give some feedback about usability issues. I think the messages are now, after David's modification, more clear but I'd prefer more opinions.
>>
>>
> The messages are clear to me.
>
> But I have some questions:
>
> 1- The clamVersion attribute did always existed on the clam network
> files? (I cannot found it in the CHANGES log) If not, there are
> probably no clam networks so much outdated being used... but what would
> happens if it doesn't exist? From
> http://doc.trolltech.com/4.5/qxmlquery.html#evaluateTo-4 : "If output is
> null behavior is undefined."
>
> 2- What would be the behavior in case of different versions? I think
> that checking the version number is OK as a first test of possible
> conflict between releases, but the needed changes and the definitely
> tests should be done looking in a migrationScript file or something like
> that. How we would deal with the different migrationScripts that we have
> in the core and different plugins? We would include all of them in the
> NetworkEditor to make such a test?
>
> 3- David: do you think that it would be difficult to put the interface
> to check the network version on the CLAM::XMLStorage class? I know that
> this improvement and interface to solve the version conflict is
> inherent to the NetworkEditor, but CLAM::XMLStorage would not be the
> ideal place to just check the version? Maybe returning diferent error
> codes on the Restore...
>
>
>
> If we maintain updated the migrationScript(s) file(s), this would be a
> very nice tool. :)
>
>
> Best regards,
> Natanael.
>
>> Xavi Serra
>>
>> _______________________________________________
>> clam-devel mailing list
>> clam-devel at lists.clam-project.org
>> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org
>>
>>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20100630/baf8af67/attachment-0001.htm>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 1 Jul 2010 00:17:56 +0200
> From: Xavier Serra <xvr.serra at gmail.com>
> To: CLAM development list <clam-devel at lists.clam-project.org>
> Subject: Re: [clam-devel] Changes to NetworkEditor
> Message-ID: <2C216FB2-8373-4995-B2FA-AB2870BFC298 at gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> On Jun 30, 2010, at 11:18 PM, Natanael Olaiz wrote:
>
>> Hi,
>>
>> El 06/30/2010 09:13 PM, Xavier Serra escribi?:
>>>
>>> On Jun 30, 2010, at 5:01 PM, David Garc?a Garz?n wrote:
>>>
>>>> On Monday 21 June 2010 17:14:57 Xavier Serra wrote:
>>>>
>>>>> Hi guys,
>>>>> I'm Xavi Serra, an student at UPF doing his final project for CLAM with
>>>>> David.
>>>>>
>>>>> We intend to extend the funcionality of the NetworkEditor. The first
>>>>> thing we are doing is to detect when a network file is outdated and
>>>>> automatically throw clamRefactor (asking permission to the user to do
>>>>> so).
>>>>>
>>>>> [snip]
>>>>>
>>>>> Xavier Serra
>>>>>
>>>> Committed after some refactorings we did yesterday together. Now a dialog is
>>>> shown on version mismatch and in the case of a network of an older version it
>>>> gives you the option to upgrade the network by using clamrefactor before
>>>> loading it. The upgrade is still dummy, but Xavi is already working on it.
>>>>
>>>> Xavi, some screenshots would be helpful so that other developers can do
>>>> comments on usability aspects. Could you put them on the wiki?
>>>>
>>>>
>>> Done.
>>>
>>> It would be great too if you guys could give some feedback about usability issues. I think the messages are now, after David's modification, more clear but I'd prefer more opinions.
>>>
>>>
>> The messages are clear to me.
>>
>> But I have some questions:
>>
>> 1- The clamVersion attribute did always existed on the clam network files? (I cannot found it in the CHANGES log) If not, there are probably no clam networks so much outdated being used... but what would happens if it doesn't exist? From http://doc.trolltech.com/4.5/qxmlquery.html#evaluateTo-4 : "If output is null behavior is undefined."
>>
>
> It didn't. Files without the attribute are treated as older file and thus, need conversion. David told me these files are pre-1.2 or so.
>
>> 2- What would be the behavior in case of different versions? I think that checking the version number is OK as a first test of possible conflict between releases, but the needed changes and the definitely tests should be done looking in a migrationScript file or something like that. How we would deal with the different migrationScripts that we have in the core and different plugins? We would include all of them in the NetworkEditor to make such a test?
>>
>
> When NetworkEditor detects that a file is older it will throw clamRefactor. The idea is to have a migrationScript file with the steps needed to go from version to version and use that when calling clamRefactor
>
>> 3- David: do you think that it would be difficult to put the interface to check the network version on the CLAM::XMLStorage class? I know that this improvement and interface to solve the version conflict is inherent to the NetworkEditor, but CLAM::XMLStorage would not be the ideal place to just check the version? Maybe returning diferent error codes on the Restore...
>>
>>
>>
>> If we maintain updated the migrationScript(s) file(s), this would be a very nice tool. :)
>>
>>
>> Best regards,
>> Natanael.
>>
>>> Xavi Serra
>>>
>>> _______________________________________________
>>> clam-devel mailing list
>>> clam-devel at lists.clam-project.org
>>> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org
>>>
>>>
>>
>> _______________________________________________
>> clam-devel mailing list
>> clam-devel at lists.clam-project.org
>> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20100701/6e0c95c8/attachment-0001.htm>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 1 Jul 2010 18:01:02 +0200
> From: David Garc?a Garz?n <david.garcia at barcelonamedia.org>
> To: <clam-devel at lists.clam-project.org>
> Subject: Re: [clam-devel] Changes to NetworkEditor
> Message-ID: <201007011801.02341.david.garcia at barcelonamedia.org>
> Content-Type: text/plain; charset="iso-8859-15"
>
>
>
> On Thursday 01 July 2010 00:17:56 Xavier Serra wrote:
>> On Jun 30, 2010, at 11:18 PM, Natanael Olaiz wrote:
>>
>> Hi,
>>
>> El 06/30/2010 09:13 PM, Xavier Serra escribi?:
>>
>> On Jun 30, 2010, at 5:01 PM, David Garc?a Garz?n wrote:
>>
>>
>> On Monday 21 June 2010 17:14:57 Xavier Serra wrote:
>>
>>
>> Hi guys,
>> I'm Xavi Serra, an student at UPF doing his final project for CLAM with
>> David.
>>
>> We intend to extend the funcionality of the NetworkEditor. The first
>> thing we are doing is to detect when a network file is outdated and
>> automatically throw clamRefactor (asking permission to the user to do
>> so).
>>
>> [snip]
>>
>> Xavier Serra
>>
>>
>> Committed after some refactorings we did yesterday together. Now a dialog
>> is shown on version mismatch and in the case of a network of an older
>> version it gives you the option to upgrade the network by using
>> clamrefactor before loading it. The upgrade is still dummy, but Xavi is
>> already working on it.
>>
>> Xavi, some screenshots would be helpful so that other developers can do
>> comments on usability aspects. Could you put them on the wiki?
>>
>>
>>
>> Done.
>>
>> It would be great too if you guys could give some feedback about usability
>> issues. I think the messages are now, after David's modification, more
>> clear but I'd prefer more opinions.
>>
>>
>>
>> The messages are clear to me.
>>
>> But I have some questions:
>>
>> 1- The clamVersion attribute did always existed on the clam network files?
>> (I cannot found it in the CHANGES log) If not, there are probably no clam
>> networks so much outdated being used... but what would happens if it
>> doesn't exist? From
>> http://doc.trolltech.com/4.5/qxmlquery.html#evaluateTo-4 : "If output is
>> null behavior is undefined."
>>
>>
>> It didn't. Files without the attribute are treated as older file and thus,
>> need conversion. David told me these files are pre-1.2 or so.
>
>
> Indeed first versioned version was 1.3.1 (unreleased) so unversioned versions
> should be considered 1.3.0 or earlier.
>
>> 2- What would be the behavior in case of different versions? I think that
>> checking the version number is OK as a first test of possible conflict
>> between releases, but the needed changes and the definitely tests should
>> be done looking in a migrationScript file or something like that. How we
>> would deal with the different migrationScripts that we have in the core
>> and different plugins? We would include all of them in the NetworkEditor
>> to make such a test?
>>
>>
>> When NetworkEditor detects that a file is older it will throw clamRefactor.
>> The idea is to have a migrationScript file with the steps needed to go
>> from version to version and use that when calling clamRefactor
>
>> 3- David: do you think that it would be difficult to put the interface to
>> check the network version on the CLAM::XMLStorage class? I know that this
>> improvement and interface to solve the version conflict is inherent to
>> the NetworkEditor, but CLAM::XMLStorage would not be the ideal place to
>> just check the version? Maybe returning diferent error codes on the
>> Restore...
>
> First approach was using XMLStorage to extract just the version in a double
> parsing like now, but that led us to some hard to solve problems. It's true
> that doing such a thing in the actual network loading would be more elegant it
> would need more insight from Xavi on the loading process. So i would left that
> for a future refactoring. Sorry for adding a new dependency but still is Qt.
>
> Besides that, current cases are:
> - Same, load as is
> - Older, warn, update and load (default)
> - Older, warn, load as is
> - Older, warn, cancel
> - Newer, warn, user cancels (default)
> - Newer, warn, user load it as is
>
> I am wondering whether, it is more usable that, in the case of older versions
> updating without asking. Something like:
> - Same, load as is
> - Older, update and load
> - Newer, warn, user cancels (default)
> - Newer, warn, user load it as is
>
> Any way, while the update is not finished, i would keep update as an option.
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> clam-devel mailing list
> clam-devel at lists.clam-project.org
> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org
>
>
> End of clam-devel Digest, Vol 44, Issue 1
> *****************************************
More information about the clam-devel
mailing list