I agree that developer.qt.nokia.com would be the right place for this, and give it some real credibility.
I just don't see how to make this out of a wiki... To me, the key points are screenshots + comments + ratings. I've learned that after using extensively CakePHP's bakery. And the later two don't seem to accomodate a wiki very well. But I admit that I have strictly no experience with wikis. On Fri, Aug 13, 2010 at 2:19 PM, <[email protected]> wrote: > And once again, my support for this idea. Greg’s idea would work but the > whole might benefit from some exposure and credibility if we could find a > way to put it up on developer.qt.nokia.com. Perhaps we could start with > the wiki (short on features but at least located in the right place) and > work from that once there’s a little content there? > > > > Simon. > > > > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *ext Gregory Schlomoff > *Sent:* 13 August 2010 07:56 > *To:* Westbrook Alan (Nokia-MS/MtView) > *Cc:* [email protected] > *Subject:* Re: [Qt-qml] Replacing a C++ listview with QML listview > > > > Hello Alan, > > > > Thanks for the tip. I'll follow your suggestion and rename the 'attachTo' > property to target. > > >So .. Who's going to make a web 2.0 site for sharing QML bits? > > > > I was meaning to do so as a week-end project, (even purchased a domain > name) but as I end up working for my main project on the week-ends as > well... You know how it is. :) > > > > But now that I see that there is definetely a need here, I'll try to come > up with something. I was thinking of something similar to CakePHP's > "Bakery", for those familiar with this framework ( > http://bakery.cakephp.org/categories/view/7) > > > > Basically, a gallery of components with a brief explanation, a link to a > repository, comments, ratings, tags, etc... Something simple and functional. > > > > > > On Fri, Aug 13, 2010 at 1:06 PM, <[email protected]> wrote: > > Hey Greg, > > > > Thanks for sharing the scrollbar, just a suggestion, as the rest of the QML > API seems to use 'target' for components that affect other components, > perhaps you should change the 'attachTo' to 'target' > > > > So .. Who's going to make a web 2.0 site for sharing QML bits? > > > > =) > > > > Alan > > > > On Aug 12, 2010, at 8:18 PM, ext Gregory Schlomoff wrote: > > > > Hi guys, > > > > Since there were a few people asking for our Scrollbar component, I just > published it in a public Mercurial repository. It lives here: > > > > https://bitbucket.org/gregschlom/qmlscrollbar > > > > If you're not using mercurial, there's a "get sources" link on the right > that allows you to download a zip file. > > > > I've included a sample qml file demonstrating the usage, as well as the > images and the photoshop file for the Scrollbar. Obvioously, you'll want to > change that to use yours. > > > > The code is released under the MIT license. It may have bugs, and it > probabably can be enhanced (adding support for horizontal scrolling, for > example). If you make any changes that make this code better, please feel > free to submit patches / merge requests. > > > > Cheers, > > > > Greg > > > > > > > > On Thu, Aug 12, 2010 at 8:40 PM, Gregory Schlomoff < > [email protected]> wrote: > > We are using QML ListViews in our desktop app. It works well... Now that a > lot of bugs have been fixed, and that we really understand how ListView > works :) > > > > As for the scrollbar, we made a quick Scrollbar component that works very > well. The code looks like this: > > > > ListView { > > id: myList > > ... > > } > > ScrollBar { > > attachTo: myList > > } > > > > The scrollbar can be attached to any Flickable (so that includes ListView). > But it only works for vertical scrolling, as of now. We may share the code > for this component, if it's of any interest to you. Just drop me a mail. > > > > (By the way, that raises again the question of a public place to share qml > componentns :) ) > > > > Cheers > > > > greg > > > > > > On Thu, Aug 12, 2010 at 8:31 PM, Riaan Kruger <[email protected]> wrote: > > I am playing with QML and is considering replacing a listview in a C++ > (desktop) application with a QML based listview using qdeclarativeview. > > I want to do this to demonstrate the capabilities of QML and because I find > customizing list/tree views in Qt C++ hard. > > > > Is this a good idea, or am I in for some hurt? > > What is the best strategy for handling scrolling; scrollbars are normally > preferred on the desktop > > > > > > Riaan > > > > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-qml > > > > > > <ATT00001..txt> > > > > >
_______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
