I am writing a brand new application that is supposed to be
deployed to the Web.  I know nothing about the Web
programming and I was kind of hoping for PB to do that part
for me.  In PB 12 Classic I see that I can create .Net
Webform Application project and go from there.  In PB12.NET
that is not available.  We are trying to avoid simply
deploying it as a Smart Client application because it is not
reliable.  Does anyone know what are my other options?

PB12.Net does not support web deployment - yet.

Your options are two:  PB Webforms in PB12 "Classic", and Appeon for 
PowerBuilder.

-- 
Paul Horan[Sybase]
http://paulhoran.ulitzer.com

<Olga Gorelik> wrote in message news:4c633dcc.2a82.1681692777@sybase.com...
>I am writing a brand new application that is supposed to be
> deployed to the Web.  I know nothing about the Web
> programming and I was kind of hoping for PB to do that part
> for me.  In PB 12 Classic I see that I can create .Net
> Webform Application project and go from there.  In PB12.NET
> that is not available.  We are trying to avoid simply
> deploying it as a Smart Client application because it is not
> reliable.  Does anyone know what are my other options? 

And, unless I'm mistaken, using the DataWindow's HTML generation
capabilities as part of an app server component that generates page
code. This is. A lot of non-PB work, but it will let you create
something much more standard web looking.

Good luck,  

Terry and Sequel the techno-kitten

"Paul Horan[Sybase]" <phoran_remove@remove_sybase.com> wrote:
> PB12.Net does not support web deployment - yet.
> 
> Your options are two:  PB Webforms in PB12 "Classic", and Appeon for 
> PowerBuilder.



-- 
Sent from a device that hobbles my fingers and numbs my brain. Please
excuse any spelling errors, grammatical errors or brevity.

Now that just sucks big time.  Why would Sybase do such a
thing?  Introduce a much touted .Net upgrade and take away
the Web capabilities.  Who takes away features?!  I was
trying to show my bosses that we can use our existing PB
resources to create cool looking Web applications. 
Apparently, not so.

Thanks anyway.

Olga

> And, unless I'm mistaken, using the DataWindow's HTML
> generation capabilities as part of an app server component
> that generates page code. This is. A lot of non-PB work,
> but it will let you create something much more standard
> web looking.
>
> Good luck,
>
> Terry and Sequel the techno-kitten
>
> "Paul Horan[Sybase]" <phoran_remove@remove_sybase.com>
> > wrote: PB12.Net does not support web deployment - yet.
> >
> > Your options are two:  PB Webforms in PB12 "Classic",
> > and Appeon for  PowerBuilder.
>
>
>
> --
> Sent from a device that hobbles my fingers and numbs my
> brain. Please excuse any spelling errors, grammatical
> errors or brevity.

They didn't take any web capabilities away. You can still do Webforms 
with PB 12 (classic).


On 8/12/2010 12:49 PM, Olga Gorelik wrote:
> Now that just sucks big time.  Why would Sybase do such a
> thing?  Introduce a much touted .Net upgrade and take away
> the Web capabilities.  Who takes away features?!  I was
> trying to show my bosses that we can use our existing PB
> resources to create cool looking Web applications.
> Apparently, not so.
>
> Thanks anyway.
>
> Olga
>
>> And, unless I'm mistaken, using the DataWindow's HTML
>> generation capabilities as part of an app server component
>> that generates page code. This is. A lot of non-PB work,
>> but it will let you create something much more standard
>> web looking.
>>
>> Good luck,
>>
>> Terry and Sequel the techno-kitten
>>
>> "Paul Horan[Sybase]"<phoran_remove@remove_sybase.com>
>>> wrote: PB12.Net does not support web deployment - yet.
>>>
>>> Your options are two:  PB Webforms in PB12 "Classic",
>>> and Appeon for  PowerBuilder.
>>
>>
>>
>> --
>> Sent from a device that hobbles my fingers and numbs my
>> brain. Please excuse any spelling errors, grammatical
>> errors or brevity.

But I don't want the Cassic look.  My bosses don't want the
Classic look in our new applications.  We got really excited
about the .Net version.  So, it's a big disappointment that
we got this cool Web look yet we can't use it on the Web by
itself.

> They didn't take any web capabilities away. You can still
> do Webforms  with PB 12 (classic).
>
>
> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
> > Now that just sucks big time.  Why would Sybase do such
> > a thing?  Introduce a much touted .Net upgrade and take
> > away the Web capabilities.  Who takes away features?!  I
> > was trying to show my bosses that we can use our
> > existing PB resources to create cool looking Web
> > applications. Apparently, not so.
> >
> > Thanks anyway.
> >
> > Olga
> >
> >> And, unless I'm mistaken, using the DataWindow's HTML
> >> generation capabilities as part of an app server
> component >> that generates page code. This is. A lot of
> non-PB work, >> but it will let you create something much
> more standard >> web looking.
> >>
> >> Good luck,
> >>
> >> Terry and Sequel the techno-kitten
> >>
> >> "Paul Horan[Sybase]"<phoran_remove@remove_sybase.com>
> >>> wrote: PB12.Net does not support web deployment - yet.
> >>>
> >>> Your options are two:  PB Webforms in PB12 "Classic",
> >>> and Appeon for  PowerBuilder.
> >>
> >>
> >>
> >> --
> >> Sent from a device that hobbles my fingers and numbs my
> >> brain. Please excuse any spelling errors, grammatical
> >> errors or brevity.
>

Make it look however you want it to look.

You could always develop your UI in Silverlight and have it wire up to 
PB .Net built assemblies.



On 8/12/2010 1:19 PM, Olga Gorelik wrote:
> But I don't want the Cassic look.  My bosses don't want the
> Classic look in our new applications.  We got really excited
> about the .Net version.  So, it's a big disappointment that
> we got this cool Web look yet we can't use it on the Web by
> itself.
>
>> They didn't take any web capabilities away. You can still
>> do Webforms  with PB 12 (classic).
>>
>>
>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
>>> Now that just sucks big time.  Why would Sybase do such
>>> a thing?  Introduce a much touted .Net upgrade and take
>>> away the Web capabilities.  Who takes away features?!  I
>>> was trying to show my bosses that we can use our
>>> existing PB resources to create cool looking Web
>>> applications. Apparently, not so.
>>>
>>> Thanks anyway.
>>>
>>> Olga
>>>
>>>> And, unless I'm mistaken, using the DataWindow's HTML
>>>> generation capabilities as part of an app server
>> component>>  that generates page code. This is. A lot of
>> non-PB work,>>  but it will let you create something much
>> more standard>>  web looking.
>>>>
>>>> Good luck,
>>>>
>>>> Terry and Sequel the techno-kitten
>>>>
>>>> "Paul Horan[Sybase]"<phoran_remove@remove_sybase.com>
>>>>> wrote: PB12.Net does not support web deployment - yet.
>>>>>
>>>>> Your options are two:  PB Webforms in PB12 "Classic",
>>>>> and Appeon for  PowerBuilder.
>>>>
>>>>
>>>>
>>>> --
>>>> Sent from a device that hobbles my fingers and numbs my
>>>> brain. Please excuse any spelling errors, grammatical
>>>> errors or brevity.
>>

If I have to develop UI using a different technology, what
do I need the PB for?  Is there a plan to provide Web
capabilities in PB.NET in the future?

> Make it look however you want it to look.
>
> You could always develop your UI in Silverlight and have
> it wire up to  PB .Net built assemblies.
>
>
>
> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
> > But I don't want the Cassic look.  My bosses don't want
> > the Classic look in our new applications.  We got really
> > excited about the .Net version.  So, it's a big
> > disappointment that we got this cool Web look yet we
> > can't use it on the Web by itself.
> >
> >> They didn't take any web capabilities away. You can
> still >> do Webforms  with PB 12 (classic).
> >>
> >>
> >> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
> >>> Now that just sucks big time.  Why would Sybase do
> such >>> a thing?  Introduce a much touted .Net upgrade
> and take >>> away the Web capabilities.  Who takes away
> features?!  I >>> was trying to show my bosses that we can
> use our >>> existing PB resources to create cool looking
> Web >>> applications. Apparently, not so.
> >>>
> >>> Thanks anyway.
> >>>
> >>> Olga
> >>>
> >>>> And, unless I'm mistaken, using the DataWindow's HTML
> >>>> generation capabilities as part of an app server
> >> component>>  that generates page code. This is. A lot
> of >> non-PB work,>>  but it will let you create something
> much >> more standard>>  web looking.
> >>>>
> >>>> Good luck,
> >>>>
> >>>> Terry and Sequel the techno-kitten
> >>>>
> >>>> "Paul Horan[Sybase]"<phoran_remove@remove_sybase.com>
> >>>>> wrote: PB12.Net does not support web deployment -
> yet. >>>>>
> >>>>> Your options are two:  PB Webforms in PB12 "Classic"
> , >>>>> and Appeon for  PowerBuilder.
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Sent from a device that hobbles my fingers and numbs
> my >>>> brain. Please excuse any spelling errors,
> grammatical >>>> errors or brevity.
> >>
>

A future version of PB will support Silverlight.

If PB doesn't suit your needs for web development (e.g. Webforms) then 
you have to pick a tool that will suit your needs.

Are you looking at creating a Silverlight style web app or an ASP.NET 
style web app?



On 8/12/2010 2:05 PM, Olga Gorelik wrote:
> If I have to develop UI using a different technology, what
> do I need the PB for?  Is there a plan to provide Web
> capabilities in PB.NET in the future?
>
>> Make it look however you want it to look.
>>
>> You could always develop your UI in Silverlight and have
>> it wire up to  PB .Net built assemblies.
>>
>>
>>
>> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
>>> But I don't want the Cassic look.  My bosses don't want
>>> the Classic look in our new applications.  We got really
>>> excited about the .Net version.  So, it's a big
>>> disappointment that we got this cool Web look yet we
>>> can't use it on the Web by itself.
>>>
>>>> They didn't take any web capabilities away. You can
>> still>>  do Webforms  with PB 12 (classic).
>>>>
>>>>
>>>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
>>>>> Now that just sucks big time.  Why would Sybase do
>> such>>>  a thing?  Introduce a much touted .Net upgrade
>> and take>>>  away the Web capabilities.  Who takes away
>> features?!  I>>>  was trying to show my bosses that we can
>> use our>>>  existing PB resources to create cool looking
>> Web>>>  applications. Apparently, not so.
>>>>>
>>>>> Thanks anyway.
>>>>>
>>>>> Olga
>>>>>
>>>>>> And, unless I'm mistaken, using the DataWindow's HTML
>>>>>> generation capabilities as part of an app server
>>>> component>>   that generates page code. This is. A lot
>> of>>  non-PB work,>>   but it will let you create something
>> much>>  more standard>>   web looking.
>>>>>>
>>>>>> Good luck,
>>>>>>
>>>>>> Terry and Sequel the techno-kitten
>>>>>>
>>>>>> "Paul Horan[Sybase]"<phoran_remove@remove_sybase.com>
>>>>>>> wrote: PB12.Net does not support web deployment -
>> yet.>>>>>
>>>>>>> Your options are two:  PB Webforms in PB12 "Classic"
>> ,>>>>>  and Appeon for  PowerBuilder.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sent from a device that hobbles my fingers and numbs
>> my>>>>  brain. Please excuse any spelling errors,
>> grammatical>>>>  errors or brevity.
>>>>
>>

It is my understanding that we are generally moving away
from Silverlight.  For this particular project all we wanted
to do is create a small application for internal use that
will be deployable to the Web so that we won't have to
install it on everyone's computer.  PB Webforms only better
looking.  I was looking at it as an opportunity to see if it
can be done using PB12.Net and only my current skills which
do not include any web development.  Since it cannot be
done, I was just told to forget about the whole thing. :(

> A future version of PB will support Silverlight.
>
> If PB doesn't suit your needs for web development (e.g.
> Webforms) then  you have to pick a tool that will suit
> your needs.
>
> Are you looking at creating a Silverlight style web app or
> an ASP.NET  style web app?
>
>
>
> On 8/12/2010 2:05 PM, Olga Gorelik wrote:
> > If I have to develop UI using a different technology,
> > what do I need the PB for?  Is there a plan to provide
> > Web capabilities in PB.NET in the future?
> >
> >> Make it look however you want it to look.
> >>
> >> You could always develop your UI in Silverlight and
> have >> it wire up to  PB .Net built assemblies.
> >>
> >>
> >>
> >> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
> >>> But I don't want the Cassic look.  My bosses don't
> want >>> the Classic look in our new applications.  We got
> really >>> excited about the .Net version.  So, it's a big
> >>> disappointment that we got this cool Web look yet we
> >>> can't use it on the Web by itself.
> >>>
> >>>> They didn't take any web capabilities away. You can
> >> still>>  do Webforms  with PB 12 (classic).
> >>>>
> >>>>
> >>>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
> >>>>> Now that just sucks big time.  Why would Sybase do
> >> such>>>  a thing?  Introduce a much touted .Net upgrade
> >> and take>>>  away the Web capabilities.  Who takes away
> >> features?!  I>>>  was trying to show my bosses that we
> can >> use our>>>  existing PB resources to create cool
> looking >> Web>>>  applications. Apparently, not so.
> >>>>>
> >>>>> Thanks anyway.
> >>>>>
> >>>>> Olga
> >>>>>
> >>>>>> And, unless I'm mistaken, using the DataWindow's
> HTML >>>>>> generation capabilities as part of an app
> server >>>> component>>   that generates page code. This
> is. A lot >> of>>  non-PB work,>>   but it will let you
> create something >> much>>  more standard>>   web looking.
> >>>>>>
> >>>>>> Good luck,
> >>>>>>
> >>>>>> Terry and Sequel the techno-kitten
> >>>>>>
> >>>>>> "Paul
> Horan[Sybase]"<phoran_remove@remove_sybase.com> >>>>>>>
> wrote: PB12.Net does not support web deployment - >>
> yet.>>>>> >>>>>>> Your options are two:  PB Webforms in
> PB12 "Classic" >> ,>>>>>  and Appeon for  PowerBuilder.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Sent from a device that hobbles my fingers and
> numbs >> my>>>>  brain. Please excuse any spelling errors,
> >> grammatical>>>>  errors or brevity.
> >>>>
> >>
>

Okay, so it sounds like you want Webforms. You can make the end product 
look however you want. Just treat your app development as SDI. Throw on 
a bunch of images to make it look pretty and away you go.

On 8/12/2010 2:22 PM, Olga Gorelik wrote:
> It is my understanding that we are generally moving away
> from Silverlight.  For this particular project all we wanted
> to do is create a small application for internal use that
> will be deployable to the Web so that we won't have to
> install it on everyone's computer.  PB Webforms only better
> looking.  I was looking at it as an opportunity to see if it
> can be done using PB12.Net and only my current skills which
> do not include any web development.  Since it cannot be
> done, I was just told to forget about the whole thing. :(
>
>> A future version of PB will support Silverlight.
>>
>> If PB doesn't suit your needs for web development (e.g.
>> Webforms) then  you have to pick a tool that will suit
>> your needs.
>>
>> Are you looking at creating a Silverlight style web app or
>> an ASP.NET  style web app?
>>
>>
>>
>> On 8/12/2010 2:05 PM, Olga Gorelik wrote:
>>> If I have to develop UI using a different technology,
>>> what do I need the PB for?  Is there a plan to provide
>>> Web capabilities in PB.NET in the future?
>>>
>>>> Make it look however you want it to look.
>>>>
>>>> You could always develop your UI in Silverlight and
>> have>>  it wire up to  PB .Net built assemblies.
>>>>
>>>>
>>>>
>>>> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
>>>>> But I don't want the Cassic look.  My bosses don't
>> want>>>  the Classic look in our new applications.  We got
>> really>>>  excited about the .Net version.  So, it's a big
>>>>> disappointment that we got this cool Web look yet we
>>>>> can't use it on the Web by itself.
>>>>>
>>>>>> They didn't take any web capabilities away. You can
>>>> still>>   do Webforms  with PB 12 (classic).
>>>>>>
>>>>>>
>>>>>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
>>>>>>> Now that just sucks big time.  Why would Sybase do
>>>> such>>>   a thing?  Introduce a much touted .Net upgrade
>>>> and take>>>   away the Web capabilities.  Who takes away
>>>> features?!  I>>>   was trying to show my bosses that we
>> can>>  use our>>>   existing PB resources to create cool
>> looking>>  Web>>>   applications. Apparently, not so.
>>>>>>>
>>>>>>> Thanks anyway.
>>>>>>>
>>>>>>> Olga
>>>>>>>
>>>>>>>> And, unless I'm mistaken, using the DataWindow's
>> HTML>>>>>>  generation capabilities as part of an app
>> server>>>>  component>>    that generates page code. This
>> is. A lot>>  of>>   non-PB work,>>    but it will let you
>> create something>>  much>>   more standard>>    web looking.
>>>>>>>>
>>>>>>>> Good luck,
>>>>>>>>
>>>>>>>> Terry and Sequel the techno-kitten
>>>>>>>>
>>>>>>>> "Paul
>> Horan[Sybase]"<phoran_remove@remove_sybase.com>  >>>>>>>
>> wrote: PB12.Net does not support web deployment ->>
>> yet.>>>>>  >>>>>>>  Your options are two:  PB Webforms in
>> PB12 "Classic">>  ,>>>>>   and Appeon for  PowerBuilder.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sent from a device that hobbles my fingers and
>> numbs>>  my>>>>   brain. Please excuse any spelling errors,
>>>> grammatical>>>>   errors or brevity.
>>>>>>
>>>>
>>

Thanks.  Yes, I just went back to Classic and found some of
the tricks that give it "the look" that weren't available in
11, so I'll go with that.

> Okay, so it sounds like you want Webforms. You can make
> the end product  look however you want. Just treat your
> app development as SDI. Throw on  a bunch of images to
> make it look pretty and away you go.
>
> On 8/12/2010 2:22 PM, Olga Gorelik wrote:
> > It is my understanding that we are generally moving away
> > from Silverlight.  For this particular project all we
> > wanted to do is create a small application for internal
> > use that will be deployable to the Web so that we won't
> > have to install it on everyone's computer.  PB Webforms
> > only better looking.  I was looking at it as an
> > opportunity to see if it can be done using PB12.Net and
> > only my current skills which do not include any web
> > development.  Since it cannot be done, I was just told
> to forget about the whole thing. :( >
> >> A future version of PB will support Silverlight.
> >>
> >> If PB doesn't suit your needs for web development (e.g.
> >> Webforms) then  you have to pick a tool that will suit
> >> your needs.
> >>
> >> Are you looking at creating a Silverlight style web app
> or >> an ASP.NET  style web app?
> >>
> >>
> >>
> >> On 8/12/2010 2:05 PM, Olga Gorelik wrote:
> >>> If I have to develop UI using a different technology,
> >>> what do I need the PB for?  Is there a plan to provide
> >>> Web capabilities in PB.NET in the future?
> >>>
> >>>> Make it look however you want it to look.
> >>>>
> >>>> You could always develop your UI in Silverlight and
> >> have>>  it wire up to  PB .Net built assemblies.
> >>>>
> >>>>
> >>>>
> >>>> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
> >>>>> But I don't want the Cassic look.  My bosses don't
> >> want>>>  the Classic look in our new applications.  We
> got >> really>>>  excited about the .Net version.  So,
> it's a big >>>>> disappointment that we got this cool Web
> look yet we >>>>> can't use it on the Web by itself.
> >>>>>
> >>>>>> They didn't take any web capabilities away. You can
> >>>> still>>   do Webforms  with PB 12 (classic).
> >>>>>>
> >>>>>>
> >>>>>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
> >>>>>>> Now that just sucks big time.  Why would Sybase do
> >>>> such>>>   a thing?  Introduce a much touted .Net
> upgrade >>>> and take>>>   away the Web capabilities.  Who
> takes away >>>> features?!  I>>>   was trying to show my
> bosses that we >> can>>  use our>>>   existing PB
> resources to create cool >> looking>>  Web>>>
> applications. Apparently, not so. >>>>>>>
> >>>>>>> Thanks anyway.
> >>>>>>>
> >>>>>>> Olga
> >>>>>>>
> >>>>>>>> And, unless I'm mistaken, using the DataWindow's
> >> HTML>>>>>>  generation capabilities as part of an app
> >> server>>>>  component>>    that generates page code.
> This >> is. A lot>>  of>>   non-PB work,>>    but it will
> let you >> create something>>  much>>   more standard>>
> web looking. >>>>>>>>
> >>>>>>>> Good luck,
> >>>>>>>>
> >>>>>>>> Terry and Sequel the techno-kitten
> >>>>>>>>
> >>>>>>>> "Paul
> >> Horan[Sybase]"<phoran_remove@remove_sybase.com>
> >>>>>>> >> wrote: PB12.Net does not support web deployment
> ->> >> yet.>>>>>  >>>>>>>  Your options are two:  PB
> Webforms in >> PB12 "Classic">>  ,>>>>>   and Appeon for
> PowerBuilder. >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Sent from a device that hobbles my fingers and
> >> numbs>>  my>>>>   brain. Please excuse any spelling
> errors, >>>> grammatical>>>>   errors or brevity.
> >>>>>>
> >>>>
> >>
>

Why can't they just run the exe off a network drive?

<Olga Gorelik> wrote in message news:4c6456d1.4249.1681692777@sybase.com...
> Thanks.  Yes, I just went back to Classic and found some of
> the tricks that give it "the look" that weren't available in
> 11, so I'll go with that.
>
>> Okay, so it sounds like you want Webforms. You can make
>> the end product  look however you want. Just treat your
>> app development as SDI. Throw on  a bunch of images to
>> make it look pretty and away you go.
>>
>> On 8/12/2010 2:22 PM, Olga Gorelik wrote:
>> > It is my understanding that we are generally moving away
>> > from Silverlight.  For this particular project all we
>> > wanted to do is create a small application for internal
>> > use that will be deployable to the Web so that we won't
>> > have to install it on everyone's computer.  PB Webforms
>> > only better looking.  I was looking at it as an
>> > opportunity to see if it can be done using PB12.Net and
>> > only my current skills which do not include any web
>> > development.  Since it cannot be done, I was just told
>> to forget about the whole thing. :( >
>> >> A future version of PB will support Silverlight.
>> >>
>> >> If PB doesn't suit your needs for web development (e.g.
>> >> Webforms) then  you have to pick a tool that will suit
>> >> your needs.
>> >>
>> >> Are you looking at creating a Silverlight style web app
>> or >> an ASP.NET  style web app?
>> >>
>> >>
>> >>
>> >> On 8/12/2010 2:05 PM, Olga Gorelik wrote:
>> >>> If I have to develop UI using a different technology,
>> >>> what do I need the PB for?  Is there a plan to provide
>> >>> Web capabilities in PB.NET in the future?
>> >>>
>> >>>> Make it look however you want it to look.
>> >>>>
>> >>>> You could always develop your UI in Silverlight and
>> >> have>>  it wire up to  PB .Net built assemblies.
>> >>>>
>> >>>>
>> >>>>
>> >>>> On 8/12/2010 1:19 PM, Olga Gorelik wrote:
>> >>>>> But I don't want the Cassic look.  My bosses don't
>> >> want>>>  the Classic look in our new applications.  We
>> got >> really>>>  excited about the .Net version.  So,
>> it's a big >>>>> disappointment that we got this cool Web
>> look yet we >>>>> can't use it on the Web by itself.
>> >>>>>
>> >>>>>> They didn't take any web capabilities away. You can
>> >>>> still>>   do Webforms  with PB 12 (classic).
>> >>>>>>
>> >>>>>>
>> >>>>>> On 8/12/2010 12:49 PM, Olga Gorelik wrote:
>> >>>>>>> Now that just sucks big time.  Why would Sybase do
>> >>>> such>>>   a thing?  Introduce a much touted .Net
>> upgrade >>>> and take>>>   away the Web capabilities.  Who
>> takes away >>>> features?!  I>>>   was trying to show my
>> bosses that we >> can>>  use our>>>   existing PB
>> resources to create cool >> looking>>  Web>>>
>> applications. Apparently, not so. >>>>>>>
>> >>>>>>> Thanks anyway.
>> >>>>>>>
>> >>>>>>> Olga
>> >>>>>>>
>> >>>>>>>> And, unless I'm mistaken, using the DataWindow's
>> >> HTML>>>>>>  generation capabilities as part of an app
>> >> server>>>>  component>>    that generates page code.
>> This >> is. A lot>>  of>>   non-PB work,>>    but it will
>> let you >> create something>>  much>>   more standard>>
>> web looking. >>>>>>>>
>> >>>>>>>> Good luck,
>> >>>>>>>>
>> >>>>>>>> Terry and Sequel the techno-kitten
>> >>>>>>>>
>> >>>>>>>> "Paul
>> >> Horan[Sybase]"<phoran_remove@remove_sybase.com>
>> >>>>>>> >> wrote: PB12.Net does not support web deployment
>> ->> >> yet.>>>>>  >>>>>>>  Your options are two:  PB
>> Webforms in >> PB12 "Classic">>  ,>>>>>   and Appeon for
>> PowerBuilder. >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Sent from a device that hobbles my fingers and
>> >> numbs>>  my>>>>   brain. Please excuse any spelling
>> errors, >>>> grammatical>>>>   errors or brevity.
>> >>>>>>
>> >>>>
>> >>
>> 

Brad's already said it, but since I seem to have caused the confusion,
I'll add. What was in PB prior to 12.0 for web (.NET WebForms, DW HTML,
ability to deploy business logic to a variety of app servers, ability to
work with Appeon) has not been taken away. I've been following the news
running up to 12.0 pretty carefully and I've never seen suggest a new
web technology would be available in 12.0, although they suggested the
technology they were putting in place with 12.0 would put them in a good
position to release a new web technology post-12.0. 

As far as "cool looking" goes, I guess I'd leave that up to the graphic
designers, and they could probably make anything look good. (Conversely,
computer history has shown people can make any good technology look
bad.) I'm on record as not liking several of the elements of WebForms,
which you can work around, but one thing I do like is the multicolumn
dropdown DataWindows. I'd imagine you *could* do this with other
technologies,but it's drop dead simple in PB, and it makes you app look
good. (OK, a little good for a moment, and I haven doubt someone could
make it look ugly. <BG>)

Good luck, 

Terry and Sequel the techno-kitten  

<Olga Gorelik> wrote:
> Now that just sucks big time.  Why would Sybase do such a
> thing?  Introduce a much touted .Net upgrade and take away
> the Web capabilities.  Who takes away features?!  I was
> trying to show my bosses that we can use our existing PB
> resources to create cool looking Web applications. 
> Apparently, not so.
> 
> Thanks anyway.
> 
> Olga
> 
>> And, unless I'm mistaken, using the DataWindow's HTML
>> generation capabilities as part of an app server component
>> that generates page code. This is. A lot of non-PB work,
>> but it will let you create something much more standard
>> web looking.
>> 
>> Good luck,
>> 
>> Terry and Sequel the techno-kitten
>> 
>> "Paul Horan[Sybase]" <phoran_remove@remove_sybase.com>
>>> wrote: PB12.Net does not support web deployment - yet.
>>> 
>>> Your options are two:  PB Webforms in PB12 "Classic",
>>> and Appeon for  PowerBuilder.
>> 
>> 
>> 
>> --
>> Sent from a device that hobbles my fingers and numbs my
>> brain. Please excuse any spelling errors, grammatical
>> errors or brevity.


-- 
Sent from a device that hobbles my fingers and numbs my brain. Please
excuse any spelling errors, grammatical errors or brevity.