Re: Re: Roadmap
Armin Bauer <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.multisync.user |
|---|---|
| Message-ID | <[email protected]> |
Thorsten Roggendorf wrote: >Hi > >I have been lurking on this list for some time without posting and have >contributed nil to multisync and opensync, so you you might as well >ignore my comments. > >If you want publicity, you might want to update the multisync page and >provide a link to opensync. I suppose multisync gets much more hits than >opensync. BTW, I just looked at the multisync page and it's broken. You >ge a directory view. You can still view the page by selecting news.php >there, but this should really be fixed (sorry, if you have just been >working on it). > > no. didnt see this before. the question is: why did sf.net stop accepting index.php as the starting document? i tried changing the mode or changing the ending .html but nothing worked. Does anyone have a idea? >I have some experience with gui design. Skript is definitely the way to >go. With ruby/python you get better results faster than with lower level >languages plus you get portability if you choose the right toolkit. >The built in toolkits are ugly (they are all based on tk from tcl/tk). I >have never used WXWindows, so I'll not comment on it. >Toolkit bindings for QT or gtk have the disadvantage, that you add >requirements without gaining much if you don't aim for thorough desktop >integration. They are particularly fiddly to install on Windows. >When using ruby I'd recommend FoxTk. It is particularly easy to >implement, it looks OKish (it does not mimic other tks so it will look a >bit alien anywhere, which is the sole disadvantage). And it comes with >the ruby installer for Windows, which is big plus. >When you want to use python, you should investigate which of the more >advanced tks is most commonly used with python. I don't think python has >something like like fox - a de facto standard advanced tk included in >standard Windows installer. Thus any tk with its own Windows installer >would suffice. >You should also look at swig to get opensync language bindings for the >scripting language of your choice (http://www.swig.org/). > > > so far i have used pyrex for the bindings with good result, but i think that swig is probably the way to go so we can provide wrappers for other languages as well. About the gui: I have no personal preference as long as the toolkit looks (fairly) good and is cross platform. @thorsten You said that you have experience with gui design. Would you be willing to help a bit when we start implementing the gui (my gui programming talents are... suboptimal :) > Cheers > > Thorsten > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Multisync-users mailing list >Multisync-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >https://lists.sourceforge.net/lists/listinfo/multisync-users > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click