Goto Page

[Mark]

Hi,

there is a way to implement a directly gotopage (like
Google) ?

Thanks

[Adam Simmonds [TeamSybase]]

Do you have a web application?

[Mark]

Yes i have a Jsp web application .

[Larry Cermak [Team Sybase]]

Are you talking about making a page automatically redirecting after so many
seconds or something like that?

response.sendRedirect("abc.htm");

--

Larry Cermak [Team Sybase]
Branick Consulting, Inc.
www.branick-inc.com
EAServer & PowerBuilder Consulting & Training
EAServer and PowerBuilder Computer Based Training Courses

<Mark> wrote in message news:46e3d143.67d...@sybase.com...

[Adam Simmonds [TeamSybase]]

You can set a default page in your web app in the WEB-INF/web.xml file

<welcome-file-list>
<welcome-file>/index.jsp</welcome-file>
</welcome-file-list>

Or just use EAServer Manager and go to the web app props and set a page
on the File Refs tab (ie. "/index.jsp" will default the web app to an
index page in the root of the web app).

a.

[Mark]

Thank you Dean .

> Yes. We have added logic to our HTML Web DW paging to
> allow you to append an Index to the bottom and you can
> jump to page x. This is commn code we append to every
> HTML DW dynamically.
>
> You want to append some JavaScript to your page and then
> you have to write common logic to jump to check page
> argument.
>
> This is very much needed when build ing an application.
> The HTML DW allows you to page data so you don't have to
> retrieve too much data, but if I have to page through 10
> pages its too slow.
>
> Look at images as example. We define the index as a
> property and the code adds this functionality to any
> Form.
>
> You can try an example at
>
http://demo.powerobjects.com/smlportal/ptwrsecurity.jsp?userid=techwave&password=techwave
>
> Jump to "Forms", "Demo Forms", "Customers", "List" You
> will get a long list of customers, we automatically index
> the list to jump through it quickly.
>
> The logic is prety simple. On the server simply apply the
> action of "PageNext"
>
> This.SetRow(il_CurrentRow)
>
> If l_rows_per_page > 0 And il_CurrentRow >
> l_rows_per_page Then
> l_new_page = Integer(il_CurrentRow/ l_rows_per_page)
>
> For i = 1 To l_new_page
> this.SetHTMLAction("PageNext", "" )
> Next
> End If
>
>
>
>
> --
> Dean Jones
> CEO
> PowerObjects
> http://www.powerobjects.com
> (612) 339-3355 Ext. 112
>
> TeamSybase
> * * Think Sybase * *
>
>
> <Mark> wrote in message
> > news:46e18585.410...@sybase.com... Hi,

> >
> > there is a way to implement a directly gotopage (like
> > Google) ?
> >
> > Thanks
>
>
>
>

> [Attachment: index.gif]
> [Attachment: asign index.gif]

[Adam Simmonds [TeamSybase]]

Oh okay.
You can do this but you will probably have to roll your own.

Can you explain in more detail what you are doing?
I have implemented this using the htmldw but as I said you have to roll
your own.

a.

Mark wrote:
> Sorry,
>
> but i intend a numeric navigator bar (see attached file) .
>
> Thanks

>>>>> ------------------------------------------------------------------------
>>>>>

[Yoyo Young]

Does your solution support XHTML and XML DW?

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message
news:46e560fa@forums-1-dub...

[Dean Jones]

there are some serious security issues to XML datawindow so we have never
looked at it. Basically we have added some of our own logic to the HTML DW.
The biggest down fall is the amount of HTML that is generated. We have built
a product that allows you to drop HTML DW into a browser fast and easy. then
apply security to control access, read/write etc. Then we put in the ability
to link the forms together through a data driven meta data, this allows each
user to have differnt fuctionality running the same system. It is really
slick, but it is not a client server solution. You don't build windows and
menus like you do with appeon and PB11 Web Forms. You build DW and write
your business rules in PB NVO. This create a application fast and easy, you
can roll out new forms and link them into existing interfaces or build new
processes very fast.

Right now we don't use XML at all.

We are very please with PB11.NET Web Services so we might build that into
smlPortal.

--
Dean Jones
CEO
PowerObjects
http://www.powerobjects.com
(612) 339-3355 Ext. 112

TeamSybase
* * Think Sybase * *

"Yoyo Young" <yo...@public1.wx.js.cn> wrote in message
news:46e5e660$1@forums-1-dub...

[Yoyo Young]

Inline property will solve security issues.
Don't you think so?

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message

news:46e5f739$1@forums-1-dub...

[Dean Jones]

then what advantage do I get from XML datawindow?

--
Dean Jones
CEO
PowerObjects
http://www.powerobjects.com
(612) 339-3355 Ext. 112

TeamSybase
* * Think Sybase * *

"Yoyo Young" <yo...@public1.wx.js.cn> wrote in message

news:46e6b6d1@forums-1-dub...

[Yoyo Young]

I think the main advantage is performance gain since css, javascript and xsl
are in seperate file and these files can be downloaded once.
But it's not why I ask the question. I am also testing PB11.NET Web Services
+ WEB DW and finding some bugs such as dropdownlistbox not rendering
correct.But it was rendering nice with XHTML DW. It seems these issues will
not be solved quickly then I have to use XHTML or XML DW.

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message

news:46e7044f$1@forums-1-dub...

[Dean Jones]

we don't use DDDW on the web. they have a lot of issues. Basically if you
have a drop down that has 100 values and you have a screen that has 25 rows,
you now have 2500 rows of data that has to be downloaded. We have build what
we call Lookup windows. They work just like a drop down, but it pops up a
window on demand and you can return one to many values. You can have a
search screen to limit the amount of data returned to the look up screen.
Also you can select multiple values across pages as well as map one to many
columns in the look up to your screen. So you could do a look up and load
the entire screen with data, not just the one column. So you can have data
plus display. But you might have multiple values, data, display and price
(example looking up product).

The cool part of the product we developed is you can create a common lookup
and reuse it on many forms or reports. A form or report can have many lookup
windows and the lookup windows are defined in the meta data, so its easy to
create a new form or report and add lookups. Example we always have to look
up client codes, in reports and in business process. we create the lookup
single select, multiple select, maybe add a search screen to allow the
lookup to find what it wants faster, done. The lookup can now be reused any
where in reports and forms.

Simple DDDW will be fine, small lists but if you have large list, you will
have a slow application.

There are several limitations to HTML DW, but you can add some common logic
to greatly improve the behavior.

Bottom line is if you are building a web application you have to think about
security and navigation. It's very easy to spoof a web server. So you have
to ask who is requesting this page, build the page with the correct security
and access to data, then when they submit an action "Update", "delete" etc.
you have to again ask who is submitting this action and if they have rights
to the page, and the action? I have help with many applications where I
simply typed a URL and deleted records. I was told a user would never do
that. Yeah right. They will and they do.

You comments about the XML are not correct. the size of the page and what is
download is about the same. If your XML is inline you have to retrieve an
entire page, so you are pulling everything down again. The JavaScript files
are cache in both cases if you coded them as files. Your XML style sheet is
generated for a given row size, so you would have to generate the XML style
sheet one every call if your going to have a dynamic app that will let users
determine how many rows they want to see.

Lastly you have to think about how you can develop the forms and components
that you don't require a new component every time you want to add another
form or report. You do this by creating an Engine that allows you to drop in
a definition of a report or form and the engine knows how to process the
report or form.

--
Dean Jones
CEO
PowerObjects
http://www.powerobjects.com
(612) 339-3355 Ext. 112

TeamSybase
* * Think Sybase * *

"Yoyo Young" <yo...@public1.wx.js.cn> wrote in message

news:46e73de0$1@forums-1-dub...

[Yoyo Young]

Sorry for late response.
I don't use DDDW too and often use DDLB for code tables. Field Lookup
windows is also my favorite.The diffcult thing when developing lookup form
is the dependency that means the lookup form need retrieve arguments from
the main form. I know it can do but it is diffcult to develop a framework
for this.
Now I am refactoring EAF for working with PB11.NET WS and I am glad to
discuss with you on WEB DW.

Thanks.

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message

news:46e76e42@forums-1-dub...

[Dean Jones]

Yes the Lookup window often needs arguments from the main web dw window. We
built this as a common object. Coded once. We can open the same lookup
window from multiple interfaces or columns and pass in different arguments
form each interface.

Three blank columns on a Web DW.

Look up State
Look up city with argument state
Look up hospital with argument state and city.

Very easy to do. We code only PB.

We differ from EAF. EAF is a framework and you have to build everything your
self. So you need to develop security and navigation. We have developed
report and form engine. We only run on the web, and you build a report that
can be dropped into our engine. This allows you to be very productive, you
don't build a new component then build a new page etc. You build a new
NVO/DataObject, deploy it and run it. Now as you application grows you end
up with 200 rows in a database not 200 pages that all need to be maintained
and improved every time you come up with a better approach.

--
Dean Jones
CEO
PowerObjects
http://www.powerobjects.com
(612) 339-3355 Ext. 112

TeamSybase
* * Think Sybase * *

"Yoyo Young" <yo...@public1.wx.js.cn> wrote in message

news:46eb3416@forums-1-dub...

[Yoyo Young]

OK. I say a example.
Suppose I create a Shipping Notice page with 2 WEB DW in 2 DIV . One WEB DW
is Shipping Notice header, there are customer, salesman , shipping date and
so on. The other WEB DW is Shipping Notice body, there are Customer Order,
Item, Description, Quantity and so on. When I look up field Customer Order,
I need pass customer argument in header page to Popup form. Keep in mind
Customer field is not in current WEB DW, it is in another WEB DW in another
DIV. Don't you think it is hard to do it with meta data?

As for EAF, because it's opensource I can look into it. EAF is good at
server-side and now I enhance it with ASP.NET frontend and Webservice
backend. I appreciate your form, report and navigation engine in smlportal.
I have been a ERP developer for 10 years and I know the how difficulty to
migrate a complicated C/S business applicatin to WEB. How to deal with
interface logic? Such as Itemchanged...? We have accomplished most of that.
After finished, I am glad to show it.

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message

news:46ee8abd$1@forums-1-dub...

[Dean Jones]

Yes I understand the issue. Passing a looked up key from one form to another
form is tricky. We do do it with meta data. But it only links data from
saved record. So you can't have multiple forms with unsaved data. You create
your header save, then create your detail and we can pass any arguments.

EAF is a nice approach and a lot of people like it, but it requires large
components, it does not have a security process built into the framework or
navigation. So if you build with EAF you still need to build your own
security and your own navigation. Its very common for developers to fail
with this aspect because they don't understand the web. I have worked on
several large projects pulling out EAF because it would not scale. I have
also help many projects understand developing a web security that not only
says who is logged on, what should I put on the screen, but also bacend
componts checking security before processing the request. Its easy to send a
URL to the server. You have to check security when building a page and you
have to check security when performing a given action. Just because you ahve
recieved a request to delete record 123, does not mean its a valid request.
Also in your approach you have more flex ability if you are build ing a new
page for every interface, but you are also creating more code to maitain and
support. our approach is a generic web interface navigation between forms
and displaying forms on a single page, master detail, tab folder etc, but
all forms use the same interface. Now I can built many PB NVO, DW and deploy
the meta data to a database and control security to access the forms. Many
PBD's and records in a database. This came about because everytime I
developed a web application with JSP and EAS I noticed every page was
basically the same except a few variables. So may goal was to have just one
page and read the meta data from a database. We have developed this and now
have a robust Forms engine and Report engine. This makes build a report or
form very fast and easy, go into PB, code the NVO and build your DW. Now
compile to a PBD, and deploy the meta data to the database (all done through
an admin tool). You can now control security and navigation as well as link
the Form to other related forms not known when the form was developed.
Example customer and order process forms. Now you develop a return fomr. May
some people handling returns need to see the order. its very easy from the
meta data to say these forms link. Done. No coding no navigation. Now
because of security one user might see the linked form one might now. There
is a huge difference from developing from an engine and developing a from a
framework. A frame work gives you some objects to make it easier to build
what you want (with some overhead), while the engine appoach limits what is
built but makes it faster and easier to build new forms. With smlPortal a
developer only needs to write code in PB. With EAF you ahve to build web
application that calls easerver and code the component that gets called and
generate stubs to access the component.

It sounds like you have a full understanding of what you are looking to do
and have the skills to do it, but often the developers want to focus on
their business and really don't care about security and navigation, they
just want to code the Customer/Order/ Order Items. That is they want to
focus on their business.

--
Dean Jones
CEO
PowerObjects
http://www.powerobjects.com
(612) 339-3355 Ext. 112

TeamSybase
* * Think Sybase * *

"Yoyo Young" <yo...@public1.wx.js.cn> wrote in message

news:46ef3531@forums-1-dub...

[Yoyo Young]

I have not found master-detail web page even not in Salesforce CRM
application.But master detail UI is commonly used in many complicated C/S
application.Master and detail datawindow updated in the same transaction is
one of the most strengh of EAF. I agree EAF has some weakpoints such as
scale,big size of component but it is qualified as application framework for
big business application. Argument service, Message service, Log,
Multi-Client support, logic unit of work and so on are all great. The major
limitation I think is EAF binded with JSP and EAServer. With the release of
PB11.NET, I have successfuly refactored it to ASP.NET and IIS WS.

As for security, it is done in customers' own application. It's not suitable
to put into framework. I have enjoyed the smlportal navigation feature. It's
really great, expecially at splendid UI. I have a different method about it.
I introduce a new concept: Program Unit. It's consisted of forms. There
serveral Program Unit type. Single, Master-Detail,Master-Detail-Detail,
Treeview, Pop, Inquery and so on. I define security by Program Unit +
Userid. Then I can define navigation rules by Field(Column) + Program Unit.
Keep in mind user don't understand what is form? It's hard for Administrator
to create and link forms. Program Unit is the interface of application.

I know smlportal has a report, form and navigation engine. They are based on
datawindow object. In my option, if you want to develop a pure engine
product, you should not use datawindow object again and use meta file
instead. I developed query, form and datawindow designer. Query, form file
are meta files. They can generate SRD on the fly. If you look into it, you
will find very flexiable if use query and form files.

I would like to open my EAF.Net. I had sent email to Carson about my plan.
But no reply. I don't want to get some legal issues.

Yoyo

"Dean Jones" <dean_dot_jones_at_powerobjects_dot_com> wrote in message

news:46efdb2a$1@forums-1-dub...