I wrote all my ideas about the new ReactOS page (that came to my mind) together:
http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&...
What is your opinion about that?
There are two (or more) possible solutions for the static main pages: * wiki system that generate the static pages (HTML/XHTML) (maybe language support problem ?) * selfwritten simple CMS system (very flexible, easy to use, only a few php-scripts so fewer bugs, better integration (design, layout), language support, generate HTML/XHTML, ...) (* CMS system like the current one)
What system do you prefer? (wiki, CMS, ...)
Compatibility and Package Manager section: * wiki based (like in the current mediawiki only a long list) * php based dynamic list (with filter features and tree structur; mysql database): example: (first alpha page) http://frik85.fr.funpic.de/packmgr/?page=tree&sec=view&sec2=2 * winehq's application database (or something else; redesign it?)
What system do you prefer? (wiki, dynamic list (tree structur), ...)
I will have time in july/august/sept. to implement the Compatibility-, Package Manager section and the simple CMS system that can generate the static pages, if it is okay for you. But I will wait until I get a "start signal". If someone else want do it alone or want help me, it will be no problem (for me; then I will have more time to code for ReactOS).
I wrote this because the current ReactOS page is awful (design and CMS system) and we need a better and more beautiful page to gain more visitors, get a bigger ReactOS community (and more devs). I hope the UI-Team will finalize the layout of the homepage in the next two months.
Thanks for reading this, and maybe you find time to write your opinion about that.
Best regards, Klemens Friedl
(PS: Tomorrow, I will have no time to answer any emails, sorry.)
Is it possible to include RSS Support at a later date, for 'New Release' notification?
As quite a few have been saying, RSS Support is very desirable if implemented in the kernel.
On 6/26/05, Klemens Friedl klemens_friedl@gmx.net wrote:
I wrote all my ideas about the new ReactOS page (that came to my mind) together:
http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&...
What is your opinion about that?
There are two (or more) possible solutions for the static main pages:
- wiki system that generate the static pages (HTML/XHTML) (maybe language
support problem ?)
- selfwritten simple CMS system (very flexible, easy to use, only a few
php-scripts so fewer bugs, better integration (design, layout), language support, generate HTML/XHTML, ...) (* CMS system like the current one)
What system do you prefer? (wiki, CMS, ...)
Compatibility and Package Manager section:
- wiki based (like in the current mediawiki only a long list)
- php based dynamic list (with filter features and tree structur; mysql
database): example: (first alpha page) http://frik85.fr.funpic.de/packmgr/?page=tree&sec=view&sec2=2
- winehq's application database (or something else; redesign it?)
What system do you prefer? (wiki, dynamic list (tree structur), ...)
I will have time in july/august/sept. to implement the Compatibility-, Package Manager section and the simple CMS system that can generate the static pages, if it is okay for you. But I will wait until I get a "start signal". If someone else want do it alone or want help me, it will be no problem (for me; then I will have more time to code for ReactOS).
I wrote this because the current ReactOS page is awful (design and CMS system) and we need a better and more beautiful page to gain more visitors, get a bigger ReactOS community (and more devs). I hope the UI-Team will finalize the layout of the homepage in the next two months.
Thanks for reading this, and maybe you find time to write your opinion about that.
Best regards, Klemens Friedl
(PS: Tomorrow, I will have no time to answer any emails, sorry.)
-- Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie! Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
I've been scouring the message boards of late, and it appears Longhorn's support for RSS has gotten people into wanting RSS-related features in Open-Source Kernels. I'm not suggesting it should be in ROS... Yet. The kernel has a long way to go yet.
It should be an option, certainly. I can see the ROS Package Manager using RSS at some point to keep up to date.
On 6/27/05, mf mf@mufunyo.net wrote:
TwoTailedFox wrote:
As quite a few have been saying, RSS Support is very desirable if implemented in the kernel.
Did I just read that right? RSS support in the _kernel_ ? *blink* Now what exactly did I miss ?
Regards, mf.
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
Last week I had the A-level exams. So I had no time to answer. Sorry! I read all your comments.
To avoid misunderstanding next time: With a simple CMS system, I mean some small scripts that allowed the Admins to edit the Pages with an online editor (wysiwyg rich text editor like http://www.kevinroth.com/rte/demo.htm ). The benefit of such a simple editor plus some small scripts to manage and reorder some site parts, is that it is simple and effective. The only function the CMS provide that is visible for the end-user is the homepage generation: This simple CMS will have a function to generate the static pages from the databased source (added with the wysiwyg editor) and store the output in different directories (e.g. english: "/en/" ; german: "/de/" ; ...) and set the links/paths in a correct way.
Another purpose of the CMS: Easy to edit content for language translators (with wysiwyg editor).
In my opinion, Mambo (or any other CMS (or Wiki) solution) is not so good for our needs. The mayor feature should be to generate static html/xhtml pages without any overhead!
The other features I mentioned are only minor features that can be implemented as "plugins" as small php scripts included with the wysiwyg editor. So there is no reason to "vote" against it. These features are not important (only extras)!
Compatibility / Package Manager Page: In my opinion, this database should be coded in php like the appdb from winehq or similar. But wine's appdb is not so powerfull as needed for ReactOS (software + hardware, packages, etc. in one database). So I think it speak nothing against. So it make sense to write such a database php script for ReactOS. Show me a good application database! I know many similar pages, but all are crappy or inconvenient. It is my freetime ... but I want to create the best solution for such a compatibility and package manager database. Please visit http://frik85.reactos.at for more information about this. -> http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&... -> http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&... -> http://frik85.fr.funpic.de/packmgr/
Best regards, Klemens Friedl
P.S.: I will be on holiday ("Maturareise" or "Abiturreise") until 2005-07-11.