Hi,
I have it half way done. Run the test program and you can see. Program works in
W2k, XP and Wine. mingw32-gcc -mwindows -Os GetGlyphOutline.c -o ggo.exe
I stopped messing with it two weeks ago, I needed to work on something else.
When testing you can select the alphanumeric character with the keyboard. The
original program had "a" but I changed it to "L" something simple to draw at
first. You will see the problem.
The test program from Dr. Dobb's Journal http://www.ddj.com/184409154?pgno=12
Thanks,
James
Runs and hides~
Magnus,
I beg my pardon, but since when is it allowed to revert someone
else's commit without discussing first?
There is a rule which might allow revert provided:
1) The change breaks booting
2) More than 24hours passed from the commit time
3) Author can not be contacted by any means
None of the above was true, so why did you make a reverting commit?
With the best regards,
Aleksey Bragin.
On Dec 30, 2006, at 4:11 AM, greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Sat Dec 30 04:11:14 2006
> New Revision: 25246
>
> URL: http://svn.reactos.org/svn/reactos?rev=25246&view=rev
> Log:
> do not use hacked vfat drv revers the 25243
> the hacked do not delete pendling or incomplte data
> and so on,
>
> Modified:
> trunk/reactos/drivers/filesystems/vfat/cleanup.c
> trunk/reactos/drivers/filesystems/vfat/close.c
> trunk/reactos/drivers/filesystems/vfat/create.c
>
greatlrd(a)svn.reactos.org wrote:
> Author: greatlrd
> Date: Fri Dec 29 03:09:54 2006
> New Revision: 25236
>
> URL: http://svn.reactos.org/svn/reactos?rev=25236&view=rev
> Log:
> freetype cache glyth patch pass last all my test.patch
> ogrinal author of this patch is royce3, modify by tinus so it work again with trunk, ThePhysicist (timo dot kreuzer at web dot de) did fix the last bugs in it. at last long leave freetype glyth patch, now we got faster text output in reactos. and I where up to 38fps in winquake with this patch (debugbuild + serial debug on). This is very fast. I wonder what speed it give in release build or qemu now.
>
>
I think you should remove the hits++ and misses++ and hits > 100/misses
>100 code because it seems perf-debugging related only.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
So I logged in and registered my user name about a week ago with
ReactOS, and now I am unable to log in. I tried resetting my password
on the site, and it still won't let me log in. Can you direct me to
information on how I can get logged in, or what may have happened?
Thanks,
Nathan
Ged Murphy wrote:
>
> *lots of things*
>
As there were no responses, I'm assuming everyone was relatively happy with
the proposed system.
The lack of action isn't doing ROS any favours though, the 0.3.1 release has
been promised on various news sites for 31st December, and we haven't even
branched for it yet!!
I'm prepared to help kick start this new release system off, if it'll help
to stop ROS going for another year without releasing.
I propose we pick the most stable recent release, branch it and prepare for
a Dec 31st release according to the new release system.
If everyone is in agreement, I'll start making the necessary arrangements.
Ged.
Hello,
there are a few ideas I would like to get feedback about:
1) iBrowser. Do we need it nowadays in the tree, when we have firefox
working?
2) In order to slightly decrease a load to our build servers, Alex
proposes to build Debug version without any optimizations at all,
thus increasing compilation speed.
For regression testing, release builds should be used, since release
builds are the most sensitive to possible errors.
3) RBuild improvement - the "components bundles" concept should be
(re)introduced: if I type "make <directory name>", I would like to
get all components inside that directory to be built.
4) Dependency map of ReactOS - maybe this should be implemented
inside of RBuild too. Dependency map is a tree, which shows how
modules depend from each other. Fortunately, we don't need to do this
by hand, since we can use rbuild's parsers/etc. Output format of the
map - open for suggestions.
If someone feels he is able to do point 3 or 4 - this is greatly
appreciated, and will help development of ReactOS.
With the best regards,
Aleksey Bragin.
Hello,
I'd like to hear opinions regarding the change in release policy.
The proposition:
Release happens on a strict time basis, like once per month. That
means, at the end of the month we look for the best revision inside
this month (probably which is closer to the end of the month), branch
from it, apply all fixes (if any), and release.
Disadvantage: a few coming releases' quality will be overall lower,
there might be things like 0.3.25 (if release frequency is set too
high, and this is not a disadvantage actually).
Advantages: in the long run quality goes up, more developers due to
higher release rate, more publicity, people will finally realize it's
an alpha product, more bugs reported, no signs of a dead project (I
doubt there are healthy projects doing 1 release per year :)).
Any thoughts are appreciated.
With the best regards,
Aleksey Bragin.
Okay, I'm in the middle of composing a test newsletter that will hopefully
be accepted. I would like all the developers to respond to this with a short
description of what they're currently working on so I can be as accurate as
possible in that section of it (and I don't want to forget anyone).
Thank you.