[maemo-developers] Proposal for streamline maemo repositories

[Devesh Kothari]

Proposal to streamline maemo repos. PLEASE give your feedback and concerns
If anyone can improve or shoot this down, then it is YOU.

Proposal:

1. To change the name of the "contrib" repository name to "extras"
   Reasons
 - "contrib" in traditional "debian" sense is used as a component
 - "contrib" in debian sense is quite different and causes confusion.
   In debian contrib is defined as
   "Contrib: Packages in this area are freely licensed by the
copyright holder but depend on other software that is not free."
 - If need be (community think a good idea and want to have it)
   we can introduce "contrib"  component in line with debian definition
   inside "extra" repository like
   deb http://repository.maemo.org/extra/   mistral free non-free
contrib

   Impact to developers/contributors/users of contrib
 - Currently configured repository in /etc/apt/sources.list would
have to
   be changed
 old : http://repository.maemo.org/contrib/ mistral free non-free
 new : http://repository.maemo.org/extra/   mistral free non-free

 - If developers have independent scripts or something depending on
"contrib"
   those needs to be changed to use "extras" instead
 - developers uploading to contrib should change their dput.cf to this:

   [garage]
   login = 
   fqdn = garage
   method = scp
   hash = md5
   allow_unsigned_uploads = 0
   incoming = /var/www/extras/incoming

2. To move python stuff and xterm kind of applications from current
   maemo2.0 "free" TO,
   free component in http://repository.maemo.org/extra/mistral/free
   Reasons
 - To streamline repository contents ("free") to include mostly
components
   on the device and their development dependendencies
 - maemo repo were designed to support SB development environment
and developer rootfs
   Having apps and language binding stuff has prompted the use of
these repo for device
   upgrade. Till we test and fix the repos to be safe for use with
device i.e test they dont
   break the device due to device upgrade (read fix our packaging
wooes), take away
   motivation from simple users to configure maemo/mistral
repository for apps.
   Developers using sardine are assumed to know what they doing :)
 - bring python and gtkmm (currently available in contrib repo) and
similar
   other language and gtk language binding components to single
consolidated
   repository "extra"
   Impact
 - same impacts as 1.


Best Regards
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] ALSA

[Devesh Kothari]

For those waiting for ALSA interface, keep an eye on

https://garage.maemo.org/plugins/scmsvn/viewcvs.php/alsa-plugin/?root=dsp-alsa

If I understood this correct, this provides the ALSA interface through
ALSA-DSP PCM plugin.

Best Regards
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] kernel code

[Devesh Kothari]

Guillem Jover wrote:

> On Sun, 2006-09-03 at 09:55:52 +0200, ext Koen Kooi wrote:
> > Kalle Vahlman schreef:
> > > The version in IT2006 is
> > >
> > >
> http://repository.maemo.org/pool/mistral/non-free/k/kernel-source-2.6.16/
> >
> > Non-free !?!?
>
> Right, could someone (Ferenc, Devesh?) please check and fix the contents
> of that repo? There's other packages which seem wrongly placed, like
> attr, bzip2, build-essential, etc.
>
This obviously needs to be fixed ! Ferenc any reason they ended up in
non-free part ?
Put it on my list of issues that need to be persued. Should plan as part
of Maemo 2.1

Devesh

> thanks,
> guillem
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Re: Repositories

[Devesh Kothari]

ext Andrey Khurri wrote:

> Hi all,
>
> I am now a bit puzzled with this repositories stuff. I've been always
> aware of that repository.maemo.org MUST NOT be used on a host
> workstation or PC. This is clear.
>
> However, how should I interpret all those warnings that this repository
> is 'ONLY' meant for using inside Scratchbox? This 'ONLY' sounds
> ambiguously to me when I look at i.e. ApplicationCatalog2006 and see
> there lots of packages meant for Nokia 770 device and available from
> repository.maemo.org. Doesn't this mean that repository.maemo.org should
> be included in /etc/apt/sources.list on Nokia 770 in order to get those
> packages installed?
>
> Or is the difference that one could fetch packages from
> repository.maemo.org and install them on Nokia 770 BUT could NOT use
> this repository to upgrade tablet (like 'apt-get upgrade')?
>
Correct. We need to look into organizing the repositories better
In most ideal and correct case, the apt-get upgrade from
repository.maemo.org should not do anything on the device so
validate perfect sync between packages on the device and packages
in the maemo repository. The problem starts from the fact that
maemo integration team takes these packages from internal package
repository for device and then
- reorganize them in a different (free/non-free) components then available
  internally
- some source packages are cleaned to meet legal requirements (these cleanup
  patches are filled as bugs in internal bugzilla, but sometimes not
applied internally
  promptly, causing a different versions of binary packages produced)
- some device binary packages are replaced with  packages delivered
specifically
  for maemo e.g binary input method, themes, bitmaps, multimedia (codecs
etc)

>From this repo, then the developer rootfs is produced, in idea case,
apt-upgrade on
this developer rootfs should be OK.

> I was also thinking that any package installable inside SB environment
> (in an armel target) can be installed on Nokia 770? If this is right can
> the same repositories be used both inside SB and on N770?
>
The problem is with upgrade :( I have put this on the agenda to be
discussed and fixed.

that doesnt help very much, but atleast hopefully clarify a few things
Devesh

> Someone please comment on this.
>
> Best regards,
>
> Andrey
>
> Devesh Kothari wrote:
> > Please note the warning on
> > http://maemo.org/downloads/download-sdk.html#Package+repository
> >
> > DONT USE THE maemo.org repository to upgrade your device. IT IS
> > CURRENTLY NOT MEANT FOR THIS AN DEVICE UPGRADE HAS NEVER BEEN TESTED.
> > UPGRADE only maemo rootstrap installed INSIDE SB development
> environment.
> >
> > Devesh
> >  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Re: rebooting constantly after upgradingpackages

[Devesh Kothari]

Please note the warning on
http://maemo.org/downloads/download-sdk.html#Package+repository

DONT USE THE maemo.org repository to upgrade your device. IT IS
CURRENTLY NOT MEANT FOR THIS AN DEVICE UPGRADE HAS NEVER BEEN TESTED.
UPGRADE only maemo rootstrap installed INSIDE SB development environment.

Devesh


ext Álvaro J. Iradier wrote:

> The audio/video playing is fixed by removing / moving a gstreamer
> library file (I can't remember the name or the location, maybe try
> searching the archives, something with "lib" and "jitter"?) that
> causes a segfault. I had to move it to another folder, then restart
> the device, and playing worked perfect again.
>
> Greets.
>
> On 8/31/06, Andrey Khurri <[EMAIL PROTECTED]> wrote:
> >
> >  Santtu Lakkala wrote:
> >  -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Álvaro J. Iradier wrote:
> >
> >
> >  Yes, basically you'll need to disable lifeguard flag, and then
> > complete the apt-get upgrade using ssh (when updating maemo-launcher
> > xterm will be killed).
> >
> >
> >
> >  This actually depends on which version of osso-xterm is used, the one
> > from maemo[1] repositories does not use maemo-launcher, so it is safe to
> > use; however, the one from maemo-hackers[2] does use, and will be
> killed.
> >
> >
> >  I was using xterm from maemo-hackers so it was killed. I followed
> the steps
> > suggested above and in some previous threads and set the flag
> > 'no-lifeguard-reset'. After that my device didn't reboot anymore. I
> > completed upgrade with 'dpkg --configure -a' and it seemed to fix
> the mess
> > with my packages. However, after that I decided to try to clear that
> flag
> > back hoping that tablet now does not need it. Clearing the flag resulted
> > again in cycle reboot of my system. I was wondering whether this
> behavior
> > is alright?
> >
> >  Also as was mentioned by Johannes  Eickhold in
> > http://maemo.org/pipermail/maemo-developers/2006-August/005349.html
> > video and audio players are not able to play files any more after this
> > failure. With regards to this problem is flashing device the only
> way to fix
> > it?
> >
>
>
> --
> (:===:)
>   Alvaro J. Iradier Muro - [EMAIL PROTECTED]
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] RE: Nokia 770 sources...

[Devesh Kothari]

ext Marius Gedminas wrote:

> On Tue, Aug 29, 2006 at 04:50:47PM +0100, Hugh Warrington wrote:
> > Andrew Flegg wrote:
> > >On 8/29/06, Devesh Kothari <[EMAIL PROTECTED]> wrote:
> > >>ext Christian Pernegger wrote:
> > >>>- setting up the developent environment was a bitch
> > >>
> > >>Could you please send me why ?
> > >>- Setting up ScratchBox ???
> > >>- Downloading, extracting maemo x.x rootstrap ?
> > >>- Setting up UI environment like Xnest/Xephyr?
> > >>- Setting up CPU_Transparency stuff ??? (need for advanced stuff) ???
> > >>
> > >>I am asking you, so we improve it.
> > >
> > >It was just a long and labourious process. The `installer' script made
> > >it trivial the second time I did it, so much so I wonder why this
> > >isn't advertised more as a recommended and supported way of
> > >installing?
>
Quite a lot of the community
- does not really want to give away control to a installer script which
ask for "root" password.
- Also as pointed out, it also does not work well for software installed
outside the control of the package management system

Now my approach has been not to make installation very specific to
debian, so that people can at the most part install scratchbox on their
distribution of choice (non-debian too), and then inside SB they after
installing the debian devkit and the maemo rootstrap, get a sandboxed
debian environment.


> >
> > I didn't find copy-pasting ten or twenty lines of clear instructions
> > into a terminal window very taxing. In fact, as cross-compilation goes,
> > setting up and working within the recommended maemo environment is a
> breeze.
>
> People have different expectations.  I have come to expect one line of
> instructions: apt-get install package-name, and that's it.
>
> I do not like to run shell script that install software.  Package
> management systems are there for a reason.
>
> It is good that I can apt-get install scratchbox into my Ubuntu laptop.
> Figuring out *which* packages to install was a bit trickier
> (scratchbox-core scratchbox-devkit-debian scratchbox-libs
> scratchbox-toolchain-cs2005q3.2-glibc-i386
> scratchbox-toolchain-cs2005q3.2-glibc-arm).
>
> Would it be possible to prepare a Debian package that
>
>   * depends on all the necessary scratchbox packages
>   * asks via debconf for a list of users that you want to add to the
> sbox group and create scratchbox user accounts
>   * automates the scratchbox target creation and configuration
> (rootstrap, .bash_profile, etc.), maybe from the same postinst
> script, maybe from a separate shell script.
>   * includes the start-maemo-xephyr shell script.
>   * ships with a shell script that sets up scratchbox when you run it
> for the first time (adduser $USERNAME sbox
>
I think atleast that makes a lot of sense and would greatly improve
atleast the developers on debian system installation and getting started
experience a lot better. I will put it on my to-do list to explore.

> ?  The main question seems to be: can I tell /scratchbox/login to run
> some command (say, a shell script that calls the necessary sequence of
> sbox-config commands)?
>
I think that sould be possible

> I think the best user experience is
>
>   one command for installation (apt-get install maemo-scratchbox)
>   one command to start Xnest (maemo-xephyr?)
>   one command to start an i386 shell (maemo-386-shell)
>   one command to start an armel shell (maemo-armel-shell)
>
> No extra configuration required.
>
I agree

> Hm... looks like a worthy project for a weekend.
>
> A VMWare virtual appliance with scratchbox preconfigured would also be
> nice, I suppose, although personally I'm not interested in it.
>
What would be really interesting is to have VMWare appliance to run the
whole maemo development enviornment native and not inside yet another
sandbox (SB)
Devesh

> Marius Gedminas
> --
> The last good thing written in C was Franz Schubert's Symphony #9.
> -- Erwin Dietrich
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] RE: Nokia 770 sources...

[Devesh Kothari]

ext Andrew Barr wrote:

> On Mon, 2006-08-28 at 18:47 -0300, Alessandro Ikeuchi wrote:
> > ...
>
> While I certainly don't agree with the angry tone used, I have to say
> Maemo and the Nokia 770 have been disappointing in terms of openness. It
> seems to me that Nokia has opened just enough to get apps ported and/or
> written for the device, which in turn sells more devices, or at least
> that appears to be the plan. Nothing has come of recurring requests for
> information about the Bluetooth hardware (e.g. for headset support), Ogg
> Vorbis support, or Gstreamer/DSP multimedia internals in general. Some
> things that are missing from the Subversion repo don't even make sense,
> e.g. there is no hardware secrets or patents associated with them (at
> least as far as I know) The media player apps come to mind here.
>
What I agree is that we need to strengthen the architecture documents
BTW getting strarted with multimedia development doc was updated
http://maemo.org/platform/docs/multimedia/getting_started.html
(section Plugin development) which describes how to enable  ogg-vorbis
 

> Maemo really isn't open in the sense that we're used to: like a
> traditional Linux distribution. It seems to be more of an SDK plus
> things that were required to be open, e.g. due to licensing terms.
>
I think one of the reason for that could also be attributed that most
general linux distributions are targetted to PC/laptop which have
relatively well defines standardized hardware architecture. What we have
tried to do with maemo is
- provide a common development environment and tools for Nokia 770 and
future devices (SB, rootstraps etc)
- provide (as a priority) to enable application development
- enable experimentation like ability to compile your own kernel, create
your own rootfs and all the benifits that could be leveraged from a
debian based component package management system

Now what we are concentrating on, beside improving the above is to
enable participation and contribution in stages to different parts of
maemo, starting with HAF/Sardine which I hope would extend. The starting
up and adoption barrier for sardine are being recognized, and we are now
trying to make it easy to adopt and use sardine, without sacrificing the
genral device usability. This would enable the patches or feature
implementations by community to be made and tested on the latest svn
codebase, so the component owners can integrate/accept/reject them.
There has been excellent work done for enabling dual boot by Frantisek Dufka
http://maemo.org/maemowiki/BootMenu

which I hope would enable the experimentation atleast in the large area
of HAF/sardine (comprising the majority of the middleware stack like
gtk+, theming, desktop, tasknavigator, control panel, application
installer etc) to happen on MMC based sardine rootfs

Devesh


> This is unfortunate, because it creates a burden on the Nokia employees
> working on this project. They are the only ones who can add many
> requested features or fix bugs, so in many cases people complain to the
> mail list because they cannot take care of things themselves. You don't
> see patch mails on the maemo-* lists. That's to say nothing of ideas
> people have had but been unable to implement--trivial stuff that would
> improve the Maemo environment but may not have been discussed on the ML.
>
> To me, the open-source economy (or whatever) that makes some projects so
> great doesn't work here because the "community" is relegated in large
> part to the role of application developer. The best you can do to
> improve some parts of Maemo is suggest it and hope someone at Nokia
> takes it up.
>
> These are just my impressions from informal observation and occasional
> participation in this endeavor. If you think I'm way off base or crazy
> or something, please feel free to tell me or ignore me.
> --
> Andrew Barr | http://www.oakcourt.dyndns.org/~andrew/
> 
>
> "Buzzword detected (core dumped)"
>   -- seen on linux-kernel@vger.kernel.org
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] RE: Nokia 770 sources...

[Devesh Kothari]

ext Christian Pernegger wrote:

> > I am just telling some truths that others should know.
>
> I'm with you insofar as
> - setting up the developent environment was a bitch
>
Could you please send me why ?
- Setting up ScratchBox ???
- Downloading, extracting maemo x.x rootstrap ?
- Setting up UI environment like Xnest/Xephyr?
- Setting up CPU_Transparency stuff ??? (need for advanced stuff) ???

I am asking you, so we improve it.

> - it still doesn't give you the same environment as a real 770 apparently
>
In general scratchbox as already pointed out provides a chrooted
environment, which is not the same as in device development. The armel
rootstrap in SB should atleast provide the same compiled binaries etc as
that on the device, so as to provide properly cross compiled binaries
for the device.

> - C++ plus custom framework doesn't exactly lend itself to RAD, maybe
> a scripting language (python, ruby, whatever) or even Java would have
> been a better choice. A lot of people, me included, don't have a clue
> about cross-compiling or embedded development.
>
I think the accepted fact is that development for different processor
non-PC devices is different.
Devesh

> C.
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Nokia 770 sources...

[Devesh Kothari]

ext Alessandro Ikeuchi wrote:

> Ok, Maemo docs sucks, the SDK sucks and the Hildon stuff looks like a
> colony of ants...
> I bought Nokia 770 because I believe OPEN SOURCE, so, Nokia is using
> it, isn´t? Where are the sources? The lack of docs could be covered by
> releasing the sources...
>
First I need to point out, I dont like the tone of this message as has
been already pointed out in responses to this thread. As for the
sources, from a legal stand point all required source is available
through the maemo repository.

http://repository.maemo.org/pool/maemo2.0rc22/free/source/

Beside that if you check the "About Product" tab in ControlPanel->Device
you will find out how you can request source code (which nokia is
legally bound to provide) CD from Nokia

> I just wanted to build my own text editor with dead keys support for
> my bluetooth keyboard, but even the Maemopad example doesn't work
> properly (try to change font color).
>
I would appreciate if you could attach a log or some more information or
file a bug in
https://maemo.org/bugzilla

Usually we do run some round of test to atleast the example codes
refered to in the tutorial.

> Unicode only works for the xterm, and worst, Notes does dead keys for
> screen keyboard, so, why is so hard to adapt Maemopad for dead keys?
> (by the way, I made a working version of Maemopad with GTK for my
> Linux x86 box that works as planned, so I am sure that's not me...)
>
I think more of your agression is directed towards maemopad and your
inability to modify and achieve your objectives. If that is the case,
then I am quite sure the community would be happy to help you out, if
you would be a bit more constructive, rather than a "shot everything
down" kind of attitude.

> "Nokia 770 is Debian based, Alessandro, should be great!"... It´s a
> piece of crap, I never used because I can´t find or port applications
> of my interest... There´s no surprise that "REAL AND USEFUL
> APPLICATIONS" never appears at maemo repository (with some exceptions)
>
Well  i think that is your perception (and in that you in your own right
maybe justified). I myself love various adventure games not available
for the device either, so I guess I would be justified in my own right
to "shoot everything down too"

> MY SUGGESTION FOR THE NEXT RELEASE OF shitOS 2007:  Forget about
> Hildon, forget desktop, give me a console based OS with Lynx, vim,
> python (python for OS 2006 appears in Maemo 2.0 repository, forget it,
> there´s no Python version for OS 2006, even the list isn´t properly
> updated) and UNICODE support, would be great if CURSES is available
> too, or better, with a good framebuffer driver. It would spare Nokia
>
Nokia 770 OS 2006 introduces the debian package management, so if thats
the way you want to go, I will certainly not come in your way. You could
have asked the community to tell you a way to achieve that. I am quite
sure, you can gain root and  open your favourite xterm and just apt-get
remove packages you dont like. You are free to do all experimentation
you like at your own risk. Please do post the findings of your results
on the mailing list, I of one would be quite interested to know the result.

There are also other tools and documentation available on maemo which
talks about customizing and building your own rootfs and kernel etc.

> budget and make the plataform usefull and with lots of space...
> Besides, with a real open source OS and simple developing tools I
> would try QTopia. The exceptions mentioned above are CONSOLE and X11
> programs, as python, smallbasic, octave, gnuplot... If you are a Hildon
>
I think there has been many flame wars about QT/GTK+, so I would not
comment anymore. Maemo and Nokia 770(OS2006) is a GTK+ based device and
application development environment. Either you accept that or not thats
your choice. By all means experiment with different toolkits and
technologies, and if they are done in constructive manner, I am quite
sure, you would still find this developer list quite willing to listen
and help.

> developer/mantainer pay attention: the best released applications are
> Console based! With no fear, Hildon sucks and it's the weakspot of
> Nokia 770...
>
There are very good reasons for us to extend and customize GTK+ which
together with desktop components and services we call hildon. We are as
a goal trying to push changes to mainstream (some will be accepted, some
wont) but you can follow the status on

http://maemo.org/maemowiki/MaemoGtk26Contributions

> Someone just confirm that I can´t get Notes sources and I'll sell my
> useless Nokia 770 and buy Samsung Q1 (try this one if you don´t have
> Nokia, believe me, the lower price of Nokia doesn't beat the ease of
> development of a Win32 x86 platform, forget the "linux, open source
> and free for all stuff", Nokia 770 is not that). And yes, I am pissed
> off... I really bought Nokia 770 for my personal business purpose,
> confident about the "debia
>
> based" OS... Hacks are goo

Re: [maemo-developers] Maemo alarms ==> retutime

[Devesh Kothari]

ext Igor Stoppa wrote:

> On Mon, 2006-07-31 at 10:34 -0400, ext Michael P. Lococo wrote:
> >  I think what Chris, me and others are really looking for is the
> alarm
> >  framework for application notification, not the mere RTC alarm.
> > >>>
> > >>> There is no alarm framework
> > >>
> > >> I would have expected such framework after the longish discussions on
> > >> the mailinglist some time ago (effectively more than half a year
> ago).
> > >
> > > Since there isn't any calendar application in the 2006 software
> edition,
> > > management didn't really prioritise a sane alarm interface.
> >
> > There is is substantial user demand, though, and there are three
> different
> > community-based or third-party calendaring applications that are all
> > hamstrung by the lack of an alarm facility.  It seems fairly clear
> at this
> > point that:
> >
> > 1) The need for an alarm framework is not a passing fancy.
> > 2) In order to be done sanely, it must be centralized... either as a
> > single community project or as a Nokia supported part of the product.
> > Applications cannot reasonably be expected to handle it without tripping
> > over each other and killing battery life with polling.
> >
> > Mike
>
> I think Devesh is the proper interface for this sort of discussion,
> since he takes care of harmonizing this sort of internal/external
> needs/demands/activities.
>
> And he's your best chance to get any statement ;-)
>
Ok, the status
- based on mailing list discussion about alarm requirements, it was
pushed as a requirement to be delivered. It is accepted and, as i
understand implemented (framework etal). What was also at design time
agreed that the alarm framework/alarmd could be installed standalone and
compatible to IT OS 2006 (so it is not tied with future product release)
- currently it is in legal check for approval to open. Once that is
done, the project would most probably move to garage
- I am hoping as soon that happens, it possibly appear in sardine


Best Regards
Devesh

> --
> Cheers,
>Igor
>
> Igor Stoppa (Nokia M - OSSO / Tampere)
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] VoIP through SIP

[Devesh Kothari]

ext Johannes Eickhold wrote:

> Am Montag, den 21.08.2006, 00:58 +0200 schrieb Jaime Ruiz Frontera:
> > > On Sat, 2006-08-19 at 18:18 +0200, [EMAIL PROTECTED] wrote:
> > >> Hello to all!
> > >
> > > Hi Jaime.
> > >
> > >> I'm wondering if is there any voip application supporting SIP in
> which
> > >> you
> > >> can choose the server you want.
> > >
> > > If you don't fear the power of the command line please feel free to
> > > check out sofsip-cli. It is a command line SIP client based on Nokia's
> > > sofia-sip SIP stack. Debian packages for the 770 and further info are
> > > available here: http://jonek.hexbox.de/?page_id=43
> > >
> > > Feedback is highly welcome.
> >
> > Hi Jonek,
> > I just tried it. I used it with voipbuster (www.voipbuster.com). I could
> > register with my username and password but when I try to make a call it
> > finishes with a segmentation fault. If you need details just tell me.
>
> Nice to see somebody taking the challange of sofsip-cli :). It is not
> very userfriendly or pretty looking but serves testing purposes very
> well as it does as an introduction to the sofia-sip library.
>
> If you need support please refer to the sofia-sip mailing list at [1].
>
http://sofia-sip.sourceforge.net/ssip-gst.html

I believe, that provides SIP VoIP capability ??? for GAIM
Best Regards
Devesh

> For further help on the 770 I definately need more info from you! At
> least enough to replicate your error or some debugging output as was
> suggested on the mailing list. You can find an unstriped version of the
> sofsip_cli binary here [2].
>
> Greets,
>   Jonek.
>
> [1] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
> [2] http://jonek.hexbox.de/uploads/2006/07/sofsip_cli
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Re: [maemo-users] Future features for Maemo Desktop (Task Navigator, Home, Status bar)?

[Devesh Kothari]

ext John B. Holmblad wrote:

> Karolina,
>
> although it does not relate specifically to the desktop, and in
> addition to recommendations that I have made previously,  I offer the
> following suggestions for improvement of the 770 for consideration by
> Nokia.
>
> * While reading this thread I discovered to my surprise that a
>   bluetooth headset is not already supported so that should
>   certainly be added to the feature set, especially given the plan
>   to support VOIP.
>
> * EVDO and HSDPA wireless support should also added as an optional
>   feature. This may require of course a new hardware release which
>   supports one of the cardbus formats on which the EVDO and HSDPA
>   cards can be obtained. By way of example, here is the url to a
>   www page at the Linksys www site that shows the new form factor,
>   in this case for a gig-e card,  that goes under the marketing
>   name of "*ExpressCard Adapter"*
>
> 
> http://www.linksys.com/servlet/Satellite?c=L_Product_C2&childpagename=US%2FLayout&cid=1147850020524&pagename=Linksys%2FCommon%2FVisitorWrapper
>
>
>
>
> Best Regards,
>
>  
>
> John Holmblad
>
>  
>
> Televerage International
>
>
>
>
> Karoliina Salminen wrote:
>
>>Hello everybody,
>>
>>I am now collecting some ideas for future development of the UI framework.
>>
>>If you have any features that you'd like to see in the future in the
>>components mentioned on the topic (Task Navigator, Home, Status bar),
>>please send your feature requests/ideas to me: karoliina.t.salminen at
>>nokia.com or reply them on this list for further discussion. So now is
>>your chance to affect to which direction you'd like us to develop the
>>desktop UI framework. Also if you have any ideas for plug-in APIs,
>>bindings etc. anything you'd wish  to see there in the future, please let
>>me know. The sooner the better, so if you have something in your mind now,
>>please let me know now (meaning Today if possible).
>>
>>No matter if you are developer or end user or both, I am waiting for your
>>ideas and comments with a great interest - "What do you want?". Thanks in
>>advance!
>>
>>Best Wishes,
>>Karoliina Salminen
>>  
>>
>
>
>___
>maemo-users mailing list
>maemo-users@maemo.org
>https://maemo.org/mailman/listinfo/maemo-users
>  
>
karoliina,
Is it possible to collect these improvement ideas in a wiki with maybe a
table and list of feature, so we dont forget this discussion thread ???

Best Regards
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] initfs hacking questions

[Devesh Kothari]

ext Frantisek Dufka wrote:

> Hello,
>
> recently  I tried to modify initfs to allow dual booting and got some
> questions:
>
> Is there a way to get code of pressed HW key in /linuxrc script? There
> is command that waits  for keypress. There is also something is sysfs
> for detecting battery door, shell, headphone jack state but nothing
> simple for keys. Anything I missed or do I need to compile my own
> executable?
>
> Which scratchbox uclibc toolchain should I use? There are two ones here
> http://scratchbox.org/download/files/sbox-releases/0.9.8/tarball/
> sf (softfloats) and non-sf.
>
> What exactly is testserver? initfs is full in IT2006 so I need to
> delete something. I deleted testserver and its shared libraries and
> device seems to boot. Is this needed for device operation or it is
> really for factory testing or something like that so it never gets
> executed automatically on boot. How do I run those test anyway?
>
> Can I distribute hacked initfs? If not, is binary patch OK?
>
I am not a legal expert, but please read the EULA (End user license
agreement). I would be pretty surprise if they would let you do so :)

Devesh

> Which functionality I loose when dsme is not executed from /linuxrc
> (battery charging?)
>
> Is is a good idea to use cal-tool frequently (i.e on each boot) to set
> various flags (root device,..)? This get stored to flash, how it is
> with wear leveling of config partition?
>
> Thanks for any answers.
>
> Frantisek
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] IT2006 image public release will includelibsdl_ttf?

[Devesh Kothari]

ext Frantisek Dufka wrote:

> Devesh Kothari wrote:
>
>> ext Uwe Koch wrote:
>>
>>> I saw many sdl libs already in the SDK but not in the
>>> Beta release on the 770.
>>>
>>> Does anybody know if they will be delivered in the public release or
>>> shall I deliver them again like in the IT2005 release?
>>>
>> check always
>> http://repository.maemo.org/unstable/2.0rc16/package_reference.html
>>
>
> Well there is no column for product image, just the rootfs which is
> something different (developer rootfs?). There is also python listed
> as being in the rootfs and it is not by default in the beta image.
>
It used to be there
http://repository.maemo.org/unstable/1.1rc5/package_reference.html

So thats a bug .. but I would presume, since the OS2006 device image is
still BETA that column is missing


> But anyway, it is probably not so important what is in the image
> because of the network repositories. If something is not by default I
> suppose the dependencies pull it from the repository (if configured
> properly) so there is no need to deliver own libs anymore.
>

> Question is whether there will be some repository preconfigured in
> final production image so it works automatically and whether it will
> be the same as maemo 2.0 used from arm scratchbox target.
>

> Even today when I have mistral-beta configured on the beta image I see
>
> /home/user # apt-get upgrade
> Reading package lists... Done
> Building dependency tree... Done
> The following packages will be upgraded:
>   certs libcst maemo-launcher osso-sounds-ui
> 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1428kB of archives.
> After unpacking 868kB of additional disk space will be used.
> Do you want to continue [Y/n]?
>
> Is the production image compatible with maemo 2.0 so can I upgrade
> safely now? I.e is the developer rootfs simply a different selection
> of packages but using same repository as final image?
>
There are some differences. Some of the packages are SDK specific and
they then subsequently provide for the packages as on the device image.
example  are theme packages etc. SO the packages to look out would be
the one with sdk in their name and what they provide.

Devesh

> Frantisek
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] IT2006 image public release will includelibsdl_ttf?

[Devesh Kothari]

ext Uwe Koch wrote:

> Hi,
>
> i just compiled sdl_ttf library and installed it on the 770 successfully.
> But when I tried to install it under scratchbox to compile my
> main program it failed because the lib already exists!
>
> I saw many sdl libs already in the SDK but not in the
> Beta release on the 770.
>
> Does anybody know if they will be delivered in the public release or
> shall I deliver them again like in the IT2005 release?
>
check always
http://repository.maemo.org/unstable/2.0rc16/package_reference.html

Devesh

> Regards
> Uwe Koch, Hannover, Germany
>
> __  _-_
> \|).---'---`---.
>  ||\._./
>  || / ,'   `---'
>   ___||_,--'  -._
>  /___  ||(-
>  `---._-'
>
> __
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden
> Schutz gegen Massenmails.
> http://mail.yahoo.com
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Contributions feed

[Devesh Kothari]

ext Florian Boor wrote:

> Hi all,
>
> is there a plan for an official feed for binary packages from external
> contributors? That would make software installations much easier for
> an average
>
Yes. Work in progress but close. Ferenc could possibly provide more details
Devesh

> user.
>
> Greetings
>
> Florian
>
> PS: The 2006 beta rocks!
>
> --
> The dream of yesterday  Florian Boor
> is the hope of todayTel: 0271-771091-14
> and the reality of tomorrow.Fax: 0271-771091-19
> [Robert Hutchings Goddard, 1904][EMAIL PROTECTED]
>
> 6C 44 30 4C 43 20 6B 61  16 07 0F AA E6 97 70 A8
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Implementing UPnP library (mpuf lib fromProtoSys)

[Devesh Kothari]

ext Zoran Duvnjak wrote:

> Hi folks,
>
> this is my first post at this mailing list, but maybe there are some
> guys with the same prob.

Maybe I can help, as I wrote most of that stack in my previous life

> I am working currently on a remote control for a music server and I am
> trying to use the mpuf lib (UPnP lib from ProtoSys) to search for the
> music servers in the network.
> Pretty the same like the *UPnP Device Monitor *plugin on the maemo site.

First try some diagnostics
- does the upnp device monitor plugin works for you ?
- are you implementing a GTK based Control point ? if yes, then you
hopefully are using the glib version of mpuf libraries.
- then I would want to sniff the local TCP/UDP traffic when I initiate
the search

> Until now I have implemented the libraries and the necessary handlers
> and control point for this task.
> It compiles without errors and the control point is successfully
> initialized, but when I start to search for UPnP devices nothing happens.
> Maybe I have forgotten to do something?

hopefully you making call to MPUF_Run :)
Devesh

> I would appreciate if someone has experiences with this and could give
> me a hint or sent me a link to helpful sites.
> So long.
>
> Best regards,
> _
>
> Zoran Duvnjak
> olive Media Products Inc.
> 555 Howard Street I San Francisco, CA 94105
> T +1  415.908.3870
> F +1  415.908.3932
> E  [EMAIL PROTECTED] 
> W http://www.olive.us 
>
>
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] maemo (1.1) connectivity : API

[Devesh Kothari]

ext Ade Bamigboye wrote:

> Hi
>  
> Can anyone point us in the direction of examples that show how the
> Connectivity API is meant to used.
>  
> Looking at the doc it seems like all that is required is "osso-ic.h"
> as an include file but we are unable to find the corresponding shared
> library.

http://repository.maemo.org/pool/maemo1.1/free/o/osso-ic-oss/
http://maemo.org/platform/docs/howtos/howto_connectivity_guide.html

Devesh

>  
> Is this actually implemented yet ? if not what option are there to
> create an application that talks to the internet ?
>  
>  
> Thanks in advance
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Re: scratchbox installation

[Devesh Kothari]

ext Santeri Lindgren wrote:

> Devesh Kothari wrote:
>
>> ext August Joki wrote:
>>
>>> In the To-Do List of the Minstral Roadmap
>>>
>>> http://maemo.org/platform/docs/roadmap.html
>>> (bottom of the page)
>>>
>> This is obviously a mistake. It should be something like
>> Future to-do :) or something though it does look like a Mistral Maemo
>> 2.0 To-Do :)
>>
>> thanks for pointing that out, that need to be fixed
>> Devesh
>>
>
> Oh buggers :(
>
> And here i was hoping that we would move using it in this update
> allready.
>
> Well, if not, can you give us an estimate on when this is going to be
> ? This year? Next year? Or maybe in the next decade ?
>
cant really say :( the reason to stick with 0.9.8.5 has been that
- we know it works for all what we need it for :).
- Our internal product development teams are using, so we want to stick
as close as possible to that environment (easies bug verification etc)

There has been on the mailing list people who have talked about SB 1.0
and there are known cases of maemo rootstraps to work on SB 1.0 but
still we havnt officially moved to 1.0 because of above reasons.

No body really has put in time to evaluate why to move to SB 1.0
(especially since the 0.9.8.5 version works well for our needs, so there
is no great significant itch).

I am not so upto date on all developments, but what would be the major
reason to move to SB 1.0 and what are the impacts if any ?

Devesh

> Santeri
>
>>
>>> -August
>>>
>>> On 5/18/06, Devesh Kothari <[EMAIL PROTECTED]> wrote:
>>>
>>>> ext Santeri Lindgren wrote:
>>>>
>>>>> Ross Burton wrote:
>>>>>
>>>>>> On Wed, 2006-05-17 at 12:42 +0300, Jussi Kukkonen wrote:
>>>>>>
>>>>>>> Eero Tamminen wrote:
>>>>>>> I wonder if there are any real problems with maemo and scratchbox
>>>>>>> 1.0.x?
>>>>>>> I haven't seen any so far... If no-one comes up with horror stories
>>>>>>> about using 1.0 for maemo development, maybe the recommendation
>>>>>>> could be
>>>>>>> upgraded -- it would make installation easier (damping the culture
>>>>>>> shock
>>>>>>> for new developers) and give everyone access to the new features*.
>>>>>>
>>>>>>
>>>>>> Oh the pain.  The true and unbelievable pain.  Trust me, keep with
>>>>>
>>>> 0.9.8
>>>>
>>>>>> for now, and wait for Maemo to switch to Scratchbox 1.0.
>>>>>>
>>>>>> Ross
>>>>>
>>>>>
>>>>> If you have checked the OS 2006 news, it says that with OS 2006 SDK
>>>>> Scratchbox 1.0 will be the thing to use.
>>>>>
>>>> Where did you hear that :) . Maemo 2.0 is not moving to SB 1.0, AFAIK
>>>>
>>>> Devesh
>>>>
>>>>> Greets, Santeri
>>>>>
>>>>> ___
>>>>> maemo-developers mailing list
>>>>> maemo-developers@maemo.org
>>>>> https://maemo.org/mailman/listinfo/maemo-developers
>>>>
>>>>
>>>> ___
>>>> maemo-developers mailing list
>>>> maemo-developers@maemo.org
>>>> https://maemo.org/mailman/listinfo/maemo-developers
>>>>
>>
>
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Re: scratchbox installation

[Devesh Kothari]

ext August Joki wrote:

> In the To-Do List of the Minstral Roadmap
>
> http://maemo.org/platform/docs/roadmap.html
> (bottom of the page)
>
This is obviously a mistake. It should be something like
Future to-do :) or something though it does look like a Mistral Maemo
2.0 To-Do :)

thanks for pointing that out, that need to be fixed
Devesh


> -August
>
> On 5/18/06, Devesh Kothari <[EMAIL PROTECTED]> wrote:
>
>> ext Santeri Lindgren wrote:
>>
>> > Ross Burton wrote:
>> >
>> >> On Wed, 2006-05-17 at 12:42 +0300, Jussi Kukkonen wrote:
>> >>
>> >>> Eero Tamminen wrote:
>> >>> I wonder if there are any real problems with maemo and scratchbox
>> >>> 1.0.x?
>> >>> I haven't seen any so far... If no-one comes up with horror stories
>> >>> about using 1.0 for maemo development, maybe the recommendation
>> >>> could be
>> >>> upgraded -- it would make installation easier (damping the culture
>> >>> shock
>> >>> for new developers) and give everyone access to the new features*.
>> >>
>> >>
>> >> Oh the pain.  The true and unbelievable pain.  Trust me, keep with
>> 0.9.8
>> >> for now, and wait for Maemo to switch to Scratchbox 1.0.
>> >>
>> >> Ross
>> >
>> >
>> > If you have checked the OS 2006 news, it says that with OS 2006 SDK
>> > Scratchbox 1.0 will be the thing to use.
>> >
>> Where did you hear that :) . Maemo 2.0 is not moving to SB 1.0, AFAIK
>>
>> Devesh
>>
>> > Greets, Santeri
>> >
>> > ___
>> > maemo-developers mailing list
>> > maemo-developers@maemo.org
>> > https://maemo.org/mailman/listinfo/maemo-developers
>>
>>
>> ___
>> maemo-developers mailing list
>> maemo-developers@maemo.org
>> https://maemo.org/mailman/listinfo/maemo-developers
>>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Re: scratchbox installation

[Devesh Kothari]

ext Santeri Lindgren wrote:

> Ross Burton wrote:
>
>> On Wed, 2006-05-17 at 12:42 +0300, Jussi Kukkonen wrote:
>>
>>> Eero Tamminen wrote:
>>> I wonder if there are any real problems with maemo and scratchbox
>>> 1.0.x?
>>> I haven't seen any so far... If no-one comes up with horror stories
>>> about using 1.0 for maemo development, maybe the recommendation
>>> could be
>>> upgraded -- it would make installation easier (damping the culture
>>> shock
>>> for new developers) and give everyone access to the new features*.
>>
>>
>> Oh the pain.  The true and unbelievable pain.  Trust me, keep with 0.9.8
>> for now, and wait for Maemo to switch to Scratchbox 1.0.
>>
>> Ross
>
>
> If you have checked the OS 2006 news, it says that with OS 2006 SDK
> Scratchbox 1.0 will be the thing to use.
>
Where did you hear that :) . Maemo 2.0 is not moving to SB 1.0, AFAIK

Devesh

> Greets, Santeri
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] GStreamer plugin development

[Devesh Kothari]

ext Corentin Baron wrote:

> Devesh Kothari wrote:
>
> >ext Corentin Baron wrote:
> >
> > 
> >
> >>Devesh Kothari wrote:
> >>
> >>   
> >>
> >>>ext Corentin Baron wrote:
> >>>
> >>>
> >>>
> >>> 
> >>>
> >>>>Hello there,
> >>>>
> >>>>I've made a gstreamer plugin for internal use here at INRIA. The
> plugin
> >>>>works well, and I have everything I need to build it on the Nokia (our
> >>>>library already works on the device), but I can't manage to build the
> >>>>plugin development package to build on the ARM target.
> >>>>
> >>>> 
> >>>>
> >>>>   
> >>>>
> >>>Any debug/trace or log info ?? Are your using GStreamer 0.8 or 0.10?
> >>>Maemo 1.1 has if I remember correctly 0.8
> >>>
> >>>Devesh
> >>>
> >>> 
> >>>
> >>Actualy my problem is first to have the gst-plugins package to compile
> >>on the ARM target inorder to have the gst-lib stuff installed. But the
> >>package fails to compile the tcp plugin because it couldn't find the
> >>dataprotocol.h header file, and I couldn't disable the tcp plugin at
> >>configure.
> >>
> >>   
> >>
> >Please describe your environment, e.g SB version, rootstrap version
> >What GStreamer source ? version? where you obtained i.e from maemo
> >repository or mainstream? config.log ? etc
> >
> >else its very difficult to figure out the reason
> >Devesh
> > 
> >
> I use Scratchbox 0.9.8.5 with Maemo 1.1 and GStreamer 0.8.10 (the one
> preinstalled with maemo), everything running on a linux fedora core 4.
>
> The error I get at compilation time with the gst-plugin package is this:
>
> > distcc[21914] ERROR: compile (null) on localhost failed
> > In file included from gsttcpclientsrc.h:36,
> >  from gsttcpplugin.c:26:
> > gsttcp.h:28:43: gst/dataprotocol/dataprotocol.h: No such file or
> directory
>
i quickly did
=
apt-get source gstreamer0.8-osso [thats what i could find in Maemo 1.1]

./configure
./make

it build ok on arm target.
==

i can see this file here
libs/gst/dataprotocol/dataprotocol.h

so if you in hurry :) then I will open the Makefile and add
-I../libs/gst/dataprotocol/ and try again

but I suspect some problem in your build environment

HTH
Devesh


> > distcc[21913] ERROR: compile gsttcpplugin.c on localhost failed
> > make[4]: *** [libgsttcp_la-gsttcpplugin.lo] Error 1
> > make[4]: Leaving directory
> `/home/cobaron/gst/gst-plugins-0.8.11/gst/tcp'
> > make[3]: *** [all] Error 2
> > make[3]: Leaving directory
> `/home/cobaron/gst/gst-plugins-0.8.11/gst/tcp'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/home/cobaron/gst/gst-plugins-0.8.11/gst'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/cobaron/gst/gst-plugins-0.8.11'
> > make: *** [all] Error 2
>
> It seems that the gstreamer installation isn't complete. If I could get
> the gst-plugin configure/make to skip or forget the tcp plugin, which I
> don't need, I think I could also have my own plugin compiling.
> Corentin
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] GStreamer plugin development

[Devesh Kothari]

ext Corentin Baron wrote:

> Devesh Kothari wrote:
>
> >ext Corentin Baron wrote:
> >
> > 
> >
> >>Hello there,
> >>
> >>I've made a gstreamer plugin for internal use here at INRIA. The plugin
> >>works well, and I have everything I need to build it on the Nokia (our
> >>library already works on the device), but I can't manage to build the
> >>plugin development package to build on the ARM target.
> >>
> >>   
> >>
> >Any debug/trace or log info ?? Are your using GStreamer 0.8 or 0.10?
> >Maemo 1.1 has if I remember correctly 0.8
> >
> >Devesh
> >
> Actualy my problem is first to have the gst-plugins package to compile
> on the ARM target inorder to have the gst-lib stuff installed. But the
> package fails to compile the tcp plugin because it couldn't find the
> dataprotocol.h header file, and I couldn't disable the tcp plugin at
> configure.
>
Please describe your environment, e.g SB version, rootstrap version
What GStreamer source ? version? where you obtained i.e from maemo
repository or mainstream? config.log ? etc

else its very difficult to figure out the reason
Devesh
BTW: please post to maemo-devel list, so others can possibly help you
better too ;)

> Thanks for your interest,
> Corentin.
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html

[Devesh Kothari]

ext Mikhail Sobolev wrote:

> On Tue, May 16, 2006 at 09:51:44AM +0100, Peter Robinson wrote:
> > Or moving it to a page for Applications IT 2005 and add a new one for IT
> > 2006.
> Like this one:
>
>   http://maemo.org/maemowiki/ApplicationCatalog2006
>
Some thinking here might help :), there have been some proposals
about how this application catalogue can be reorganized and managed

I for one am looking for a system
1. which is as easy as wiki to add
2. some policy what is acceptable and not acceptable [remember the
thread we had about
when one of the entry was removed]
3. possiblity to sort/search applications (already thinking about
device/maemo/IT SW edition compatible/WIP/testing/stable i.e this
application is known to work with Maemo 2.0)
4. some kind of user ranking system (user feedback possibility)
5. some possibility to have top 5 new submitted applications
6. some possibility to have top 5 popular applications

More ideas welcomed, lets solve this for a better solution (i dont know
if wiki will continue to solve our needs)

Devesh


> :)
>
> /me ducks and runs...
>
> --
> Misha
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html

[Devesh Kothari]

ext Frantisek Dufka wrote:

> Devesh Kothari wrote:
> > Another reason, is we dont just want to push the Maemo 2.0 till we
> get the
> > public upgrade IT 2006. Since we know Maemo 2.0 would be binary
> > incompatible,
> > the applications cross compiled on the development environment would not
> > run
> > on the current IT 2005 edition (on device) out there, so developers cant
> > really
> > test it on the device.
>
> Can't we have at least developer rootfs for Maemo 2.0? But with working
> multimedia if posible. Opera etc. isn't needed for testing.
>
Thats what is the internal goal to get Maemo 2.0 pre release together with a
developer rootfs, with a functionality similar to Maemo 1.1 but upgraded
components,
new toolchain etc BUT to tell you the truth, its not looking very good,
but will post
more updates later this week

Devesh

> Frantisek
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html

[Devesh Kothari]

ext Koen Kooi wrote:

> Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html
>

> Devesh Kothari schreef:
> > ext Koen Kooi wrote:
>
> >> [maemo-developers] http://press.nokia.com:80/PR/200605/1051308_5.html
> >>
>
> >> Hi,
> >>
> >> In case anyone missed it:
> >> http://press.nokia.com:80/PR/200605/1051308_5.html
> >>
> >>
> >> The biggest error in the statement:
> >>
> >> "It is downloadable free of charge from the Internet
> www.nokia.com/770."
> >>
> > It will be :) This is the 2006 IT SW Edition launch (which means we are
> > close to public release). Currently we do not yet have the exact final
> > public release date. We also intend to coincide the release of Maemo 2.0
> > release candidate  with the public  release. Trust me team is working
> > real hard :)
>
> So we won't get the SDK before the release, but at the same time? Given
> the huge incompatibilities (app-installer, EABI) I would have thought
> nokia would release the sdk a bit earlier to give the app developers a
> chance to get their software out on time.
>
Unfortunately so :( , we are trying hard but due to so many major changes
we just dont want to push out something which is either poor quality or
half cooked. IF we still are able to beat the IT 2006 to public launch
(assuming
we get things stabilized enough), we will push it out the door :)

Another reason, is we dont just want to push the Maemo 2.0 till we get the
public upgrade IT 2006. Since we know Maemo 2.0 would be binary
incompatible,
the applications cross compiled on the development environment would not
run
on the current IT 2005 edition (on device) out there, so developers cant
really
test it on the device.

What do you guys think? Should we try to push out the SB development
environment early, even if the developers can test apps on real device?

Devesh

> regards,
>
> Koen
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers]http://press.nokia.com:80/PR/200605/1051308_5.html

[Devesh Kothari]

ext Andrew Flegg wrote:

> On 5/16/06, Koen Kooi <[EMAIL PROTECTED]> wrote:
> > Andrew Flegg schreef:
> >
> > > Otherwise people'll get upset very quickly when they upgrade and their
> > > favourite app doesn't work!
> >
> > I suggest removing the application catalog wiki page(s) when IT2006 gets
> > released and fill them with apps that are known to work on IT2006.
>
> Interesting idea: the opportunity could also be taken to better structure
> them. The only slight niggle is that with zero third party software, how
> many end-users will NOT upgrade immediately, and still want the old app
> catalogues?
>
I am of the opinion that everyone MUST be advised to upgrade
Since
- it is a free upgrade
- Maintaining Maemo 1.1 and 2.0 which are incompatible is a big
  problem (proposal is move Maemo 1.1 to archive status)
- It just causes confusion if  Maemo 1.1  and 2.0 applications  start  to
  coexist especially to the end user (Maemo 2.0 Application installer
  would refuse to install anyway)

So I am of the opinion as Koen, to deprecate the Application Catalogue
page and start with a clean slate, and as suggested take the opportunity
to reorganize the new catalogue better.

Remember now the concept of
- click on download link in application catalogue page, browser opens AI, AI
  installer installs WOULD NOT WORK since we moving to full package
management and
  repository structure (Unless off course packages are as self
constained as they
  with Maemo 1.1, but that we all agree is not real package management :).


So we need to come up with the concept of community contrib repository
where the
3rd party applications could be uploaded


Devesh


> Cheers,
>
> Andrew
>
> --
> Andrew Flegg -- mailto:[EMAIL PROTECTED]  |  http://www.bleb.org/
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] http://press.nokia.com:80/PR/200605/1051308_5.html

[Devesh Kothari]

ext Koen Kooi wrote:

> [maemo-developers] http://press.nokia.com:80/PR/200605/1051308_5.html
>

> Hi,
>
> In case anyone missed it:
> http://press.nokia.com:80/PR/200605/1051308_5.html
>
>
> The biggest error in the statement:
>
> "It is downloadable free of charge from the Internet www.nokia.com/770."
>
It will be :) This is the 2006 IT SW Edition launch (which means we are
close to public release). Currently we do not yet have the exact final
public release date. We also intend to coincide the release of Maemo 2.0
release candidate  with the public  release. Trust me team is working
real hard :)

Cheers
Devesh



> nokia.com only has IT2005 downloads :(
>
>
> regards,
>
> Koen

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] GStreamer plugin development

[Devesh Kothari]

ext Corentin Baron wrote:

> Hello there,
>
> I've made a gstreamer plugin for internal use here at INRIA. The plugin
> works well, and I have everything I need to build it on the Nokia (our
> library already works on the device), but I can't manage to build the
> plugin development package to build on the ARM target.
>
Any debug/trace or log info ?? Are your using GStreamer 0.8 or 0.10?
Maemo 1.1 has if I remember correctly 0.8

Devesh

> Does anyone know how I could handle this?
>
> Thanks,
> Corentin BARON.
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] GTK+/glib versions

[Devesh Kothari]

ext Murray Cumming wrote:

> What GTK+ and glib versions does Maemo plan to use for Maemo  2.0?
>
> In Maemo 1.1, I think it's GTK+ 2.6 and glib 2.6.
>
> As long as the cairo problems are not resolved (though they probably can
> be), I'd expect Maemo 2.0 to use GTK+ 2.6 and glib 2.10.
>
http://maemo.org/platform/docs/roadmap.html

gtk - based on 2.6.10

Devesh

> This is the kind of information that could be mentioned here:
> http://maemo.org/maemowiki/MaemoModules/1.1
> and in a version of that page for 2.0.
>
> --
> Murray Cumming
> [EMAIL PROTECTED]
> www.murrayc.com
> www.openismus.com
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] hildon-lgpl is now gone

[Devesh Kothari]

ext Luc Pionchon wrote:

> Dear friends,
>
> last night hildon-lgpl passed away :(
>
> After long discussions, we created hildon-gpl3
> (No, joking.)
>
>
> The historical hildon-lgpl is now merged into hildon-libs.
>
> Expect more changes into hildon-libs in the coming days.
>
Luc,
It would be nice to have a wiki page which provides a kind of porting
instructions due to these changes, e.g
- change in automake scripts etc due to change in package names
- changes to include files

Also the impact on language bindings like C++/hildon bindings, python
bindings etc
BTW GPL3??? isnt that still in draft proposal stage?

Devesh

> For the ones who like to play with the latest source, stay synchronized!
>
> luc
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Re: Installation on Nokia 770

[Devesh Kothari]

ext Fabien Herrent wrote:

>Hello,
>
> 
>
>I call you because of a problem of installation on the Nokia770.
>
>I'm trying to install a .deb file and the machine displays this error message  
>"integrated component".
>
>Do you know what it means ?
>
>  
>
Fabien,
the developer list is a better place of these kind of req. Your query is
already answered on the developer mailing list, so I suggest you search
the mailing list for this

Devesh

> 
>
>Meilleures salutations mit freundlichen Grüssen
>Best regards 
>
>Fabien HERRENT 
>Technicien Informatique
>  
>Bureau / Office : +33 3 87 84 75 00 
>Fax : +33 3 87 84 75 13 
>
>[EMAIL PROTECTED]  
>  http://www.integrasys.fr/
>
>IntegraSys '' Choisissez aujourd'hui le partenaire qui maîtrise les 
>technologies de demain '' 
>ZWF SA - Pôle Technologique Sud - Rue Avogadro - BP 40092 - F-57602 FORBACH 
>
> 
>
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] HttpWebRequest in C#/Mono on N770 : The request timed out

[Devesh Kothari]

ext marc.pub wrote:

> Hello,
>
> I try to access Internet in a C# / mono program with the
> HttpWebRequest class on my Nokia 770. See my program WebFetch below.
>
> When I execute the program it wait one minute at the
> HttpWebRequest.GetResponse(); method and exit with a time out. See my
> log below.
>
> With the use of TcpDump I found that there is no exchange of data.
>
> The program is not asking to initiate a new wifi connection
>
> The behaviour is the same if the connection is active or not.
>
> I can access the same url with the opera navigator in the same time.
>
> I use the mono environment that I found at
> http://www.mono-project.com/Mono:ARM. I believe it is the 1.1.9 mono
> release.
>
> I compiled the program (.exe) on Linux Ubuntu I386 with the 1.1.9 mono
> Release.
>
> Is someone succeeding with httpConnection and mono for the N770?
>
> Maybe I should 'activate' the connection specifically for mono before
> using HttpWebRequest class? But how to do?
>
Use the LD_PRELOAD

export LD_PRELOAD=/usr/lib/libosso-ic-preload.so;

in shell script, before launching your app.
I dont know how that would work out in mono scenario, I am assuming that mono 
runtime or whatever would finally 
try to make socket calls 


give it a shot
cheers
Devesh

> Any idea?
>
> Regards,
>
> Marc Bordessoule.
>
>  Exec log 
>
> ~/mono/mono-nokia $ ./mono WebFetch.exe
>
> WebRequest.Create...
>
> Execute the request...
>
> Unhandled Exception: System.Net.WebException: The request timed out
>
> in <0x001b4> System.Net.HttpWebRequest:EndGetResponse (IAsyncResult
> asyncResult)
>
> in <0x0007b> System.Net.HttpWebRequest:GetResponse ()
>
> in <0x0017f> WebFetch:Main (System.String[] args)
>
> ~/mono/mono-nokia $
>
> -- WebFetch.cs 
>
> …
>
> class WebFetch
>
> {
>
> static void Main(string[] args)
>
> {
>
> StringBuilder sb = new StringBuilder();
>
> byte[] buf = new byte[8192];
>
> Console.WriteLine ("\nWebRequest.Create...");
>
> HttpWebRequest request = (HttpWebRequest)
> WebRequest.Create("http://www.monbureau.com";);
>
> Console.WriteLine ("\nExecute the request...");
>
> HttpWebResponse response = (HttpWebResponse) request.GetResponse();
>
> Console.WriteLine ("\nRead data...");
>
> Stream resStream = response.GetResponseStream();
>
> string tempString = null;
>
> int count = 0;
>
> do
>
> {
>
> count = resStream.Read(buf, 0, buf.Length);
>
> if (count != 0)
>
> {
>
> tempString = Encoding.ASCII.GetString(buf, 0, count);
>
> sb.Append(tempString);
>
> }
>
> }
>
> while (count > 0);
>
> Console.WriteLine(sb.ToString());
>
> Console.WriteLine ("\nEnd.");
>
> }
>
> }
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] modifying root filesystem

[Devesh Kothari]

ext Lorn Potter wrote:

>I tried the instructions and scripts for modifying the root filesystem,
>http://maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html
>
>It seems the rootfs.packages and sources.list are out of date, or there are a 
>few packages missing (hildon-status-bar-display).
>
>The make_rootimage.sh script seems a bit unfinished, as it's help lists 
>--outprefix and --jffs2 which do not work.
>(looking at the script, it seems there are a few missplaced 'x' characters, 
>and variable not all caps)
>
>I manually tar.gz the resulting root filesystem (the web page doesn't mention 
>the need to do this part), and ran the tar2jffs2.sh, script, flashed the 
>device, but the device keeps rebooting..
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
make sure you dont miss this step below

The reference root filesystem includes some binary modules that can be
downloaded separately. These packages are not necessary, you may create
a root filesystem without them, but some functionality will be missing.
To download these packages, please follow this link
.

http://maemo.org/downloads/d2.php

If you have successfuly downloaded those packages, then create a
workarounds/ directory under your rootfs working directory and copy the
binary packages there.


Devesh


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: DSP vs CPU for multimedia,Re: [maemo-developers] Audio enabled dev-platform?

[Devesh Kothari]

ext Frantisek Dufka wrote:

>BTW, did you think about using main CPU for decoding multimedia too? I 
>was a bit shocked when playing the Ice Age trailer and saw in load 
>plugin that main CPU is completely idle and both video and audio is 
>decoded by DSP. I have no benchmarks or practical experience so far but 
>from the documentation about C55x and ARM926TEJ it looks like the main 
>cpu with edsp instructions could do similar work in similar speed as DSP 
>does. If multimedia jobs could be distributed across both cpus (like dsp 
>doing audio and color conversion into framebuffer, mpu decoding video) 
>we could see higher resolution or frame rates.
>
>  
>
I am not an expert in this area, but if I understand correctly the
way it is architected is that n770 has gstreamer dsp sinks for different
formats like mp3 etc which work using DSP gateway with their
counterpart on the DSP. DSP controls all the audio rendering hardware.
But I think it should still be possible to construct a gstreamer pipeline
which would for example do ogg decoding on arm side and feed to the
DSP PCM sink or something. But  I am just reasonably guessing :)

>Is the gstreamer framework able to support more implementations for same 
>codec (DSP vs CPU) and chose one based on priority? Will the stuff you 
>are talking about releasing in future be enough for hacking in this area?
>
>  
>
You can hack I guess even today, but you would have to try it on the
real product. You cant try it on the developer rootfs, which gives you
a lot many other tools too, which ease development and hacking.

check
http://repository.maemo.org/pool/maemo1.1rc7/free/source/g/gstreamer0.8-osso/

Devesh

>Frantisek
>
>Devesh Kothari wrote:
>
>  
>
>>improving multimedia support is one of priority area. I hope we are able
>>to push that out. Just to let you know we are working on it :) AFAIK it
>>is mostly issues related to redistribution of the DSP side stuff (even
>>in binary) which would enable the layer below DSPGateway.
>>
>>Devesh
>>
>>
>>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Audio enabled dev-platform?

[Devesh Kothari]

ext Christian Fredrik Kalager Schaller wrote:

>Hi would it be possible for Nokia to release a version of
>Maemo_Dev_Platform_rootfs_v1.1rc5.jffs2 or newer which contains the
>audio stuff?
>
>Not having any way to output audio with the current dev image makes it
>useless for me, and having to install the normal image and get root,
>xterm and ssh working on it is a tad painfull for something which I do
>relativly frequent.
>
>Christian
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
improving multimedia support is one of priority area. I hope we are able
to push that out. Just to let you know we are working on it :) AFAIK it
is mostly issues related to redistribution of the DSP side stuff (even
in binary) which would enable the layer below DSPGateway.

Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Gazpacho/hildon - added extra properties

[Devesh Kothari]

ext Florian Boor wrote:

>Hi,
>
>Luc Pionchon wrote:
>  
>
>>I committed a few more properties for hildon widgets.
>>This should complete Gazpacho support, and help for bindings. 
>>
>>
>
>this sounds promising. It might be very useful to include Gazpacho in the SDK.
>If this is easy to achieve maybe in the next release? :-)
>
>Greetings
>
>Florian
>
>  
>
yes Gazpacho would soon be there. It has to wait because (as far as i
understand), the widget changes done to support gazpacho would make into
the product only in next IT 2006 SW edition release. So hopefully in
Maemo 1.3 release [no dates planned yet :)]

Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Building Maemo from scratch

[Devesh Kothari]

ext Florian Boor wrote:

>Helo,
>
>Russell Geldmacher wrote:
>
>  
>
>>So, as I'd assume, there are package-specific patches for Maemo? These
>>apply to the pristine tarballs I'm guessing? Where can one get these
>>patches? (Is that a dumb question showing I know nothing about OE?)
>>
>>
>
>well... you have two sorts of patches:
>The maemo source packages are Debian-style sources which sometimes contain
>patches to be applied before building the source. In addition you sometimes 
>need
>patches to apply additional fixes to build the sources with OE. These patches
>are managed in OE, but so far OE doesn't have a mechanism to handle the patches
>included in the source package. Of course you can extract these patches and add
>them to OE manually, but it makes maintainance of it much more complicated.
>
>
>Greetings
>
>Florian
>
>  
>
Wouldnt it be just easier to do it the debian way inside SB.

1. get the list of packages right so the dependencies are met.
2. If you need to modify or add some components then have them available
in a different local repo [building, packaging and resolving their
dependencies is a step that should be done seperately, possibly in
another SB maemo rootstrap]
3. for nokia 770 add the magic packages from nokia binary distribution

and you have your new rootfs for nokia 770.

For other devices, to use maemo, you would have to provide device
specific stuff. Or even better to get the reverse dependencies on what
packages depend on packages provided by nokia, and approximate what in
functionality they would mean for the different device, and have
packages (dummy or providing similar functionality but for your device
like device state management, battery management, input methods and VKB etc)

Then comes the desktop part etc, which is hildon, remove all af-desktop
related components from your build as hildon is  quite n770 800x480
resolution tied. See what could be used from e.g GPE etc package them as
debian [that could be quite a work]

Also lot of device startup procedure would have to be streamlined

would be quite lot of work but IMHO doable :) Just IN MY PERSONAL
OPINION, it would great to see option of 2 toolkits (GPE , Hildon), a
core base maemo platform + adaptation layers , and device specific
layer, and common set of development tools and environment [SB etc, with
different toolkits etc]

Devesh




___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Using osso-browser-interface

[Devesh Kothari]

ext maukka maukkanen wrote:

> Hi
>
> Anyone having experience in using osso-browser interface? I've spent
> some time trying to launch browser in embedded mode from hildonapp but
> all I'm able to launch is "Web loading" notification and then nothing.
> See the code snipplet below:
>
> <>
>
>  osso_return_t ret;
>  hildon_app_set_appview ( data->app, data->browser_view );
>  hildon_app_notify_view_changed( data->app, data->browser_view );
>  ret =osso_rpc_run_with_defaults(data->osso,
> "osso_browser","plug_new_window", NULL,
> DBUS_TYPE_UINT32,
> hildon_app_find_view_id(data->app,data->browser_view),
>   DBUS_TYPE_STRING, "file://localhost/media/mmc1/test_page.html",
> DBUS_TYPE_STRING, NULL,
>   DBUS_TYPE_BOOLEAN, TRUE,
> DBUS_TYPE_BOOLEAN, FALSE,
>   DBUS_TYPE_STRING,
> "com.nokia.osso_browser", 
> DBUS_TYPE_INVALID);
>  if (ret != OSSO_OK) {
>  gtk_infoprint(GTK_WINDOW(data->app), "Browser launch failed");
> }
>
> <-->
>
> Something is going therribly wrong but I have no idea whatsoever about
> the error:( I'd also be interested in knowing if videoplayer has
> similar interface available.
>
> Thanx,
> -mp
>
> _
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers

I am not so sure about the URL I always get confused by the number of
slashes etc maybe that is something you can try playing with ;)

Devesh


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Problem with building application (tutorial document).

[Devesh Kothari]

ext Erik Bågfors wrote:

>2006/1/4, Edlinoor Syahril Ramlan <[EMAIL PROTECTED]>:
>  
>
>>Hi,
>>
>>I really do not understand some of the steps written in chapter 4 section 4.2
>>in the tutorial document.  In item 2 of the section it is mentioned that I
>>need to copy the maemopad_1.4.tar.gz to my home directory inside Scratchbox,
>>and uncompress it.  The thing that I do not understand is:
>>
>>1) Where is the user directory in Scratchbox.  Is it
>>in: /scratchbox/users/edlinoor/targets/SDK_PC/home/user?
>>by the way "edlinoor" is the username that is used for scratchbox.  I tried to
>>copy the maemopad_1.4.tar.gz into that directory but when I do:
>>[sbox-SDK_PC: ~] > ls I get "MyDocs" but no maemopad_1.4.tar.gz.
>>
>>
>
>/scratchbox/users/$USER/home/$USER
>
>/Erik
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
or what i typically do is to copy to /tmp [it is shared between SB and
the host system], loging into SB and just pick from /tmp like tar -zxvf
/tmp/xxx.tgz

Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Perl on the Nokia 770

[Devesh Kothari]

check the repository.maemo.org
http://repository.maemo.org/pool/maemo1.1rc7/free/p/perl/

you should be able to get it using apt-get on developer rootfs atleast.

Best Regard
Devesh

Package: perl
Priority: standard
Section: perl
Installed-Size: 10560
Maintainer: Brendan O'Dea <[EMAIL PROTECTED]>
Architecture: arm
Version: 5.8.3-3osso1
Replaces: perl-5.005 (<< 6), perl-5.6 (<< 6), perl-doc (<< 5.8.0-1), 
perl-modules (<< 5.8.1-1), libdigest-md5-perl, libmime-base64-perl, 
libtime-hires-perl, libstorable-perl
Provides: perl5, libdigest-md5-perl, libmime-base64-perl, libtime-hires-perl, 
libstorable-perl
Depends: perl-base (= 5.8.3-3osso1), perl-modules (>= 5.8.3-3osso1), libc6 (>= 
2.3.2.ds1-4), libdb4.0, libgcc1 (>= 1:3.3.3-1), libgdbm3
Suggests: perl-doc, libterm-readline-perl-perl
Conflicts: perl-5.004 (<< 6), perl-5.005 (<< 6), perl-5.6 (<< 6), perl-doc (<< 
5.8.3-1), libdigest-md5-perl (<< 2.33-1), libmime-base64-perl (<< 2.21-1), 
libtime-hires-perl (<< 1.52-1), libstorable-perl (<< 2.08-1)
Filename: pool//maemo1.1rc7/free/p/perl/perl_5.8.3-3osso1_arm.deb
Size: 3133154
MD5sum: fe2ea3adebf5504026eaa719458c466c
Description: Larry Wall's Practical Extraction and Report Language.
 An interpreted scripting language, known among some as "Unix's Swiss
 Army Chainsaw".
 .
 Perl is optimised for scanning arbitrary text files and system
 administration.  It has built-in extended regular expression matching
 and replacement, a data-flow mechanism to improve security with
 setuid scripts and is extensible via modules that can interface to C
 libraries.





ext Xavier Calbet wrote:

>  I was willing to run perl on the Nokia 770, in fact
>my objective
>is to run PDL (pdl.perl.org) on it, if the hardware
>permits. The
>reason for this is that it would turn the Nokia770
>into a powerful
>caculator, numerical computation machine.
>  I was going to compile perl on the maemo platform
>when I just noticed
>that it is already installed in scratchbox. I am new
>to maemo and I am
>still a bit confused on how to use it. Would it be
>possible to transfer
>in some way the perl executables in scratchbox to the
>Nokia770, preferably,
>of course, inside a deb package?
>
>  Any suggestions welcome.
>
>  Xavier Calbet
>
>
>
>   
>__ 
>LLama Gratis a cualquier PC del Mundo. 
>Llamadas a fijos y móviles desde 1 céntimo por minuto. 
>http://es.voice.yahoo.com
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Maemo Alarm/Notifier Interface

[Devesh Kothari]

Great this is feedback I was looking for. Now just to bring on same page
again

First the end user use cases
1. An application e.g Calender or task wanting to alart and notify the
user of scheduled events. This notification should have a certain
accepted granularity and delivery promise
   - Resolution of most end user use case can live with 1 minutes
granularity [IMHO]
   - Events must be delivered regardless of the device state e.g sleep,
deep sleep or poweroff state [but with battery plugged in]
   - User should be able to schedule Events/Notification in any future
time e.g my mothers birthday which is 8 months away.

Every other use case is more secondary use case
2. User is able to work on all scheduled events from one common point 
UI (e.g as simon pointed, in a cinema, want to silent all alarms, cancel
or enable alarms).
  - You can argue that switching off the device speaker would result the
same, though you might have the nuisance of screen turn ons.
  - The ability to cancel/enable alarm might make things complicated for
application developers, as then events not delivered to the registered
apps, somebody need to tell them that the alarm was either cancelled or
rescheduled, so they can reach a sync state.

>From a Developer Perspective
1. There should be a easy to use API enabling/disabling and notification
of scheduled events.
2. Alarm/Notifier sub system should have the capability to delivery
events to applications, even in case the application is not running [e.g
starting the app with a specific startup reason code, so that the whole
app window need not be started e.g in case of calendar, only a dialog
pops up saying event due ... with option like open event (causing all
app window to come), reschedule/snooze, cancel
3. It would also be useful that the implemented solution is also
available/complaint/builds upon other solutioins like that mentioned
about hh.org and iPAQs
4. IN case of reshedule, or cancel, only the app which scheduled it, is
able to do that [some kind of inbuild security]

What I have learnt on this discussion thread
First the hardware
- On n770 RTC is the provided by retu, which has a granularity of 1
minutes and can only handle 1 event at a time and that too for only
between now and 23:59
- I am assuming that it is capable of waking up the hardware, even if it
is powered off [but with a alive and kicking battery]

About the implementation (As a application developer I would not care
about the real implementation, till I can get a simple to use API
interface enabling basic use cases :) but from Maemo perspective, it is
benificial that the Maemo development Platform get a sane design.

- some kind of D-BUS to auto activate and deliver events
- some kind of library to abstract the inner working of the
implementation [good also from point of view of application
portability], could be extension to lib_osso or another brand new
lib_alarm or whatever. This should also enable simultaneous concurrent use.
- some kind of UI , maybe a control panel applet to work with all
alarms/events scheduled. Now that depends if it is free for all to know
about all events scheduled by other apps [not so nice from security
point of view, so if security of this time is important then to drop
this completely]
- some sort of a daemon to provide software intelligence to make up for 
hardware constrains.
- existing open source components should not be changed e.g reduces
maintainence overhead (proposals being crond, atd)


I think it would be good idea to have a wiki page?  My objective is
quite achieved that there is community participation, and people inside
nokia  need to look  into what the community had wanted and what was
delivered :) even when I know product  schedules and  requirements are
highest priority [read as , you wont get always what you wanted ;)].

cheers
Devesh








ext Igor Stoppa wrote:

>On Wed, 2006-01-11 at 11:35 -0800, ext Jason Mills wrote:
>  
>
>>A few items:
>>
>>0) The RTC subsystem is served off a chip known as "Retu". Most of the ASICs
>>on the Nokia 770 board seem to have nice nordic names to them. :-)
>>
>>
>>1) The RTC subsystem only supports one future alarm event, and that event may
>>not be more than 24h59m from "now". Maximum alarm granularity is +/-1 minute
>>or so.
>>
>>
>23h59m if memory serves me well
>
>Only Retu can wake up the device from poweroff state at a preset time;
>unfortunately this is the time resolution that it canprovide. In order
>to extend alarms and events scheduling one could have the daemon
>scheduling periodic wakeups (every 24h) till the real alarm is closer
>than 24h.
>The granularity problem could be overcome using either a sw timer or an
>internal HW timer, with better resolution than 1m.
>It would be programmed by the daemon, after the last wakeup and  before
>reaching the scheduled time for the event.
>
>  
>
>>2) The actual definition of "now" is a bit arbitrary, because of how the RTC
>>synchronization works.
>>
>>
>>3) There i

Re: [maemo-developers] Open URL with 770's browser

[Devesh Kothari]

ext David Woodhouse wrote:

>On Mon, 2006-01-09 at 19:01 -0500, Roland Krikava wrote:
>  
>
>>Can anyone suggest a way to open a URL using the native browser on the
>>770? I noticed that someone posted earlier about attempting to use
>>dbus to accomplish this..
>>
>>
>
>I just hacked up a shell script to make this work for viewing images and
>URLs from pine (http://david.woodhou.se/maemo-pine.html) ...
>
>#!/bin/sh
>
>if ! dbus-send --system --type=method_call  --dest="com.nokia.osso_browser" 
>--print-reply /com/nokia/osso_browser/request com.nokia.osso_browser.load_url 
>string:"$1" ; then
>DISPLAY=:0 run-standalone.sh /usr/bin/browser &>/dev/null &
>sleep 5
>dbus-send --system --type=method_call  --dest="com.nokia.osso_browser" 
> --print-reply /com/nokia/osso_browser/request com.nokia.osso_browser.load_url 
> string:"$1"
>fi
># give it a while to access local files before they're deleted
>if echo "$1" | grep ^/ ; then
>sleep 10
>fi
>
>
>(Btw, please could we have the Subject line mangling on this mailing
>list removed or at _least_ reduced to a sane number of characters.
>Removing it completely would be best -- there are much better ways to
>filter mail, and people who really want it there can always _add_ it for
>themselves; adding it locally is much easier than trying to remove it
>again once it's been added).
>
>  
>

There is a file (part of maemo):

https://stage.maemo.org/viewcvs.cgi/maemo/projects/browser/browser/trunk
/osso-browser-interface/osso-browser-interface.h?rev=1344&view=markup

And there is a d-bus interface described in this file.

You need one of these functions:

/* URL loading service */

/**
 * Open new browser window. \n
 * \b url: The URL to load in new browser window\n
 * \b Example: Open new window with home page
 * \code
 * ret = osso_rpc_run_with_defaults(app_ctx, "osso_browser",
 * OSSO_BROWSER_OPEN_NEW_WINDOW_REQ, NULL, 
 * DBUS_TYPE_STRING, "new_window",
DBUS_TYPE_INVALID);
 * \endcode
 * \b Example: Open new window with url 
 * \code
 * ret = osso_rpc_run_with_defaults(app_ctx, "osso_browser",
 * OSSO_BROWSER_OPEN_NEW_WINDOW_REQ, NULL, 
 * DBUS_TYPE_STRING, url, DBUS_TYPE_INVALID);
 * \endcode
 *
 */ 
#define OSSO_BROWSER_OPEN_NEW_WINDOW_REQ"open_new_window"


/**
 * Load URL in current browser window.\n
 * \b url: The URL to load\n
 * \b Example: Load Home page in currently open browser window 
 * \code
 * ret = osso_rpc_run_with_defaults(app_ctx, "osso_browser",
 * OSSO_BROWSER_LOAD_URL_REQ, NULL, 
 * DBUS_TYPE_STRING, "new_window",
DBUS_TYPE_INVALID);
 * \endcode
 * \b Example: Load URL in the currently open browser window. 
 * \code
 * ret = osso_rpc_run_with_defaults(app_ctx, "osso_browser",
 * OSSO_BROWSER_LOAD_URL_REQ, NULL, 
 * DBUS_TYPE_STRING, url, DBUS_TYPE_INVALID);
 * \endcode
 *
 */ 
#define OSSO_BROWSER_LOAD_URL_REQ"load_url"


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Info on FIASCO components/hackers' guide to the N770

[Devesh Kothari]

ext Dave Neuer wrote:

>Hi all, and thank you Nokia for finally getting my lovely new 770 to me.
>
>I'm still in the process of familiarizing myself w/ the device and the
>Maemo/N770 environment. Let me first complement all of the people who
>have made this impressive little device so usable and compelling
>already. Great job.
>
>One of the first things I generally do when I get a new Linux-capable
>device is remove all proprietary software, and replace it with Free
>Software or Open Source alternatives if possible (or otherwise do
>without).
>
>I'm still running the stock image on the 770, but I've been
>investigating over the last week what it would take to rip out all of
>the proprietary stuff, and how much customization of the device is
>possible.
>
>  
>
developer rootfs is the place to start, as it contains no propreitary
applications. It do require a binary blob under nokia license,
containing device specific and closed software from nokia.

>One thing I've noticed is there seems to be lack of a comprehensive
>set of documentation for the device at the "how it all works" level,
>from "processor beings executing code at location 0x" to "this
>is how you assemble a FIASCO image."
>
>  
>
flasher is capable of flashing independently the kernel, initfs, rootfs.
So its not necessary to have a FIASCO file.

>I can kind of understand why this information might not be available.
>Nokia no doubt wants us to concentrate on developing useful end-user
>applications which enhance rather than replace the existing
>functionality and environment.
>
>However, given the existence of the information at [1] and [2], it
>seems that the djinn is already half out of the bottle. For instance,
>I've already been able, using the resources cited above on the
>maemo.org website, to unpack a FIASCO image and determine that the
>initfs and rootfs are JFFS2 images, and that the remaining components
>aren't. So, I was wondering if it would be possible to have such a
>"Hacker's Guide to the N770 and Maemo." Something which describes the
>function of the various FIASCO components and the recipe for creating
>a valid custom FIASCO image (obviously certain components couldn't be
>replaced).
>
>I'm most interested in creating my own kernel, initfs and rootfs
>images and sewing them back together, and flashing them to the device
>without breaking anything.
>
>  
>
with resources available on maemo.org, you should be able to compile
your own kernel and rootfs. There are issues with initfs [so that piece
is not possible, as it contains some software like wlan drivers etc,
which are closed]

look at
http://maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html


Br,
Devesh

>I'd love to know what Nokia's position is on this as well as what
>other developers here think about it.
>
>Also, is flasher a supported way to upgrade to the latest system image
>from Nokia's support site?
>
>Thanks in advance.
>
>Dave
>
>[1] http://maemo.org/maemowiki/HowDoiBecomeRoot (section entitled "The Hard 
>Way"
>[2] http://maemo.org/maemowiki/Flasher_tool_usage
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Maemo Alarm/Notifier Interface

[Devesh Kothari]

I am currently looking for what developer requirements would be from
such an Alarm/Notifier interface. Specially lot of developers working on
applications which need to schedule events and notifications like PIM
aplications need this functionality, and it is just not there yet in the
Maemo Development Platform.

Some starters

1. API to
   - enable notifier/alarm events
   - cancel previously scheduled events
   - ability to specify sound file to be played for events [I guess this
can be done by the application handling the notifier event, so maybe not
relevant]

2. Alarm/Notifier sub system features
- ability to schedule multiple notifier alarm event
- ability to wake up device on events


Devesh


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] U.S. developer devices query

[Devesh Kothari]

ext Roger Sperberg wrote:

>Now that the Nokia 770 is already for sale in Europe, and sales are reported 
>to begin next Friday in the U.S., I'm wondering if the developer devices for 
>non-E.U. countries are being made available?
>
>Are there any U.S.-based developers who have gotten their code? Or 
>non-E.U.-based developers?
>
>Thanks. If anyone from Nokia would care to provide hard information, that 
>would be especially welcome.
>
>Roger
>
>PS: I've been told I'm way too impatient on this matter, more than once. 
>Apologies for this impatience breaking out again. :-)
>
>  
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
The US developers will start getting their mails this week starting
today 07.11
Best Regards
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Maemo and Independent software vendors orcommercial software vendors

[Devesh Kothari]

ext Adilson Oliveira wrote:

>Olivier Bornet escreveu:
>  
>
>>Hello,
>>
>>On Wed, Nov 02, 2005 at 08:07:23AM -0500, Brad Clements wrote:
>>
>>    
>>
>>>On 2 Nov 2005 at 10:34, Devesh Kothari wrote:
>>>
>>>
>>>  
>>>
>>>>- Proposals from your side what we need to improve
>>>>
>>>>
>>>Start shipping the developer units in the USA.. ;-)
>>>  
>>>
>>And in switzerland. ;-)
>>
>>At least, try to give a estimated planning for it.
>>
>>
>
>Same here in Brazil. I know at least 3 companies very interested in
>evaluate the 770 and 1 more already contacted me about it's viability
>but there's nothing we can do yet until have the devices.
>
>[]s
>
>Adilson.
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
For all such cases, my suggestion is to contact me with a clear proposal
of the intended objective, and I would look into how we can work here to
solve issues with device availabilities.


Best Regards
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Maemo and Independent software vendors or commercial software vendors

[Devesh Kothari]

I want to open a dialog with all ISV/Commercial vendors wanting to work
with developing solutions for maemo based devices like the Nokia 770
Internet tablet

Objectives
 - To understand your requirements and expectations
 - Proposals from your side what we need to improve
 - Proposals what you would like us to do (given an option differently:)

If you feel more comfortable, you can  write private email to me

Best Regards
Devesh Kothari

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Starting application from task navigator menuwon't work

[Devesh Kothari]

[EMAIL PROTECTED] wrote:

>Hi all,
>
>I created a small helloworld application and created the .deb package
>pretty much by copying stuff from Jarkko Oikarinen's Mammasnake package
>(by the way, a million thanks to Jarkko for not using autotools - for a
>newbie like me the shell script is way, way, WAY easier to understand
>than autotools scripts)
>
>Anyway - I manage to install the package to a real N770 device and it
>shows under "Extras" in the menu - but selecting it doesn't do anything.
>In fact, the only thing that happens that I no longer can start anything
>(like file manager or anything under Games etc) from the task bar menu
>anymore. Otherwise the device works fine - I can e.g. adjust volume
>settings from the top right corner.
>
>Any ideas for what could be wrong? I checked with "ps -aux | grep user"
>in XTerm on the device and apparently my application does not even
>start, so the problem is likely to be somehow with the installation
>package, not the actual application.
>
>As I said, I pretty much copied the package.sh script, the .service
>file, the .desktop file, and the control file from the Mammasnake
>package by replacing all 'mammasnake' references with the name of my own
>application. So the links etc should work fine.
>
>  
>
be careful with the .desktop file as it contains the Exec="xxx"
where xxx is the executable to launch.

check that it contains the right executable i.e your executable

>Oh, and I did the whole compile under ARM target and checked (with
>'file') that the executable really is an ARM executable.
>
>   -Sami-
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] OGG support

[Devesh Kothari]

ext Martin Grimme wrote:

>Hello,
>
>I have written a little program which can fluently play OGG Vorbis
>files on the device. This shows that OGG support is technically
>possible and, by utilizing the DSP, it could even be implemented more
>efficient. My CPU-only implementation causes about 20% CPU load for
>playing in CD quality.
>
>I'm going to add a little GUI and provide an installer package
>for my OGG player soon.
>
>
>Regards, Martin
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
I am trying to get a How-To which should describe the multimedia
architecture explained and how to write custom codec and how to
integrate and install them.

could you post your code ???  this could be quite useful or even start a
How-To page on the Wiki

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Announce: Applications for download available

[Devesh Kothari]

ext Gustavo Sverzut Barbieri wrote:

>On 10/20/05, Rodrigo Parra Novo <[EMAIL PROTECTED]> wrote:
>  
>
>>On 10/20/05, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote:
>>
>>
>>>We could have a package called "KernelConceptsRepository", that, when
>>>installed, it will just append your repository to apt/sources.list.
>>>  
>>>
>>   For security reasons, Application Installer runs under user
>>'install', so unfortunately (or fortunately :) ) it can't update
>>/etc/apt/sources.list. Also, as 'install' is an ordinary user, no
>>files installed with Application Installer can be suid root.
>>
>>
>
>Couldn't maemo have a "system service" (app) to do request a new
>mirror to be installed?
>   Maybe the final version could have a few trusted sites and some PGP
>keys to protect users.
>   Or we could have some central place to put free maemo applications,
>this would come in maemo platform and we can have a review board to
>make sure the package offers no danger to people's software/device.
>
>
>  
>
We have been internally toying with similar idea (still in idea phase)
about "maemo ok" for applications, but we need more discussion
and thought on that together with maemo community.

Br,
Devesh

>  
>
>>>After that we can have some GUI to browse packages from
>>>repositories... but we should come with a clean solution to mask out
>>>system packages! With that user would see a pretty "AbiWord - Text
>>>processor" "Gnumeric - Spread sheet" ... icons in his device.
>>>This would be something like Linspire "Click-n-Run".
>>>
>>>But then we have the security problem to edit /etc/apt/sources.list ... 
>>>ideas?
>>>  
>>>
>>   Give time some time, I believe it will only be a matter of time
>>before someone (from the Maemo community) releases an AI++ (which
>>installs software on the root directory).
>>
>>
>
>I don't think it's necessary.
>We could use the concept of "self contained" packages really easy,
>like Rox does and some KDE people wants to with http://klik.atekon.de/
>
>Problem is always dependencies... however if we have a base of
>applications user may want to install, we can check common
>dependencies and after evaluating their size x benefit, decide if we
>provide it by default. Maemo being a single device/kernel by _now_
>helps a lot.
>
>But I still want the former approach, using apt-get and a GUI to
>manage user packages (not system/libraries)
>
>--
>Gustavo Sverzut Barbieri
>---
>Computer Engineer 2001 - UNICAMP
>GPSL - Grupo Pro Software Livre
>Cell..: +55 (19) 9165 8010
>Jabber: [EMAIL PROTECTED]
>  ICQ#: 17249123
>   MSN: [EMAIL PROTECTED]
> Skype: gsbarbieri
>   GPG: 0xB640E1A2 @ wwwkeys.pgp.net
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Enough theory...

[Devesh Kothari]

ext Chris Ball wrote:

>>>On 19 Oct 2005 15:59:50, Mattias Schlenker <[EMAIL PROTECTED]> said:
>>>  
>>>
>
>   > I wanted to start installing applications, AbiWord from
>   > indt.org.bra but maemo refused to install libfribidi with a strange
>   > error message saying something like "component already included",
>   > the same with Maemo Word processor.
>
>My 770 turned up today too, and I got the above error installing
>minisip.  "Component not included" obviously isn't what's wrong;
>can anybody tell us what is?  :)
>
>Thanks!
>
>- Chris.
>  
>
best way to find what it means is by looking at the code :)
https://stage.maemo.org/svn/maemo/projects/haf/trunk/osso-application-installer/

but in nutshell
the Application Installer
1. does not install anything which does not have maemo as one of the
component in Depends: line of control file. If "maemo" does not
exist, it thinks humm... I am not supposed to be installing this , as
this package is not built for me .. and give out that cryptic message.
2. you can have dependencies, but then these dependencies should be met
through the alternative dpkg pakage DB i.e the one which is used by AI,
and starts afresh
so for example

for package A [x, y, z] dependencies
If you know what packages are included on device [that info would be
available from ameo.org] in this example x, y, you just remove those
packages from depends line and replace it with maemo

Depends: maemo, z

Now you need to worry about packaging z for maemo. first follow the same
rule as above e.g if z depends on [s,t] and bothe s,t are included in
the device
then
Depends: maemo

Now you would need to install first Z and then A

Since no pre/post install scripts are permitted either, so effectively
AI is
1. dpkg to store installed package information
2. effectively, just untar that data.tar.gz in a debian package
3. minimal conflict identification [no resolve]


Hope that at least provide a start point
Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Mono on Nokia 770

[Devesh Kothari]

ext Günter Wolter wrote:

>Hi,
>
>I tried to get it work on my device, but I got the following error message:
>
># ~/mono/mono-nokia/mono button.exe
>--
>The assembly mscorlib.dll was not found or could not be loaded.
>It should have been installed in the 
>'/usr/local/lib/mono/1.0/mscorlib.dll' directory.
>--
>
>The next problem is, that I can't create a new folder under '/usr' to 
>copy the needed files into, because I have not the permissions to do 
>that. (as root) ?!
>
>// Günter
>
>Paolo Molaro wrote:
>
>  
>
>>I guess people on this list would be interested:
>>Mono runs on the Nokia 770, including Gtk# apps.
>>There is a tarball of the binaries here:
>>  http://primates.ximian.com/~lupus/mono-nokia.tgz
>>
>>It includes a README with a couple of instructions to setup
>>env vars.
>>You should be able to just copy a Gtk# app and have it run.
>>There is no support yet for Hildon-specific widgets.
>>Happy hacking!
>>
>>lupus
>>
>> 
>>
>>
>>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
I tried it, just make sure you set up your LD_LIBRARY_PATH properly. It
is described in the README, included in the tar file

Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] build system

[Devesh Kothari]

ext Gustavo Barbieri wrote:

>Hello,
>
>I use a system where / doesn't have much space, but I have some spare
>in /mnt/extra, so I want to install maemo/scratchbox in
>/mnt/extra/maemo/, however everything is hard coded to /scratchbox.
>
>While trying to build it by hand and also create an ebuild (Gentoo),
>I've found out that many other things are hard coded and the build
>process is not that usual (ie: doesn't use autotools and stuff like
>that). There is any reason?
>
>Is anyone working to improve this situation? I want to help, but also need 
>help.
>
>  
>
i had the same issue once, and I used mount --bind
once installed, i just replace the /scratchbox as a symlink

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] maemo.org Roadmap

[Devesh Kothari]

ext Matthias Steinbauer wrote:

>Do I understand right, that the Roadmap on the maemo.org Roadmap shows planned 
>things. So if I choose lets say a C++ Layer for Hildon widget set as as 
>summer project for me ... everybody would be happy?
>
>Matthias
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
sure. The best is to announce your project or effort in the announce
mailing list, and possibly where you hosting your efforts so other could
contribute too.

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] wiki

[Devesh Kothari]

ext Karoliina T. Salminen wrote:

>ext Daniel Monteiro wrote:
>
>  
>
>>hi folks,
>>when its going to be available a wiki, so we can
>>contribute with documentation?
>> 
>>
>>
>>
>It is up to Devesh/Ferenc. Hopefully soon.
>
>  
>
>>I want to translate things =-)
>> 
>>
>>
>>
>That help is always very welcome! I am looking forward to it.
>
>Best Regards,
>Karoliina
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>
Wiki is on very high priority, so hopefully soon :)

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] Come and visit maemo at LinuxTag 2005

[Devesh Kothari]

LinuxTag, *Karlsruhe, Germany
*22nd-25th June 2005

Maemo would be at booth D84

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] UI guidelines

[Devesh Kothari]

We are working to make the UI guideline available to foster UI consistency.
Br,
Devesh

ext Rui Carmo wrote:

>
> On Jun 1, 2005, at 16:50, Tommi Komulainen wrote:
>
>> On Fri, 2005-05-27 at 23:21 +0100, ext Rui Carmo wrote:
>>
>>> Hmmm. I suppose there is some sort of UI guidelines around?
>>>
>>
>> Sure, just pop in to our office, sign an NDA and we might be able  to
>> let
>> you have a peek at the documentation which is currently  confidential ;)
>
>
> Hmmm. It might be getting warm enough to go to Finland... ;)
>
>> I filed a bug at https://maemo.org/bugzilla/show_bug.cgi?id=64
>> We'll see what we can do about it.
>
>
> Great. I think you'll find it to be a necessity after the first 
> generation of applications/ports comes out and people start griping 
> about consistency - as they eventually do. :)
>
> R.
>
> ___
> maemo-developers mailing list
> maemo-developers@maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Developer Device Program

[Devesh Kothari]

ext Chris Faherty wrote:

>Hello,
>
>I sent an e-mail to the maemo developer program on may 30 but i didn't
>receive any response yet.
>
>Does all (500) responses will be send once or did i miss something ?
>Thanks.
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>
>  
>
To be honest, we didnt really expect so huge amount of emails :),
so now we have a little logistic problem, but we will start sorting
and answering very soon. So please dont resend :)

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Maemo Live-CD?

[Devesh Kothari]

I was thinking if we could maybe turn the Live CD to mirror more of the
real target hardware i.e like Nokia 770 so that it would be like running
the whole maemo root file system on x86 + development tools but without
the limitations of x86 scratchbox. for example lot of issues come from
the fact that you are not real root in scratchbox, and that becomes a
problem with deamons which access the device nodes etc e.g bluetooth.
Once the live CD boots up, it is like boothing up the x86 version of
Nokia 770 (offcourse somethings would always be missing like the DSP),
and then this live CD could mount the host machine partitions for
developer home directory. Maybe the other option would be UML but last I
checked UML had lacked host USB support (has that changed), so you can
have USB peripherals like Bluetooth dongle, WLAN etc and then you have
an x86 version of the Nokia 770.

Maybe I dont make any sense :)
Br,
Devesh


ext Roger Sperberg wrote:

> Matthias wrote:
>
> OK, every reply so far asks for a live CD aimed to developers,
> not
> something small that would also fit on a credit card sized CD
> or a USB
> stick.
>
> I'll build a quick and dirty version based on Kanotix Lite
> during the
> next days.
>
>Don't mean to be anal about this, but it would also be a good idea :-o to 
>include some of the apps and python and such on this LivceCD. Please.
>
>Thank you,
>
>Roger
>
> -- 
> [EMAIL PROTECTED] 
>
>
>
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] maemo application porting and effort duplication

[Devesh Kothari]

I agree we need some coordination about application porting and effort
duplication? we can create a new mailing list where people can announce
their efforts and others can search the archive to see if someone is
already working on it, or the other option is to open up a bug against a
dummy package in bugzilla. Any ideas/opinions ???

Br,
Devesh

>Is there any list of applications mameo guys wants
>port on priority? I was able to cross-compile mplayer
>and running on my board with 3gpp support. List will
>help us not to duplicate the work in porting.
>
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] X86 Virtualization

[Devesh Kothari]

I think the objective will be to run a sandboxed maemo root filesystem
on Linux, very much like UML( there possibly are other ways of achieving
the same) and access the host pheripherals like BT and WLAN. This way
you can mimic the entire Nokia 770 on  your host machine, and that would
really simplyfy development and hacking. Offcourse their would be a
performace difference between this sandboxed and the real target.

Br,
Devesh

ext Ramanujan T.P wrote:

>Hi,
>
>Was seeing the road map of Maemo, and was interested to see that one of
>the "ToDo's" marked as
>
>Support for full x86 device virtualization 
>
>--Wondering if a hardware virtualization is attempted, then its cons
>like overhead, latency etc.
>
>Or is a S/W virtualization attempted?
> -- Vserver for Linux availability
>
>More information / thoughts on this would be pretty interesting.
>
>Best Wishes
>Ramanujan
>
>
>
>
>Confidentiality Notice 
>
>The information contained in this electronic message and any attachments to 
>this message are intended
>for the exclusive use of the addressee(s) and may contain confidential or 
>privileged information. If
>you are not the intended recipient, please notify the sender at Wipro or 
>[EMAIL PROTECTED] immediately
>and destroy all copies of this message and any attachments.
>___
>maemo-developers mailing list
>maemo-developers@maemo.org
>https://maemo.org/mailman/listinfo/maemo-developers
>
>  
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] how we can enhance the maemo.org

[Devesh Kothari]

to support developers better. Any ideas??

Br,
Devesh

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

[maemo-developers] maemo applications

[Devesh Kothari]

I assume their are some maemo applications in work out there. Can
someone point me to them. It would be nice to have a page on maemo,
listing current projects/efforts around maemo [till we get out own wiki,
then people can do that themselves :)]


Br,
Devesh


___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers

Re: [maemo-developers] Mic input on 770?

[Devesh Kothari]

In fact as far as I know their is a mic on the N770, though that is not
an advertised feature, as currently their is no software on the product
which uses that. So it is waiting their to be hacked :)

Br,
Devesh



ext Neil Cherry wrote:

> Javier Cardona wrote:
>
>>
>> Hi,
>>
>> Is see that there is no microphone input on the Nokia 770 (
>> http://www.nokia.com/nokia/0,,75023,00.html ). 
>> Anyone has any ideas on how to capture voice on the device?  Bluetooh
>> microphones?
>
>
> I'm guessing USB sound card or perhaps a Bluetooth head set?
>

___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers