[Freeciv-Dev] [patch #3020] "Soundset" category for modpack installer

[Jacob Nevins]

Update of patch #3020 (project freeciv):

  Status:  Ready For Test => Done   
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

[Freeciv-Dev] [patch #3020] "Soundset" category for modpack installer

[Jacob Nevins]

Update of patch #3020 (project freeciv):

  Status:None => Ready For Test 
 Assigned to:None => jtn

___

Follow-up Comment #2:

> I'm strongly for keeping soundsets in version specific 
> directory.
OK. Makes the patch simpler...

(I suppose the proper way of avoiding users having to gratuitously re-install
add-ons for new Freeciv versions in this scenario would be to have a
file-dependent search path, so that e.g. soundsets would look in both /2.4/
and /2.3/. But our file search paths are already beyond my simple
understanding, so I'm not really in favour of even more complication.)

> Actually, if we strictly follow what was decided about 
> capability strings before 2.3, 2.4 soundsets will be 
> incompatible with 2.3 ones, just because capability string is 
> changed. Obviously that capability string change makes no 
> sense, so I think we should omit it. 
Definitely. As I thought I muttered for patch #2154, but now can't find: we
have little enough momentum getting add-on content from the community without
making creators jump through needless hoops every couple of years just to keep
their add-ons working.

> I remembered that there already is soundset category, but 
> maybe it was just something I meant to do.
Can't see it, so here's the patch.

(file #14437)
___

Additional Item Attachment:

File name: trunk-S2_4-modinst-soundset.diff Size:0 KB


___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

[Freeciv-Dev] [patch #3020] "Soundset" category for modpack installer

[Marko Lindqvist]

Update of patch #3020 (project freeciv):

 Planned Release: => 2.4.0, 2.5.0   

___

Follow-up Comment #1:

>From techincal perspective soundsets are equivalent to tilesets. When ever
there is development in respective code, there will be compatibility break. It
just happens that in practice we've had not much development in sound front.
Scenarios are different since there we maintain backward compatibility. So, to
avoid nightmare when there *is* some sound capability development, I'm
strongly for keeping soundsets in version specific directory.

Actually, if we strictly follow what was decided about capability strings
before 2.3, 2.4 soundsets will be incompatible with 2.3 ones, just because
capability string is changed. Obviously that capability string change makes no
sense, so I think we should omit it.

I remembered that there already is soundset category, but maybe it was just
something I meant to do.

___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

[Freeciv-Dev] [patch #3020] "Soundset" category for modpack installer

[Jacob Nevins]

URL:
  

 Summary: "Soundset" category for modpack installer
 Project: Freeciv
Submitted by: jtn
Submitted on: Sat Nov  5 19:09:47 2011
Category: module installer
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: 

___

Details:

Currently, I've put "freesounds" in the modpack installer as a "Modpack", but
that seems wrong since it is just a sound scheme. It would be easy to add a
new category "Soundset", although it would only be cosmetic.

While I think about it: more significantly, soundsets like this go in the
version-specific subdirectory (e.g., ~/.freeciv/2.3/). But soundsets aren't
heavily version-dependent in practice; I have 2.3 and trunk versions symlinked
to the same place.

So, perhaps soundsets should live in a versionless directory, as scenarios
do. (Perhaps they could be searched in the versioned subdirectory too.)

Opinions?




___

Reply to this item at:

  

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev