Menu
▾
▴
Re: [Basket-devel] class Basket on basis of QScrollArea
|
From: Vyacheslav T. <sl...@go...> - 2007-10-30 20:24:29
|
Hi, I've spent a last couple of days researching what can we do with qt4 and kd= e4=20 technologies. I'm sure we need to spend a lot of time on planning api, designing, reviewi= ng=20 the whole architecture, and the rest implementations won't be so hard at al= l.=20 (of course, if we choose the right design) 1) my comments about : http://basket.kde.org/version2.php I'm totally agree with the vision about the project : it should be easy, fa= st=20 and very powerfull at the same time. Don't include not-needed features. But I don't understand 1 point :=20 "Free-positioning of notes lead to disordered notes. BasKet Note Pads has=20 automatic layout using columns;" - what do you mean by that ? What is=20 about "free" template for baskets now ? 2) Vision of 2.0: a) Document-like interface: Paragraph sounds great, but as I understand they are more convenient for=20 restricted basket with fixed layout. What about free-layout form ? I think= =20 it's more powerfull because you can rearrange all items as you want. And it= 's=20 a lot of fun I think. (it's just my point of view) There are definetely use-case where people put items occasionnally and then= =20 try to sort them, connect by arrows, group etc. It's all need more mockups and clarifications. b) Save searches - sounds great. And use one search for each basket togethe= r -=20 seems more intuitive. c) Section and pages: We shouldn't do that! have 3 different ways to do the same things is awful Tree-like structure of notes is good, and it's very easy to understand - yo= u=20 see your whole information at once - that's what you need. (be easy) And if have tree structure on left, pages on top sections on right... turn= =20 head to left, right, top, left, right, top... trying to find what you need = :)=20 It's like a real mess :) d) Note Connectors is ok It's just the beginning. I'll probably change my mind on some points here :) What technologies do we have (in arbitrarily order) : 1) sonnet - spellchecking support in kde4 The last week (probably the week before the last) the project becomes alive= =20 again. I think by the time we will have basket in shape it will be there. So short summary is here :=20 http://techbase.kde.org/Development/Tutorials/Sonnet/SonnetTutorial 2) phonon - it's easy way to integrate audio and video support in the notes suppose you have some audio file in your note. with description, reminder o= r=20 whatever. if you hovering over this file some "playing" icon shows on it an= d=20 you can just click this icon and see or listen. in some embedded window I=20 suppose (very lightweight and easy) And phonon provides that. some example here, and it's very easy : http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apido= cs/phonon/html/phonon_tut1.html 3) strigi integration : don't know a lot about that 4) nepomuk : meta-data is usefull probably. in the future we can tagged our= =20 basket files with meta-descriptions . But not for now I think. But do think= =20 about that opportunity. 5) of course good integration with kde4 applications ( don't really know -= =20 what's about that ) 6) The tough decision :=20 QGraphicsView for basket QGraphicsItem for notes We should use that for every type of basket. Of course it will be easier to= =20 use QVBoxLayout with QTextEdit for fixed one column basket.=20 But we want some general API that can be used for everything at once. Maybe we can use QGraphicsTextItem for notes, and declared new class=20 BasketParagraph : QGraphicsItem that can hold as child different text notes= ,=20 images, audios, videos, sketchings etc. It's possible with new Model/View=20 framework to group QGraphicsItems so it won't be a problem to group several= =20 BasketParagraphs together. Arrows and similar stuff - should more research here - it's not clear what= =20 will be better. make new class Connectors and let paragraphs be connected=20 with several connectors or what Also, we need to find out howto designed possibilities for different=20 paintings, sketches, marks with let's say red color. just mark some note=20 (it's important I want it to be very bright) It's not clear what to do when= =20 moving sketched note. how to group it together etc. 7) make everything shine - transparent different colors, all AntiAliased to= =20 look great There are a lot of ideas here : 1) if hover the tree widget : apple-like menu roll-over items, preview if h= old=20 mouse on the basket-item in the list (as Desktop in Beryl) 2) split the basketview into 2 different on the left and right sides with=20 different baskets in it ( don't think it's usable :) tough )=20 3) a lot of animations etc It's very important to do that , cause in other case basket won't be used o= n=20 macos and windows. =2D--------------------------------------- It was my first attempt to consider some directions of development. So let'= s=20 discuss it a little bit more.=20 p.s. I'm sure I forgot about many things, but it's too late anyway :) Best regards, Vyacheslav Tokarev On Monday 29 October 2007 19:49:56 S=E9bastien Lao=FBt wrote: > Le dimanche 28 octobre 2007, perihelion a =E9crit=A0: > > Hi, tsjoker > > > > > Hi, > > > > > > We can think of that from 2 different points of view: > > > > > > 1) Basket is still will be available for kde4, as all old apllications > > > are. the kde guys don't want to break all things down. so the users c= an > > > use basket 1.0. While we creating new break-through version 2.0 > > > > If it's sure, this raw porting dont add value from a kde3 app running in > > kde4, and then i think we can go to the next step. > > We must check if a kde3 app works in kde4 without kde3 installed. > > Okay. > > BasKet Note Pads 1.0 may work well under KDE 4, but for how long? > Sure, distributions are going to ship both KDE 3 and KDE 4 at the beginin= g. > As more and more applications get ported to KDE 4, KDE 3 libraries can > disapear from distributions when we haven't finished a proper KDE4-version > of BasKet Note Pads. > > ** > > Back to writting this email: > I've done a ride on #kde-devel and I have answers. > > [14:20] <CyrilleB> Sebien: to give you an idea, in april next year, ubuntu > will release a Long Term Support version, with 5 years support, and it's > very likely that kubuntu will be default to KDE3 and not KDE4 > [14:21] <pusling> Sebien: and debian lenny is expected in around a year. = It > might very well be shipped with kde3 as well > [14:21] <jpwhiting> shouldn't be a problem > [14:22] <pusling> Sebien: members of the kde release team have said that > only insane distributiotns ship anything less than 4.1.2 as default deskt= op > [14:23] <pusling> Sebien: don't worry too much yet - for example kmail > might not ship with kde4.0 > > So BasKet Note Pads 1.0 will run on KDE 4, and for at least a year. > It should be Ok. > > So now, I'm Ok with the idea of doing the very-deep changes right now. > It may be the best solution, after all. > That's going to be exciting :-D > > > > 2) Incremental development. Don't rewrite all things at once. At first > > > port to qt4, then to QGraphicsView, then will be something else also. > > > > and maybe think how we store data, can we make basket colaborate with > > strigi, koffice, how make plugins easier todo etc.. > > Yes, since you're going the deep-change way, it is "the occasion or never" > to include changes in the user interface, in features, and all. > > See http://basket.kde.org/version2.php to know what solutions were > envisoned. And especially: > http://basket.openusability.org/wiki/index.php/Main_Page > > It's better for the deep-change to include (most of) those new features a= nd > interface (like a framework for Undo/Redo using the History Qt classes, > etc). > > That's also why an IRC meeting is very important to be able to discuss all > of those and choose a direction, visionnary, but still realist. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Basket-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/basket-devel |