Recently I made a simple application and tried to publish it to webform successfully. The following is a summary:
1. The webform development method is completely different from the C/S development method. Theoretically, it can be released in two ways at the same time. I was so happy for a while at first, but it actually didn't work.
1.1 The web does not support too many functional attributes.
1.2 different color systems. C/s color background (silver gray) should be almost all changed to white. If silver gray is used on the web, it seems that it is not something.
1.3 No client interaction functions are available under C/S. For example, DW responses are not supported in the Web, double-click events are supported, and right-click events are supported. However, if you click a row, when you move the mouse over DW, clicking events frequently causes callback to the server. So JS should be good, but I didn't study it, because I haven't learned about JS yet. In addition, it seems that only DW supports JS Code. If you do not know that JavaScript is supported for detecting a systemic logic.
1.4 after reading the HTML and CSS tutorials, I feel that if you want to implement simple forms and control, Pb does not leave a necessary channel for HTML and CSS, or use a table element. Some interfaces are simple, and static elements are the fastest to implement. For example, in the CGI template HTML, input conditions to the customer, or input data, use JavaScript to check validity, and then submit the data to the CGI database or return the result interface. However, in the Pb-based conversion to the webform framework, we are far away from these basic designs and controls. If you can add some controls that can be directly converted into standard HTML controls in aspx, it is good.
The source code of 1.5 Pb-to-web conversion is extremely complex because it has a complete framework. This makes it difficult for ordinary people to modify HTML, CSS, JS, and apsx unless they are familiar with HTML, CSS, and apsx. After the app is published again, you cannot retain the modified content. That is to say, it is impossible to participate in direct control of aspx, HTML, and CSS (CSS). The key is that it cannot be retained ). Because it is the idea of translate, it is not a design mode that can be switched between layout and code. From the link style, the CSS of radcontrols is mainly used in the control interface. It can be said that if you are familiar with HTML, CSS, JS, and apsx, you can still be well involved in some control.
1.6 It is said that PHP and other developed websites are fast, and where is it, because its interface is directly designed in HTML, and then embedded in PHP or embedded in HTML with placeholders as templates, write the template and output it. Of course. Let's look at the client source code generated by Pb-converted Aspx. It is estimated that the traffic alone is several times larger. It's too complicated. Of course, interactions between browser websites or business shopping websites and projects such as MIS and ERP are incomparable. A housekeeper's pharmacy manager can create more than 400 tables (a bit of that... FK table can be set, at least I think this is an improper design ). Generally, ERP has hundreds of tables. However, the structure of a general browser-type website or a business-type shopping website is not too complex. In addition, the first factor to consider for large websites is speed and traffic endurance. Therefore, the fastest web development method is CGI + HTML placeholder templates, as well as PHP embedding and PHP + HTML placeholder templates. This is because all content except the interaction part is static. The interaction part is filled with text.
1.7 How to obtain common HTML development technologies, such as directly processing the data transmitted in an HTML form, is there a way to receive and process Pb of standard HTML get or post data?
1.8 How to call some other setcookies?
Other problems:
* One of my Query Interfaces (form) has many fields. An error occurs (11.5 ). It is okay to compile with 12. So it is a bug. Some people complain that there are many bugs in 11.5. you can use 12 to compile them.
* Access via a web site or IP address. As long as it is not a local machine (http: // localhost), the password verification box cannot be displayed. Only a trusted website can be set to pop up.
* The number of items displayed by the DW used as the list cannot be too large (20 pages by default). If there are too many items (that is, the data is displayed by moving the DW vscroll), the other interfaces are very slow to open. It may be a bug for even a dozen seconds. I tested it. Just set DW. Reset immediately. If we can only use about 20 pages, the advantages of DW seem to be almost the same.
* I use a main window. It seems that MDI cannot be used or is difficult to use. Besides, because it is not executed locally by C/S, there is no need for MDI at all.
On the contrary, it is easy to directly switch the form through the "window" menu in the upper right corner. If it is a conditional input window, a response window or a pop-up window is required.
* Export and save. My own practice is to export the list as XLS (there is a function on the Internet that can transfer the title, rather than display the English), and save the form as WMF (I feel that the form is rarely used for XLS conversion ), the program directly generates a file to the server directory by DW name + time (temporary directory or you put it in the root directory of the program just like C/S), and then calls the download function immediately. In this way, I feel better, and it is in line with the webpage operation habits. The file manage window is not intuitive to the customer.
* To beautify the interface, you can only use images. In the past, there was a simple method for Beautifying c/s, that is, if it is the same large block area, you can use a horizontal or vertical 1px image, which is very small, and then you increase the size of the image, the 1px image is automatically filled. Avoid using large images. Tip: The title of DW is very ugly. You can do this.
I think Pb is a joke if it cannot directly manipulate HTML and CSS like. Because how can we say that technical things, such as CPU dual-core, won't be used again, lag behind or don't class, naturally cannot be used.
So I suggest you lock the PB on the C/S. According to Sybase's suggestion, if the C/S-based application occasionally uses web queries or read-only display, it can be easily implemented using web conversion. For traditional interaction functions. It takes at least some effort to write the code, and many places have to be optimized. The main object of optimization is to consider the speed. There is also the interface senses. The Web is like that, and people already have a basic sensory requirement.
In fact, I really want to learn about web page design. So I saw some PHP, HTML, and CSS from the past year. I am thinking: If you are building a website that really means something, PHP and Java are all popular now. C # is also good. But after reading it, I understand that the speed of a business website or a Website visited by many people is exquisite. I think most of them use templates + CGI. Templates are designed with DW and placed with placeholders .. If the background is faster, it seems that php development is better. It seems that Baidu and Google have all heard about PhP improvements. In other words, enterprise applications mainly involve interaction ..... It may be the C # control or Pb-to-web conversion method. Because, although I am not developing a website myself, I am not even getting started. However, I feel that websites that are dedicated for browsing are not likely to be swallowed up and use datawindow. If they are not used, they are all specially modified columns .. Therefore, the application is different. The Web developed by petabytes is mainly used for data processing and interaction... Different applications. It is also troublesome for you to use a general website development model to develop a program that can enrich interaction. If you don't believe it, try it .. So I thought for a long time, but there is actually a line. Know this. Basically, pbweb has a correct attitude.