Pete's Front Nine - Printable Version +- QB64 Phoenix Edition (https://qb64phoenix.com/forum) +-- Forum: QB64 Rising (https://qb64phoenix.com/forum/forumdisplay.php?fid=1) +--- Forum: QBJS, BAM, and Other BASICs (https://qb64phoenix.com/forum/forumdisplay.php?fid=50) +--- Thread: Pete's Front Nine (/showthread.php?tid=1094) |
Pete's Front Nine - dbox - 11-10-2022 Hey Pete, here's a little proof of concept for your golf score card project. I didn't have your background image file so I just focused on the mechanics of what I think you are trying to achieve. As you enter the scores the total field is updated automatically. Clicking the Save Scores button will add the current set of scores to the saved score list. This list will be saved to the browser's local storage as well as to a "scores.csv" file in the QBJS virtual file system. You can access this in the Files tab of the Console. Code: (Select All) Import Dom From "lib/web/dom.bas" View in QBJS RE: Pete's Front Nine - Pete - 11-10-2022 Okay, that produces about 300 lines of JavaScript with several functions. It looks like instead of working with the form elements, it replaces them. So what's next for embedding it my HTLM doc? Wouldn't I need to strip out all the JavaScript functions, enclose them in <SCRIPT></SCRIPT> tags and then there would be the whole process of figuring out a way to call it. If concepts like this could be integrated directly into an HTML doc, that means use over the Internet is achieved. +2 for the example code, as it looks like it totally handles the mechanics. Pete RE: Pete's Front Nine - CharlieJV - 11-10-2022 (11-10-2022, 04:31 PM)Pete Wrote: Okay, that produces about 300 lines of JavaScript with several functions. It looks like instead of working with the form elements, it replaces them. So what's next for embedding it my HTLM doc? Wouldn't I need to strip out all the JavaScript functions, enclose them in <SCRIPT></SCRIPT> tags and then there would be the whole process of figuring out a way to call it. If concepts like this could be integrated directly into an HTML doc, that means use over the Internet is achieved. I'd consider the security implications of embedding anybody else's javascript in your website/whatever. It isn't so much about the potential for the author(s) of that javascript having bad intentions (although that can happen), but the potential for mistakes to get into that code, for some of that code coming from who knows where as it got pasted in for expediency, or whatever. I'd suggest that you isolate all code that isn't yours by displaying it within an iframe. Browsers are secure to the point of being annoying sometimes, but it is a good thing. It all falls flat when you introduce into it code that is too big to personally and closely scrutinise before letting it intermingle with your stuff. Might not matter any for what you are doing, but still worth keeping in mind for those cases in which "sure you can do that, but just because you can doesn't mean you should" moments ... RE: Pete's Front Nine - dbox - 11-10-2022 I think I get where you are coming from. If I understand correctly, you are wanting to use QBJS more like VBScript so that you could do something like: Code: (Select All) <html> It's interesting, that might be feasible... I'll have to look into it further. At present though it's more analogous to the single-page application paradigm where you are creating web UIs that function more like thick client applications and are more dynamically constructed. As far as sharing what you've constructed on the web though there are a couple of options in the current release. You can create a share link like this one that will launch QBJS in "Auto" mode which will hide the IDE and automatically compile and run your web program: Simple Web Calculator Or, you can export the "compiled" version of the application to a standalone zip folder with the Export feature if you'd like to host it elsewhere. I've attached an example of the exported version of the same Simple Web Calculator application. RE: Pete's Front Nine - Pete - 11-10-2022 I think the pseudo code you posted does reflect quite closely what I'm looking for. I see HTML/CSS as the best way to design content, and QB64 translated into JavaScript as the best way to make that page content interactive. My thought was since the QBJS system produces the JS, just copy and past that into head or link it as a file, and then figure out how to call it in the page. The calculator running as the webpage is solid. Put that in a JS popup window on a site and it's perfect. One note, and you probably know this. The calculator is susceptible to floating point errors. You may want to note that so no one expects to use the demo as a reliable website calculator. If you haven't seen the issue before, try 10 addition iterations of a penny, .01 + .01... At 6 and 10 it will error. I will take some time and digest the components provided and see what I can come up with. Fun stuff and maybe a whole new future opening up.To think, I was almost retired! Pete RE: Pete's Front Nine - SMcNeill - 11-10-2022 I'm wondering if what Pete's looking for isn't geared a little more towards a html5 version, rather than a javascript based version. RE: Pete's Front Nine - Pete - 11-10-2022 HTML 5 mostly helps get rid of plugins for vids and music. Uses a canvas tag. I've never used that, but I have used the <NAV> tag. Pete |