Ros-dev

ros-dev@reactos.org

5790 discussions

Postponing the July Meeting
by Colin Finck 02 Aug '18

02 Aug '18

Hi all! Looking at the calendar, it would be time for the July Meeting today. However, I didn't receive any agenda proposals and also forgot to announce it in the course of releasing 0.4.9. So I suggest we postpone the meeting to next week's Thursday, August 2. Please send agenda proposals by then. That meeting also allows us to handle last-minute planning regarding the Hackfest. Best regards, Colin

4 6

Re: [ros-dev] Postponing the July Meeting
by Giannis Adamopoulos 02 Aug '18

02 Aug '18

Hi, I really like this idea. Actually i was thinking something similar about user mode apps like paint or even the file browser of the shell which can be used from windows xp to windows 10. (You need just these three files from us: filebrowser.exe, rshell.dll and browseui.dll). Ged Murphy <gedmurphy.maillists(a)gmail.com> wrote on Wed, August 1st, 2018, 11:30 PM: > We could keep components in the reactos git project and just create a new repo for them, however it might still get lost/overshadowed slightly by the main reactos codebase. Another option would be to create a new separate project with one\multiple repos. This would allow us to truly separate components from the reactos project and try to generate interest on their own merit. > > We'd need to maximize their visibility by adding a good README.rd files with plenty of buzzwords for the google crawler bot to pick up. > > If it was successful and we decide to do more, then we'd need to come up with a format as to how to best manage multiple components. > Do we have individual repos for each component, which allows dedicated README.rd files? This would give maximum flexibility and allow us to have a separate README.rd for each component. > Do we bundle everything into one repo similar to how the WDK samples are setup? This is easier to manage, but less convenient for end users, and won't be as visible for people to find in google searches. > > Ged. > > > -----Original Message----- > From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Hermès BÉLUSCA-MAÏTO > Sent: Wednesday, 01 August 2018 20:20 > To: 'ReactOS Development List' <ros-dev(a)reactos.org> > Subject: Re: [ros-dev] Postponing the July Meeting > > Hi, > > This sounds interesting, for potential developers wanting just to work on some module, but not wanting to deal with the whole OS thing. > Would this mean that we also have to think about git submodules? Because (in the case of the NTFS driver for example) it would be in a different git repo, and then it would have to be automatically downloaded and updated whenever one of the core ROS dev updates his own ROS git repo. > > Cheers, > Hermes > > > -----Message d'origine----- > > De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Ged > > Murphy Envoyé : mercredi 1 août 2018 20:16 À : 'ReactOS Development > > List' > > Objet : Re: [ros-dev] Postponing the July Meeting > > > > I have an item for the agenda. I'd like to discuss the possibility of > > moving some of our drivers out of the main repo and into something more convenient. > > > > In case I don't make the meeting, I'll put forward some of my reasons here: > > > > This thought has come about due to the btrfs driver which we use from > > Mark Harmstone. Mark's project receives quite a bit of interest on > > github, and I'm assuming one of the reasons is that it's so easy to > > find and build. Searching for 'btrfs windows' lists his project as the > > top hit in google, and building is as simple as cloning, opening the > > project in VS and clicking build (assuming you have the > > WDK) > > > > I'm wondering if we did the same thing to some of our drivers, we > > might generate more interest in them. A good example would be our NTFS driver. > > When searching for open source NTFS solutions you're only really given > > Linux and Max options. The reactos driver is buried deep in the search > > list, and you only see it if you know what you're looking for. Next if > > you want to build it, you need to clone the main reactos repo, install > > the build tools, setup and build the environment, build the tool > > chain, build the linkers libs, etc, etc. There are so many barriers > > for people who aren't part of the reactos development team that the chance of getting anyone interested in it are practically zero. > > > > This process would be much simpler if the code was available to clone > > as a separate project, and could simply build with the WDK and VS. > > There's then a chance that it might start to generate interest, and > > people may start working on it instead of it just bit-rotting deep in our main repo. > > > > If we're going to do that, why not consider others too. Network cards, > > sound stack, USB, boot loaders, printer drivers, directx, etc, There's > > lots of things that people might be interested in working on and using > > if they weren't tied to the reactos code base. We obviously benefit > > from any external interest, and simply pull/import it back into the reactos project. > > > > Ged. > > > > > > > > -----Original Message----- > > From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Colin Finck > > Sent: Thursday, 26 July 2018 17:58 > > To: 'ReactOS Development List' <ros-dev(a)reactos.org> > > Subject: [ros-dev] Postponing the July Meeting > > > > Hi all! > > > > Looking at the calendar, it would be time for the July Meeting today. > > However, I didn't receive any agenda proposals and also forgot to > > announce it in the course of releasing 0.4.9. > > So I suggest we postpone the meeting to next week's Thursday, August 2. > > > > Please send agenda proposals by then. > > That meeting also allows us to handle last-minute planning regarding > > the Hackfest. > > > > Best regards, > > > > Colin > > > > > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev(a)reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > > > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev

2 1

Repetitive "shell submit results failed" errors when running testbot manually
by Hermès BÉLUSCA - MAÏTO 01 Aug '18

01 Aug '18

Hello! I repeatedly get an error "shell submit results failed" while trying to run testbot on a PR  patch, see for example https://build.reactos.org/builders/Test%20KVM/builds/20818 and as a result I cannot obtain the results under reactos.org/testman . Can someone investigate what is going on? Regards, Hermes

2 1

Needs DejaVuMathTeXGyre.ttf?
by katahiromz 01 Aug '18

01 Aug '18

Dear everyone, I think DejaVuMathTeXGyre.ttf is bad font for normal use. Why do we need this font? Thanks

2 1

ReactOS Software installer ignores proxy settings
by Thomas Schweikle 26 Jul '18

26 Jul '18

ReactOS Software installer ignores proxy settings. If you are behind some firewall allowing internet connections only by proxy, you are lost. The software installer ignores any proxy setting. -- Thomas

3 2

metric analyze
by katahiromz 24 Jul '18

24 Jul '18

https://jira.reactos.org/secure/attachment/47741/47741_MetricAnalyze.csv Can you analyze the relations between these parameters? I want the formulas to get (tmHeight, tmAscent, tmDescent, tmInternalLeading, tmExternalLeading) values from lfHeight and the other parameters. NOTE: The formula differs depending on the sign of lfHeight.

1 0

ReactOS 0.4.9 to be released tomorrow, July 23, 2018 - Press Kit is online!
by Colin Finck 22 Jul '18

22 Jul '18

Hi all! With the great last-minute work on the press release, we can finally release ReactOS 0.4.9 tomorrow, Monday, July 23, 2018! The download will be officially available around noon (CEST). A Press Kit for the ReactOS 0.4.9 release is already available: https://download.reactos.org/reactos/ReactOS/0.4.9/ReactOS-0.4.9-PressKit.z… Feel free to send it to interested parties to let them know about the upcoming release in advance. Best regards, Colin Finck

1 0

Re: [ros-dev] [ros-diffs] 01/01: [WIN32SS] Fix NtUserGetClipboardData for text paste (#645)
by Pierre Schweitzer 08 Jul '18

08 Jul '18

For the record, that commit seems to have broken ReactOS testing (see testman, which records last successful test run for 2170901, ie, previous commit). Starting with that commit, any regression test run never ends. It seems bug reports have been creating regarding regressions (timeouts) in the tests but got ignored so far. It would be great to fix these before pushing any other commits. Cheers, Pierre Le 30/06/2018 à 17:12, Katayama Hirofumi MZ a écrit : > https://git.reactos.org/?p=reactos.git;a=commitdiff;h=6abc9f5b5af6cc7b7c57f… > > commit 6abc9f5b5af6cc7b7c57ff9c6bcc4a919cf85d1e > Author: Katayama Hirofumi MZ <katayama.hirofumi.mz(a)gmail.com> > AuthorDate: Sun Jul 1 00:12:23 2018 +0900 > Commit: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito(a)reactos.org> > CommitDate: Sat Jun 30 17:12:23 2018 +0200 > > [WIN32SS] Fix NtUserGetClipboardData for text paste (#645) > > Fix the NtUserGetClipboardData function for the synthesized text formats (CF_TEXT, CF_OEMTEXT and CF_UNICODETEXT). > CORE-11471 > --- > win32ss/user/ntuser/clipboard.c | 47 ++++++++++++++++++++++++++--------------- > 1 file changed, 30 insertions(+), 17 deletions(-) > > diff --git a/win32ss/user/ntuser/clipboard.c b/win32ss/user/ntuser/clipboard.c > index 92109953cc..04e5d22291 100644 > --- a/win32ss/user/ntuser/clipboard.c > +++ b/win32ss/user/ntuser/clipboard.c > @@ -294,8 +294,8 @@ IntAddSynthesizedFormats(PWINSTATION_OBJECT pWinStaObj) > bHaveBm = IntIsFormatAvailable(pWinStaObj, CF_BITMAP); > bHaveDib = IntIsFormatAvailable(pWinStaObj, CF_DIB); > > - /* Add CF_LOCALE format if we have CF_TEXT */ > - if (!bHaveLocale && bHaveText) > + /* Add CF_LOCALE format if we have CF_TEXT, CF_OEMTEXT or CF_UNICODETEXT */ > + if (!bHaveLocale && (bHaveText || bHaveOemText || bHaveUniText)) > { > PCLIPBOARDDATA pMemObj; > HANDLE hMem; > @@ -881,6 +881,7 @@ NtUserGetClipboardData(UINT fmt, PGETCLIPBDATA pgcd) > HANDLE hRet = NULL; > PCLIP pElement; > PWINSTATION_OBJECT pWinStaObj; > + UINT uSourceFmt = fmt; > > TRACE("NtUserGetClipboardData(%x, %p)\n", fmt, pgcd); > > @@ -898,18 +899,7 @@ NtUserGetClipboardData(UINT fmt, PGETCLIPBDATA pgcd) > } > > pElement = IntGetFormatElement(pWinStaObj, fmt); > - if (pElement && IS_DATA_DELAYED(pElement) && pWinStaObj->spwndClipOwner) > - { > - /* Send WM_RENDERFORMAT message */ > - pWinStaObj->fInDelayedRendering = TRUE; > - co_IntSendMessage(pWinStaObj->spwndClipOwner->head.h, WM_RENDERFORMAT, (WPARAM)fmt, 0); > - pWinStaObj->fInDelayedRendering = FALSE; > - > - /* Data should be in clipboard now */ > - pElement = IntGetFormatElement(pWinStaObj, fmt); > - } > - > - if (!pElement || IS_DATA_DELAYED(pElement)) > + if (!pElement) > goto cleanup; > > if (IS_DATA_SYNTHESIZED(pElement)) > @@ -921,20 +911,43 @@ NtUserGetClipboardData(UINT fmt, PGETCLIPBDATA pgcd) > case CF_UNICODETEXT: > case CF_TEXT: > case CF_OEMTEXT: > - pElement = IntGetFormatElement(pWinStaObj, CF_UNICODETEXT); > + uSourceFmt = CF_UNICODETEXT; > + pElement = IntGetFormatElement(pWinStaObj, uSourceFmt); > if (IS_DATA_SYNTHESIZED(pElement)) > - pElement = IntGetFormatElement(pWinStaObj, CF_TEXT); > + { > + uSourceFmt = CF_TEXT; > + pElement = IntGetFormatElement(pWinStaObj, uSourceFmt); > + } > if (IS_DATA_SYNTHESIZED(pElement)) > - pElement = IntGetFormatElement(pWinStaObj, CF_OEMTEXT); > + { > + uSourceFmt = CF_OEMTEXT; > + pElement = IntGetFormatElement(pWinStaObj, uSourceFmt); > + } > break; > + > case CF_BITMAP: > IntSynthesizeBitmap(pWinStaObj, pElement); > break; > + > default: > ASSERT(FALSE); > } > } > > + if (pElement && IS_DATA_DELAYED(pElement) && pWinStaObj->spwndClipOwner) > + { > + /* Send WM_RENDERFORMAT message */ > + pWinStaObj->fInDelayedRendering = TRUE; > + co_IntSendMessage(pWinStaObj->spwndClipOwner->head.h, WM_RENDERFORMAT, (WPARAM)uSourceFmt, 0); > + pWinStaObj->fInDelayedRendering = FALSE; > + > + /* Data should be in clipboard now */ > + pElement = IntGetFormatElement(pWinStaObj, uSourceFmt); > + } > + > + if (!pElement || IS_DATA_DELAYED(pElement)) > + goto cleanup; > + > _SEH2_TRY > { > ProbeForWrite(pgcd, sizeof(*pgcd), 1); > -- Pierre Schweitzer <pierre at reactos.org> System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V.

2 1

Website migrated to a new Login system
by Colin Finck 04 Jul '18

04 Jul '18

Hello all, Our website has been migrated to a new Login system today and all components have been upgraded to their latest versions. In the course of that, the user database has also been moved into an LDAP directory and cleaned from accounts that have never been used. Please check that everything is working alright and report bugs in our JIRA: https://jira.reactos.org You are also advised to change your password in the self-service at https://reactos.org/roslogin/?p=selfservice - even to the same one. Every password change from now on will use a state-of-the-art hashing algorithm (salted SHA-512 with 6000 rounds) to protect your account from credential theft. Unfortunately, there have been several newer accounts, for which the password could not be migrated. If you encounter problems logging in, please reset your account password at https://reactos.org/roslogin/?p=forgot to regain access. Best regards, Colin Finck

3 2

Website Maintenance on Wednesday, July 4
by Colin Finck 01 Jul '18

01 Jul '18

Hi all! The ReactOS Website along with the Forum, Wiki, and JIRA bug tracker will be down for maintenance for several hours during the day (European time) on Wednesday, July 4. In the course of this process, the user database will be migrated to the new RosLogin Single-Sign-On system (https://github.com/reactos/web/tree/master/www/www.reactos.org/roslogin) and the Forum and Wiki software will be upgraded to their latest releases. This is expected to put an end to our login weirdnesses (dead Login buttons, 30 minute propagation delay to JIRA), solve the CAPTCHA problems people were reporting, and increase the maintainability of the website. I will be on the #reactos IRC channel during the migration and give status updates there. Best regards, Colin

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev