Re: [ql-users] basic HTML viewer?
Lots of ideas, thanks guys. Basically, the two things that I need it to do is different font sizes (CSize is just fine), some form of graphics (compressed), hyperlinks, and tables. Frames is an option but not really necessary, at least for first round. If it is ready to go great, but am expecting to have to do some work on it so the source code is very good. I am also concerned with size of the code and speed. You all gave me a lot of options so I will start looking at them, probably on the plane on the way to the US QL show. I guess we are still waiting for a response from Tarquin on his efforts. Again, thanks for the input. Any other ideas or advice will of course be appreciated. I will let everyone know what I find. Jim On Monday, May 20, 2002, at 06:01 PM, Timothy Swenson wrote: At 10:40 AM 5/20/2002 +0100, you wrote: Hi James. There was an HTML browser for the QL going around some time back, written in SuperBasic. The last I heard was that there were a couple of problems with it, and I haven't heard much since then. (Was it Tarquin ?) I believe you are talking about Hyperbrowse. There was also an earlier browser written by somebody in Italy. They used CSIZE to show the different font sizes from HTML. I've got a copy around but I don't know if the source code was distributed. Tim Swenson
Re: [ql-users] More C68 help - pointer env; positioning windows
Here's the other question, as another refloat for anyone who missed it. Any suggestions more comments/suggestions anyone? Thanks, Jim On Thursday, May 16, 2002, at 12:12 AM, James Hunkins wrote: Here's another question while I am at it. Normally when I position a window at an absolute location in the pointer environment, it goes where it belongs. However, I am resizing a window (I manually remove the definition, reset the data structure, and reopen it) and it goes where it belongs every other time. The off times it shoots to the left of the screen, pretty much in parallel with its correct location. The next resize sends it back to where it belongs. It has been suggested that it is because the window position is relative to the cursor, even when I do an absolute address. This sounds familiar and I think that I had this problem before and figured it out. However, I seem to be stuck again. Could someone walk me through the peculiarities of window positioning within the pointer environment. I do not want to set the window relative to the pointer but instead in an absolute location. Thanks guys, Jim
Re: [ql-users] Event help in C68?
I would like to refloat this (seems that a couple of people missed these questions last weekend). Below is my original request for help on eventlists and communicating between jobs. I did get the note to look at Jonathan's CSM and will do so. But any advice on using events such as the pointer environment is set up to do would be great. Thanks, Jim On Thursday, May 16, 2002, at 12:01 AM, James Hunkins wrote: Hey Guys, I have finally decided to join this list as my work on QDT progresses (thanks Marcel for recommending that I try this). Was putting it off due to time constraints but now seems like a good time with a cry or two for help. I could use some assistance in using C68 in the pointer environment in passing an event from one job to another, which I can not currently get to work. I have tried two scenarios. 1) using sms_sevt and sms_wevt - I used the job ID received back as an integer from sms_info for each job . when these were checked they matched the job ID listed with the SBASIC command jobs but did not include any tag info, etc. ? is this the correct job id to use in these calls? If not, how can I obtain the correct ID? - I set the eventlist for sms_wevt = 0xFF so that it would accept any event sent it - sent an event with sms_sevt to the sms_wevt program - nothing received 2) using iop_rptr (enhanced for the upper 8 bits for vectors) and sms_sevt - same job ID as described in 1) - assumed that sms_sevt is actually using the upper 8 bits of the vector list that iop_rptr checks - sent event - nothing received (checked both upper and lower bytes) Can anyone help me with this? If not in C68, then in assembly. I should be able to match the two. I need to do this to communicate between my icon objects and their associated folder in QDT. Thanks, Jim
Re: [ql-users] Source Code
I am sorry to say that I am very, very disappointed. I have been a loyal QL user from nearly day 1, have never made any money off of it, but keep going at it. I am now working extremely hard on QDT as some of you may know. To be honest, it is a labor of love. I will be happy if I ever make enough money to pay for my trips to the shows that I do get the chance to attend. I am very appreciative of all who have kept the QL alive. Some make money off if (not much I bet) and others don't. This includes both those involved in the hardware and software; all very much appreciated, whether or not I use their product. Everyone counts in this group. I recently just joined this email list because I was hoping to get some help on some implementation problems that I am having with the QDT project. Instead I have been getting this stream of emails that, to be very blunt, sounds like a lot on non-productive whining. I understand that there are major disagreements in the license plans for SMSQ/E. But I would hope that, instead of putting the dirty laundry out for the public to see (and it is very disappointing to have to see all this), that the parties who are involved would try to have some constructive and pro-active direct contact amongst themselves to resolve the disagreements. And, as it is in the real world, not everything is going to be perfect for everyone. The parties involved need to step back, take a breath, try to understand what is important to them AND to the others. And then, and only then, with that understanding and acceptance, come up with some real proposals that try to do the best for all involved. I will continue to work on QDT. I made a decision a long time ago that it will require SMSQ/E to run as there are some major pieces that I need from SMSQ/E to to it properly without having to write a tremendous amount of additional code. I would hope that everyone can come to an agreement about this license that will support SMSQ/E for all systems currently available which will allow QDT to also run on them. Just as a final reality check, until a few months ago, SMSQ/E was not open source or anything else. It was being maintained by Tony and a few vendors who put a lot of effort into getting changes done as required to run on different systems and to add important capabilities (such as color drivers). And I suspect that there hasn't been much money made off of it for some time for anyone. As far as I can see, with the new licensing being worked out, everyone should try to make the best of it for everyone, instead of making it ideal for themselves. I hope that this didn't come over too bluntly, but I have to deal with disagreements much larger than this everyday in my 'real' job and we get them resolved, without resorting to the kind of stuff that I have been reading for the last couple of days. I really enjoy working on my system and my development of QDT. So, please guys, just find a way to resolve this and get on with it. Jim
[ql-users] QDT
QDT seems a very interesting development. A GUI would put 'QL_ware' into the frame with modern OS's. I learn't computing on non-GUI machines, yet I now use the GUI's available for other OS's all the time. I haven't commented on QDT before ... yet if you need any help with user testing, then I could oblige. Actually, while QDT started, as you say, as a desktop GUI, it is growing rather dynamically. It turns out, as most of us realize, there are a lot of capabilities available for the QL thanks to different people who developed things like FileInfo, Scratch, Screen Dazzler, pointer environment, etc. However, many users (including myself) have not taken advantage of all of them due to knowledge limits and/or time constraints. So QDT will be trying to give easy and clear access to many of these capabilities under its desktop GUI environment. After the US QL show in a couple of weeks, I will start working on updating my websight. The update will show hints at a lot of the 'new' interfaces to the different QL capabilities. I suspect that it will take 3-4 weeks after the show and I will let everyone know when the update is completed. I will be showing some of the interfaces at the US show for those who can attend. The beta testing will be done by a small and tightly 'controlled' group (resources and time are a huge problem for me - as they are for most people). I will keep your offer in mind when the time approaches. Cheers, Jim
[ql-users] Event help in C68?
Hey Guys, I have finally decided to join this list as my work on QDT progresses (thanks Marcel for recommending that I try this). Was putting it off due to time constraints but now seems like a good time with a cry or two for help. I could use some assistance in using C68 in the pointer environment in passing an event from one job to another, which I can not currently get to work. I have tried two scenarios. 1) using sms_sevt and sms_wevt - I used the job ID received back as an integer from sms_info for each job . when these were checked they matched the job ID listed with the SBASIC command jobs but did not include any tag info, etc. ? is this the correct job id to use in these calls? If not, how can I obtain the correct ID? - I set the eventlist for sms_wevt = 0xFF so that it would accept any event sent it - sent an event with sms_sevt to the sms_wevt program - nothing received 2) using iop_rptr (enhanced for the upper 8 bits for vectors) and sms_sevt - same job ID as described in 1) - assumed that sms_sevt is actually using the upper 8 bits of the vector list that iop_rptr checks - sent event - nothing received (checked both upper and lower bytes) Can anyone help me with this? If not in C68, then in assembly. I should be able to match the two. I need to do this to communicate between my icon objects and their associated folder in QDT. Thanks, Jim
[ql-users] More C68 help - pointer env; positioning windows
Here's another question while I am at it. Normally when I position a window at an absolute location in the pointer environment, it goes where it belongs. However, I am resizing a window (I manually remove the definition, reset the data structure, and reopen it) and it goes where it belongs every other time. The off times it shoots to the left of the screen, pretty much in parallel with its correct location. The next resize sends it back to where it belongs. It has been suggested that it is because the window position is relative to the cursor, even when I do an absolute address. This sounds familiar and I think that I had this problem before and figured it out. However, I seem to be stuck again. Could someone walk me through the peculiarities of window positioning within the pointer environment. I do not want to set the window relative to the pointer but instead in an absolute location. Thanks guys, Jim
