Why htmlb is prefered to normal html code ?

[Former Member]

Hi,

I'am new to this forum, so excuse me for such basic questions.

We have already developed 2 small projects (vendor portal/gate computer system ) in my co using BSP , but since we had a background of asp/jsp/javascript we easily developed all the layouts in plain html lang , and we used max javascripting where we required , which we found more easy and confortable.

So may I know some major advantages of using htmlb besides the normal reasons of look and feel , as by and large almost every thing what htmlb does same can be done by javascript/html.

Re

Jignesh

[thomas_jung]

Remember that nothing is stopping you from creating your BSP extensions. This way you can still get some of the major advantages of HTMLB (reuse, event handeling, etc) with your own layout and javascript.

Don't get me wrong though. I think there are huge advantages to using the SAP libraries as have been stated. My team is a group of ABAP developers with no web development background (including myself). We would never be at the place we are with BSP without the HTMLB libraries.

[Former Member]

Thanks for all replies,

Ye it's true that for a non-web developer b'grnd it is easy to use htmlb.

Even handler is a part of BSP so in that case we cannot use html in any event handlers of bsp.

Any way it all depends on ur b'grnd as myself and ny team was more of web developer so can easily roll out semi portals without any formall training of bss and could develop it also very fast.

Re

Jignesh

[Former Member]

I would recommend trying small projects with it maybe even try out this tutorial:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/exploring bsp development and the miniwas.htm

[maximilian_schaufler]

Yes, you're quite right, htmlb is nothing else than packing some html and javascript code together, adding some CSS styles, ...

BUT, there are a million ways to take advantage of this:

Basically, you save a huge amount of time and effort using htmlb compared to writing the same functionality all by yourself.

Just take a look at some HTMLB examples, you will see many different scenarios where you could this and that implementing such elements in your application.

Unfortunately, unless you really start using these elements, you will only recognize part of the advantages, that's what I learned.

Although I used them from the beginning, I never stopped finding out some new information, or finding new elements for some purpose I wrote a workaround some time before.

Using htmlb just for design reasons can be a pain in the *** sometimes, because just as every additional "layer" between your finger and the HTML output it restricts your possibilities. For design I use a mixture of htmlb and html, but I try to use htmlb-like add-ons to my regular html wherever it's possible.

[Former Member]

Hi Jignesh,

You've got basically the same questions I had as well as Thomas Jung when we started (both of us have Weblogs on the subject).

Here are some of my reasoning for moving away from the question HTML/JAVASCRIPT

- More functionality and quicker to realize

- Overall design and layout compatibility throughout apps

- Event Handling

- Quicker development time

Basically for me, bringing people into from a non-webdesign background it made more sense. me being a web designer going way back it took a little while but I got used to them and now I resort to standard HTML only when adding in <a href="/people/sap.user72/blog/2004/11/16/bsphowto-add-a-maginfying-glass-to-your-application features</a>

[eddy_declercq]

HTMLB and MVC might be a step closer to Webdynpro (for ABAP) than 'normal' HTML. On the other hand, one has to think about browser support (see also ).

One can prefer plain HTML for its flexibilty and all CSS and Javascript goodies one can do.