Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread Graeme Geldenhuys
2010/10/25 luciano de souza: > Finally, I ask: does someone have an idea what can I do? Does someone > know other interfaces container based compatible with Pascal? I much prefer code based designing compared to Visual Form Designing. In a similar way you can compare OpenOffice or MS-Office to Lat

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread Vincent Snijders
2010/10/25 luciano de souza > Vincent, You got the point. When I came across LFMs, I thought a hard > code focus could not be used. > > But, I can imagine another problem. Lazarus interface is unbelievably > worse. So I would like to compile my projects only doing: fpc > project.pp. Using this me

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread luciano de souza
Marcos, it's not exactly a problem. My example in Lua is supplied only to show the hard code styly needed to my targets. Even if more code is required, it's always possible to enclose the complexity in classes. I really like Pascal and I expect to find a solution using only Pascal. I don't know h

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread Vincent Snijders
2010/10/25 luciano de souza > > My question is: is it possible to create all the interface with tform > without using the Lazarus interfaces, in other words, only typing > codes in a text editor? > Yes, everything you can do in the form designer can be done in code too. Take a look at all examp

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread Marcos Douglas
2010/10/25 luciano de souza : > [snip] > My question is: is it possible to create all the interface with tform > without using the Lazarus interfaces, in other words, only typing > codes in a text editor? Yes, but you will write more in Pascal than with IUP. Marcos Douglas ___

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread luciano de souza
It's really interesting. After looking for so libraries, it would be fantastic to find a solution with tform. But, regarding everything needs to be created only writing codes, without opening the inaccessible interface of Lazarus, do you believe can it be done? I give you an example using Lua. re

Re: [fpc-devel] [patch] removing compiler warning from aasmtia.pas unit

2010-10-25 Thread Jonas Maebe
On 25 Oct 2010, at 17:16, Graeme Geldenhuys wrote: > So yes, tai_section might have that "one" constructor as private, but in no > way does it stop anybody from creating an instance of that class with all > the inherited constructors (all being public). That's correct. > And in doing so, it wil

Re: [fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread Josι Mejuto
Hello FPC, Monday, October 25, 2010, 7:12:25 PM, you wrote: lds> 1. tform - it fulfills the items 1 and 3. A blind person cannot lds> program it. At first, because Lazarus environment is not accessible lds> and a blind people prefer to use only hard code without move objects lds> on a form. Secon

[fpc-devel] Chosing a graphical interface for specific proposals

2010-10-25 Thread luciano de souza
Hi listers, I am blind and I would like to program graphical interfaces in Freepascal. Perhaps, it sounds a little bit curious. Being blind, would I have interest in graphical interfaces? As the subject can be new for many of then, I will explain in detail what I really want. Blinds have been pro

Re: [fpc-devel] [patch] removing compiler warning from aasmtia.pas unit

2010-10-25 Thread Graeme Geldenhuys
Hi, I'd like to learn something here, so that's why I'm asking for a further explanation of this. Jonas said in the now resolved Mantis report: "The code is not trying to lower any visibility. The first declaration of that constructor is in tai_section itself. And making it private does make it

[fpc-devel] DWARF WinCE

2010-10-25 Thread Dimitrios Chr. Ioannidis
Hi all, i tried to cross build for the arm wince using a compiler ( builded by me ) from the trunk rev. 16218 with : "make all crossinstall OS_TARGET=wince CPU_TARGET=arm UPXPROG=echo OPT="-glw3" INSTALL_PREFIX=C:\Programming\Compiler\fpc BINUTILSPREFIX=arm-wince- FPC=C:\Programming\Compiler\