ReactOS Forum

Duck wrote:USB support (so people can use usb mouse and keyboard)

Judging by recent commits to the svn this is already under development so it might well be ready in time for the next major release.

Once you have basic networking done, updates directly to ROS then become a reality a la ReactOS Update.

If you're going to support networking drivers, support for Integrated Network Ports (Like those on current motherboards, i.e. nForce 4) should not be forgotten.


One thing we can do is cram more drivers in a small space. Microsoft use the CAB format. We can use the 7z method (Open-Source, let me add), that also has support for MSI, ZIP, CAB, and RAR files, to boot.

Once we have support for the use of Windows PnP Drivers, this project should take leaps and bounds after that.

To really start working with ROS, I need the following:
1.) driver support
- network is a must
- usb would be nice (I don't have usb keyb/mouse, but others do...)
- graphics (may speed up the ui a little)
- sound (I#d really like to hear something in ROS)
(I don't need PnP now)

2.) App compatiblity!
- Firefox, Thunderbird, DevCpp, OOo, FTP-Prog, 2xExpl, EAC, AcrRead,,
- Miranda, Skype, TexNic Center, VLC, WinAmp, Nero

3.) Improved UI
- little faster (Hope that windowing/handle lock prob will be solved)
- display improvements (some apps still look a little weird)

I voted for the wine thing, because if network is working, I want to use some Apps! I don't need an OS with driver support for xyz 6ch audio sound card, internal streamer, xyz graphics card, tv card, etc. as long as there is no software to use it.

I think what we're really doing here is dreaming about ReactOS 1.0

But for me, the big thing on my wishlist is sound driver support.

ReactOS 0.3.0 = Networking release

After the networking is up, I would really like to see some kind of ROS Update -feature. It should work so that you don't need to install new version of ReactOS ever again. You just update your system. When this works, ReactOS will be usable.

Exactly. This would be the first thing I'd like to see introduced after the networking is stable.
This would enable easier testing and use for people.

In my point of view, next important steps would be.

1) Introducing (auto) update feature, which would update your ROS on the fly. (You could set it on i.e. stable-auto mode, stable-manual etc.)
2) Introducing two different levels of updates. Beta and stable. For update feature the stable branch would be the default but those who would like to participate could try the beta branch for testing purposes.
3) Feature which would send the error report to error repositry. This again would be turned off, as default, but those who wold like to participate more could turn this on. However, careful planning would be needed to decide what information should be sent.
4) Rollback feature. This would enable people to rollback from certain beta release back to stable, if the system becomes unstable/unusable.

After these steps, the sky is the limit. 8)

Also, I would like to see something like lite SQL implemented on the OS. There is soooo many great things for ROS to gain for it. It would even make the rollback feature more efficent. (If there is such thing like rollback without DB, anyways?)

The first thing ReactOS should focus on is making sure the installer works. None of those other items even matter at all if I can't install it.

Well, uh, haven't ever installed ROS.. Well, that would be main issue, indeed.

crappish wrote:Well, uh, haven't ever installed ROS.. Well, that would be main issue, indeed.

Well now we know why you call yourself crappish

(Just kidding!)

Yes you need a better installer /bootloader one that is on par with grub atleast

Why should i have to already have a fat partion it should make one for me?

After that................. networking networking networking!

This would be the first thing I'd like to see introduced after the networking is stable.
This would enable easier testing and use for people.

In my point of view, next important steps would be.

1) Introducing (auto) update feature, which would update your ROS on the fly. (You could set it on i.e. stable-auto mode, stable-manual etc.)

(SNIP)

Shouldn't Windows application compatability be a higher priority?

Asraniel wrote:improve the explorer so that i can use it on windows as a explorer replacement

i CAN use it. I'm thinking about using it in BartPE

but i want some improvements too.

Physicus wrote:To really start working with ROS, I need the following:
1.) driver support
- network is a must
- usb would be nice (I don't have usb keyb/mouse, but others do...)
- graphics (may speed up the ui a little)
- sound (I#d really like to hear something in ROS)
(I don't need PnP now)

About USB - i have USB ADSL modem and i want to use it under ReactOS. PnP, Graphics and Sound would be nice.

Physicus wrote:2.) App compatiblity!
- Firefox, Thunderbird, DevCpp, OOo, FTP-Prog, 2xExpl, EAC, AcrRead,,
- Miranda, Skype, TexNic Center, VLC, WinAmp, Nero

Also Delphi, or Lazarus at least. When i launched IrfanView under Reactos 0.2.4 live my pc had reset - dunno why.

Physicus wrote:3.) Improved UI
- little faster (Hope that windowing/handle lock prob will be solved)
- display improvements (some apps still look a little weird)

Exactly. Maybe skinning ability? sth like WindowBlinds, whose scripts have INI structure.

I

Physicus wrote: voted for the wine thing, because if network is working, I want to use some Apps! I don't need an OS with driver support for xyz 6ch audio sound card, internal streamer, xyz graphics card, tv card, etc. as long as there is no software to use it.

Me too. Compability with Windows Apps should be priority.

...

And, heello RactOS community!

chris319 wrote:

This would be the first thing I'd like to see introduced after the networking is stable.
This would enable easier testing and use for people.

In my point of view, next important steps would be.

1) Introducing (auto) update feature, which would update your ROS on the fly. (You could set it on i.e. stable-auto mode, stable-manual etc.)

(SNIP)

Shouldn't Windows application compatability be a higher priority?

I'd say no. Since we already have some level of compatiblity to show off that it can be done. For now on it is just a matter of time.
The update feature would make testing easier and would show testers/users that the OS is being developed constantly. Also it would enable people easier way to actually using the OS since they don't have to i.e. make new install every time new version comes along.
Besides, the compatibility is developing constantly even if the update feature would be priority #1. (Because every dev wouldn't be occupied by the update feature) Also introducing the feature at this point would be easier than in later phase when the OS is starting to form into shape.

_

Physicus wrote:App compatiblity!
- Firefox, Thunderbird, DevCpp, OOo, FTP-Prog, 2xExpl, EAC, AcrRead
- Miranda, Skype, TexNic Center, VLC, WinAmp, Nero

OpenOffice 1.1.4 and Nero Bruning Rom already work in ReactOS

http://reactosde.re.funpic.de/applications.php