12/21/2023 0 Comments Gui web editorThe issue of the errant main-view / browser Javascript helps us move some of the legwork from the server to the client, by allowing us to have a "smarter" controller for our view - just like in iOS. You can have a whole web app that acts without javascript, using only the default actions offered by links - in which case the browser will usually ask the server (the main controller) what to do. Javascript and links help us tell the controller what we want it to do, but it is the browser that acts (and willfully at times). The browser is the web-app's view's controller - it makes it all work together and serves it up to the screen. They could look something like this: body They have properties and values (like key-value pairs) that determine how the HTML data is displayed (if it's displayed). This "language" makes me think more about dictionaries in iOS (I think that's what they're called in Objective C). If your web app does't have any CSS, it will use the browser's default CSS/styling to be applied on the data in the HTML. The CSS (cascading style sheets) is the view - it states HOW the html DATA should be displayed. This should look familiar to you if you read any XML. HTML is a variation on the XML format and it contains data organized in a similar way to an XML file. The HTML is the view's model for the web-app - it contains the data to be displayed or used. It's not all that clear cut, but thinking like this helps me practice better and cleaner coding. If we break down the main-view (the browser) to a sub-MVC system, I would consider the HTML as the model, the CSS as the view and the browser (through links and javascript) as the controller. Just like any model in MVC, the view (the browser) can talk to the model (the database), but really it shouldn't. Just like in iOS, each of these can be (but doesn't have to be) broken down into sub-MVC systems. If we look at the whole of a web app from an MVC perspective, then the browser is the view, the server is the controller and the database is the model. I would start by trying to put the world of web programming and design into concepts that correlate with iOS coding. I think a bit of background will help you reach a correct decision. You can read about WYSIWYG html editors on this link, or try out ckeditor (someone said it's good). I can answer shortly stating that (technically) you can design web pages without coding in HTML or CSS, or even Javascript - although, you would be somewhat limited in your creative abilities and applications. If I have to learn HTML and CSS, so be it, but I'd like to know what my options are and the tradeoffs between each of them. I'm mainly just looking for a list of the accepted ways to develop the GUI for a web application. Is there any analog to the web front end? I know in iOS, you can use the Interface Builder (part of xcode that lets you graphically create the xml that describes the display) to create GUI's without any knowledge of how iOS translates the xml to some rendering, or even what is written in your xml files. I know that a web front end consists of html and CSS to create the display and javascript as the bridge between the back end and the GUI, but I don't know the best way to put something together. I'm interested in learning a stack to develop web applications, but I'm not sure what the right way to build the GUI is. I come from an iOS background where I exclusively wrote native code, so if you write your answers like I know nothing outside the shallow parts, that would be great. I have next to no knowledge about web applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |