Re: java build problem...

Joern Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> Jörn Nettingsmeier schrieb:
>>> hi *!
>>>
>>> i'm trying to update the Instantiator class. i
have it working, but
>>> there are a number of hard-coded strings in
there i'd like to get rid
>>> of. so i'd like to do:

[...]

> is this build problem i'm seeing part of the
"fundamental problem" you
> describe?

Yes, this is exactly the fundamental problem.

> if so, can you give details?

The location and content of the publication.xconf file is
private
information of the PublicationConfiguration. They are
implementation
details, therefore the PublicationConfiguration is not part
of the
Lenya API. You can't compile anything which accesses this
class.
This protects you from losing binary backwards compatibility
when the
syntax of publication.xconf changes.

If you want to configure a publication, this should be done
using the
Lenya API. But ATM we don't provide these configuration
options
(i.e., there are no corresponding setters in the Publication
interface).

There are two options:

1) add these setters now and everything which that implies

2) leave the duplicated strings in the Instantiator until
   we have these setters


-- Andreas


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Do not reply to this via email (we are currently unable to
handle email
responses and they get discarded).  You can add comments to
this bug at
http
://bugzilla.gnome.org/show_bug.cgi?id=412597

  GStreamer | gst-plugins-good | Ver: HEAD CVS

           Summary: Simplify GstSunAudioSrc
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: opensolaris
            Status: UNCONFIRMED
          Severity: trivial
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugslists.sourceforge.net
        ReportedBy: julien.puydtlaposte.net
         QAContact: gstreamer-bugslists.sourceforge.net
                CC: brian.cameronsun.com
     GNOME version: Unspecified
   GNOME milestone: Unspecified


After an initial proposition to add GstPropertyProbe to
GstSunAudioSrc and
GstSunAudioSink (reported as an enhancement bug), a (mail)
discussion with
Brian prompted the realisation that it made little sense to
even have a
"device-name" property for GstSunAudioSrc.

Since GstSunAudioSink lacks this property, it sounds saner
to remove this
property from GstSunAudioSrc, for more consistency.

(The other bug was tagged WONTFIX.)


-- 
Configure bugmail: htt
p://bugzilla.gnome.org/userprefs.cgi?tab=email

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
gstreamer-bugs mailing list
gstreamer-bugslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gstreame
r-bugs

Andreas Hartmann wrote:
> Joern Nettingsmeier schrieb:
>> Andreas Hartmann wrote:
>>> Jörn Nettingsmeier schrieb:
>>>> hi *!
>>>>
>>>> i'm trying to update the Instantiator
class. i have it working, but
>>>> there are a number of hard-coded strings in
there i'd like to get rid
>>>> of. so i'd like to do:
> 
> [...]
> 
>> is this build problem i'm seeing part of the
"fundamental problem" you
>> describe?
> 
> Yes, this is exactly the fundamental problem.
> 
>> if so, can you give details?
> 
> The location and content of the publication.xconf file
is private
> information of the PublicationConfiguration.

doh. of course, "private static final..."
/me hides under a stone.

> They are implementation
> details, therefore the PublicationConfiguration is not
part of the
> Lenya API. You can't compile anything which accesses
this class.
> This protects you from losing binary backwards
compatibility when the
> syntax of publication.xconf changes.
> 
> If you want to configure a publication, this should be
done using the
> Lenya API. But ATM we don't provide these configuration
options
> (i.e., there are no corresponding setters in the
Publication interface).
> 
> There are two options:
> 
> 1) add these setters now and everything which that
implies
> 
> 2) leave the duplicated strings in the Instantiator
until
>    we have these setters

should these setters go into Publication or rather 
PublicationConfiguration? anyways, looks like post-1.4
stuff.

for now, i wonder whether it would be the lesser evil to
make the string 
constants in PublicationConfiguration public? like "if
you want to screw 
around on my turf, at least have the manners to do it my
way...".


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org