|
« Return to Thread: v11 update
Re: v11 update
by Alexander Heintz
::
Rate this Message:
Hi Aparajita,
sorry to bother again, but I have a mojor customer on my heels.
I delivered them the V11 conversion of their custom application and
now they are eager to put it into production.
But for this we need Active4D, they cannot go for more than 8 days
without their up to date data in the web catalogue, and I have as of
yet no idea how much work it will be to impelement A4D Version 5.
Any news for us? Preliminary documentation or a rough date for a first
alpha?
Or will I have to write an interim solution for getting the data
changed back into their old 2004 database? No point in doing so for 2
weeks of patience, for 2 months though...
TIA
Alex
> Hi all,
>
> Just an update on v11 progress. You may remember this picture of the
> Active4D architecture:
>
> runtime
> lexer | interpreter | server
> lists
> SymbolTable | values
> Variable4D
> framework
> arrays | text | date/time | files | 4D environment | logging
>
> I have worked my way up to the next to last layer. The lexer is now
> working, which is the piece which scans source text and converts it
> to tokens. That was a big (and obviously important) piece, and the
> key point at which I support Unicode. One nice new feature is that I
> scan the first 1K of an HTML page to see if there is a meta http-
> equiv tag which specifies the charset. If so, I use that charset to
> convert to Unicode, which I use internally. So I support all
> charsets now -- utf-8, big5, shift_jis, euc, you name it. You don't
> have to worry about the charset of a page not matching the
> configured platform charset.
>
> In the case of libraries and config files, if the first line is a
> comment and contains "charset=<charset>", I will use that charset
> when converting to Unicode.
>
> Now I'm working on the interpreter, which as you can imagine is a
> huge amount of work. But so far it is going quite smoothly -- at
> least as far as converting to Unicode and getting it to compile.
> Whether it works correctly I won't know until I start testing. I
> still have a few days of work left until the interpreter is done.
>
> I said I was shooting for the beginning of June for a beta, but I'm
> a lousy shot, and I forgot about the lexer, which took almost a
> week. At the rate it's going right now I can't see anything until
> the middle of June.
>
> Regards,
>
> Aparajita
> www.aparajitaworld.com
>
> "If you dare to fail, you are bound to succeed."
> - Sri Chinmoy | www.srichinmoy.org
>
> _______________________________________________
> Active4D-dev mailing list
> Active4D-dev@...
> http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
> Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
Active4D-dev@...
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
sorry to bother again, but I have a mojor customer on my heels.
I delivered them the V11 conversion of their custom application and
now they are eager to put it into production.
But for this we need Active4D, they cannot go for more than 8 days
without their up to date data in the web catalogue, and I have as of
yet no idea how much work it will be to impelement A4D Version 5.
Any news for us? Preliminary documentation or a rough date for a first
alpha?
Or will I have to write an interim solution for getting the data
changed back into their old 2004 database? No point in doing so for 2
weeks of patience, for 2 months though...
TIA
Alex
> Hi all,
>
> Just an update on v11 progress. You may remember this picture of the
> Active4D architecture:
>
> runtime
> lexer | interpreter | server
> lists
> SymbolTable | values
> Variable4D
> framework
> arrays | text | date/time | files | 4D environment | logging
>
> I have worked my way up to the next to last layer. The lexer is now
> working, which is the piece which scans source text and converts it
> to tokens. That was a big (and obviously important) piece, and the
> key point at which I support Unicode. One nice new feature is that I
> scan the first 1K of an HTML page to see if there is a meta http-
> equiv tag which specifies the charset. If so, I use that charset to
> convert to Unicode, which I use internally. So I support all
> charsets now -- utf-8, big5, shift_jis, euc, you name it. You don't
> have to worry about the charset of a page not matching the
> configured platform charset.
>
> In the case of libraries and config files, if the first line is a
> comment and contains "charset=<charset>", I will use that charset
> when converting to Unicode.
>
> Now I'm working on the interpreter, which as you can imagine is a
> huge amount of work. But so far it is going quite smoothly -- at
> least as far as converting to Unicode and getting it to compile.
> Whether it works correctly I won't know until I start testing. I
> still have a few days of work left until the interpreter is done.
>
> I said I was shooting for the beginning of June for a beta, but I'm
> a lousy shot, and I forgot about the lexer, which took almost a
> week. At the rate it's going right now I can't see anything until
> the middle of June.
>
> Regards,
>
> Aparajita
> www.aparajitaworld.com
>
> "If you dare to fail, you are bound to succeed."
> - Sri Chinmoy | www.srichinmoy.org
>
> _______________________________________________
> Active4D-dev mailing list
> Active4D-dev@...
> http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
> Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
Active4D-dev@...
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
« Return to Thread: v11 update
| Free embeddable forum powered by Nabble | Forum Help |
