yh but can u desighn one
From: amsn-devel-requ...@lists.sourceforge.net
Subject: Amsn-devel Digest, Vol 36, Issue 8
To: amsn-devel@lists.sourceforge.net
Date: Wed, 24 Jun 2009 06:20:47 +0000
Send Amsn-devel mailing list submissions to
amsn-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/amsn-devel
or, via email, send a message with subject or body 'help' to
amsn-devel-requ...@lists.sourceforge.net
You can reach the person managing the list at
amsn-devel-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Amsn-devel digest..."
--Forwarded Message Attachment--
From: taniaere...@hotmail.co.uk
To: amsn-devel@lists.sourceforge.net
Date: Wed, 24 Jun 2009 07:18:56 +0100
Subject: Re: [Amsn-devel] Amsn-devel Digest, Vol 36, Issue 7
can i have a better msn please i cant even do cam on there and it so annoying
when my friends ask for me to go on cam and doesnt even work
From: amsn-devel-requ...@lists.sourceforge.net
Subject: Amsn-devel Digest, Vol 36, Issue 7
To: amsn-devel@lists.sourceforge.net
Date: Tue, 23 Jun 2009 23:28:18 +0000
Send Amsn-devel mailing list submissions to
amsn-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/amsn-devel
or, via email, send a message with subject or body 'help' to
amsn-devel-requ...@lists.sourceforge.net
You can reach the person managing the list at
amsn-devel-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Amsn-devel digest..."
--Forwarded Message Attachment--
From: pablog.ubu...@gmail.com
To: amsn-devel@lists.sourceforge.net
Date: Tue, 23 Jun 2009 02:31:11 +0200
Subject: [Amsn-devel] About the design of amsn2 and gui bases
Hello there.
I have a doubt about the design of amsn2.
First, well... we all know that want amsn2 to be front-end independent,
but while I am coding I feel like there should be some more things
commons to all front-ends.
For example, we could impose all login windows implementations to have a
self._account_views variable to store all accountviews that will be
displayed in the login screen.
This way, we could also have the self.getAccountViewFromEmail(email)
method that finds the accountview from the selected email in the
combobox (or whatever it is depending on the front-end) because that
function knows that the list of accountviews are stored in
self._account_views. Besides, after all we are not restricting the
freedom to implement your favorite front-end as you want, because I'm
(almost?) sure that every front-end will need it (correct me if I'm
wrong), and so all frontends could use it.
I think that at this point that the matter is clear.
But now the problem is that we have the class aMSNLoginWindow from which
every login window implementation inherits (I'm talking about the one
defined here: amsn2/gui/base/login.py). We could define all common
methods there, but I don't think it is the right place. I understand
that those files (amsn2/gui/base/*.py) are the base for every
implementation: they are templates and they are essential for anyone
that wants to make his own front-end for amsn2 and wants to know which
methods he has to redefine. Aren't they for that purpose?
So if everyone agree, we should now determine if it should be created a
new superclass (in this case for all login window implementations) and
leave the base there as is. Or on the contrary we (*I* this time) should
write all common methods/variables there, in the base.
To see what I'm talking about see my last commit here:
http://github.com/PabloCastellano/amsn2/commit/fc794680ccbbda7801fbbda9b91314d8ea4c2a7e
Any idea? Am I wrong about anything?
aMSN2 lives.
--
Regards, Pablo.
--Forwarded Message Attachment--
From: kakar...@kakaroto.homelinux.net
To: amsn-devel@lists.sourceforge.net
Date: Tue, 23 Jun 2009 13:42:28 -0400
Subject: Re: [Amsn-devel] About the design of amsn2 and gui bases
Hi,
As soon as you said "I have a doubt about the design of amsn2" you lost me...
:pAnyways, you're right, but all that you said isn't against the design. For
now the base classes are simply 'templates' (empty interfaces) because there is
nothing common to all front ends, but if you find something that should be
common to the templates, then yes, it *can* be put in the base classe, like you
described... however, my question would be :
why ? why would you put that common thing in the base class? If it's something
common, then it should be in the core...why not put the account_views in the
core, and the getAccountViewFromEmail in the core too? and leave the front end
classes to have only the UI specific tasks ?
KaKaRoTo
On Mon, Jun 22, 2009 at 8:31 PM, Pablo Castellano <pablog.ubu...@gmail.com>
wrote:
Hello there.
I have a doubt about the design of amsn2.
First, well... we all know that want amsn2 to be front-end independent,
but while I am coding I feel like there should be some more things
commons to all front-ends.
For example, we could impose all login windows implementations to have a
self._account_views variable to store all accountviews that will be
displayed in the login screen.
This way, we could also have the self.getAccountViewFromEmail(email)
method that finds the accountview from the selected email in the
combobox (or whatever it is depending on the front-end) because that
function knows that the list of accountviews are stored in
self._account_views. Besides, after all we are not restricting the
freedom to implement your favorite front-end as you want, because I'm
(almost?) sure that every front-end will need it (correct me if I'm
wrong), and so all frontends could use it.
I think that at this point that the matter is clear.
But now the problem is that we have the class aMSNLoginWindow from which
every login window implementation inherits (I'm talking about the one
defined here: amsn2/gui/base/login.py). We could define all common
methods there, but I don't think it is the right place. I understand
that those files (amsn2/gui/base/*.py) are the base for every
implementation: they are templates and they are essential for anyone
that wants to make his own front-end for amsn2 and wants to know which
methods he has to redefine. Aren't they for that purpose?
So if everyone agree, we should now determine if it should be created a
new superclass (in this case for all login window implementations) and
leave the base there as is. Or on the contrary we (*I* this time) should
write all common methods/variables there, in the base.
To see what I'm talking about see my last commit here:
http://github.com/PabloCastellano/amsn2/commit/fc794680ccbbda7801fbbda9b91314d8ea4c2a7e
Any idea? Am I wrong about anything?
aMSN2 lives.
--
Regards, Pablo.
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--Forwarded Message Attachment--
From: gustavo.d...@gmail.com
To: amsn-devel@lists.sourceforge.net
Date: Tue, 23 Jun 2009 20:28:15 -0300
Subject: Re: [Amsn-devel] 0.98 TODO
OK,
About
the VoIP images... exist in this new skin, i dont know why you dont see
it... and i told you the other day in the IRC about the sizes... so,
i've tested and i see the new pixmaps, just does not fit well cause of
the sizes, which is not skin problem.
Here a screenshot of this: http://img151.imageshack.us/img151/9356/amsn.png
As you can see, is not using the
buthangup_mini.png but the buthangup.png instead. So, is a code
problem... not skin problem since buthangup_mini.png already exist.
In
this screenshot you can see the close button of the tab, which is
another problem: whatevever you set the X position of it, will not
move... and plus as we know, there is no close hover effect as before.
About the colors of the contacts states, already has less saturation now. In
last commit I've added grouptopback* images (even when i dont know how to use
them...).
So, i think for now, there is no more.
About the Bg, i know that you are not a Designer KKRT, but that style is being
used a lot lately... And is better that the BG of the old skin.
Cheers.
2009/6/22 Youness Alaoui <kakar...@kakaroto.homelinux.net>
On Mon, Jun 22, 2009 at 7:12 PM, Youness Alaoui
<kakar...@kakaroto.homelinux.net> wrote:
On Sun, Jun 21, 2009 at 6:55 PM, Gustavo A. Díaz <gustavo.d...@gmail.com> wrote:
Hi,
Well, i think i've finished the Sapphire 2.5 Skin. I didnt have time to finish
my own set of smiles, which has more the look of the skin than the current made
from Ubitux, but is ok, those are nice.
cool!Yes, the smileys from ubitux are really nice and I'd wish we'd always keep
those by default. They are great and people got used to them, so...
I think no images is missing, except of grouptopback_dark.png,
grouptopback_light.png and the ccard ones (which even when KKRT said how to
enable it, it does not get enabled in the application... so i didnt updated
those since are not being used)
About grouptopback_*, i've asked how to enabled those in settings.xml, but no
reply... so i didnt added those pixmaps either.About
grouptopback_dark/light:<topgroupbg></topgroupbg> <!-- if it's empty it means
use the skin images -->
<topgroupbg_style></topgroupbg_style> <!-- it works only if topgroupbg is set
and style allowed are: light, dark.--> In the default skins's
settings.xml..and the code basically does a "if topgroupbg != "" : if
$topgroupbg_style == "light"... elseif $topgroupbg_style == "dark" else ..."
so there you go, that's how you test it..about the ccard, you need to go to
view->Show spaces icon, and in the Ctrl-shift-C console, type :::config::setKey
spacesinfo ccard
then clicking on the star next to the nickname should bring up the ccard
window...ok scratch this last part.. you don't need to do the ccard_* images
anymore.. I just found out that spaces support is dead, WLM removed the feature
and the server is down (unknown host), so we'll remove the feature completely..
vivia should be commiting a patch soon to remove the option from the view menu,
so there's no need to have those pixmaps anymore!
KaKaRoTo
This skin use only 3 images of the box_*, which does not affects the
performance of the skin, already is fastest than using the hole box_* set of
images, so is ok.
cool,
This week will be the last to see if i need to finish/add something to this
skin. I will not modify the color scheme of the images, i dont have time.
Besides i dont think it hurts to much the eyes.
Alright, I had another look at the skin, it's quite nice! good job there!
However, the colors are still hurting the eyes, but it's not the pixmaps, it's
just the status colors! So you only need to change the color definitions in the
settings.xml, it shouldn't be too hard... I don't think there's any need to
change the dp borders though, they're small so they won't bother... Try to keep
the same color scheme as with the current default.
I'm also not sure about the background, it looks bubbly.. which in my head
means : haha, fun, i'm 5 years old! I don't know, it looks childish, but some
people are still using this at work and are 40+ years old, so either something
more simple and subtle, or no background at all (we don't *need* a
background)...
By the way, I also looked at the voip controls and the images weren't changed
from the bad ugly default skin ones.. could you redo them please? Simply do a
'start audio call' on someone and they'll appear on your right...
The repos: svn://svn.tuxfamily.org/svnroot/amsnskins/amsnskins/trunk/Sapphire
Tarball:
http://svnweb.tuxfamily.org/dl.php?repname=amsnskins%2Famsnskins&path=%2Ftrunk%2FSapphire%2Fskin%2F&rev=0&isdir=1
Cheers.Thanks!
--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar
2009/6/13 Gustavo A. Díaz <gustavo.d...@gmail.com>
Lets see if i understand... you want me to use the group bg of my new skin to
the actual default skin? Which means that the skin for 0.98 will be the same as
0.97 is?
Btw, the buthangup_mini.png is the same as the actual button? or only is the
icon of the button?
2009/6/12 Youness Alaoui <kakar...@kakaroto.homelinux.net>
sorry for being unclear.. all I meant was that if we remove the group box right
now, then the image behind the group will look ugly because it 'expects' the
body to be under it.. but in your saphire it doesn't, the left and right sides
don't have a rounded edge, the sides actually gradient into white, so
basically, just copy the group bg from saphire to the current default and adapt
its colors to fit the current default color scheme.
by the way, I added a pixmap yesterday, it's buthangup_mini.png it's the
'hangup' button that should go into voip controls during an audio call...Thanks!
KaKaRoTo
On Fri, Jun 12, 2009 at 8:50 AM, Gustavo A. Díaz <gustavo.d...@gmail.com> wrote:
I will see what i can do.
Btw, i didnt get the 2 point... what do you mean?
As i said in the IRC, i've replaced 90% of group images by empty images and
just using 3 of them just for the group name bg... so, you said that this can
be replaced for a gradient?
Anyways, when i did that i saw much more improvements in speed.
Cheers.
2009/6/11 Youness Alaoui <kakar...@kakaroto.homelinux.net>
Thanks MontBlanc, but we (or I?) actually decided not to continue with the
minimalskin.. the only advantage of minimal skin is that it doesn't have the
boxes around groups, which are the cpu consuming ones...
but now with the svn, the skin can disable box drawing by a skin option, so
doing that for the current default skin would improve performance and
everyone's happy... We were going to use saphire 2.5 from Gustavo, but he sent
it to me, and I tried it and... well.. the color scheme was way too 'bright',
it hurts the eyes... he doesn't really have time to adapt it to a lower tone of
color, so I guess we'll have to stick with the current default theme...
Gus, do you think you can at least adapt the current default skin to have the
small needed improvements :1 - remove the box around groups2 - change the
group's bg pixmap to look like the one from saphire 2.5 (gradient on the side)
3 - see if there's some missing pixmaps and add them...Thanks,KaKaRoTo
On Thu, Jun 11, 2009 at 5:08 PM, Montblanc <toto...@gmail.com> wrote:
Hello everybody,
I saw adding missing pixmaps to minimal skin was in todo list and I
checked the recent updates on amsn-extras. There are still some
pixmaps missing (SkinColor, aMSN Plus and Inkdraw buttons) so I
decided to do the job. I took Dark Matter 4 ones and modified them
according to Minimal pixmaps resolution and hover background. Since
this is no original work, whether you choose to add it or not to svn
is up to you.
Here's the pixmaps list, a link to a snapshot and another to the tgz archive:
amsnplusbutton_hover.png
amsnplusbutton.png
butdraw_hover.png
butdraw.png
butgridoff_hover.png
butgridoff.png
butgridon_hover.png
butgridon.png
buttext_hover.png
buttext.png
butwipe_hover.png
butwipe.png
colorskin.png
http://img142.imageshack.us/img142/1797/minimalpixmapsz.jpg
http://www.mediafire.com/file/jod2dm3ajdl/minimal_missing_pixmaps.tar.gz
Best Regards,
Montblanc
2009/1/28 Vivia Nikolaidou <vi...@ee.auth.gr>:
> Time to start this :)
>
> - Add missing pixmaps to minimal skin and make sure tab flickering is visible
> - Fix MSNP2P stuff that broke with WLM 2009
> - Option to integrate webcam in the chatwindow (needed for maemo)
> - Finish VoIP UI
> - Small annoyance: when a CW gets opened because they nudge you, you
> don't see their DP
> - Make block/unblock work when using the byrdr server (I suspect that
> byrdr performs the change before redirecting us to omega, might not be
> the case though)
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar
Beyond Hotmail - see what else you can do with Windows Live. Find out more.
_________________________________________________________________
Share your photos with Windows Live Photos – Free.
http://clk.atdmt.com/UKM/go/134665338/direct/01/------------------------------------------------------------------------------
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
