[kgraphviewer-devel] Preparing a release

[Tomaz Canabrava]

yes we do.    =) ( I'm the 'other guy' )
just sometimes too busy to respond ( akademy - br last week, flisol this week )
but I'm reading everything.


On Sat, Apr 24, 2010 at 8:44 AM, Milian Wolff <mail at milianw.de> wrote:
> On Saturday 24 April 2010 10:50:39 Gaël (aka Kleag) wrote:
>> On Friday 23 April 2010 11:23:49 Milian Wolff wrote:
>> > Gaël (aka Kleag), 23.04.2010:
>> > > On Thursday 22 April 2010 14:46:34 Milian Wolff wrote:
>> > > > Gaël (aka Kleag), 22.04.2010:
>> > > > > Hello,
>> > > > >
>> > > > > As noted by some of you, one of the things to do for kgraphviewer
>> > > > > is to prepare a release.
>> > > > >
>> > > > > What do you think should be done before doing this release ? Is
>> > > > > there some missing or incomplete feature to implement before
>> > > > > releasing ? Maybe the final replacement of the external dot
>> > > > > process by the graphviz library ?
>> > > >
>> > > > I'd welcome that. And furthermore I'd like to get more feedback on my
>> > > > interface. We shouldn't provide ABI compatibility for the first
>> > > > release, but should come up with a working interface anyways...
>> > >
>> > > Concerning, the interface, don't you think that most of the part slots
>> > > should be available through the interface, like addNewNode or
>> > > removeNode ? Otherwise what would be the right criterion to include a
>> > > feature in the interface or not ?
>> >
>> > Yes, good point. As long as the signals are pure virtual members (not
>> > signals) in the interface, they can be easily overwritten by slots in the
>> > actual implementation. That's also what's done in e.g. the KTextEditor
>> > interfaces.
>>
>> Yes. Do you want to do it ?
>>
>> But, in the class definition, they are called "slotXyz", and it would be
>> strange in an interface to have such names. "xyz" would be more natural.
>> What do you think ?
>
> full ack. The slot... stuff should be removed. I'll see whether I can get
> around to do it.
>
> Other question: Do you know whether sandroandrade + one other guy read this
> list now? We could need more feedback from them...
>
>> > > > > I have started to set up a suse build service to be able to produce
>> > > > > packages for several Linux distributions when the release will be
>> > > > > ready.
>> > > >
>> > > > Cool. But imo there are packagers for many repos out there who'd help
>> > > > you here, at least we from kdevelop don't do any custom packaging...
>> > >
>> > > Yes, you're right. And kgv is already packaged by several distros, but
>> > > that can allow to give a compatibility with current and previous
>> > > distros versions.
>> > >
>> > > > Simply announce on kde-packagers or how that ML was called.
>> > >
>> > > I did not know this kde-packagers list... I'll try to remember. I don't
>> > > understand what you mean by "or how that ML was called." ?
>> >
>> > Well, is it really kde-packagers at kde.org or was it something-else at kde.org
>> >
>> > :)
>>
>> Oh, yes, I see. I'm sometimes a little bit "slow" when reading English.
>
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
> _______________________________________________
> kgraphviewer-devel mailing list
> kgraphviewer-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kgraphviewer-devel
>
>