Author | Topic: "W" Problem | |
---|---|---|
AUGE_OHR | "W" Problem on Tue, 01 Dec 2009 09:58:43 +0100 | |
AUGE_OHR | Re: "W" Problem on Thu, 03 Dec 2009 01:55:42 +0100 hi, >Arial 8 or 10 funny now i have test it with Arial.9 and 11 and it work ?! greetings by OHR Jimmy | |
JAYARAM MYSORE | Re: "W" Problem on Wed, 09 Dec 2009 04:51:22 +0530 Sir, I am new to OOPs and I have been migrating from Clipper 87. I see you have created a editing/display box while browsing. Could you please show me your code to do this. I would appreciate your help. Regards Jayaram "AUGE_OHR" <AUGE_OHR*AT*WEB.DE> wrote in message news:711b529f$7282f338$4081b@news.alaska-software.com... > hi, > >>Arial 8 or 10 > > funny now i have test it with Arial.9 and 11 and it work ?! > > greetings by OHR > Jimmy > > | |
AUGE_OHR | Re: "W" Problem on Wed, 09 Dec 2009 00:51:44 +0100 hi, > I am new to OOPs and I have been migrating from Clipper 87. I see you have > created a editing/display box while browsing. Could you please show me > your code to do this. I would appreciate your help. Shure ... hm .. how to start ... Question : if you are migrating you Cl*pper 87 Source ... did you know about Codeblock ? Codeblock are interdruce in Cl*pper v5.x and a "must" to understand how Xbase++ Callback Slot work Question : did you have begin to migrate ? Hybrid or "full" GUI ? so if you use Hybrid you might use Tbrowse ? under "full" GUI you might use XbpBrowse. to "setup" a Browse you have to build each Columne (TbColumne or XbpColumne) for each Database Field (or Array) which you want to display. both have a "Stable" Codeblock where you can sycronisize Browse (show only some data) with a other "Window" to display "full" data of a Record. now, which XbpBrowse, you have a Callback Slot :Itemselect where you can put you Codeblock for your "Action" you want to do: oBrowse:itemselect := {|| Do_my_Procedure(Parameter1,Parameter2 ...) } now while i use MDI i can open multiple "Windows", so i run every "Window" as own Thread thats in general, but it is a log Way from S87 ... you might have a look at "TopDown" 3PP Lib to migrate your S87 Source. also "Express++" may help you to migrate to Xbase++ if you like Cl*pper Command Style greetings by OHR Jimmy | |
JAYARAM MYSORE | Thank You on Wed, 09 Dec 2009 21:58:04 +0530 Dear Jimmy , Thank you for your kind reply. I am working on a hybrid. I am slowly understanding OOPs. My application is very huge and does lots of things, but is all in S87 style. I have studied all the samples and help, but I do not have a correct understanding of the Xbase parts and it's usage. So I am trying to get some tips. I have "TopDown" and "Express++" and am using them. But with limitations. Thank you once again. If you have time for me I could show my application on Teamviewer. Regards Jayaram "AUGE_OHR" <AUGE_OHR*AT*WEB.DE> wrote in message news:52f68f89$49801c5$c4a5@news.alaska-software.com... > hi, > >> I am new to OOPs and I have been migrating from Clipper 87. I see you >> have created a editing/display box while browsing. Could you please show >> me your code to do this. I would appreciate your help. > > Shure ... hm .. how to start ... > Question : if you are migrating you Cl*pper 87 Source ... did you know > about Codeblock ? > > Codeblock are interdruce in Cl*pper v5.x and a "must" to understand how > Xbase++ Callback Slot work > > Question : did you have begin to migrate ? Hybrid or "full" GUI ? > > so if you use Hybrid you might use Tbrowse ? under "full" GUI you might > use XbpBrowse. > > to "setup" a Browse you have to build each Columne (TbColumne or > XbpColumne) > for each Database Field (or Array) which you want to display. > > both have a "Stable" Codeblock where you can sycronisize Browse (show only > some data) > with a other "Window" to display "full" data of a Record. > > now, which XbpBrowse, you have a Callback Slot :Itemselect where you can > put you Codeblock for your "Action" you want to do: > > oBrowse:itemselect := {|| Do_my_Procedure(Parameter1,Parameter2 ...) } > > now while i use MDI i can open multiple "Windows", so i run every "Window" > as own Thread > > thats in general, but it is a log Way from S87 ... > > you might have a look at "TopDown" 3PP Lib to migrate your S87 Source. > also "Express++" may help you to migrate to Xbase++ if you like Cl*pper > Command Style > > greetings by OHR > Jimmy > | |
Clifford Wiernik | Re: Thank You on Wed, 09 Dec 2009 20:44:47 -0600 On 12/9/2009 10:28 AM, JAYARAM MYSORE wrote: > Dear Jimmy , > Thank you for your kind reply. > I am working on a hybrid. I am slowly understanding OOPs. > My application is very huge and does lots of things, but is all in S87 > style. I have studied all the samples and help, but I do not have a correct > understanding of the Xbase parts and it's usage. So I am trying to get some > tips. > I have "TopDown" and "Express++" and am using them. But with limitations. > Thank you once again. > > If you have time for me I could show my application on Teamviewer. > Regards > Jayaram > > "AUGE_OHR"<AUGE_OHR*AT*WEB.DE> wrote in message > news:52f68f89$49801c5$c4a5@news.alaska-software.com... >> hi, >> >>> I am new to OOPs and I have been migrating from Clipper 87. I see you >>> have created a editing/display box while browsing. Could you please show >>> me your code to do this. I would appreciate your help. >> >> Shure ... hm .. how to start ... >> Question : if you are migrating you Cl*pper 87 Source ... did you know >> about Codeblock ? >> >> Codeblock are interdruce in Cl*pper v5.x and a "must" to understand how >> Xbase++ Callback Slot work >> >> Question : did you have begin to migrate ? Hybrid or "full" GUI ? >> >> so if you use Hybrid you might use Tbrowse ? under "full" GUI you might >> use XbpBrowse. >> >> to "setup" a Browse you have to build each Columne (TbColumne or >> XbpColumne) >> for each Database Field (or Array) which you want to display. >> >> both have a "Stable" Codeblock where you can sycronisize Browse (show only >> some data) >> with a other "Window" to display "full" data of a Record. >> >> now, which XbpBrowse, you have a Callback Slot :Itemselect where you can >> put you Codeblock for your "Action" you want to do: >> >> oBrowse:itemselect := {|| Do_my_Procedure(Parameter1,Parameter2 ...) } >> >> now while i use MDI i can open multiple "Windows", so i run every "Window" >> as own Thread >> >> that´s in general, but it is a log Way from S87 ... >> >> you might have a look at "TopDown" 3PP Lib to migrate your S87 Source. >> also "Express++" may help you to migrate to Xbase++ if you like Cl*pper >> Command Style >> >> greetings by OHR >> Jimmy >> > > > I also own both Express++ and Topdown. Had to make a decision back in 2002. I use Topdown for some features but the majority of the work is in Express++. Not to say anything bad about Topdown, but at that time I went for the Express++ approach but learn alot from Topdown also. My application was a basic Summer87 but knew how to use codeblocks as it was in Clipper 5.2e for quite some time. I don't see any limitations and a basic template can be established that is used over and over. Cliff. |