Re: PB 12 : no more PBL's

[John Strano[Sybase]]

Michael:

When you distribute the PBDs to each customer, do you distribute an exe as
well,
or do you fully rely on AddToLibraryList() for runtime resolution?

Thank you.

--
John Strano - Sybase Technology Evangelist

"M. Searer" <nos...@nospam.com> wrote in message
news:4c28e509@forums-1-dub...
> Any considerations for adding non-dws to runtime dynamically?
> The lack of setliblist type of functionality in pb.net is a critical
> drawback for our application and will prevent us from moving forward with
> pb.net.
>
>
> Also, thanks for your explaination on the pbls storage. I had thought it
> was just a way to group the objects and that putting it into a directory
> really isnt any different other than it allows easier access to other
> apps. I also figure it made the setlibrarylist and similar easier.
>
>
>
> "Reed Shilts [Sybase]" <reed dot shilts at sybase dot com> wrote in
> message news:ka9a269bempkhla9e...@4ax.com...
>> ***** Background Information Only *****
>> ***** NOTHING SYBASE OFFICIAL HERE FOLKS *****
>>
>> The two separate topics - "exploded PBLs" and "dynamic DW" are being
>> rolled into a single discussion (oh - and don't forget "incremental
>> build")...
>>
>> First - the PBL file or PBL-directory is (at a high level) - an
>> implementation detail. It's a container of "objects".
>> Some people wanted the PBL to be a ZIP file, and in the
>> PB 6 timeframe we even considered whether to have
>> the PBL actually be an ASA database.
>> Regardless, currently the exploded PBL format makes
>> many things in the VS world easier,
>> and SCC is no longer the hack it is in Classic
>> (and 3rd party tools are a lot easier too)...
>> However, to the typical user, this is just a implementation detail
>> that should not affect their development or application design.
>>
>> About the dynamic DataWindows...
>> The PB.NET DW engine can create a DW from a string and even
>> a file, which is what the SRD file is.
>> (I think we can even create a DW from an XML format definition, but
>> I'm not sure that is public or just some early design doc I
>> once read...)
>> From a string - this is so you can store the DW definitions as records
>> in a database.
>> The DW engine can also add an arbitrary _directory_ to
>> its search path (like the library list). I'm just not sure that is
>> exposed to the PowerScript user, shucks it may be as trivial as
>> adding the directory to the library list and feeding it to the
>> control, I just am not sure (maybe one of the DW guys can pipe up?).
>>
>> Today a DW guy reminded me there is the binary format of the SRD (like
>> what you'd see in the PBD file). I'm not sure if this binary format
>> is exposed or stored on disk in any manner, but it's something to kick
>> around (so you are not storing your intellectual property in plain
>> text).
>>
>> About incremental build, for the last two years (and they are still
>> on-going) MANY internal discussions about the entire build process
>> and what artifacts to leave around for the IDE to use.
>> However I should not comment too much here about that whole
>> topic. Just to say that I "lost" most of those discussions, so I
>> don't want to taint anybody nor throw flame-bait...
>>
>> HTH,
>> Reed Shilts
>> Concord, Mass
>> <Standard-Disclaimers-Apply/>
>> ***** NOTHING SYBASE OFFICIAL HERE FOLKS *****
>> ***** Background Information Only *****
>>
>>
>> On 23 Jun 2010 17:26:50 -0700, "Michael K"
>> <michae...@stiearc.com.au> wrote:
>>
>>>If we no longer have PBL's can we still support dynamic datawindows. We
>>>store most of our datawindow syntax in the database and at runtime the
>>>local
>>>client PBL's are updated on the fly via libraryimport. Also we need to
>>>use
>>>addtolibrarylist for these libraries to support child reports and
>>>dropdowndatawindows. Will this still be possible in PB12?
>>>
>