El 06/03/2014 19:48, "Martin Decky" <[email protected]> escribió: > > Hello Sergio, > > >> Woops, it seems I forgot to upload the web design. The design it's for >> the main site, but maybe I will be able to do one for trac if needed. > > > You design looks promising. Currently it's a little bit too spartan for my taste and it's hard to judge how it would look like with all the additional content that needs to be there in the end, but I am looking forward to the future improved versions.
> As I understood it is basically a learning-by-doing experience for you. Thus I suggest you keep working on that, you are on a good path. Indeed, it's inspired by SPARTAN :) . Jokes aside I'm aware it does not look very good and. I'm working on a new design which will look ( at least I hope so) awesome. >> Whowever I also thought that a good, high-permformance (even though initially basic) drawing library would greatly favour HelenOS, however I'm not really sure whether this is smaller/larger than what is needed for GSoC. > > > A drawing library is a good topic and it is also a scalable topic -- the assignment can range from a simple bunch of screen drawing routines (lines, circles, etc.) to a fully-blown, integrated, vector-based, device-independent, antialiased library similar to libcairo. > > If you are thinking about proposing this as a GSoC project, you should divide the whole idea into three parts: > > 1. Requirement specification and design: Despite the fact that you > won't be able to implement everything, the library should be designed > from the day one as extensible, open-ended and well-fitting > component of our graphics stack. Surveying and taking inspiration > from existing libraries (libcairo, Allegro, Quartz 2D and others) is > also necessary here. > > 2. Basic mandatory features: A set of mandatory features what would > serve as a proof-of-concept of the design and that would also make > the library practically usable, even with some limitations. This > calls for some drawing routines and device independence (maybe with > only the most basic transformations), but for example the > antialiasing might be omitted. > > 3. Advanced features: Optional features that you might implement as > time permits you. Antialiasing, scene graph construction, advanced > transformations and advanced drawing primitives (Bezier curves, > etc.) go here. > > > > M.D. > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel I was wondering whether it was better to fo it from scratch or port one existent ( since we have no c++ the only I could port would be evas or cairo).
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
