wyodesktop-devel Mailing List for wyoDesktop
Status: Alpha
Brought to you by:
wyo
Menu
▾
▴
wyodesktop-devel — Development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
|---|
|
From: Otto W. <ott...@or...> - 2004-09-27 15:46:09
|
> Jonas () has submitted this feedback > Thanks, this helps me to concentrate on the most important issues if I'm able. > The editor works well in Windows. I use it all the time and am happy I found it. In Linux > however it has a tendency to crash and I regretfully decided not to use it. I have been > looking for an editor that behaves the same in windows and Linux for a long time ... :( > I still use it on Linux because I haven't found anything better :-( . BTW that was my first reason to create wyoEditor. Now it's also a marketing item to show others how to write good applications. Crashes in Linux are while most pressing unfortunately also something I can't do much. Most (if not all) of these crashes are rooted within wxWidgets and/or GTK+. All I can try is to see if the crashes are within my sources or try to locate the problems within wxWidgets myself. Saddening even if discover them they aren't fixed within wxWidgets, just look at the patches I still have to put up. And most saddening if I only can attribute it to wxWidgets, my bug reports are simply closed (see "http://sourceforge.net/tracker/index.php?func=detail&aid=998555&group_id=9863&atid=109863"). All I can do is hope that any crash is fixed by other means and leave it to the user to submit bug reports. Very sorry :-(( > When I whent back to see if a newer version would solve the problem I found that the > dependencies where to something that would force me to manually upgrade some stuff > and NO NOTE about that change in the release. > I'm hard pressed to just look for the most important issue although I spend _all_ my spare time for development (haven't played any doom for years!). Caring for changelog doesn't have by far enough high priority, you either have to look at the release statements at "http://freshmeat.net/projects/wyoeditor/" or walk through CVS. Of course anyone else is welcomed to take over this task. > Having control over the dependencies and installation is a thing the open-source still > fail in. This makes me sad since many projects are so good. I know there are many > people that thinks it\'s all right to download source and manually resolve dependencies, > build, install and configure software. But me and the many others that have a life and > whant to USE lots of good software will eventually fall back. This leaves many of the > projects only suitable to entusiasts. I see this as a great loss to us all.... > I see your point but sorry I've absolute _no_ time to care myself. I also prefer to just USE instead of DEVELOP good software. I still hope and do everything I can so we all are able to USE in a not too distant future. > I wonder how many good projects die because of this lack shutting out a LARGE user-base > ... and then similar projects are started again ... and fails again. Eventually no one thinks > the idea is good. But it is, they just fail to complete the delivery part, and decay is > introduced.. > As long as users don't take over their share of work this situation won't change! See that I get much more time to care for all the issues a normal user shouldn't be confronted. To solve exactly this issue I've created the wyoDesktop project "http://wyodesktop.sourceforge.net/" but without your help, you have to wait some decades until you can USE it. Why don't you start an OpenSource fan club which does some lobbying - in newspapers and public forums to spread the news about wyoDesktop - to attract others (developers and users) to participate as much as they can - to attract sponsors (companies and politicians) to solve resource problems - at universities to enhance and enforce the wxGuide guidelines - ... so there is finally enough man power to take care for all the outstanding issues. > ... Good editor, barely usefull project. > Thanks, what do you with "barely useful project". O. Wyss -- See a huge pile of work at "http://wyodesktop.sourceforge.net/" |
|
From: Otto W. <ott...@or...> - 2004-09-17 18:00:16
|
IMO mimetypes are the only way to access all the different applications on a desktop in a user friendly manner. Mimetypes are the glue how applications are connected to files, how applications are visible so a user can work with them. But the current implementation and the current standard at freedesktop.org is a complete mess. The following mimetype concept tries to solve the situation. Concept: A mimetype library with an easy usable API handles the current implementation, _may_ handle the freedesktop standard and allows to handle a future Berkeley DB implementation. This API has to conform to the following points: - allows for a simple future Berkeley DB implementation - provides translations between current and future implementation - allows to retrieve file types according to mimetype, extension, creator and/or magic ids - allows to easily create and change mimetypes by any application - handles all information needed for connecting files with applications - handles all inforamtion how applications are visible on the desktop - handles all information how applications are visible in menus, docks, etc. - handles default information if not provided by applications. All the mimetype information have to be provided and installed by the application, it's their responsibility to care that the information are complete and correct any time they are needed. This may mean each application has to check and correct this information each time it's run. At least any user without _any_ computer knowledge and without any rights has to be able to restore these information anytime. A tool has to be created to take care for conflicts between different applications and to add, change or remove informations. Any change of this tool has a higher priority than changes by applications. There might be a common source, a public repositiory, for such changes. O. Wyss -- See a huge pile of work at "http://wyodesktop.sourceforge.net/" |
|
From: ABX <ab...@ab...> - 2004-08-28 02:27:32
|
Hi! I thought you would be interested in knowing what I gathered in the past: 1. Regarding thread "wxWidgets/wxUniv: Samples testing" I would like to mention that I put a lot of effort for stabilisation of demos, utils and samples in general in wxWidgets repository. There should not be many = holes in samples and they in general are very stable with no asserts (at least = that was my intention). So that stuff should be a good start for searching holes = in your wxUniv usage. For sure there are four places not working for me: - helpgen util with unicode; - memcheck sample because nobody want to explain how to adjust setup.h; - mfc sample because none of my windows compilers has mfc built in (I do= not=20 use VisualC) - tab sample because this is supposed to be replaced by notebook and is = =20 maintained only because one port (motif? or x11?) does not have = notebooks =20 iirc. 2. As for thread "Difference between 2.5.2 and CVS wrt wxUniv/GTK2" = Theodore asked: apart stock buttons we all know, there are plenty of changes = regarding fixing best size handling which iirc was seriously broken in 2.5.2. Some other changes can be reviewed through http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/docs/changes.txt.diff?r1=3D= 1.514&r2=3D1.454 3. As for my own changes I fixed long problem I observed of not = responding to command in submenus (only menuitems in top wxMenu generated events). I = fixed it in common code thought I never investigated it under other platforms = than MSW. 4. As for other issues I know regarding wxMSWUniv: - launch bombs demo, Ctrl+1 and other keyboard accelerators do not work = until you do not enter menu once - forty demo - whole window is in one green colour (it can be fault in = demo design but I never figured what is wrong exactly) I hope above list will help you a little. BTW: Otto, while I understand that if you do not use something and if it = cause problems you do not like it. But please do not call stock buttons "silly"= just for respect for those persons and platforms who need it. Best regards to wyoDesktop developers, ABX |
|
From: Otto W. <ott...@or...> - 2004-08-27 21:20:40
|
"Theodore R. Smith" wrote: > > Actually, "all" I really have to do is fix wxToolBar. It is the only thing that > doesn't look right with wxUniv/GTK2. Unfortunately, it is proving elusive to > draw the label under the picture. Sure? Well there is at least a segfault with the accelerators when deleting menus. Try once wxGuide demo or the menu sample. O. Wyss -- See a huge pile of work at "http://wyodesktop.sourceforge.net/" |
|
From: Theodore R. S. <the...@xm...> - 2004-08-27 20:58:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |>My goal is to focus on wxUniv/GTK2 until it can display xMule as well as wxGTK2, |>and then split off towards creating a wxUniv/GDK themer, so that GDK can be used |>instead of GTK. |> | | I think it's a rather hard task to bring xMule to work with wxUniv/GTK2 | and probably nobody will ever use wxUniv/GTK2 productive. Actually, "all" I really have to do is fix wxToolBar. It is the only thing that doesn't look right with wxUniv/GTK2. Unfortunately, it is proving elusive to draw the label under the picture. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBL59+y4tlS+M78e0RAodZAJ91dp1LQC5vOLxufcKlgoC0LRmofwCfQL9Y AxPQon3j23ZXYVDFTq04zb4= =vUxK -----END PGP SIGNATURE----- |
|
From: Otto W. <ott...@or...> - 2004-08-27 20:49:49
|
"Theodore R. Smith" wrote: > > I would like to know what ostensibly has changed from 2.5.2 to current cvs in > wxUniv...I'm not even fully aware of when 2.5.2 was released, as I spent most of > my time with 2.4.2... > It was released May 31st, 2004. The only changes I remember are the stock buttons but I may have forgotten something. We can equally well take the current snapshot and simply remove the silly buttons if they don't work. And of course we may try to sync if 2.6 really is released in october. > My goal is to focus on wxUniv/GTK2 until it can display xMule as well as wxGTK2, > and then split off towards creating a wxUniv/GDK themer, so that GDK can be used > instead of GTK. > I think it's a rather hard task to bring xMule to work with wxUniv/GTK2 and probably nobody will ever use wxUniv/GTK2 productive. > Outside of that slight detour, I'm committed to getting to Stage 1 as fast as > possible. > Perfect. O. Wyss -- See a huge pile of work at "http://wyodesktop.sourceforge.net/" |
|
From: Theodore R. S. <hop...@xm...> - 2004-08-27 20:13:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to know what ostensibly has changed from 2.5.2 to current cvs in wxUniv...I'm not even fully aware of when 2.5.2 was released, as I spent most of my time with 2.4.2... My goal is to focus on wxUniv/GTK2 until it can display xMule as well as wxGTK2, and then split off towards creating a wxUniv/GDK themer, so that GDK can be used instead of GTK. Outside of that slight detour, I'm committed to getting to Stage 1 as fast as possible. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBL5T7y4tlS+M78e0RAgohAJ9lhlEzpk8dUrwGdPjGLtyzSPivkACfZSWU 4uwt5gEOEhISF701jglJneU= =xnob -----END PGP SIGNATURE----- |
|
From: Julian S. <ju...@an...> - 2004-08-27 17:51:02
|
At 18:39 27/08/2004, Otto Wyss wrote:
>Julian suggested to me to go ahead and split wxUniv off wxWidgets and
>take care of it myself. This suits me well I hope it does you too.
Er, I didn't suggest it, I just said if that's what you wish to do,
fair enough. It's regrettable you're taking this
stuff-you-I'll-do-it-my-way tone, but I wish you luck.
Regards,
Julian
>If you agree or if you don't have better alternatives, I'll do the following:
>- The split will be based on release 2.5.2 and might include some needed
>bug fixes.
>- Only directly to wxUniv related files are taken to minimize any impact
>in the common parts.
>- I'll try to prevent any incompatibilities until wyoDesktop finishes
>pre-state.
>- I'm not going to actively keep the two version in sync, that's someone
>else task.
>- Any API changes within wxWidgets won't be taken care of by me in wxUniv.
>- I may but can't guarantee I'll do a merge back, someone else might
>volunteer.
>
>I don't see many problems. Of course I and you may miss bug fixes in the
>common parts but since lower level W32 is rather stable and lower level
>GDK is only used in wxUniv this won't be a big problem. Also a simple
>mail to the other project might be sufficient. On the other side no API
>changes are reasonably possible unless taken care of by _you_ in _both_
>version. Okay, okay, you can simply go on but no sensible application
>developer will use features he knows he has to scrap in a year or so.
>
>To say it with other words, the API of wxUniv will stick with the
>version of 2.5.2 unless you submit _all_ the necessary changes. Even
>than I might not apply them if I consider them not important enough.
>I'll stick to this policy until the pre-stage of wyoDesktop is finished
>("http://wyodesktop.sourceforge.net/index.php?page=tasks.html"). So if
>you aren't happy with this, help that this stage is reached as soon as
>possible.
>
>IMO this is a fair deal we both can live with. The resources of
>wyoDesktop is sufficient but still limited, so the goal has to be set
>accordingly. I cannot take over any responsibility for anything unless
>the resources are available. Please don't complain and understand that.
>
>To be kept informed it's a good idea to subscribe to the
>wyodesktop-devel mailing list.
>
>O. Wyss
>
>--
>See a huge pile of work at "http://wyodesktop.sourceforge.net/"
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: wx-...@li...
>For additional commands, e-mail: wx-...@li...
=========================================================================
Julian Smart ju...@an...
28/5 Gillespie Crescent, Edinburgh, www.anthemion.co.uk
Midlothian, U.K., EH10 4HU +44 (0)131 229 5306
Writer's Cafe: power tools for writers www.writerscafe.co.uk
HelpBlocks: HTML help authoring www.helpblocks.com
DialogBlocks: cross-platform dialogs www.anthemion.co.uk/dialogblocks
=========================================================================
|
|
From: Otto W. <ott...@or...> - 2004-08-27 17:39:26
|
Julian suggested to me to go ahead and split wxUniv off wxWidgets and
take care of it myself. This suits me well I hope it does you too.
If you agree or if you don't have better alternatives, I'll do the following:
- The split will be based on release 2.5.2 and might include some needed
bug fixes.
- Only directly to wxUniv related files are taken to minimize any impact
in the common parts.
- I'll try to prevent any incompatibilities until wyoDesktop finishes pre-state.
- I'm not going to actively keep the two version in sync, that's someone
else task.
- Any API changes within wxWidgets won't be taken care of by me in wxUniv.
- I may but can't guarantee I'll do a merge back, someone else might volunteer.
I don't see many problems. Of course I and you may miss bug fixes in the
common parts but since lower level W32 is rather stable and lower level
GDK is only used in wxUniv this won't be a big problem. Also a simple
mail to the other project might be sufficient. On the other side no API
changes are reasonably possible unless taken care of by _you_ in _both_
version. Okay, okay, you can simply go on but no sensible application
developer will use features he knows he has to scrap in a year or so.
To say it with other words, the API of wxUniv will stick with the
version of 2.5.2 unless you submit _all_ the necessary changes. Even
than I might not apply them if I consider them not important enough.
I'll stick to this policy until the pre-stage of wyoDesktop is finished
("http://wyodesktop.sourceforge.net/index.php?page=tasks.html"). So if
you aren't happy with this, help that this stage is reached as soon as possible.
IMO this is a fair deal we both can live with. The resources of
wyoDesktop is sufficient but still limited, so the goal has to be set
accordingly. I cannot take over any responsibility for anything unless
the resources are available. Please don't complain and understand that.
To be kept informed it's a good idea to subscribe to the
wyodesktop-devel mailing list.
O. Wyss
--
See a huge pile of work at "http://wyodesktop.sourceforge.net/"
|
