On Tue, Dec 15, 2009 at 11:07 AM, <dreimer(a)svn.reactos.org> wrote:
> Author: dreimer
> Date: Tue Dec 15 17:07:47 2009
> New Revision: 44603
>
> URL: http://svn.reactos.org/svn/reactos?rev=44603&view=rev
> Log:
> Using the right Cross Compiler is useful, of course. Now We just need a native one, because the cygwin one has evil *nix, blasphemical, god negating and devil worshipping search paths.
Don't hold back. Tell us how you really feel.
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
You victory Alex....you know...
--
Técnico en la FPGISB UCP 'Pepito Tey'
'Creo en el software libre'
Ubuntu "Linux for human beings"
Lo último que se sabe cuando se realiza un trabajo es por donde empezar.
(Blaise Pascal, matemático francés)
Hi,
Let us take in an example from the PROCESS/THREADINFO merge or
morphing. It was all done in small steps and it also needed more
structure support to make the move possible. The same is going on with
the move to Wnd. Naming the entries in WINDOW_OBJECT the same as Wnd
makes it just as easy so when the WINDOW_OBJECT is removed the minimum
changes are made. This too includes new code to replace missing
entries in Wnd that had been added to WINDOW_OBJECT. This is the new
support that is need. Another example is LastChild from WINDOW_OBJECT,
support to replace it will need to be added.
This is the safest way to merge and morph to the new structure without
killing ReactOS in the process.
Thanks,
James
On Mon, Dec 14, 2009 at 8:02 AM, Timo Kreuzer <timo.kreuzer(a)web.de> wrote:
>
> I don't see any use in renaming the WINDOW_OBJECT structures.
> spwndXxx means shared pointer to a WND, this does not reflect it's
> current usage in WINDOW_OBJECT.
> We already have a WND and it has spwndXxx members and they are in use.
> You should rather try to get rid of them completely inside WINDOW_OBJECT
> and only use the ones from WND instead.
> But that's probably the last move after all the rest is gone.
>
> Anyway, as long as we end up with the WND structure only, do as you like
> on the way to there.
>
> Regards,
> Timo
>
On Sat, Dec 12, 2009 at 8:40 PM, <hyperion(a)svn.reactos.org> wrote:
> Author: hyperion
> Date: Sun Dec 13 02:40:56 2009
> New Revision: 44558
>
> URL: http://svn.reactos.org/svn/reactos?rev=44558&view=rev
> Log:
> added Wine on ReactOS - Inkscape.svg
> added Wine on ReactOS.svg
> My "Wine on ReactOS" diagram, in SVG format, two variants (Inkscape-friendly and optimized for the web)
>
> added COPYING
> Licensing information on the images
>
> Added:
> trunk/press-media/art/COPYING
> trunk/press-media/art/Wine on ReactOS - Inkscape.svg
> trunk/press-media/art/Wine on ReactOS.svg
Maybe there should be translucent wine bottles over
user32/gdi32/kernel32/etc where we use snippets and whole source
files. I do like this image though! I will use it the next time I give
a presentation. Thanks!
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
I'm pretty much sticking to the way it is done in most other places.
Ref:
http://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=ZeroInit
2009/12/12 KJK::Hyperion <hackbunny(a)reactos.org>
> gschneider(a)svn.reactos.org wrote:
> > - The field ZeroInit should be initialized to zero - do that by assigning
> the message type directly
>
> please do this by zero-initializing ZeroInit instead. Don't play with
> unions
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
