Return-Path: Delivered-To: apmail-pivot-user-archive@www.apache.org Received: (qmail 8519 invoked from network); 12 Jan 2011 13:25:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2011 13:25:21 -0000 Received: (qmail 78580 invoked by uid 500); 12 Jan 2011 13:25:21 -0000 Delivered-To: apmail-pivot-user-archive@pivot.apache.org Received: (qmail 78417 invoked by uid 500); 12 Jan 2011 13:25:19 -0000 Mailing-List: contact user-help@pivot.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@pivot.apache.org Delivered-To: mailing list user@pivot.apache.org Received: (qmail 78409 invoked by uid 99); 12 Jan 2011 13:25:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jan 2011 13:25:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mabcastillo@gmail.com designates 74.125.82.182 as permitted sender) Received: from [74.125.82.182] (HELO mail-wy0-f182.google.com) (74.125.82.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jan 2011 13:25:09 +0000 Received: by wyf19 with SMTP id 19so544440wyf.13 for ; Wed, 12 Jan 2011 05:24:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Lk3Yel4T98iOfi6rhkyEPi0IsP/ZY8aYoo8Ee6HSbmQ=; b=wPG6AvW41+iDhyMrw4xA+AaQeq7Izs1u1SZP0Z5o//M1hSizJNDbnsQBn7Gf3Bfykl JgORymH1wtaGiIiuuBEhX0X6HCh1/OIWKK9hbKJBLcFnKxHjl4gnxgwfG/jUKK4JFZaD ahJAA5mA9BM5On/CnIBd9n1s0vCzitB6jRV/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=P6xF1h9z35GkmIuEHe4XlfO888384Ux8nCZiVVbH23WZSg8ySpGHJR13WFR7kaR1rS a0PD+zfiZe/FwFuxlgBlR/DioWB9aY1sQWCJOoW7o/k31RDXQLv8/OBI9813hzrL3JiH j6wGjBwp8pmA0DXzoUVzyeF3FMn9xGQIvDYdM= MIME-Version: 1.0 Received: by 10.216.173.18 with SMTP id u18mr811772wel.37.1294838689433; Wed, 12 Jan 2011 05:24:49 -0800 (PST) Received: by 10.216.88.204 with HTTP; Wed, 12 Jan 2011 05:24:49 -0800 (PST) In-Reply-To: References: Date: Wed, 12 Jan 2011 07:24:49 -0600 Message-ID: Subject: Re: Meaning of baseType parameter in BXMLSerializer#readObject(baseType, resourceName) From: Marco Castillo To: user@pivot.apache.org Content-Type: multipart/alternative; boundary=0016e64c1cf02007dc0499a620f8 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64c1cf02007dc0499a620f8 Content-Type: text/plain; charset=ISO-8859-1 Thanks, it is clear now. Regards Marco On Wed, Jan 12, 2011 at 7:00 AM, Greg Brown wrote: > Yeah, it's sort of a confusing method signature. :-( The base type is > just the class that the file is relative to. The method signature that takes > a URL may be clearer: > > bxmlSerializer.readObject(getClass().getResource("foo.bxml")); > > On Jan 12, 2011, at 7:17 AM, Marco Castillo wrote: > > > Dear List: > > Which is the meaning of the parameter baseType in the call of > BXMLSerializer#readObject(baseType, resourceName). In the documentation it > states that is the base type!! > > I'm asking this because I have many .bxml files and one loader class > associated with each .bxml file. Inside each .bxml file is a border pane > with a layout in it. I want to load each .bxml file and then insert each > component created inside a CardPane as it is done in the KitchenSink demo. > The difference is that I'm not embedding each class loader class into the > main class, I have each class in its own separate file. > > I saw in the KitchenSink demo that the baseType parameter was always the > KitchenSink.class. So in my case, which class should I put as the baseType > parameter in the readObject call? the loader class or the main class? > > > > Thank you in advance for your kind reply. > > > > Regards > > > > --0016e64c1cf02007dc0499a620f8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks, it is clear now.

Regards

Marco

On Wed, Jan 12, 2011 at 7:00 AM, Greg Brown &= lt;gk_brown@verizon.net> wrote:
Yeah, it's so= rt of a confusing method signature. =A0:-( =A0The base type is just the cla= ss that the file is relative to. The method signature that takes a URL may = be clearer:

bxmlSerializer.readObject(getClass().getResource("foo.bxml"));

On Jan 12, 2011, at 7:17 AM, Marco Castillo wrote:

> Dear List:
> Which is the meaning of the parameter baseType in the call of BXMLSeri= alizer#readObject(baseType, resourceName). In the documentation it states t= hat is the base type!!
> I'm asking this because I have many .bxml files and one loader cla= ss associated with each .bxml file. Inside each .bxml file is a border pane= with a layout in it. I want to load each .bxml file and then insert each c= omponent created inside a CardPane as it is done in the KitchenSink demo. T= he difference is that I'm not embedding each class loader class into th= e main class, I have each class in its own separate file.
> I saw in the KitchenSink demo that the baseType parameter was always t= he KitchenSink.class. So in my case, which class should I put as the baseTy= pe parameter in the readObject call? the loader class or the main class? >
> Thank you in advance for your kind reply.
>
> Regards
>


--0016e64c1cf02007dc0499a620f8--