Ros-general

ros-general@reactos.org

1048 discussions

by Magnus Olsen

Hi I should love to see some new gudieles how to get svn access. Today it seam anyone that provide with a patch that is coder can getting svn access. But I think we need start think how we should handle it, Here is some ideas how it can be 1. A maling list with patch or in Bugzila I love see a maling list with the patch 2. When people have submit the patch to us we start examing it see if it any godd (we are doning that already) 3. To get SVN write access u need lest provide patch in regual basic under 6 month lest, Then after 6 month the provider can write to mailing list see if can getting SVN write access before he grant SVN write access, the full name and mailing address must be provided, and we should have a vote if that provder can getting SVN write access. no accpect from all this rules. Yestday some was granted svn access his name was not on the mailing list why he got one, he did not write either on the mailing list asking for svn access that why I want see new guide lines how svn write access handles. so every one know how he is and why he was granted to be granted after few patcher are not accpect in my eys. For we are starting getting alot with people with svn write access. And new guide lines must be create. BestReagds Magnus Olsen

18 years, 11 months

Re: ReactOS UI Team - Concept, Plan, and: help wanted

by mf

Mikko Tikkanen wrote: > Aye. I'm still in. Just have been a tad busy. I've been watching my > mail but that's about it but since I started my school few weeks ago I > have more time on my hands. At least when project deadlines aren't > pushing too close. Great. > The school also has new advantages; since I'm studying UI/usability > design I could do some actual user testing, with live subjects. I > could also get artists involved as the schools also has art teaching. Be careful not to make ReactOS into some kind of guinea pig for eccentric design though. One of the most important goals for ReactOS, interface-wise, is not requiring any retraining for people switching from Windows. Max Well wrote: > As you said, there are already two UI designer, so I would like to > redesign the setup. I believe the setup is already being UI-ified. Contact Alex Ionescu for details. See also: http://www.reactos.org/wiki/index.php/Alex_Ionescu/RosGooeySetup Richard Campbell wrote: > I don't think i quite understand this...Are you saying we should develop > a new UI? I don't think so. The Windows UI is standard, and several > million users KNOW this UI. Our UI should be kept as close as possible > to windows without breaking any laws. I honestly don't know where you got this idea from, but we will be staying close to the Windows feel, as I explained above. jwalsh(a)bigpond.net.au wrote: > Richard is correct. > I understand the statement below as a recipe for suicide. > If you are having trouble getting skills on the ground now, this will make sure you never do. > Being SLAPP'ed by a multibillion business is no picnic. What's this, chinese whispering? What exactly did I say we're going to do which is going to make msft get interested in SLAPPing us? I'm calling for help to improve our UI which currently is somewhere in the pre-win95 age. Martin Fuchs wrote: > Yes, that's the best way: Write down what you intend to implement > exactly on the Wiki or in Bugzilla. I will help in explorer, winefile > and ibrowser as far as possible. But my available time is limited. > Branching the code is possible, if you want to change explorer > completely. But I would prefer to maintain only one code base. The > already existing "lean-explorer" branch may be enough. ;-) First off, PLEASE reply ONLY in ros-general. My initial mail states: > Please reply to this mail only on the general list or to me in person > (if you're not on the list and only get digests), it is only > crossposted in ros-dev to get a wider range of attention. Keeping track of conversation on multiple lists is only confusing. Thanks. As for your suggestion, I'd like to say that I personally dislike indirect communication like the wiki or bugzilla. Stuff gets done in a fraction of the time if you can reach a quick concensus by means of word exchange. I don't know why you seem to avoid IRC, but mailing list seems alright with me as well. Seeing that you're as "in charge" of the look of explorer as you currently are, maybe it would be beneficial if you would join the UI Team yourself? Just a suggestion :). Cheers, mf.

18 years, 11 months

ReactOS UI...

by Al Hartman

First of all, thanks to all of you for all your work on ReactOS. Secondly, why reinvent the wheel? Why not simply assure that ReactOS is compatible with WindowBlinds? http://www.stardock.com/products/windowblinds/ I'm much more interested in ReactOS having Rock-Solid base functionality... - Printing - Networking - Speed - Compatibility with Apps. Rather than UI eye-candy. That stuff can come later, or by using the many third party skinning apps for Windows. Thanks! Al

18 years, 11 months

Reactos 0.2.8 RC-1 is out

by Robert Köpferl

You can find a new version on SF.NET Initial network support and some more complex apps as firefox respectively seamonkey seem to work. Against to what I wrote, there's no additional app included in this RC. I try to include some in the qemu variant for the next RC. And for the intermediate time I question you to download the RC1 and try it out, PLUS report bugs into our nice bugzilla!

18 years, 11 months

Re: [ros-general] How can I see Japanese message in ReactOS?

by tsk

I got how to make Japanese version of ReactOS. I'll report results to ros-dev. > > > Hello. I'm a Japanese translator. > > I have translated some rc-files in Japanese. > Before sending rc-files, I want to confirm my translations. > How can I do this? > > Following is all that I have done. > 1) added jpn.nls to \lib\kernel32\nls\ > 2) modified \lib\kernel32\locale_rc.rc > 3) added Mona Font (Japanese font) to \media\fonts\ > 4) added next line to \bootdata\hivesft.inf > HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\SysFontSubstitutes","MS UI Gothic",0x00 00 > 0000,"mona" >

18 years, 11 months

Smalltalk on ReactOS?

by jwalsh＠bigpond.net.au

Hi, I looked at ReactOS some years ago, with a mind to using it with Smalltalk: Digitalk V both for the pcXT and the pcAT. Or Smalltalk Express. I would appreciate any information at all. Regards Justin Walsh

18 years, 11 months

How can I see Japanese message in ReactOS?

by tsk

Hello. I'm a Japanese translator. I have translated some rc-files in Japanese. Before sending rc-files, I want to confirm my translations. How can I do this? Following is all that I have done. 1) added jpn.nls to \lib\kernel32\nls\ 2) modified \lib\kernel32\locale_rc.rc 3) added Mona Font (Japanese font) to \media\fonts\ 4) added next line to \bootdata\hivesft.inf HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\SysFontSubstitutes","MS UI Gothic",0x0000 0000,"mona" P.S. explorer-ja.rc has an attribute of a binary file (svn:mime-type application/octet-stream), so I can't make a patch file for it. Please someone remove this attribute. Thank you. tsk

18 years, 11 months

Re: [ros-general] ReactOS UI Team - Concept, Plan, and: help wanted

by jwalsh＠bigpond.net.au

Richard is correct. I understand the statement below as a recipe for suicide. If you are having trouble getting skills on the ground now, this will make sure you never do. Being SLAPP'ed by a multibillion business is no picnic. JW. > > -Recruiting- > > So getting down to business. The UI team is recruiting two kinds of > > people. > > Primarily: Programmers who have sufficient knowledge to hack other > > people's code, even if said code is rooted deeply in system libraries. ---- Richard Campbell <eek2121(a)comcast.net> wrote: > I don't think i quite understand this...Are you saying we should develop > a new UI? I don't think so. The Windows UI is standard, and several > million users KNOW this UI. Our UI should be kept as close as possible > to windows without breaking any laws. > > Aleksey Bragin wrote: > > > Hi, our UI Team Coordinator - mf - asked me to sent this email on his > > behalf, because unfortunately mails from his address doesn't reach any > > mailing-list. > > > > Here is the original message: > > *From: *mf <mf(a)mufunyo.net <mailto:mf@mufunyo.net>> > > *Date: *October 6, 2005 1:20:56 AM GMT+04:00 > > *Subject: **ReactOS UI Team - Concept, Plan, and: help wanted* > > > > > > Greetings ReactOS developers and interested parties! > > > > For the unintroduced, I am your humble UI coordinator. In addition, I > > also made some graphics for the project. > > > > -Concept- > > I am here to remind you of a post that was made in the ReactOS user > > forum, written by crappish (Mikko Tikkanen). In it the author wrote of > > the need of a consistent user interface, the need of people that > > actually have knowledge of such things, and how these people would > > have to be in charge of enforcing such an interface. They should be > > familiar with Windows, know how to make things accessible and > > newbie-friendly, and have enough creativity to improve on existing > > concepts. In addition to that, there should be someone who represents > > this team and can interface it with the rest of the project, and make > > sure everything is the way everyone wants it to be. Now, this > > representative has been chosen. But there is no team to back him up! > > > > -Recruiting- > > So getting down to business. The UI team is recruiting two kinds of > > people. > > Primarily: Programmers who have sufficient knowledge to hack other > > people's code, even if said code is rooted deeply in system libraries. > > Skill in writing user interfaces and piecing together dialog > > resources. No advanced skills beyond that required. This is most > > important, since developers in this category can get straight to > > business and get started on improving ReactOS. > > Secondarily: Interface concept designers who have advanced knowledge > > of human interfacing, easy access, logical positioning, and the > > creativity to improve and expand on existing ideas. This is a > > secondary category because a) right now there is little to do in this > > respect, b) there are already two (counting Mikko?) of these people in > > ReactOS, and c) for every 1 concept designer, there can be up to 10 > > implementing developers. > > Even more appreciated, would be someone who fits both gloves and can > > write code AND design interfaces. Sadly, experience proves that these > > two traits don't usually come together in one person. > > > > And! Just as important, though not actively recruited, I welcome icon > > designers, graphic designers, font designers (that includes you, > > wierd_w!), sound effect samplers, and programmers willing to implement > > missing UI features (think of things such as extended cursor/icon > > support, alpha blitting, runtime freetype configuration, recycle bin > > functionality, control panel, autorun support, etc), on individual > > application (mail me at mf(a)mufunyo.net <mailto:mf@mufunyo.net>). > > > > -Plan- > > The plan(tm) to kickstart the UI team is as follows: > > Our first goal will be to make the surface experience of ReactOS > > familiar. Surface in this context means the things a user will see > > during and after bootup. This mainly involves modifying explorer; to > > display a consistent and familiar start menu, and to show a friendly > > explorer when My Computer or the Explore link is opened. This means > > making all the surface icons consistent (my task), modifying > > explorer's interface (the 'programmer' category), and figuring out the > > best layout for the start menu (the 'designer' category). > > There is no plan past this first task, because I cannot predict how > > small or big the team is going to be, what feedback we are going to > > get, and how fast things will move. > > > > > > > > And that's it for my first big announcement. I hope this will get some > > discussion going, and some balls rolling. I would also like to take > > this opportunity to request a mailing list for the UI team, this > > should have been set up right after the coordinator vote was over, but > > it wasn't-- so to whoever's in charge of that, I count on you. Thanks. > > Please reply to this mail only on the general list or to me in person > > (if you're not on the list and only get digests), it is only > > crossposted in ros-dev to get a wider range of attention. > > > > > > Thanks for reading, > > mf. > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >ros-general mailing list > >ros-general(a)reactos.org > >http://www.reactos.org/mailman/listinfo/ros-general > > > > _______________________________________________ > ros-general mailing list > ros-general(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-general

18 years, 11 months

ReactOS UI Team - Concept, Plan, and: help wanted

by Aleksey Bragin

Hi, our UI Team Coordinator - mf - asked me to sent this email on his behalf, because unfortunately mails from his address doesn't reach any mailing-list. Here is the original message: From: mf <mf(a)mufunyo.net> Date: October 6, 2005 1:20:56 AM GMT+04:00 Subject: ReactOS UI Team - Concept, Plan, and: help wanted Greetings ReactOS developers and interested parties! For the unintroduced, I am your humble UI coordinator. In addition, I also made some graphics for the project. -Concept- I am here to remind you of a post that was made in the ReactOS user forum, written by crappish (Mikko Tikkanen). In it the author wrote of the need of a consistent user interface, the need of people that actually have knowledge of such things, and how these people would have to be in charge of enforcing such an interface. They should be familiar with Windows, know how to make things accessible and newbie- friendly, and have enough creativity to improve on existing concepts. In addition to that, there should be someone who represents this team and can interface it with the rest of the project, and make sure everything is the way everyone wants it to be. Now, this representative has been chosen. But there is no team to back him up! -Recruiting- So getting down to business. The UI team is recruiting two kinds of people. Primarily: Programmers who have sufficient knowledge to hack other people's code, even if said code is rooted deeply in system libraries. Skill in writing user interfaces and piecing together dialog resources. No advanced skills beyond that required. This is most important, since developers in this category can get straight to business and get started on improving ReactOS. Secondarily: Interface concept designers who have advanced knowledge of human interfacing, easy access, logical positioning, and the creativity to improve and expand on existing ideas. This is a secondary category because a) right now there is little to do in this respect, b) there are already two (counting Mikko?) of these people in ReactOS, and c) for every 1 concept designer, there can be up to 10 implementing developers. Even more appreciated, would be someone who fits both gloves and can write code AND design interfaces. Sadly, experience proves that these two traits don't usually come together in one person. And! Just as important, though not actively recruited, I welcome icon designers, graphic designers, font designers (that includes you, wierd_w!), sound effect samplers, and programmers willing to implement missing UI features (think of things such as extended cursor/icon support, alpha blitting, runtime freetype configuration, recycle bin functionality, control panel, autorun support, etc), on individual application (mail me at mf(a)mufunyo.net). -Plan- The plan(tm) to kickstart the UI team is as follows: Our first goal will be to make the surface experience of ReactOS familiar. Surface in this context means the things a user will see during and after bootup. This mainly involves modifying explorer; to display a consistent and familiar start menu, and to show a friendly explorer when My Computer or the Explore link is opened. This means making all the surface icons consistent (my task), modifying explorer's interface (the 'programmer' category), and figuring out the best layout for the start menu (the 'designer' category). There is no plan past this first task, because I cannot predict how small or big the team is going to be, what feedback we are going to get, and how fast things will move. And that's it for my first big announcement. I hope this will get some discussion going, and some balls rolling. I would also like to take this opportunity to request a mailing list for the UI team, this should have been set up right after the coordinator vote was over, but it wasn't-- so to whoever's in charge of that, I count on you. Thanks. Please reply to this mail only on the general list or to me in person (if you're not on the list and only get digests), it is only crossposted in ros-dev to get a wider range of attention. Thanks for reading, mf.

18 years, 11 months

Kudus on the new reactos.com

by Jason Filby

Hi all Better late than never: I'd like to thank the web team for a great job on the new ReactOS site! Especially to Klemens Friedl, Ge van Geldorp and Michael Wirth for the efforts that they put in, this was a big task and they did it well. The site is easy to navigate, looks great and should see us well into the future as we continue to expand content and our user base grows. Well done! Regards Jason

18 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Ros-general