And you're lucky if you get votes !
I can imagine nobody cares about pwsafe (except 2 people) but does that
mean that if you get no vote in extras-testing you'd better forget about
your app and start something new ?
I know you can't force people to vote or test ... But it means that if
an app
Hi!
There are some important widgets which are deprecated without a
replacement in Fremantle. Those widgets are still available, but they
are not fully finger-friendly or don't look good.
Developers are expected to implement those widgets by them selfs which
could lead us to a situation where we
Extras-testing QA is not working as it is implemented now! There are
two main issues:
* Comments are stored into a wrong place. Those belong to Bugzilla! It
is double effort for a developer to track two different places or to
transfer reports into bug tracking system manually.
* Developers
ext Graham Cobb wrote:
> By all means add a comment if you are unhappy with the UI but it
> should get a +1 as long as it doesn't conflict with the requirements.
> Ideally every -1 should require a comment saying which of the QA
> requirements is violated.
Agreed.
And even better, a link to a b
Thanks for the information.
On 9/23/09, Bruno Araujo wrote:
> Hi,
>
>
>> The reason I'm slightly skeptical is because my
>> applet is working fine in my scratchbox in the correct path
>> (/usr/lib/hildon-home/).
>>
>>
> Probably you have an outdated version of python-hildondesktop, because the
>
My long reply was lost when my N900 crashed while writing it. So this will
have to do.
I strongly disagree. Testers should be testing against the agreed requirements
only. The subjective element should be eliminated as much as possible - we are
using human testers because it is impossible to
Hi,
> The reason I'm slightly skeptical is because my
> applet is working fine in my scratchbox in the correct path
> (/usr/lib/hildon-home/).
>
>
Probably you have an outdated version of python-hildondesktop, because the
search path for home widgets have changed to /usr/lib/hildon-desktop. I
ins
I recently created in Python a Home Plugin for Fremantle and promoted
it to extras-testing. The feedback I received on it is that it doesn't
show up on the Desktop. Benoît HERVIER thought that it might be
because:
"the launcher module doesn't use the right path to search the home
applet, but use i
ext Ville M. Vainio wrote:
> On Wed, Sep 23, 2009 at 2:35 PM, Kate Alhola wrote:
>
>
>> If you just talk about "vanilla" application, it just takes your GTK+
>> Style and renders
>> widgets using that style. Using new special features needs to some
>> change to your
>> code and because there ar
Hum ... so i ll be able to play with it ...
2009/9/23 Ville M. Vainio :
> On Wed, Sep 23, 2009 at 1:27 PM, gary liquid wrote:
>
>>> Sounds like you want to use Python, with few select extensions in C/C++
>>> ;-).
>>
>>
>> probably, but performance for many things in python limits it.
>> liqbase i
On Wed, Sep 23, 2009 at 2:35 PM, Kate Alhola wrote:
> If you just talk about "vanilla" application, it just takes your GTK+
> Style and renders
> widgets using that style. Using new special features needs to some
> change to your
> code and because there are not equivalent counterparts in Diablo,
ext Attila Csipa wrote:
> On Wednesday 23 September 2009 12:26:01 Ville M. Vainio wrote:
>
>> it would be nice if the Qt apps written for Fremantle would look
>> identical in Diablo - i.e. implement it so that they would use
>> "fremantle style" in Diablo. I don't think people care as much about
On Wednesday 23 September 2009 13:10:43 you wrote:
> switching to Mer). The twist here is that you can use the same
> codebase for both Diablo and Fremantle, and expect the app to work the
> same.
Yes, I understand that, it's just there area few things that are not
applicable or different on Dia
On Wed, Sep 23, 2009 at 1:49 PM, Attila Csipa wrote:
>> it would be nice if the Qt apps written for Fremantle would look
>> identical in Diablo - i.e. implement it so that they would use
>> "fremantle style" in Diablo. I don't think people care as much about
>> "retaining a consistent feel", as t
On Wednesday 23 September 2009 12:26:01 Ville M. Vainio wrote:
> it would be nice if the Qt apps written for Fremantle would look
> identical in Diablo - i.e. implement it so that they would use
> "fremantle style" in Diablo. I don't think people care as much about
> "retaining a consistent feel",
On Wed, Sep 23, 2009 at 1:27 PM, gary liquid wrote:
>> Sounds like you want to use Python, with few select extensions in C/C++
>> ;-).
>
>
> probably, but performance for many things in python limits it.
> liqbase is optimized to hell and runs amazingly fast even on n8x0 hardware
Indeed (I've tr
Am Mittwoch, den 23.09.2009, 11:07 +0100 schrieb Andrew Flegg:
> It's easy to find problems, but our basic QA procedure started off as
> "installs cleanly, uninstalls cleanly, doesn't waste battery, has
> human readable description, has nice icons" and now "uses /opt and
> doesn't waste disk space
On Mon, Sep 7, 2009 at 5:09 PM, Kate Alhola wrote:
> Because there has been lot of discussion about these some widgets that
> do not yet have 1 to 1 counterpart in current Maemo Qt, we are going to have
> solution
> this question soon.
To return a bit to this old discussion -
it would be nice i
On Wed, Sep 23, 2009 at 4:47 AM, gary liquid wrote:
> what if those principles and methods and optimizations and streamlined
> development efforts were transfered and done in a qt context?
>
> that is:
>
> finding a streamlined way to continue the live development on the device as
> I currently d
On Wed, Sep 16, 2009 at 14:22, Graham Cobb wrote:
>
> The bottom line is that we need to try to use the process and see
> how well it works.
I've got a concern on the other side. There still seems to be
murkiness about what our processes are here - and these will evolve
through time, as you say.
20 matches
Mail list logo
