Buttons on a web page

[ILEllis]

Re: Buttons on a web page

One other quick note before I get some sleep...I can build a grid component from the member registration table. A quick experiment with that proved successful but does not provide the actions I described in my first post here. Plus I didn't have time tonight to see how customizations would work out on the grid component.

My method would actually display a simple web page with two buttons that I had hoped to attach script to that would then display my already custom built form from the desktop application and go from there. Can I do this and is it the most efficient way? Or must I go the grid component path for sure? Are the desktop made forms and applications completely isolated from use with the web application server? What are some of the options maybe available via raw XBasic code (and I'm sure there is) compared to the genies using the scenario above as an example?

In the future I'll probe further into the XBasic but I'm primarily looking for the efficient way at the moment as I have a time frame to work in.

[ILEllis]

Re: Buttons on a web page

Sorry guys, the post above was meant for another thread I started...

[[email protected]]

Re: Buttons on a web page

Howdy Clint, no problem and the suggestion about tables is really great in more than one way as mentioned.

My greatest hurdle though is my new Web Application Server recently purchased so I could create a virtual club of sorts. I've taken care of most of the basics and can get it up and running on the web. Several web pages are taking form but I believe I have a need to understand the "big picture" better. Maybe one of you could enlighten me some.

I have been using Alpha software in one form or another for years now. Long ago I use to develop relational databases using basic programming and eventually Alpha Four (the old DOS version...and I still have it today) and have always been comfortable with XBasic (even though I'm currently a little rusty at it) with my Alpha Five version 5. Now it is Alpha Five version 7 and the web application.

From much that I have read I have a good understanding of the bits and pieces within the packages I have purchased but I'm having trouble (and not for the lack of researching this) bringing it together with the new Web Application Server.

I read somewhere that one way to look at it was the data files are the common element between the two distinct applications, 1) the desktop Alpha Five application and 2) the web application server. The web application server allows you most of the flexibility of the desktop application when it comes to deploying the tables of data (in the form of forms and browses) to be used on the web (correct me if I'm wrong?).

So as I see it my biggest problem is learning the proper path to take to deploy the forms and browes and such on my web pages. In other words I can pretty much manipulate just about all the elements currently in either application but learning the "steps" with each element is really the slow part for me. Its the lack of having the "big picture" put before me.

The tutorials are all excellent as I grasp them well but even so they haven't brought the image to mind on how all the pieces of the application work together and the "steps" to put those forms and browes on the web pages. If I get past that I'll break the barrier so to speak and be on my way. :o

So if you can spare some time and explaination I'm all ears! If you know of a good reference for what I have described I'd be most grateful to be pointed to where I might find it. I not afraid to read and learn, just got to have the right stuff. :)

[Begin rambling:]
When starting a relatively new concept, the key is to start modularly. Make sure each piece works with as little frills (securing the web page can wait till you have real data for example and the server shouldn't allow browsing [undirected scans] anyway by default).

Make a rough drawing of your desired flow and put the grids/dialogs up that fill each task. When you have a basic grasp on what your application needs to look like, flesh out those components.

A great programmer once wrote, and I'm paraphrasing, "to get an application right, you need to write it 3 times. The first time you learn so much that it's clear you need to start over. The second time you find out what was really wanted and by the third time it's pretty close to what was really needed."

However, who has that kind of time/money?

By going modular in your development, you can approach the above concept. You'll learn each time you make a new module (ideally) and take that knowledge with you onto the next module.

You might want to tap a few of the professional developers here to get a price to make a few pieces for you. You could then use those pieces that reflect your desired outcome as a guide on the go-forward. That is what I did to get jump started myself (thanks to those developers /wave).

Of all the web development I've done, WAS is by far the easiest in comparison.
However, instantly intuitive, it's not. Don't let yourself spin your wheels too long, people here can't remotely write your application for you (alas...) but quite a few will if you pay them /smiles (I'm not looking for work, fyi).

[End Rambling:]

[ILEllis]

Re: Buttons on a web page

Thanks Clint...no problem, modular is the word. That is exactly the way I used to do raw flat out programming. I always built the "blocks" that I could use over and over again. Much better than the old "spaghetti" programming. Once I get use to the WAS and putting up stuff I'll be doing just that, I'll actually try to refine my scripts and save the common ones as "building blocks" for later. As long as I have used Alpha I have always liked it and that knowledge of how they (Alpha) brought it along compared to other relational database software has kept me a solid customer with them whenever I needed those tools (and that has never changed). I own many version of Alpha software.

I definitely don't want to scare off the help I have received so far. I probably have over explained things (my fault) to try and make sure you can see what I was getting at. I really don't need help programming or even using the Alpha software, I will sit and read for hours if need be to overcome even the smallest problem myself there, the documentation does a fine job in that area, but falls a little short in bringing the big picture together (it is scattered through the details) so it is the big picture concept, or methods I was looking for help on. I understand relational database programming very well, and the WAS stuff fairly well (web security is no doubt a major concern of my own).

I read a very interesting thread last night with Peter, Chris and Lenny about a method Peter questioned. In that discussion Lenny mentioned an interesting concern about how even the most obscure web site that collects passwords and personal data could possibly be held liable for compromise of such data that could be used elsewhere due to a mere fact of how people use passwords and such. Not as risky as someone just walking off with a disc such as recently happened in the US veterans administration but lessons we should all pay attention too. Back on subject...

Peter made one really short commit to me in another thread that really help me "see" something more clear. I had already stated the correct idea but I myself was just unsure if I had it right, he said I was right and now I can approach that thinking with confidence and research things further myself with that correct point of view. That really helps. The other thing is becoming familiar with where some things are. I know what to do but need to know where the thing is to do it with.

Peter cleared up the fact that I can not use the forms and browses made within the desktop side of the application to use on the WAS. I must go to the web design components to do this. That is a hugh help knowing this. Now I probably need to go back and read things again some because I'll know how to keep them separated. I just need those small prods now and then to keep me straight and I appreciate any you can share...and I'll try not to bore you to much...end rambling. :D

[[email protected]]

Re: Buttons on a web page

Thanks Clint...no problem, modular is the word. That is exactly the way I used to do raw flat out programming. I always built the "blocks" that I could use over and over again. Much better than the old "spaghetti" programming. Once I get use to the WAS and putting up stuff I'll be doing just that, I'll actually try to refine my scripts and save the common ones as "building blocks" for later. As long as I have used Alpha I have always liked it and that knowledge of how they (Alpha) brought it along compared to other relational database software has kept me a solid customer with them whenever I needed those tools (and that has never changed). I own many version of Alpha software.

I definitely don't want to scare off the help I have received so far. I probably have over explained things (my fault) to try and make sure you can see what I was getting at. I really don't need help programming or even using the Alpha software, I will sit and read for hours if need be to overcome even the smallest problem myself there, the documentation does a fine job in that area, but falls a little short in bringing the big picture together (it is scattered through the details) so it is the big picture concept, or methods I was looking for help on. I understand relational database programming very well, and the WAS stuff fairly well (web security is no doubt a major concern of my own).

I read a very interesting thread last night with Peter, Chris and Lenny about a method Peter questioned. In that discussion Lenny mentioned an interesting concern about how even the most obscure web site that collects passwords and personal data could possibly be held liable for compromise of such data that could be used elsewhere due to a mere fact of how people use passwords and such. Not as risky as someone just walking off with a disc such as recently happened in the US veterans administration but lessons we should all pay attention too. Back on subject...

Peter made one really short commit to me in another thread that really help me "see" something more clear. I had already stated the correct idea but I myself was just unsure if I had it right, he said I was right and now I can approach that thinking with confidence and research things further myself with that correct point of view. That really helps. The other thing is becoming familiar with where some things are. I know what to do but need to know where the thing is to do it with.

Peter cleared up the fact that I can not use the forms and browses made within the desktop side of the application to use on the WAS. I must go to the web design components to do this. That is a hugh help knowing this. Now I probably need to go back and read things again some because I'll know how to keep them separated. I just need those small prods now and then to keep me straight and I appreciate any you can share...and I'll try not to bore you to much...end rambling. :D

You can inexpensively protect your offsite backup by encrypting it before it leaves the building (TrueCrypt). A better way is to encrypt, in place, the data on the server. Then it's only available to those who have proper authorization.

WAS can encrypt via Xbasic (it's not a powerful as AES maybe) but you'd be showing due diligence I believe.

I'm assuming encryption on the fly will be more easily implemented in following releases (hoping).

[Rayr]

Re: Buttons on a web page

Thanks Clint...no problem, modular is the word. That is exactly the way I used to do raw flat out programming. I always built the "blocks" that I could use over and over again. Much better than the old "spaghetti" programming. Once I get use to the WAS and putting up stuff I'll be doing just that, I'll actually try to refine my scripts and save the common ones as "building blocks" for later. As long as I have used Alpha I have always liked it and that knowledge of how they (Alpha) brought it along compared to other relational database software has kept me a solid customer with them whenever I needed those tools (and that has never changed). I own many version of Alpha software.

I definitely don't want to scare off the help I have received so far. I probably have over explained things (my fault) to try and make sure you can see what I was getting at. I really don't need help programming or even using the Alpha software, I will sit and read for hours if need be to overcome even the smallest problem myself there, the documentation does a fine job in that area, but falls a little short in bringing the big picture together (it is scattered through the details) so it is the big picture concept, or methods I was looking for help on. I understand relational database programming very well, and the WAS stuff fairly well (web security is no doubt a major concern of my own).

I read a very interesting thread last night with Peter, Chris and Lenny about a method Peter questioned. In that discussion Lenny mentioned an interesting concern about how even the most obscure web site that collects passwords and personal data could possibly be held liable for compromise of such data that could be used elsewhere due to a mere fact of how people use passwords and such. Not as risky as someone just walking off with a disc such as recently happened in the US veterans administration but lessons we should all pay attention too. Back on subject...

Peter made one really short commit to me in another thread that really help me "see" something more clear. I had already stated the correct idea but I myself was just unsure if I had it right, he said I was right and now I can approach that thinking with confidence and research things further myself with that correct point of view. That really helps. The other thing is becoming familiar with where some things are. I know what to do but need to know where the thing is to do it with.

Peter cleared up the fact that I can not use the forms and browses made within the desktop side of the application to use on the WAS. I must go to the web design components to do this. That is a hugh help knowing this. Now I probably need to go back and read things again some because I'll know how to keep them separated. I just need those small prods now and then to keep me straight and I appreciate any you can share...and I'll try not to bore you to much...end rambling. :D

Hi ILEllis,
What is the link to the thread you talk about?

[ILEllis]

Re: Buttons on a web page

Howdy Ray,

If it is the thread I read the other night this should be the link...

http://msgboard.alphasoftware.com/al...ad.php?t=62286

[Rayr]

Re: Buttons on a web page

Howdy Ray,

If it is the thread I read the other night this should be the link...

http://msgboard.alphasoftware.com/al...ad.php?t=62286

Thank you