Two petitions

Hiya

Its still at least two weeks until next meeting, hence i suppose ros-dev could be used in decision making even before that. I have two things i would like to push, things that i discussed a bit with varioius team memebers on IRC and got positive feedback. I would like you guys to comment on those and if you feel that one of both of them are wrong/unnecessary/not needed, please voice it out here. If there is no opposition for them, i`ll consider those two accepted and push for them to be finialised. Here we go:

1. Adding a default theme to ReactOS.
We need at least one to test Themes service in trunk ootb and avoid copying it to ros install each time, which is really important in regression testing. Also, a theme is a must for our upcoming release. Since its not a big file usually, it should be present in trunk, not only in release ISO.

2. Moving Starfield screensaver from rosapps to trunk.
Rosapps, no matter how much cheered, is a wasteland, a museum, a forgotten place. It will not be even buildable when we move away from rbuild. Old and unneeded code should land there, but not a new creation Carlo has been working on. Apart from that, Starfield is using OpenGL, which is also a handy ootb test tool for 3d acceleration, also important in regression testing. If you think that two screensavers are the top amount you can accept, then lets replace one of the trunk screensavers with Starfield.
-- 
With best regards
Caemyr

[Kamil Hornicek]

Hi,

1) Unless it's enabled by default I say yes.

2) 3D text would be a nice ootb ogl test if someone fixed the font 
engine. I can live with starfield too.

Dne 16.10.2011 3:07, [e-mail] napsal(a):
> Hiya
>
> Its still at least two weeks until next meeting, hence i suppose ros-dev could be used in decision making even before that. I have two things i would like to push, things that i discussed a bit with varioius team memebers on IRC and got positive feedback. I would like you guys to comment on those and if you feel that one of both of them are wrong/unnecessary/not needed, please voice it out here. If there is no opposition for them, i`ll consider those two accepted and push for them to be finialised. Here we go:
> Adding a default theme to ReactOS.
>
> We need at least one to test Themes service in trunk ootb and avoid copying it to ros install each time, which is really important in regression testing. Also, a theme is a must for our upcoming release. Since its not a big file usually, it should be present in trunk, not only in release ISO.
> Moving Starfield screensaver from rosapps to trunk.
>
> Rosapps, no matter how much cheered, is a wasteland, a museum, a forgotten place. It will not be even buildable when we move away from rbuild. Old and unneeded code should land there, but not a new creation Carlo has been working on. Apart from that, Starfield is using OpenGL, which is also a handy ootb test tool for 3d acceleration, also important in regression testing. If you think that two screensavers are the top amount you can accept, then lets replace one of the trunk screensavers with Starfield.

ad.1 Having it in the iso, ready to run is good enough imo. We dont have to set Theme service to automatic start ootb.

Also, we need to pick a default theme for ROS. In my opinion, Lautum by Pisarz (available on our forum) is more than good enough for us to use:

En 16/10/2011 03:20:13, "Kamil Hornicek" [e-mail] escribió:
> Hi,
> Unless it's enabled by default I say yes.
-- 
With best regards
Caemyr

Posted too soon. The theme name is Lautus:

http://www.reactos.org/forum/viewtopic.php?f=25&t=9293
http://imageshack.us/photo/my-images/812/clipboard01da.png/

I suppose our PR team will want community to decide about the default theme, i have no problem with that, just please make sure you add this one to the list.
-- 
With best regards
Caemyr

[Javier Agustìn Fernàndez Arroyo]

"1) Unless it's enabled by default I say yes."

Oh, why not? it would be great if ReactOS comes with themes support and,
with one applied by default

Or maybe you want to keep OS as simple as possible by default....

On Sun, Oct 16, 2011 at 3:56 AM, [e-mail] wrote:
> Posted too soon. The theme name is Lautus:
>
> http://www.reactos.org/forum/viewtopic.php?f=25&t=9293
> http://imageshack.us/photo/my-images/812/clipboard01da.png/
>
> I suppose our PR team will want community to decide about the default
> theme, i have no problem with that, just please make sure you add this one
> to the list.
>
> --
> With best regards
> Caemyr
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Bernd Blaauw]

Op 16-10-2011 10:48, Javier Agustìn Fernàndez Arroyo schreef:
> "1) Unless it's enabled by default I say yes."
>
> Oh, why not? it would be great if ReactOS comes with themes support and,
> with one applied by default
>
> Or maybe you want to keep OS as simple as possible by default....

Taste is a personal thing, maybe not everyone likes the (single default) 
theme that gets activated by ReactOS installation in such a case. If 
proper file/folder structure is present after installation, user can 
always select to activate the theme (hopefully as in Windows, thus 
regular location, no extra work, no reboot, but all bits help).

[Daniel Reimer]

I say yes to both. I just wonder if we can s´put a theme in there. All 
themes are based on modded MS Themes, because theres no open source 
skeleton till now afaik.

Am 16.10.2011 03:07, schrieb [e-mail]:
> Hiya
>
> Its still at least two weeks until next meeting, hence i suppose ros-dev could be used in decision making even before that. I have two things i would like to push, things that i discussed a bit with varioius team memebers on IRC and got positive feedback. I would like you guys to comment on those and if you feel that one of both of them are wrong/unnecessary/not needed, please voice it out here. If there is no opposition for them, i`ll consider those two accepted and push for them to be finialised. Here we go:
> Adding a default theme to ReactOS.
>
> We need at least one to test Themes service in trunk ootb and avoid copying it to ros install each time, which is really important in regression testing. Also, a theme is a must for our upcoming release. Since its not a big file usually, it should be present in trunk, not only in release ISO.
> Moving Starfield screensaver from rosapps to trunk.
>
> Rosapps, no matter how much cheered, is a wasteland, a museum, a forgotten place. It will not be even buildable when we move away from rbuild. Old and unneeded code should land there, but not a new creation Carlo has been working on. Apart from that, Starfield is using OpenGL, which is also a handy ootb test tool for 3d acceleration, also important in regression testing. If you think that two screensavers are the top amount you can accept, then lets replace one of the trunk screensavers with Starfield.

[Timo Kreuzer]

Am 16.10.2011 11:01, schrieb Daniel Reimer:
> I say yes to both. I just wonder if we can s´put a theme in there. All 
> themes are based on modded MS Themes, because theres no open source 
> skeleton till now afaik.

Giannis mentioned a theme that was (allegedly) not based on MS and which 
looked very good.
Luna Inspirat: http://krosavcheg.deviantart.com/art/Luna-Inspirat-102972534

[Javier Agustìn Fernàndez Arroyo]

And  it works in Wine... i tested it :)

On Sun, Oct 16, 2011 at 11:41 AM, Timo Kreuzer [e-mail] wrote:
> Am 16.10.2011 11:01, schrieb Daniel Reimer:
>
> I say yes to both. I just wonder if we can s´put a theme in there. All
> > themes are based on modded MS Themes, because theres no open source skeleton
> > till now afaik.
>
> Giannis mentioned a theme that was (allegedly) not based on MS and which
> looked very good.
> Luna Inspirat: http://krosavcheg.deviantart.**com/art/Luna-Inspirat-**
> 102972534 http://krosavcheg.deviantart.com/art/Luna-Inspirat-102972534
>
> ______________________________**_________________
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev

[Rafał H]

> Giannis mentioned a theme that was (allegedly) not based on MS and which  
> looked very good.
> Luna Inspirat:  
> http://krosavcheg.deviantart.com/art/Luna-Inspirat-102972534

I'm for Luna Inspirant as well. IMO it should be enabled by default at  
least in release ISO.

[Giannis Adamopoulos]

What Daniel means is that all non-ms themes are created by modifying the .msstyles that ship with windows. That's why I'm still reluctant to add a them in trunk.
Regarding Luna Inspirat I like it more than Lautus however in case we ship with it I don't think it is a good idea to keep the name Luna Inspirat or we should change it a bit.

ReactOS Development List [e-mail] wrote on Sun, October 16th, 2011, 11:41 AM:
> Am 16.10.2011 11:01, schrieb Daniel Reimer:
> > I say yes to both. I just wonder if we can s´put a theme in there. All 
> > themes are based on modded MS Themes, because theres no open source 
> > skeleton till now afaik.
>
> Giannis mentioned a theme that was (allegedly) not based on MS and which 
> looked very good.
> Luna Inspirat: http://krosavcheg.deviantart.com/art/Luna-Inspirat-102972534
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Javier Agustìn Fernàndez Arroyo]

i've been thinking about this...

what about adding a new category into the ROS Application Manager, called
"themes", and link to those we want?
this way users can download whatever they want in an easy way....

On Sun, Oct 16, 2011 at 1:01 PM, Giannis Adamopoulos <
[e-mail]> wrote:
> What Daniel means is that all non-ms themes are created by modifying the
> .msstyles that ship with windows. That's why I'm still reluctant to add a
> them in trunk.
> Regarding Luna Inspirat I like it more than Lautus however in case we ship
> with it I don't think it is a good idea to keep the name Luna Inspirat or we
> should change it a bit.
>
> ReactOS Development List [e-mail] wrote on Sun, October 16th,
> 2011, 11:41 AM:
> > Am 16.10.2011 11:01, schrieb Daniel Reimer:
> > > I say yes to both. I just wonder if we can s´put a theme in there. All
> > > themes are based on modded MS Themes, because theres no open source
> > > skeleton till now afaik.
> >
> > Giannis mentioned a theme that was (allegedly) not based on MS and which
> > looked very good.
> > Luna Inspirat:
>
> http://krosavcheg.deviantart.com/art/Luna-Inspirat-102972534
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Giannis Adamopoulos]

Sure this could be a nice short term solution for the upcoming release.

However in order to bundle a theme we have to recreate one. Theme files are normal dll files that doesn't contain any code but contain resources. We could recreate these dlls in our tree by adding bit by bit all the parts of the theme without copying anything from the themes created by ms or by the modified ms themes.

ReactOS Development List [e-mail] wrote on Sun, October 16th, 2011, 2:51 PM:
> i've been thinking about this...
>
> what about adding a new category into the ROS Application Manager, called
> "themes", and link to those we want?
> this way users can download whatever they want in an easy way....

Reply from Pisarz, author of Lautus theme:

"Lautus is based on Luna Inspirat (which is an open-source visual style by krosavcheg) and was made using TGTSoft StyleBuilder. I think you should ask guys from TGTSoft about that. I was thinking about it earlier. If we know the structure of msstyle files, we could try to reverse engineer the visual style file and find a way to compile it from the sources I've provided."

On Sunday, October 16, 2011 3:00 PM, "Giannis Adamopoulos" [e-mail] wrote:
> Sure this could be a nice short term solution for the upcoming release.
>
> However in order to bundle a theme we have to recreate one. Theme files
> are normal dll files that doesn't contain any code but contain resources.
> We could recreate these dlls in our tree by adding bit by bit all the
> parts of the theme without copying anything from the themes created by ms
> or by the modified ms themes.
-- 
With best regards
Caemyr

[Aleksey Bragin]

16.10.2011 3:07, [e-mail] пишет:
> Hiya
>
> Its still at least two weeks until next meeting, hence i suppose ros-dev could be used in decision making even before that. I have two things i would like to push, things that i discussed a bit with varioius team memebers on IRC and got positive feedback. I would like you guys to comment on those and if you feel that one of both of them are wrong/unnecessary/not needed, please voice it out here. If there is no opposition for them, i`ll consider those two accepted and push for them to be finialised. Here we go:

I support both 1 and 2. With the only exception that when we move to 
cmake, rosapps will be moved too, so it would still remain a museum, but 
a working museum. In fact, rosapps contains quite a bunch of important 
stuff too (like all those cmd line utilities).

Also I would want indeed 2 screensavers in trunk - one "simple" and one 
"opengl" based. Everything else should go to rosapps as 
additional/optional stuff. Which of those - please decide, I don't have 
any strong preference myself.
> Adding a default theme to ReactOS.
>
> We need at least one to test Themes service in trunk ootb and avoid copying it to ros install each time, which is really important in regression testing. Also, a theme is a must for our upcoming release. Since its not a big file usually, it should be present in trunk, not only in release ISO.
> Moving Starfield screensaver from rosapps to trunk.
>
> Rosapps, no matter how much cheered, is a wasteland, a museum, a forgotten place. It will not be even buildable when we move away from rbuild. Old and unneeded code should land there, but not a new creation Carlo has been working on. Apart from that, Starfield is using OpenGL, which is also a handy ootb test tool for 3d acceleration, also important in regression testing. If you think that two screensavers are the top amount you can accept, then lets replace one of the trunk screensavers with Starfield.

On Thursday, October 20, 2011 9:23 PM, "Aleksey Bragin" [e-mail] wrote:
> I support both 1 and 2. With the only exception that when we move to 
> cmake, rosapps will be moved too, so it would still remain a museum, but 
> a working museum. In fact, rosapps contains quite a bunch of important 
> stuff too (like all those cmd line utilities).

That would require porting rosapps to cmake (and building it, occasionally). I cannot do it and i cannot make anyone do that. If there are no volounters
> Also I would want indeed 2 screensavers in trunk - one "simple" and one 
> "opengl" based. Everything else should go to rosapps as 
> additional/optional stuff. Which of those - please decide, I don't have 
> any strong preference myself.

I`m fine with reducing the screensavers to two of them. Which one should be picked apart from starfield?
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
With best regards
Caemyr

[Sylvain Petreolle]

If no one already take it, I volounter to write cmake files for rosapps.

Kind regards,
Sylvain Petreolle
> De : "[e-mail]" [e-mail]
> À : ReactOS Development List [e-mail]
> Envoyé le : Vendredi 21 Octobre 2011 23h38
> Objet : Re: [ros-dev] Two petitions
>
> On Thursday, October 20, 2011 9:23 PM, "Aleksey Bragin" [e-mail] wrote:
> > I support both 1 and 2. With the only exception that when we move to 
> > cmake, rosapps will be moved too, so it would still remain a museum, but 
> > a working museum. In fact, rosapps contains quite a bunch of important 
> > stuff too (like all those cmd line utilities).
>
> That would require porting rosapps to cmake (and building it, occasionally). I cannot do it and i cannot make anyone do that. If there are no volounters
> > Also I would want indeed 2 screensavers in trunk - one "simple" and one 
> > "opengl" based. Everything else should go to rosapps as 
> > additional/optional stuff. Which of those - please decide, I don't have 
> > any strong preference myself.
>
> I`m fine with reducing the screensavers to two of them. Which one should be picked apart from starfield?
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> -- 
> With best regards
> Caemyr
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Aleksey Bragin]

Thanks a lot! Your help is really appreciated.

WBR,
Aleksey.
> If no one already take it, I volounter to write cmake files for rosapps.
>
> Kind regards,
> Sylvain Petreolle
> > De : "[e-mail]"[e-mail]
> > À : ReactOS Development [e-mail]
> > Envoyé le : Vendredi 21 Octobre 2011 23h38
> > Objet : Re: [ros-dev] Two petitions
> >
> > On Thursday, October 20, 2011 9:23 PM, "Aleksey Bragin"[e-mail]  wrote:
> > > I support both 1 and 2. With the only exception that when we move to
> > > cmake, rosapps will be moved too, so it would still remain a museum, but
> > > a working museum. In fact, rosapps contains quite a bunch of important
> > > stuff too (like all those cmd line utilities).
> >
> > That would require porting rosapps to cmake (and building it, occasionally). I cannot do it and i cannot make anyone do that. If there are no volounters
> > > Also I would want indeed 2 screensavers in trunk - one "simple" and one
> > > "opengl" based. Everything else should go to rosapps as
> > > additional/optional stuff. Which of those - please decide, I don't have
> > > any strong preference myself.
> >
> > I`m fine with reducing the screensavers to two of them. Which one should be picked apart from starfield?
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > -- 
> > With best regards
> > Caemyr