You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(60) |
Jul
(35) |
Aug
(32) |
Sep
(5) |
Oct
(5) |
Nov
(58) |
Dec
(34) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(114) |
Feb
(184) |
Mar
(153) |
Apr
(90) |
May
(153) |
Jun
(59) |
Jul
(24) |
Aug
(43) |
Sep
(17) |
Oct
(34) |
Nov
(11) |
Dec
(204) |
2007 |
Jan
(84) |
Feb
(119) |
Mar
(38) |
Apr
(28) |
May
(52) |
Jun
(105) |
Jul
(64) |
Aug
(67) |
Sep
(14) |
Oct
(3) |
Nov
(28) |
Dec
(55) |
2008 |
Jan
(228) |
Feb
(55) |
Mar
(30) |
Apr
(30) |
May
(15) |
Jun
(20) |
Jul
(12) |
Aug
(3) |
Sep
(13) |
Oct
(54) |
Nov
(35) |
Dec
(35) |
2009 |
Jan
(19) |
Feb
(20) |
Mar
(34) |
Apr
(4) |
May
(60) |
Jun
(25) |
Jul
(16) |
Aug
(51) |
Sep
(19) |
Oct
(62) |
Nov
(21) |
Dec
(12) |
2010 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
(12) |
May
(23) |
Jun
(13) |
Jul
(1) |
Aug
(40) |
Sep
(18) |
Oct
(21) |
Nov
(26) |
Dec
(34) |
2011 |
Jan
(17) |
Feb
(23) |
Mar
(1) |
Apr
(10) |
May
(1) |
Jun
(5) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(43) |
2012 |
Jan
(5) |
Feb
(19) |
Mar
(6) |
Apr
(24) |
May
(39) |
Jun
(83) |
Jul
(29) |
Aug
(36) |
Sep
(64) |
Oct
(55) |
Nov
(12) |
Dec
(7) |
2013 |
Jan
(17) |
Feb
(10) |
Mar
(37) |
Apr
(27) |
May
(13) |
Jun
(9) |
Jul
(7) |
Aug
(61) |
Sep
(23) |
Oct
(23) |
Nov
(30) |
Dec
(16) |
2014 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(17) |
May
(2) |
Jun
(11) |
Jul
(2) |
Aug
|
Sep
(9) |
Oct
(24) |
Nov
(2) |
Dec
(14) |
2015 |
Jan
(6) |
Feb
(4) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(3) |
Jul
|
Aug
|
Sep
(2) |
Oct
(21) |
Nov
(6) |
Dec
(2) |
2016 |
Jan
(4) |
Feb
(2) |
Mar
(7) |
Apr
(3) |
May
(11) |
Jun
(6) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(4) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: John L. <jla...@gm...> - 2006-02-22 14:59:49
|
On 2/22/06, k. holwerda <kla...@nl...> wrote: > If we can not make it work, we better tell the user, or diable those in > the project files. Or leave them on with a warning and maybe somebody more knowledgeable will know how to fix it or at least understand the problem. If we disable it, nobody can help us. > The next change, improves it a bit. > > #include "wx/dynarray.h" > WX_DECLARE_OBJARRAY_WITH_DECL( wxLuaState, wxArrayLuaState, class > WXDLLIMPEXP_WXLUA ); > > #include "wx/hashmap.h" > WX_DECLARE_VOIDPTR_HASH_MAP_WITH_DECL( wxLuaStateRefData *, > wxHashMapLuaStateRefData, class WXDLLIMPEXP_WXLUA ); > > will check it in this evening, Already done. -John Labenski |
From: k. h. <kla...@nl...> - 2006-02-22 10:11:30
|
Hi John, John Labenski wrote: >I've updated wxStEdit in wxCode's CVS to remove the warnings. I'm >sorry, I've never tried to compile wxWidgets as a DLL so I have no >experience on why you get so many unresolved function errors. > i have seen the before in wxArt2D, and in VC6 it is often impossible to solve. ( that is why i like the idea of seperating the project files in VC6 and VC.NET versions. Like that we can make them work for what they can work, just diable the generation of DLL flavours in VC6 etc. ) But in higher version it is/can be oke. I am also not experienced with this, but in wxArt2D there is this dll wizard Leo, and i gladly take over his tricks ;-) > Do you >have to cross link libraries to get it to work? Dunno. > > If we can not make it work, we better tell the user, or diable those in the project files. The next change, improves it a bit. #include "wx/dynarray.h" WX_DECLARE_OBJARRAY_WITH_DECL( wxLuaState, wxArrayLuaState, class WXDLLIMPEXP_WXLUA ); #include "wx/hashmap.h" WX_DECLARE_VOIDPTR_HASH_MAP_WITH_DECL( wxLuaStateRefData *, wxHashMapLuaStateRefData, class WXDLLIMPEXP_WXLUA ); will check it in this evening, Klaas -- Unclassified |
From: klaas.holwerda <kho...@xs...> - 2006-02-21 23:42:15
|
Oops wrong link: http://www.xs4all.nl/~kholwerd/tmp/wxluacan.tgz klaas.holwerda wrote: |
From: klaas.holwerda <kho...@xs...> - 2006-02-21 23:40:30
|
Hi John, Here i put a wxCanLua which has the smart pointerlist as i suggested. I works oke. In the top of the cansim.cpp its MyFrame::MyFrame you can how to use it. http://www.xs4all.nl/~kholwerd/tmp/wxLua2.zip The idea is that the object created in lua script are added to such a list. And for instance wxlCanObj will be stored in such a list too. Next it does not matter who deletes the lists/smartpointers first, the last one will simply delete the wxObject derived objects which we wanted to delete save. I can make wxlCanLua so that it uses this list already, but that would really make sence if the m_pTrackedList would be of this type. regards, Klaas klaas.holwerda wrote: > > > Shall i prepare something like the above, next you can choose ;-) > |
From: John L. <jla...@gm...> - 2006-02-21 23:12:45
|
On 2/21/06, klaas.holwerda <kho...@xs...> wrote: > >> If so we might pay less attention to VC6 which is not to good i think. > > I think MSVC6 is going to be completely 'deprecated' in few years... > That is what i think too. But at the moment? > > maybe we could: > > a) move msvc6 project files in the new build\msvc6 folders > > b) convert msvc6 project files and add them in the build\msvc7/8 folder= s > Good idea. > > > > Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats... > > I'm going to see if I can add these formats to bakefile. But, don't they both support converting from dsp files to their sln files? I use 2005, the free one new and I've also used .NET (a few years back) and both converted the dsp files just fine. You had to be careful about deleting the sln files if you edited the dsp files, but that wasn't a big deal. > >> I myself get linking errors, etc. i wonder if this is because of VC6 > >> or soemthing else. > I put the two logs files here. > > First i tried to make wxStedit which i downloaded at wxCode. ( I tried > first CVS but had problems so i downloaded it eventually.) > It is not clear yet from install.html which one i should get. > That i tried to build without success. > Next the log file for wxLua. > > http://www.xs4all.nl/~kholwerd/tmp/logs/ I've updated wxStEdit in wxCode's CVS to remove the warnings. I'm sorry, I've never tried to compile wxWidgets as a DLL so I have no experience on why you get so many unresolved function errors. Do you have to cross link libraries to get it to work? Dunno. John Labenski |
From: John L. <jla...@gm...> - 2006-02-21 23:01:00
|
On 2/21/06, k. holwerda <kla...@nl...> wrote: > wx_object.cpp > ..\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251: > 'm_coroutineStates' : class 'wxArrayLuaState' needs to have > dll-interface to be used by clients of class 'wxLuaStateRefData' > ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration > of 'wxArrayLuaState' > ..\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251: > 's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to > have dll-interface to be used by clients of class 'wxLuaStateRefData' > ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration > of 'wxHashMapLuaStateRefData' > ..\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: non > dll-interface class 'wxLuaDebugDataItemArray' used as base for > dll-interface class 'wxLuaDebugData' > ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see > declaration of 'wxLuaDebugDataItemArray' Fixed. Regards, John Labenski |
From: John L. <jla...@gm...> - 2006-02-21 22:48:34
|
On 2/21/06, Francesco Montorsi <f18...@ya...> wrote: > Hi, > > John Labenski ha scritto: > > On 2/21/06, Francesco Montorsi <f18...@ya...> wrote: > >> Hi John, > >> I see there are various project files and Makefiles not > >> bakefile-generated scattered among the wxLua tree... could we remove t= hem ? > >> > >> If the makefiles are still up2date, I think we could keep them as > >> 'safety' system in case bakefile-generated ones fail in some way. > > > > I use all the "old" Makefiles regularly and I would like them to stay. > > They are based on wx-config and should work in linux on any system > > that has wx-config in their path. They're also very easy to understand > > so that I can add profiling and other temporary things easily. > ok, sure. > Just one question: is there anything in hand-written makefiles which you > can't do with ./configure ? Heh, I can understand the hand written ones and they're easy to modify. The bakefile Makefiles are basically incomprehensible, there's way too many conditions to make it parseable by a mortal at a glance. If the existing makefiles conflict with something, we can rename them to Makefile.wx-config. -John Labenski |
From: klaas.holwerda <kho...@xs...> - 2006-02-21 21:59:23
|
Hi, Francesco Montorsi wrote: > >> If so we might pay less attention to VC6 which is not to good i think. > I think MSVC6 is going to be completely 'deprecated' in few years... That is what i think too. But at the moment? > maybe we could: > a) move msvc6 project files in the new build\msvc6 folders > b) convert msvc6 project files and add them in the build\msvc7/8 folders Good idea. > > Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats... > I'm going to see if I can add these formats to bakefile. Arrg! > > >> Did you both compile all flavours in batch build using 2005 ? > > If so do they compile well? > I don't like to do batch builds with IDE. I know. > I usually use makefiles for that and makefile.vc allowed me to compile > wxLua with any combination of options I've tried so far... With project files we must get it too work too, this is what the general user will use. Especially when debugging i prefer much to debug inside the linked libraries and all. That is often how i understand where the problems are. > > > >> I myself get linking errors, etc. i wonder if this is because of VC6 >> or soemthing else. I put the two logs files here. First i tried to make wxStedit which i downloaded at wxCode. ( I tried first CVS but had problems so i downloaded it eventually.) It is not clear yet from install.html which one i should get. That i tried to build without success. Next the log file for wxLua. http://www.xs4all.nl/~kholwerd/tmp/logs/ Let me know what i should do to test more, Klaas |
From: Francesco M. <f18...@ya...> - 2006-02-21 19:50:05
|
Hi, John Labenski ha scritto: > On 2/21/06, Francesco Montorsi <f18...@ya...> wrote: >> Hi John, >> I see there are various project files and Makefiles not >> bakefile-generated scattered among the wxLua tree... could we remove them ? >> >> If the makefiles are still up2date, I think we could keep them as >> 'safety' system in case bakefile-generated ones fail in some way. > > I use all the "old" Makefiles regularly and I would like them to stay. > They are based on wx-config and should work in linux on any system > that has wx-config in their path. They're also very easy to understand > so that I can add profiling and other temporary things easily. ok, sure. Just one question: is there anything in hand-written makefiles which you can't do with ./configure ? Francesco |
From: John L. <jla...@gm...> - 2006-02-21 19:10:07
|
On 2/21/06, Francesco Montorsi <f18...@ya...> wrote: > Hi John, > I see there are various project files and Makefiles not > bakefile-generated scattered among the wxLua tree... could we remove them= ? > > If the makefiles are still up2date, I think we could keep them as > 'safety' system in case bakefile-generated ones fail in some way. I use all the "old" Makefiles regularly and I would like them to stay. They are based on wx-config and should work in linux on any system that has wx-config in their path. They're also very easy to understand so that I can add profiling and other temporary things easily. > Project files I think are not maintainable by hand and thus should be > removed... Yes, I'll remove all the XXX_wx26.dsp files soon. Regards, John Labenski |
From: Francesco M. <f18...@ya...> - 2006-02-21 17:40:43
|
Hi John, I see there are various project files and Makefiles not bakefile-generated scattered among the wxLua tree... could we remove them ? If the makefiles are still up2date, I think we could keep them as 'safety' system in case bakefile-generated ones fail in some way. Project files I think are not maintainable by hand and thus should be removed... Francesco |
From: Francesco M. <f18...@ya...> - 2006-02-21 17:35:16
|
Hi, k. holwerda ha scritto: >> Is there any other problem which must be solved before the release ? >> > What should compile in VC when using batch build? > > ( I read that VC2005 is for free now, is it true?? ) the express edition is free but it has some limited features. Nonetheless it's a great thing: something free from ms ;) > If so we might pay less attention to VC6 which is not to good i think. I think MSVC6 is going to be completely 'deprecated' in few years... maybe we could: a) move msvc6 project files in the new build\msvc6 folders b) convert msvc6 project files and add them in the build\msvc7/8 folders Unfortunately AFAIK MSVC.NET and MSVC2005 use two different formats... I'm going to see if I can add these formats to bakefile. > Did you both compile all flavours in batch build using 2005 ? > If so do they compile well? I don't like to do batch builds with IDE. I usually use makefiles for that and makefile.vc allowed me to compile wxLua with any combination of options I've tried so far... > I myself get linking errors, etc. i wonder if this is because of VC6 or > soemthing else. > > Klaas > > wx_object.cpp > ...\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251: > 'm_coroutineStates' : class 'wxArrayLuaState' needs to have > dll-interface to be used by clients of class 'wxLuaStateRefData' > ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration > of 'wxArrayLuaState' > ...\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251: > 's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to > have dll-interface to be used by clients of class 'wxLuaStateRefData' > ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration > of 'wxHashMapLuaStateRefData' > ...\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: > non dll-interface class 'wxLuaDebugDataItemArray' used as base for > dll-interface class 'wxLuaDebugData' > ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see > declaration of 'wxLuaDebugDataItemArray' these are warnings, what about the linking errors? Francesco |
From: k. h. <kla...@nl...> - 2006-02-21 14:10:56
|
Francesco Montorsi wrote: > > Is there any other problem which must be solved before the release ? > What should compile in VC when using batch build? ( I read that VC2005 is for free now, is it true?? ) If so we might pay less attention to VC6 which is not to good i think. Did you both compile all flavours in batch build using 2005 ? If so do they compile well? I myself get linking errors, etc. i wonder if this is because of VC6 or soemthing else. Klaas wx_object.cpp ..\..\..\modules\wxlua/include/wxlstate.h(184) : warning C4251: 'm_coroutineStates' : class 'wxArrayLuaState' needs to have dll-interface to be used by clients of class 'wxLuaStateRefData' ..\..\..\modules\wxlua/include/wxlstate.h(156) : see declaration of 'wxArrayLuaState' ..\..\..\modules\wxlua/include/wxlstate.h(190) : warning C4251: 's_wxHashMapLuaStateRefData' : class 'wxHashMapLuaStateRefData' needs to have dll-interface to be used by clients of class 'wxLuaStateRefData' ..\..\..\modules\wxlua/include/wxlstate.h(159) : see declaration of 'wxHashMapLuaStateRefData' ..\..\..\modules\wxluadebug/include/wxldebug.h(108) : warning C4275: non dll-interface class 'wxLuaDebugDataItemArray' used as base for dll-interface class 'wxLuaDebugData' ..\..\..\modules\wxluadebug/include/wxldebug.h(100) : see declaration of 'wxLuaDebugDataItemArray' -- Unclassified |
From: John L. <jla...@gm...> - 2006-02-21 04:33:49
|
On 2/20/06, Francesco Montorsi <f18...@ya...> wrote: > Francesco Montorsi ha scritto: > > Hi, > > as you can see, I start to think to the first release of wxLua ;) Thanks! > > So, let's discuss this issue. > > > > I'd make a total of 4 releases: > > > > 1) a win32 MSI install package. This can be generated using InnoSetup > > and it should distribute all wxLua tree including EXE, doxygen generate= d > > docs and .lib files, all built in release mode, possibly against a > > static build of wxWidgets. > I have created this package and added it to CVS. > I also uploaded an experimental setup installer for win32 at > > http://wxlua.sourceforge.net/wxLua-2.6.2.1-setup.exe > > I've tried it out for a while and it works nice. If someone can test it > and confirms it installs wxLua and that it works it would be good. > However it needs: > > 1) to have all wxLua sample files to be renamed with .wxlua extension > (.wx.lua extension is not good for windows when you need to associate a > program to it - at least programmatically) That will make syntax highlighting editors not be able to immediately hilight it for lua. I'm not sure that's a good idea. > 2) to have wxLuaEditor able to open .wxlua files which are passed to it > as first parameter... John, can you do that ? If you really think that that's a good idea, I don't think so. > BTW I think that all wxLua samples should be reviewed as they look quite > old and some doesn't work smoothly... Heh, there are more samples from the original distribution, but I just took the ones that work out of the box. But I do agree that they are not very exciting. > Is there any other problem which must be solved before the release ? > Besides the website completion, obviously... (any help writing pages > would be very appreciated ;)) I will try to put some text up there tomorrow. -John Labenski |
From: Francesco M. <f18...@ya...> - 2006-02-20 23:27:33
|
Hi, Francesco Montorsi ha scritto: > Hi, > as you can see, I start to think to the first release of wxLua ;) > > So, let's discuss this issue. > > I'd make a total of 4 releases: > > 1) a win32 MSI install package. This can be generated using InnoSetup > and it should distribute all wxLua tree including EXE, doxygen generated > docs and .lib files, all built in release mode, possibly against a > static build of wxWidgets. I have created this package and added it to CVS. I also uploaded an experimental setup installer for win32 at http://wxlua.sourceforge.net/wxLua-2.6.2.1-setup.exe I've tried it out for a while and it works nice. If someone can test it and confirms it installs wxLua and that it works it would be good. However it needs: 1) to have all wxLua sample files to be renamed with .wxlua extension (.wx.lua extension is not good for windows when you need to associate a program to it - at least programmatically) 2) to have wxLuaEditor able to open .wxlua files which are passed to it as first parameter... John, can you do that ? BTW I think that all wxLua samples should be reviewed as they look quite old and some doesn't work smoothly... Is there any other problem which must be solved before the release ? Besides the website completion, obviously... (any help writing pages would be very appreciated ;)) Francesco |
From: John L. <jla...@gm...> - 2006-02-20 19:22:52
|
On 2/15/06, k. holwerda <kla...@nl...> wrote: > >I'm still a little sketchy about smart pointers. Does the template > >code work in MSVC 6? > > > Sure, it is simple template code. > >Your smart pointer class is just a single header file right? > > > Not exactly. The class itself yes, but a list of smrt pointers now uses > a simple a2dlist as base, is derived from STL as container. > Before we used wxList as container, but i am glad i moved to STL. > Anyway for wxLua wxList is maybe the best choice for the moment, so i > can easily make that again. > Just a few lines of code. > > I think i best prepare a header and source file, containing all that is > needed here. > This will make it simple for you to use it. I've looked it over and I'm a little confused. We'd use a a2dSmrtPtrList of template classes a2dSmrtPtr right? Would we have to have templated versions of the a2dSmrtPtr for every class type in order for it to know how to delete it? For example, you've got a class MyDataClass that you can create in C++ and push into lua or create in lua and pass to a C function that may or may not delete it. Does this mean that your class has to be derived from the template version of a2dSmrtPtr? What if someone has an existing class from some other library, like wxWidgets, that they cannot make it derived from a2dSmrtPtr? How would this work? How would deleting the object be able to tell the smart pointer that it's gone? If these issues can't be resolved I think it would be best to have your C code pull the data from lua and take ownership of it. If you wanted to get it back in lua you'd have a function to get it back by using an id of some sort. int DoStuffWithMyData(MyDataClass* data) pull *data from lua and take ownership return an int id to access the data again MyDataClass* GetMyDataClass(int id) return pointer to data based on id or null for none Does this second way work for you? This way we don't have to force every class to be derived from a2dSmrtPtr. Regards, John Labenski |
From: Francesco M. <f18...@ya...> - 2006-02-20 10:44:12
|
klaas.holwerda ha scritto: > Francesco Montorsi wrote: > >>> >>> I now put a black rectangle in illustrator. So i commited the blue >>> in front image. >> >> well, the black rectangle is quite visible in the right border of the >> image, where the gradient is going toward the yellow... >> maybe it was better the transparent background... could you try to >> create a last logo without it (but with blue box over the ring) so >> that I can try some last touchs ? > > http://www.xs4all.nl/~kholwerd/tmp/lualogo/ > > 10 11 12 take the one you like best, > > Here the anitaliased 11 looks fine, but how it wroks out with the > backgorund i don;t know, I modified one antialiased but with transparent background and updated the CVS and the website; it looks good ! I've also modified the gradient so that the logo is more plunged in the black ;) I'd say that the logo now is good as is; I'd focus now on the real contents of the website :) BTW I'm also working to get wxLua autopackages working... but it's hard specially because 64bit systems like mine are difficult to handle :( Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-02-19 23:32:32
|
klaas.holwerda wrote: > Francesco Montorsi wrote: > > http://www.xs4all.nl/~kholwerd/tmp/lualogo/ and now number 14 with polygon black background, anitliased transparent :-) Klaas |
From: klaas.holwerda <kho...@xs...> - 2006-02-19 23:18:03
|
Francesco Montorsi wrote: >> >> I now put a black rectangle in illustrator. So i commited the blue >> in front image. > > well, the black rectangle is quite visible in the right border of the > image, where the gradient is going toward the yellow... > maybe it was better the transparent background... could you try to > create a last logo without it (but with blue box over the ring) so > that I can try some last touchs ? http://www.xs4all.nl/~kholwerd/tmp/lualogo/ 10 11 12 take the one you like best, Here the anitaliased 11 looks fine, but how it wroks out with the backgorund i don;t know, Klaas |
From: Francesco M. <f18...@ya...> - 2006-02-19 22:44:08
|
Hi, klaas.holwerda ha scritto: > Francesco Montorsi wrote: > >>> >> I added a few more here: >> wxlua5.gif is the one which looks better: I've committed it to CVS... > > How many times the site is updated? once per day >> >>> >>> If it does i finish that one to look proper again. >> >> IIRC paint shop pro allows you to unsert the 'antialiasing' property >> in vector objects and that would probably help - even better would be >> to tell paint shop pro to use black pixels for the antialiasing (since >> the image must go on a black background) > > I did it in illustrator, only the last step in psp. > I now put a black rectangle in illustrator. So i commited the blue in > front image. well, the black rectangle is quite visible in the right border of the image, where the gradient is going toward the yellow... maybe it was better the transparent background... could you try to create a last logo without it (but with blue box over the ring) so that I can try some last touchs ? > >> >> >> Anyway if you can regen the logo with the blue block above, I can >> remove the white pixels manually with GIMP :) > > Having add addware/virus, which i don't succeed to remove, and which > irritates me to the bone, i am thinking about reinstalling my notebook, > and i might as well use SUSE, although for GIMP one can use windows > these days ;-) good luck ;) BTW SuSE was one of the fastest distro I've ever tried but Ubuntu really is my favourite distro now ;) Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-02-19 22:33:03
|
Francesco Montorsi wrote: >> > I added a few more here: > wxlua5.gif is the one which looks better: I've committed it to CVS... How many times the site is updated? > >> >> If it does i finish that one to look proper again. > > IIRC paint shop pro allows you to unsert the 'antialiasing' property > in vector objects and that would probably help - even better would be > to tell paint shop pro to use black pixels for the antialiasing (since > the image must go on a black background) I did it in illustrator, only the last step in psp. I now put a black rectangle in illustrator. So i commited the blue in front image. > > > Anyway if you can regen the logo with the blue block above, I can > remove the white pixels manually with GIMP :) Having add addware/virus, which i don't succeed to remove, and which irritates me to the bone, i am thinking about reinstalling my notebook, and i might as well use SUSE, although for GIMP one can use windows these days ;-) Klaas |
From: Francesco M. <f18...@ya...> - 2006-02-19 21:25:37
|
Hi, klaas.holwerda ha scritto: > Francesco Montorsi wrote: > >> sorry - I added them as normal files. >> I've removed and readded them as binary files. > > I see that is how one makes gradients ;-) yes, CSS does not natively support gradients so that trick is required... > I added a few more here: > > http://www.xs4all.nl/~kholwerd/tmp/lualogo/ > > They are not ready ( paint shop pro i used to put the blue rectangle in > the front. > I resized them in vector format to get samller bitmaps. > > But can you see if it helps? wxlua5.gif is the one which looks better: I've committed it to CVS... > > If it does i finish that one to look proper again. IIRC paint shop pro allows you to unsert the 'antialiasing' property in vector objects and that would probably help - even better would be to tell paint shop pro to use black pixels for the antialiasing (since the image must go on a black background) > > The problem is that here i do not see white pixels. > > And i do not know how to get the result as on the webpage , which is > looking bad :-( just put the image (which has a transparent background) to a black background Anyway if you can regen the logo with the blue block above, I can remove the white pixels manually with GIMP :) Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-02-19 21:13:43
|
Francesco Montorsi wrote: > sorry - I added them as normal files. > I've removed and readded them as binary files. I see that is how one makes gradients ;-) I added a few more here: http://www.xs4all.nl/~kholwerd/tmp/lualogo/ They are not ready ( paint shop pro i used to put the blue rectangle in the front. I resized them in vector format to get samller bitmaps. But can you see if it helps? If it does i finish that one to look proper again. The problem is that here i do not see white pixels. And i do not know how to get the result as on the webpage , which is looking bad :-( Klaas |
From: Francesco M. <f18...@ya...> - 2006-02-19 20:58:33
|
klaas.holwerda ha scritto: > Hi Francesco, > > Or you sure you did check in the images on the website binary? > I can not read them somehow, and i see CRLF here and there. sorry - I added them as normal files. I've removed and readded them as binary files. Francesco |
From: klaas.holwerda <kho...@xs...> - 2006-02-19 20:39:04
|
Hi Francesco, Or you sure you did check in the images on the website binary? I can not read them somehow, and i see CRLF here and there. Klaas Francesco Montorsi wrote: > Hi, > > klaas.holwerda ha scritto: |