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~
The source code for ReactOS is only 30MB.
The project has been going for 10 years so why so small?
Is there a need for any developers who can program assembler?
I use the ReactOS assembler. RosAsm. http://www.rosasm.org
Or do you only program in C and C++?
Hi,
I promised a new testing/development environment but unfortunately I cannot
pursue my work because nobody has been able to fix rbuild to my
requirements. If anyone does want to see the standardized environment I
promised, please prod your local ReactOS developer for the following
features:
1) *Working* ROS_INTERMEDIATE and ROS_OUTPUT directories. They are
broken in many ways:
a. Don't work with relative pats.
b. Don't work at all for .pch files and/or compilation units.
c. Create other sorts of unpredictable errors due to hard-coded
strings/directories in makefiles or rbuild.
2) ROS_TOOLS_DIRECTORY. The ability for the tools to be outside the
ROS_OUTPUT directory, such as in c:\rosde\tools. Someone committed such a
patch but it was reverted without a newer version/fix.
a. Also requires making rbuild check if the binaries are present, and
if so, NOT to rebuild them.
b. Create -forcetools switch to rbuild which would force it to bypass
the check in 2a.
3) Tools must be built and work with the -O3 optimization setting.
Of course, I won't go into the fact that my request for the other rbuild
features such as a graphical dependency map have gone unanswered. Many
thanks to those who _have_ worked on some of the MSVC features/bugfixes I
brought forward and do the small attempt at a depmap.
--
Best regards,
Alex Ionescu
Project Lead, TinyKRNL
Kernel-Mode Software Design Engineer, ReactOS
While I agree in spirit with the revert, we should use DDK #defines for compatibility. Please re-commit that part.
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of fireball(a)svn.reactos.org
Sent: March-30-07 11:39 AM
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [fireball] 26210: - Revert useless commit: * No need to copy stuff from DDK, it's prohibited (#define _INC_NEWDEV) * #pragma was put there especially, and no reason to remove it was said * pushpack /
I recenly found out about this website. I checked out the sources (great)
and tried to run React OS under VMware player (not so great) and even tried
some of my sw to run under it (disaster!).
I have a few questions:
1. I noted some inconsistencies in handling 8-bit/UTF-16 translation in
..A/..W calls between ...A functions in graphics (TextOut...) and
synchronization (CreateSemaphore...). Graphics part always allocates memory
(HeapAlloc) - a waste of time, IMHO.
2. I'm, not sure if is there a list of already checked/done, but not
verified/not implemented API?
3. How could I help (I know some C)
Regards,
dn
PS Meanwhile, I was reading Doxygen & could not figure out how
MultiByteToWideChar() works (=i.e. how you implemented it), but I think it
calls RtlMultiByteToUnicodeN(), which implements CP -> UTF-16 mapping for
currently selected CP, and RtlCustomCPToUnicodeN() for any other CP. Some my
programs use MultiByteToWideChar() with CP_UTF8 which is IMHO NOT
implemented!?!?
May I work on this (in my spare time)? Is somebody else working on this
area?
Is it possible, that one of the official ROS-developer can contact
http://scan.coverity.com/index.html
to let also searched the ROS-code for bugs?
Greatings
theuserbl
_________________________________________________________________
Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit
Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu!
http://desktop.msn.de/ Jetzt gratis downloaden!
We'll.... I found out how MultiByteToWideChar (MBTWC) is implemented, and
looks OK.
But then, there are following issues:
1 some functions (DefWindowProcA) call MBTWC, but with CP_ACP and HeapAlloc
ALWAYS (IMHO should be: CP_THREAD_ACP, use some local cache if the 8-bit
string is short enough, for performance)
2 some functions (GetMonitorInfoA) call MBTWC using CP_THREAD_ACP
3 yet other functions (RegisterClassExA) call
RtlCreateUnicodeStringFromAsciiz and and RtlFreeUnicodeString later (no TEB
cache, allocation ALWAYS)
4 and some other functions (CreateEventExA) call
RtlAnsiStringToUnicodeString and use cache from TEB
5 other functions use RtlAnsiStringToUnicodeString with allocation, and
RtlFreeUnicodeString later.
6 and some other functions (SetWindowTextA) call
RtlAnsiStringToUnicodeString and RtlFreeUnicodeString (allocation ALWAYS)
Is this inconsistent or what?!
Best regards
Daniel
I verified that bug occuring on a Pentium MMX, and then ran the liveCD on bochs with a breakpoint at
the faulty instruction... It's a CMOVZ (Conditional MOVe if Zero flag set)...
Conditional moves were introduced in Pentium II, but never mind!
What *really* matters is that that code looks like resulting from compilation (because of the C
calling convention clearly used, and no one uses C calling conventions in handwritten ASM code)...
So..... Either this isn't a bug (and recompilation is required for non-default configurations), or
there is a -march option when compiling the default LiveCD that shouldn't be there... Personally, I
would go for the later...
PS: Can I view a symbol map for the freeloader image in the prebuilt liveCD?
JJ
_______________________________________________________
Yahoo! Mail - Sempre a melhor op��o para voc�!
Experimente j� e veja as novidades.
http://br.yahoo.com/mailbeta/tudonovo/
Hello,
I just finished upgrading svn.reactos.org to SVN 1.4.3. You should
feel noticeable improvements - faster work and less traffic. However,
if any problem arise, don't hesitate to email ros-general / ros-dev.
For a full list of changes over previous version, please look to
http://subversion.tigris.org.
With the best regards,
Aleksey Bragin.
Hi and welcome,
thanks for your offer to help - we were just discussing today in the
irc-channel that there are some people in our current team who are
willing to guide newbies through the process (get src code, build,
run, modify something, try writing something new, send in patches, etc).
If you have ability, please join #reactos on freenode irc network. If
not, then email is allright (ask questions right here, so other can
read and learn too).
WBR,
Aleksey Bragin.
On Mar 13, 2007, at 11:33 PM, Arko Provo Mukherjee wrote:
> Dear friends,
> We are 3 undergrad comp sc. and IT students from India. We have
> some coding experience but have never worked for the Open Source
> Community as developers. Yet we have always admired the concept and
> used FLOSS stuff like GNU/Linux.
> We came across ReactOS project and got really interested in it. We
> really want to contribute to the development of React OS and since
> we are new in Open Source development, we would require your
> guidance and support in stuff like understanding the code, building
> the build environment etc.
> Among other shortfalls that we have, we haven't programmed much on
> Windows platform (almost always Linux ie) and hence know little
> about the Windows API. But we are eager to learn and can definitely
> learn parts of the API as long as you can guide us.
> We humbly request you to guide us and give us some problems so that
> we can try and support this community. A lot is left to be done in
> ReactOS and it would be great being a part of such a project.
> Also we are better at writing C codes than reading them ( like
> almost everyone ;) ) and hence would request you to give us some
> problems that we can write from stratch rather than bug fixing that
> would require reading all codes.
> But we are ready to contribute in any way you feel we can as
> developers and support this community.
> Regards
> Arko Provo Mukherjee
> Abhishek Biswas
> Biswanath Banik
