jsynthlib-devel

[Jsynthlib-devel] Re: [jsynthlib-dev] JSynthLib-0.19-pre1is released.

[Hiroo H. <hir...@co...>]

> But currently the patch<=>device/driver assignment isn't very
> usefull yet.  I think we should store this assignment in the
> core.IPatch class. But not as deviceNum/driverNum.

> I preferr a human readable format like "YamahaDX7/singleVoice". This
> would also allow JSynthLib to load the required device if it isn't
> already loaded.

> If we store this information while requesting a patch, creating a
> new patch or load/save a "patchlib" file the "p.chooseDriver()" call
> isn't needed furthermore. Only an import of sysex files would need
> the p.chooseDriver() call.

Patch object does not have to have the human readable format string.
But I agree with you the string should be saved in Patch data in
storage.  I guess this also help the XML driver.

But we have the following problem you wrote.

> In the past I tried to store this information in the "patchlib"
> file, but this wasn't compatible with the current file format. So I
> let it.

We need a extendable file format.
My take is a combination of binary Sysex data and XML as I wrote before.
-- 
Hiroo Hayashi

[Jsynthlib-devel] How to create a release.

[Hiroo H. <hir...@co...>]

> BTW, do you have any idea how to move the midiprovider directory from
> "cvs.sourceforge.net:/cvsroot/jsynthlib/JSynthLib" to
> "cvs.sourceforge.net:/cvsroot/jsynthlib/midiprovider"?

> This would prevent downloading the midiprovider with a checkout of
> JSynthLib.  But maybe I should ask the guys from sourceforge.

We cannot remove a directory from CVS repository.  Because we have to
be able to recreate (check out) old directory structure.  But as I show
you a CVS manual before (I've put it at the bottom of this mail), by
doing 'cvs update' with -P option cvs does not create a empty directory.

> We don't get many bugreports in the past and and I like to create a
> 0.19-pre2 release with all fixes of the last time.  How I can upload
> a new release to the sourceforge file section?

You are one of administrator.  By going FILE section you can upload as
I could.  It's well designed.  You don't need my bad English
explanation:-)  If you have question, let me know.

FYI, I did the following steps to create jar file.

------------------------------------------------------------------------
cd "branch_0_19 directory"
cvs update -r
# add tag
cvs tag rel_0_19_pre2
# create directories without CVS directories
cvs export -r rel_0_19_pre2 pre2
cd pre2
javac */*/*.java */*.java *.java
jar cmf misc/mainClass JSynthLib-0.19-pre2.jar @misc/MANIFEST
------------------------------------------------------------------------

Here is from CVS info manual.

Removing directories
====================

   In concept removing directories is somewhat similar to removing
files--you want the directory to not exist in your current working
directories, but you also want to be able to retrieve old releases in
which the directory existed.

   The way that you remove a directory is to remove all the files in
it.  You don't remove the directory itself; there is no way to do that.
Instead you specify the `-P' option to `cvs update' or `cvs checkout',
which will cause CVS to remove empty directories from working
directories.  (Note that `cvs export' always removes empty directories.)
Probably the best way to do this is to always specify `-P'; if you want
an empty directory then put a dummy file (for example `.keepme') in it
to prevent `-P' from removing it.

   Note that `-P' is implied by the `-r' or `-D' options of `checkout'.
This way CVS will be able to correctly create the directory or not
depending on whether the particular version you are checking out
contains any files in that directory.
-- 
Hiroo Hayashi

Re: [Jsynthlib-devel] How to create a release.

[<tt_...@gm...>]

Hi Hiroo,

Hiroo Hayashi wrote:
>>BTW, do you have any idea how to move the midiprovider directory from
>>"cvs.sourceforge.net:/cvsroot/jsynthlib/JSynthLib" to
>>"cvs.sourceforge.net:/cvsroot/jsynthlib/midiprovider"?
> 
> 
>>This would prevent downloading the midiprovider with a checkout of
>>JSynthLib.  But maybe I should ask the guys from sourceforge.
> 
> 
> We cannot remove a directory from CVS repository.  Because we have to
> be able to recreate (check out) old directory structure.  But as I show
> you a CVS manual before (I've put it at the bottom of this mail), by
> doing 'cvs update' with -P option cvs does not create a empty directory.

Sorry, my question wasn't clear enough.
I know the problem with removing directories and this wasn't my topic.

I meant another point:
If someone want to checkout JSynthLib he type the command:
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/jsynthlib co JSynthLib.

Now I like to move the midiprovider to an own directory in the jsynthlib path,
so a user can checkout midiprovider with a command like:
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/jsynthlib co midiprovider.

For this it's necessary to create the path /cvsroot/jsynthlib/midiprovider.
My hope was that you have an idea how to create this path resp. if this means to create a new project.

Do you have any ideas?

>>We don't get many bugreports in the past and and I like to create a
>>0.19-pre2 release with all fixes of the last time.  How I can upload
>>a new release to the sourceforge file section?
> 
> 
> You are one of administrator.  By going FILE section you can upload as
> I could.  It's well designed.  You don't need my bad English
> explanation:-)  If you have question, let me know.
> 
> FYI, I did the following steps to create jar file.
> 
> ------------------------------------------------------------------------
> cd "branch_0_19 directory"
> cvs update -r
> # add tag
> cvs tag rel_0_19_pre2
> # create directories without CVS directories
> cvs export -r rel_0_19_pre2 pre2
> cd pre2
> javac */*/*.java */*.java *.java
> jar cmf misc/mainClass JSynthLib-0.19-pre2.jar @misc/MANIFEST
> ------------------------------------------------------------------------

Yes, this was my hope. A concrete tip for making new releases.
I will take a look at the upload function in the FILE section.

Thanks and bye
Torsten

Re: [Jsynthlib-devel] How to create a release.

[Hiroo H. <hir...@co...>]

I forgot one thing.

Edit PatchEdit.VERSION at first.

> ------------------------------------------------------------------------
> cd "branch_0_19 directory"
> cvs update -r
> # add tag
> cvs tag rel_0_19_pre2
> # create directories without CVS directories
> cvs export -r rel_0_19_pre2 pre2
> cd pre2
> javac */*/*.java */*.java *.java
> jar cmf misc/mainClass JSynthLib-0.19-pre2.jar @misc/MANIFEST
> ------------------------------------------------------------------------

At this point I have no idea for your question about CVS, sorry.
-- 
Hiroo Hayashi

Re: [Jsynthlib-devel] How to create a release.

[<tt_...@gm...>]

Hi Hiroo,

while following your instructions I run into some trouble.

Is it possible that you misspelled the mentioned line?

Hiroo Hayashi wrote:
> I forgot one thing.
> 
> Edit PatchEdit.VERSION at first.
> 
> 
>>------------------------------------------------------------------------
>>cd "branch_0_19 directory"
>>cvs update -r
>># add tag
>>cvs tag rel_0_19_pre2
>># create directories without CVS directories
>>cvs export -r rel_0_19_pre2 pre2

cvs export -r rel_0_19_pre2 -d pre2 JSynthLib

>>cd pre2
>>javac */*/*.java */*.java *.java
>>jar cmf misc/mainClass JSynthLib-0.19-pre2.jar @misc/MANIFEST
>>------------------------------------------------------------------------

Thanks and bye
Torsten