Ros-dev

ros-dev@reactos.org

5791 discussions

Visual IDE for ROS
by Joseph Miller 12 Jun '05

12 Jun '05

Hello list, I am new to ReactOS, but very interested in Win32 programming. I am also very new to Win32 and C++, but I began a project about a year ago to develop and open source Visual C++ IDE for Win32 because I had not found an open source one yet. Well, it was one of my first attempts at Win32 and at C++, but I managed to create a very basic IDE and I have successfully created several programs for both work and other projects. Everything is based on a class called GWin. I feel like the GWin code is very stable, even at this point, but much of the API will probably still change as I learn about Win32. Unfortunately, the IDE code is pretty dang crappy because I did not understand some very basic programming concepts. To make a long story short, the IDE has been developed to a usable point, and the code in the GWin class is worth continuing. The IDE itself is undergoing a major rewrite for better functionality and structure. Yesterday I installed ReactOS for the very first time on my computer. I was impressed with the number of programs that actually work at this stage of development. Even Scite (an excellent, code-highlighting editor) works! So I am currently working on making my Visual GWin++ project work under ReactOS. I have managed to get it running and compile a test program under ReactOS, so with a little more testing, I will release a version just for ROS. I will also be working on a tutorial for how to get started with it. Visual GWin++ currently has support for windows, edit controls, static controls, listbox controls, MDI clients (limited), tabcontrols, and scrollbars (limited). The program can load and save projects in an XML file format using libxml. The current version is v0.02-pre-alpha. You can see the Windows version at http://www.calcmaster.net/visual-c++/ . When the ROS version is ready, I will release it. I would like some feedback on what you guys think about this project and whether or not you think it will be a benefit to ROS. BTW, I came across some message handling bugs in ROS and I guess this is the mailing list to report it? I will try to download the source and look it over, but I wanted to let you guys know first. I had a handler set up for EN_KILLFOCUS on one of my edit controls. The function was supposed to modify another window and then return. I'm assuming what happened was that as my function was modifying the other window, ROS kept assuming that it needed to send more EN_KILLFOCUS messages to me to let me know my control had lost focus. I had to add a hack to make sure that after the handler is called the first time, it is not called again until it has completed what it needs to do. I had a similar problem with LBN_SELCHANGE when I tried to kill the control's parent window. ROS assumed that this meant it needed to tell me that the selection had changed and sent LBN_SELCHANGE. This caused the same type of loop that I described above. Where do I look to correct this? -Joseph

1 0

winfile czech translation
by Martin Fuchs 12 Jun '05

12 Jun '05

Hello, is there some native czech speaker? I have attached two different czech resource files of winefile: one from WINE, and the other from ReactOS. Perhaps some one can compare the two files and search the better alternatives where the strings differ. Thanks, Martin

4 4

Re: [ros-svn] [hbirr] 15877: Print more informations on a BSOD by enabling the debug prints to the screen.
by Alex Ionescu 12 Jun '05

12 Jun '05

hbirr(a)svn.reactos.com wrote: >Print more informations on a BSOD by enabling the debug prints to the screen. > > > >Updated files: >trunk/reactos/ntoskrnl/ke/bug.c > > > Hi... Erm...I don't understand this change. BSOD data is already printed on screen during a crash. The only thing that's not printed is ROS-Specific Debug Data, because that's part of "debug output" and not of an official BSOD. At least that's how it's fundamentaly defined... I really don't like this hack, although I know you'll probably say you want the debug data on screen, but my question is why don't you use /DEBUGPORT=SCREEN for this? You're hacking the kernel to display debug data when debugging is off... And I hate the #if 0 #else #endif stuff you've added, it makes this hack even nastier! If you *really* want to bypass the debuging design and force debug-data to be printed when it shouldn't, at least make a nicer hack please (ie, modify KeDumpStackFrames to use InbvDisplayString). I'm sorry but this patch is unacceptable to me...it makes the code look like shit. Best regards, Alex Ionescu

2 1

make module_depends
by Casper Hornstrup 12 Jun '05

12 Jun '05

I've implemented the module_depends targets as a substitute for make module_clean && make module. This is much faster than the depends target since it only checks the dependencies for a single module. Casper

1 0

N/T: Cirrus Binary: http://www.relsoft.net/cirrus.rar
by Alex Ionescu 11 Jun '05

11 Jun '05

1 0

ROS Performance Numbers
by Alex Ionescu 11 Jun '05

11 Jun '05

3 4

Re: New OS built on ReactOS and WinuxOS technology!
by Hartmut Birr 11 Jun '05

11 Jun '05

Hi, it seems, that the Hostilix's people doesn't like their own past. The WinuxOS project on SourceForge was deleted. - Hartmut

2 1

Re: [ros-svn] [ion] 15854: Support QEMU Hardware Acceleration
by Alex Ionescu 10 Jun '05

10 Jun '05

ion(a)svn.reactos.com wrote: >Support QEMU Hardware Acceleration > > >Updated files: >trunk/reactos/bootdata/hivesys.inf > > I will provide a working binary soon. It hits some bugs in our BitBlt code, maybe due to the recent optimizations. However a rosperf gives me 1600 fills/sec vs 232 fills/sec on the same machine with the same testing setup. That's a 8x improvement! Best regards, Alex Ionescu

1 0

New OS built on ReactOS and WinuxOS technology!
by Rafal Kupiec 10 Jun '05

10 Jun '05

Hi... I'm from BetaComp Team and I with all team members are making new operating system that will be compatible with Windows NT. It will also have Posix and its own sybsystems. It's based on knowed for most people project named ReactOS and our previously project named WinuxOS. More about HostiliX you can read on www.betacomp.info web page in Our projects sections. Actually we're working on v0.1. When we done do it we will publish binary version and all source code. Currently we're looking for people who knows C/C++ or Assembler and wants to help us. If you have a free time, please help us and join to our team! Contact: rafkup(a)gmail.com

15 42

Re: [ros-dev] PowerPC arcitecture?
by Quandary 10 Jun '05

10 Jun '05

On Sat, Jun 04, 2005 at 12:03:48PM -0500, Rick Langschultz wrote: > > I use Outlook XP to compose mail to my boss and to a support team. I > have to use HTML formatting in my mail messages. Sorry for the > inconvenience I have caused. If people want to get picky about the mail > format and not the content of the message, they should re-evaluate their > purposes involved in developing code, and material for computers. > If you've ever tried to read an XML/HTML message in a plain-text reader (such as mutt, which is my client of choice), you would understand why folks complain. To draw an analogy as to how silly your claim is (that the formatting should be ignored completely), consider the following scenarios: 1. A huge C program that works, but has no comments and obfuscated code. "If you can't understand it without comments, you should re-evaluate your programming ability." 2. A patch that has thousands of formatting changes intermixed with bugfixes. "If you can't appreciate the functionality of a freely offered patch that seems to fix a bug, you should re-evaluate your stance as a community-based project." 3. Documentation provided in rendered PS (or another opaque format). "If you can't appreciate the accuracy and user-friendliness of the documentation, you should re-evaluate your position on having a well-documented system." See, these are all silly. It's easy for one side to just ignore the other -- yes, you may need whatever formatting HTML provides you for work correspondence; it's easy for you to forget that it's even there. Likewise, it's easy for those of us who edit and send raw text to ignore how engrained HTML can be in some mail front-ends. But at the end of the day, the lowest common denominator is plain-text -- and that's something folks will expect you to conform to. Just like a patch with a thousand formatting changes, now matter how many bugs it fixes, it will be rejected. So to with your mails -- no matter how good the merit is, if we have to mind-parse the gibberish, it's just going to be outright rejected. Thanks for understanding, -- Travis > Rick Langschultz > > -----Original Message----- > From: ros-dev-bounces(a)reactos.com [mailto:ros-dev-bounces@reactos.com] > On Behalf Of Mike Nordell > Sent: Saturday, June 04, 2005 9:19 AM > To: ReactOS Development List > Subject: Re: [ros-dev] PowerPC arcitecture? > > Rick Langschultz wrote: > > > <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = > > xmlns:w=3D"urn:schemas-microsoft-com:office:word" = > > xmlns=3D"http://www.w3.org/TR/REC-html40"> > > [lots and lots of useless XML tags mixed in an unholy cesspool with HTTP > snipped] > > Could you please trim that crap? I am, as I hope the majority of list > subscribers are too, not especially interested in that you wrote an > e-mail > in MSWord and that your "SpellingState" is "Clean". > > Please use plain-text only. > > Thank you for your cooperation. > > /Mike > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > __________________________________ Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev