 |
|
<
< | Looking Glass Summer of Code 2006 projects | >
> | Looking Glass Summer of Code 2006 projects | | | Me
My name is Pierre Ducroquet, and I'm french. I discovered Looking Glass a bit before it was opensourced... | | | Project #501 : a presentation tool (my favorite SoC? project) | |
<
< | | | | Fast analysis
Currently, when we want to show Looking Glass, we have to use flat 2D presentation tools out of Looking Glass because of the lack of full screen support. Such presentations should be done using 3D features of Looking Glass : the presentation would speak a bit for "itself" that way. Off course, it'd be also interesting for other presentations to have amazing blazingly fast 3D effects (current applications like OpenOffice.org Impress have far too slow transitions between slides... That's often not smooth enough to be really pleasant.). | | | Let the fun continue  | |
<
< | | | | Fast analysis
During the Summer of Code 2005, I already worked on the Looking Glass performances. | | | Extra knowledge needed
The things I don't know and that can be useful here are some C, JNI and OpenGL? knowledge to work on Java3D?. | |
>
> |
Project #107 : LG3D? Desktop Configuration Tool (UI)
Fast analysis
I often show Looking Glass to users, and I always have different opinions. Some like it the way it is, but some other would prefer it another way... The same apply for flat 2D desktops like KDE. I never saw two power users with the same KDE Look. Since a 3D environment will be interesting mostly for power users at least at the beginning, it's mandatory to fill in this need : configurability.
It requires :
1- a tool to access the various LG3D? configuration settings easily
2- some extra configuration files to customise LG3D? even more
Motivation
My main motivation here is filling needs of users like my friends... They're probably going to help me and give me some tips about what is lacking, what is good, what is bad... Such a feedback is (I think) mandatory for such a project.
I also target the 1.0 release, because when it'll reach users computers, they'll immediately ask such features.
Work planning
I'm really sorry, I don't have any idea of a planning yet ! That's not the way I work usually...
Extra knowledge needed
The things I don't know and that can be useful here are every configuration entry of LG3D?, advanced Java UI... (The UI I wrote until yet are quite simple, I suppose this one would be far bigger) |
| | Looking Glass Summer of Code 2006 projects | |
<
< | | | | Me
My name is Pierre Ducroquet, and I'm french. I discovered Looking Glass a bit before it was opensourced... | | |
| |
<
< | Project #501 : a presentation tool (my favorite SoC? project) | >
> | Project #501 : a presentation tool (my favorite SoC? project) | | | Fast analysis
Currently, when we want to show Looking Glass, we have to use flat 2D presentation tools out of Looking Glass because of the lack of full screen support. Such presentations should be done using 3D features of Looking Glass : the presentation would speak a bit for "itself" that way. Off course, it'd be also interesting for other presentations to have amazing blazingly fast 3D effects (current applications like OpenOffice.org Impress have far too slow transitions between slides... That's often not smooth enough to be really pleasant.). | | |
| |
<
< | Project #210 : Performance Analysis and Tuning | >
> | Project #210 : Performance Analysis and Tuning | | | Let the fun continue | |
>
> | | | | Fast analysis
During the Summer of Code 2005, I already worked on the Looking Glass performances. |
|
<
< | Looking Glass Platform changes
Summer of Code - Include subject #001
I'll describe here what I'm planning to work on during the holidays for the google summer of code.
That work will be done on the Looking Glass platform. Looking Glass aims at creating a new desktop environment, written using Java and using 3D. | >
> | Looking Glass Summer of Code 2006 projects | | | | |
<
< | Fast analysis
Currently, an user who wants to test Looking Glass will face a lot of "problems".
The first (and the bigger) problem he'll face is the poor performances of the Looking Glass Platform. Currently, Looking Glass is in a primitive state, no big optimisation work was never done on it. So the user feels slowed down in its work, while he expects that 3D environment to help him imagine how his work could be done in a more efficient way (and I think that the 2D X11 applications integration allows our user to work in a better way than the current desktop environment like GNOME, because of for instance the windows thumbnails, translucency and other killer feature like windows parking.). | >
> | Me
My name is Pierre Ducroquet, and I'm french. I discovered Looking Glass a bit before it was opensourced... | | | | |
<
< | The second problem a "power user" will face is the lack of some functionnalities available in every other 2D environment. For instance I'll take a look at my previous customised KDE desktop. My desktop gave me a lot of informations, like the weather, the current track in my multimedia player, how hot my CPU is and so on. That's done on KDE by either some panel applets, either some "desktop" applets. This is evolving for KDE 4, where the desktop and the panels will be one application, sharing the same applets, with (expected) beautiful design. You can also take a look at Enlightenment 17 : a lot of people believes in there features, because it allows transparent applets. The only real thing in this desktop are currently the applets. Actually, Looking Glass has nothing available for that. That lack has to disappear. | >
> | I'm currently a student at the "ENIC", a french enginner school (city : Villeneuve d'Ascq, région : Nord). | | | | |
<
< | Motivation
I believe in Looking Glass. Looking Glass is THE current Open Source Project able to compete with the next Longhorn "revolutionnary" interface (Aero) or with the current Mac OS X interface (Aqua). What I can see on some forum or IRC channels about Looking Glass is a sorry picture. | >
> | *Needed knowledge* : I already know Java, I often designed files using XML, I already worked with CVS, and I know a bit about the major X servers available...
*Other things I know* : I know SQL (using sqlite or mysql), Python (my favorite programming language), C++, Qt, KDE, PHP... I know also a lot about how a linux distribution works, since I'm creating a distro with some friends (I developed the package manager, using sqlite for the database and XML for the packages)... And everything I forget to mention here  | | | | |
<
< | They consider Looking Glass as a slow and featureless desktop, because they faced the problems I mentionned before.
But I really want Looking Glass to survive in the desktop environment jungle : the people considering Looking Glass as bad aren't totally wrong because of its current state, but they are also impressed by the other desktops, showing common features with new graphics before innovating features (will they show any new feature ?) | | | | |
>
> |
| | | | |
<
< | Some months ago, I worked on Looking Glass in order to solve a problem I faced : the backgrounds and icons were "statically" written in the source code. That was a wrong behaviour, so I decided to work on it. After six hours, I learned a lot about Looking Glass, and I get a taste for the Looking Glass core. Because of the school, I had no time to work on it, but yet I'm ready to help developing what may be the future of our desktops ! | >
> | Project #501 : a presentation tool (my favorite SoC? project) | | | | |
>
> | Fast analysis
Currently, when we want to show Looking Glass, we have to use flat 2D presentation tools out of Looking Glass because of the lack of full screen support. Such presentations should be done using 3D features of Looking Glass : the presentation would speak a bit for "itself" that way. Off course, it'd be also interesting for other presentations to have amazing blazingly fast 3D effects (current applications like OpenOffice.org Impress have far too slow transitions between slides... That's often not smooth enough to be really pleasant.).
Motivation
I will probably demonstrate Looking Glass in a Lug but also perhaps at RMLL. For these events I have to show Looking Glass itself, but also slides. That'd really be boring for me to have two parts (that's something I really didn't like in a Xgl+Compiz presentation I saw at FOSDEM). I also showed Looking Glass at the ENIC open days, but it lacked a presentation. I couldn't show Looking Glass AND explain it with slides, that was a problem... It'd also be a nice 3D application.
So even if this is refused as a Summer of Code project, I will work on this, but it'd have to be later sadly :/ | | | Work planning | |
<
< | Even if the two problems look totally unrelated, I think that both can be worked on together. The optimisation work will probably need some core changes, while an applet system will need some core changes in order to be well integrated into the desktop. Doing the both work may be hard in two months, but nothing is impossible, especially with great languages like Java ! | >
> | My planning is really really short. | | | | |
<
< | I forgot to mention : I'm not a "planning man" at all ! My work method is quite anarchistic, but it just worked with a lot of other projects | >
> | First step : design and implement using Swing (or any other Java toolkit) a flat 2D presentation tool, to get the logic behind the application. It also includes creation of a simple file format, with a simple gui to create such files. | | | | |
<
< | Current planning (may (or most likely "will") evolve) : | >
> | I already have a lot of ideas about this, so I don't think it's really an issue. | | | | |
<
< | 1- First week : run a profiler on the Looking Glass core, identify the slowing points, identify the bugs related to the slowness in the bug tracker in order to have specific problems to solve... | >
> | Second step : extend the 2D presentation tool to be in the Looking Glass desktop as a 3D application. It'd basically look a bit like Zeotrope, but without the circle of pictures... | | | | |
<
< | 2- Second and third week : work on some bugs found, and trying other X server in order to see if a X server with a good Render acceleration can improve Looking Glass (may need a lot of hacks on one of the most horrible project I know, so I'm really not sure about that) | >
> | I plan to achieve these two steps before 14. July. | | | | |
<
< | 3- Until the end of August : really not sure about what will be done, it's relying on the previous weeks of work. | >
> | Third step : implement as many slide transitions as possible, work on Javascript integration into the file format. This Javascript integration must allow custom transitions to be written and tested quickly. | | | | |
>
> | The main issue I see here is Java5 compatibility. Java6 includes a great looking scripting engine, but what about Java5 (I'm pretty sure there is a Java5 compatible solution, but I have to look at it more closely). | | | | |
>
> | Optional step, requiring extra knowledge I can find in a book I have : OpenOffice.org macro to export Impress/Powerpoint files directly to our file format. | | | | |
<
< | If I can work on the applet system, then it would have another planning : | >
> | Here are basic ideas for the file formats : | | | | |
<
< | 1- First and second week : designing how an applet would have to be written. For instance, which language would be used for the applets scripting ? Python through Jython ? Javascript through Rhino (this may be better since Javascript is going to be included in Java 6.0) | >
> | 1- pictures based : font rendering would probably be out of topic, even if it's an interesting thing to look at. But using fonts means you can't use the export to HTML feature of OpenOffice impress, which creates several pictures... OpenDocument? support is totally out of topic here (it's a far too big task !) | | | | |
<
< | 2- After about four weeks : first prototype running some applets (samples : a clock, a CPU monitor, a memory monitor) | >
> | 2- everything in one zip file : this file would have low/null compression, because pictures aren't well compressed. Main advantage of zip files : they are extremely easy to use in Java | | | | |
<
< | 3- For the end of August : it may be possible to give people a clean way to write and add applets to Looking Glas. | >
> | 3- informations in one xml file : easy to parse, easy to extend/adapt, accessible with any programming language... Perfect choice for everything | | | | |
>
> | Extra knowledge needed
The things I don't know and that can be useful here are some OpenOffice API knowledge and Looking Glass applications API (I worked mostly in the displayserver). | | | | |
<
< | Me
My name is Pierre Ducroquet, and I'm french. I discovered Looking Glass one year ago. | >
> |
| | | | |
<
< | I'm currently a student in the "Lycée César Baggio" (city : Lille. région : Nord), and the next year I'm going to be a student at the "ENIC", a french enginner school (city : Villeneuve d'Ascq, région : Nord). | >
> | Project #210 : Performance Analysis and Tuning | | | | |
<
< | *Needed knowledge* : I already know Java (I'm not an expert, but I learn quickly), I often designed files using XML (usable for the applets for instance), I already worked with CVS (for the translation of the Looking Glass website in french), and I know a bit about the major X servers available... The things I don't know are more Java knowledge and some Looking Glass internal knowledge. | >
> | Let the fun continue | | | | |
<
< | *Other things I know* : I know SQL (using sqlite or mysql), Python (my favorite programming language), C++, Qt, KDE, PHP... I know also a lot about how a linux distribution works, since I'm creating a distro with some friends (I developed the package manager, using sqlite for the database and XML for the packages)... And everything I forget to mention here | >
> | Fast analysis
During the Summer of Code 2005, I already worked on the Looking Glass performances.
One of my own targets was achieved : a DivX? is now playable under LG3D?, and the startup time has been dramatically decreased.
But now, I've some additionnal targets :
1- be able to play a DVD (the harder target)
2- improve if possible the startup time of LG3D? and some other key components like BgManager?
3- find other hotspots and fix them
4- work on memory usage (again)
Motivation
My main motivation here is fun. I had fun during the SoC? 2005 doing this, and I want fun again
My second motivation here is to target the 1.0 release. It will be a big step for LG3D?, and we have to be ready for this step. It means we have to satisfy main queries for users :
- speed and memory efficiency
- look'n'feel
- features
These are really vast queries, but that's what most users want... and I really want LG3D? to be successful !
Work planning
I'm not able to plan a lot of things here. My DVD target should be feasible in one month of heavy work. Heavy because it includes Java3D? performance issues. Heavy because it could also require some additionnal X integration knowledge...
I suppose other hotspots would appear while working on the DVD thing. They must be solved at the same time if possible. | | | | |
>
> | The LG3D? startup time is already good enough, but it has increased since my SoC? 2005 project. I already have some ideas about what is responsible of this regression, but I don't know whether it'll be easy to fix them or not. | | | | |
<
< | Work in progress
I started working on the core... | >
> | And finally, the memory usage : I think it'll also appear during the DVD target since on my desktop computer a big slowdown is caused by swapping... | | | | |
<
< | I already did 4 small patches in order to understand how LG3D? works... They are here : http://pinaraf.robertlan.eu.org/LG3D/modifs/ | >
> | So to sum up : one target, one mission to achieve in two months... And no real planning :/ (I'm sorry, I'm not able to plan something)... | | | | |
>
> | Extra knowledge needed
The things I don't know and that can be useful here are some C, JNI and OpenGL? knowledge to work on Java3D?. | | | | |
<
< | Yes, my english is poor, but I'm doing my best in order to be understandable... So I hope you can understand me, and that you'll understand why I can't really write a lot of things about me... (and that would be boring, boring !) |
| | Looking Glass Platform changes
Summer of Code - Include subject #001 | | | *Other things I know* : I know SQL (using sqlite or mysql), Python (my favorite programming language), C++, Qt, KDE, PHP... I know also a lot about how a linux distribution works, since I'm creating a distro with some friends (I developed the package manager, using sqlite for the database and XML for the packages)... And everything I forget to mention here | |
>
> | Work in progress
I started working on the core...
I already did 4 small patches in order to understand how LG3D? works... They are here : http://pinaraf.robertlan.eu.org/LG3D/modifs/ | | | Yes, my english is poor, but I'm doing my best in order to be understandable... So I hope you can understand me, and that you'll understand why I can't really write a lot of things about me... (and that would be boring, boring !) |
| | Looking Glass Platform changes
Summer of Code - Include subject #001 | | | If I can work on the applet system, then it would have another planning :
1- First and second week : designing how an applet would have to be written. For instance, which language would be used for the applets scripting ? Python through Jython ? Javascript through Rhino (this may be better since Javascript is going to be included in Java 6.0) | |
>
> | | | | 2- After about four weeks : first prototype running some applets (samples : a clock, a CPU monitor, a memory monitor) | |
>
> | | | | 3- For the end of August : it may be possible to give people a clean way to write and add applets to Looking Glas. |
|
>
> | Looking Glass Platform changes
Summer of Code - Include subject #001
I'll describe here what I'm planning to work on during the holidays for the google summer of code.
That work will be done on the Looking Glass platform. Looking Glass aims at creating a new desktop environment, written using Java and using 3D.
Fast analysis
Currently, an user who wants to test Looking Glass will face a lot of "problems".
The first (and the bigger) problem he'll face is the poor performances of the Looking Glass Platform. Currently, Looking Glass is in a primitive state, no big optimisation work was never done on it. So the user feels slowed down in its work, while he expects that 3D environment to help him imagine how his work could be done in a more efficient way (and I think that the 2D X11 applications integration allows our user to work in a better way than the current desktop environment like GNOME, because of for instance the windows thumbnails, translucency and other killer feature like windows parking.).
The second problem a "power user" will face is the lack of some functionnalities available in every other 2D environment. For instance I'll take a look at my previous customised KDE desktop. My desktop gave me a lot of informations, like the weather, the current track in my multimedia player, how hot my CPU is and so on. That's done on KDE by either some panel applets, either some "desktop" applets. This is evolving for KDE 4, where the desktop and the panels will be one application, sharing the same applets, with (expected) beautiful design. You can also take a look at Enlightenment 17 : a lot of people believes in there features, because it allows transparent applets. The only real thing in this desktop are currently the applets. Actually, Looking Glass has nothing available for that. That lack has to disappear.
Motivation
I believe in Looking Glass. Looking Glass is THE current Open Source Project able to compete with the next Longhorn "revolutionnary" interface (Aero) or with the current Mac OS X interface (Aqua). What I can see on some forum or IRC channels about Looking Glass is a sorry picture.
They consider Looking Glass as a slow and featureless desktop, because they faced the problems I mentionned before.
But I really want Looking Glass to survive in the desktop environment jungle : the people considering Looking Glass as bad aren't totally wrong because of its current state, but they are also impressed by the other desktops, showing common features with new graphics before innovating features (will they show any new feature ?)
Some months ago, I worked on Looking Glass in order to solve a problem I faced : the backgrounds and icons were "statically" written in the source code. That was a wrong behaviour, so I decided to work on it. After six hours, I learned a lot about Looking Glass, and I get a taste for the Looking Glass core. Because of the school, I had no time to work on it, but yet I'm ready to help developing what may be the future of our desktops !
Work planning
Even if the two problems look totally unrelated, I think that both can be worked on together. The optimisation work will probably need some core changes, while an applet system will need some core changes in order to be well integrated into the desktop. Doing the both work may be hard in two months, but nothing is impossible, especially with great languages like Java !
I forgot to mention : I'm not a "planning man" at all ! My work method is quite anarchistic, but it just worked with a lot of other projects
Current planning (may (or most likely "will") evolve) :
1- First week : run a profiler on the Looking Glass core, identify the slowing points, identify the bugs related to the slowness in the bug tracker in order to have specific problems to solve...
2- Second and third week : work on some bugs found, and trying other X server in order to see if a X server with a good Render acceleration can improve Looking Glass (may need a lot of hacks on one of the most horrible project I know, so I'm really not sure about that)
3- Until the end of August : really not sure about what will be done, it's relying on the previous weeks of work.
If I can work on the applet system, then it would have another planning :
1- First and second week : designing how an applet would have to be written. For instance, which language would be used for the applets scripting ? Python through Jython ? Javascript through Rhino (this may be better since Javascript is going to be included in Java 6.0)
2- After about four weeks : first prototype running some applets (samples : a clock, a CPU monitor, a memory monitor)
3- For the end of August : it may be possible to give people a clean way to write and add applets to Looking Glas.
Me
My name is Pierre Ducroquet, and I'm french. I discovered Looking Glass one year ago.
I'm currently a student in the "Lycée César Baggio" (city : Lille. région : Nord), and the next year I'm going to be a student at the "ENIC", a french enginner school (city : Villeneuve d'Ascq, région : Nord).
*Needed knowledge* : I already know Java (I'm not an expert, but I learn quickly), I often designed files using XML (usable for the applets for instance), I already worked with CVS (for the translation of the Looking Glass website in french), and I know a bit about the major X servers available... The things I don't know are more Java knowledge and some Looking Glass internal knowledge.
*Other things I know* : I know SQL (using sqlite or mysql), Python (my favorite programming language), C++, Qt, KDE, PHP... I know also a lot about how a linux distribution works, since I'm creating a distro with some friends (I developed the package manager, using sqlite for the database and XML for the packages)... And everything I forget to mention here
Yes, my english is poor, but I'm doing my best in order to be understandable... So I hope you can understand me, and that you'll understand why I can't really write a lot of things about me... (and that would be boring, boring !) |
|