<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.6(BH)" -->
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>Brainstorm: Sandbox, waiting, category Programming</title>
        <description></description>
        <link>http://maemo.org%2Fcommunity%2Fbrainstorm%2Flist%2Fxml%2F%3Fstatus%3Dsandbox_waiting%26category%3DProgramming/</link>
        <lastBuildDate>Wed, 19 Jun 2013 01:10:19 +0000</lastBuildDate>
        <generator>FeedCreator 1.7.6(BH)</generator>
        <language>en</language>
        <item>
            <title>PDF page memory</title>
            <link>http://maemo.org/community/brainstorm/view/pdf_page_memory/</link>
            <description><![CDATA[The standard PDF reader that comes with N900 is great for reading a PDF document. In my opinion it lacks one very important feature, remembering what page you are on in the PDF document.

Using Mandriva with KDE I have gotten used to my PDF reader remembering the page I am on for each individual PDF document I might open.

I can imagine with all the talented people who contribute to Maemo that the programming to have the PDF reader remember not only the page it is on for the last document, but for any document, is not that hard to program. I would be extremely happy with anyone that would be able to make tgis possible, and I am sure I am not alone.

Please.<br /><br />0 solutions for this brainstorm.]]></description>
            <author>kfjellda@hotmail.com (max zeebra)</author>
            <category>|Office|User Experience|Programming|</category>
            <pubDate>Wed, 18 May 2011 19:19:39 +0000</pubDate>
            <guid>http://maemo.org/midcom-permalink-c6c5c5d0818311e09aa565e20425e75ce75c</guid>
        </item>
        <item>
            <title>sms vcs calendar events to and from calendar</title>
            <link>http://maemo.org/community/brainstorm/view/sms_vcs_calendar_events_to_and_from_calendar/</link>
            <description><![CDATA[<p>please I just purchased an N900 to replace my n97's (I have 3) and love linux. However my programming skills are poor at best. I would like to duplicate the sms / text  calendar entrys to my symbian based phones in my business. Please. I can offer a small amount of money to make this happen please. I wish there were true compatibility between the N97 to the N900 (just an observation sorry)</p>
<p> </p>
<p>Thank you all for your awesome work on so many other things!  So far I love it much more than any android I have purchased / used!  Why did nokia remove the purchase links for the N900??? Does that mean a new maemo device is coming very soon? Any idea if it will perform this sms text vcal / ical feature?</p>
<p> </p>
<p>Thanks so much.</p>
<p> </p><br /><br />0 solutions for this brainstorm.]]></description>
            <author>maemo.org@rosn.net (arden bohanec)</author>
            <category>|Office|User Experience|Programming|</category>
            <pubDate>Fri, 25 Feb 2011 11:47:43 +0000</pubDate>
            <guid>http://maemo.org/midcom-permalink-0e9c203840d511e0bd39954258038ccd8ccd</guid>
        </item>
        <item>
            <title>Call Rejector- Developers Needed</title>
            <link>http://maemo.org/community/brainstorm/view/call_rejector-developers_needed/</link>
            <description><![CDATA[<p>Call Rejector<br /> a simple call rejector application which rejects calls listed by the user.<br /> 1. allow list - when active only calls from the listed numbers will be allowed.<br /> 2. reject list - all calls are allowed EXCEPT the ones listed in "reject list"<br /> 3. auto reject unknown numbers - numbers not stored in the users contacts are auto rejected. (option to turn this feature off)<br /> 4. private numbers - private numbers are auto rejected (option to turn this feature off)<br /><br /> the application will be similar/a replica of HandyBlacklist for the S60 platform.<br /><br /> Future Improvements - SMS/MMS rejection following the same examples/options as above.</p>
<p> </p>
<p>Im not a developer but would be keen on going through the process to help with develpment.</p><br /><br />0 solutions for this brainstorm.]]></description>
            <author>roberth@ovi.com (Robert Hall)</author>
            <category>|Desktop|Utilities|System|Programming|</category>
            <pubDate>Mon, 11 Jan 2010 23:01:04 +0000</pubDate>
            <guid>http://maemo.org/midcom-permalink-31e0322cff0511de8d9f0f096a0c1a2b1a2b</guid>
        </item>
        <item>
            <title>Dynamic Help Documentation</title>
            <link>http://maemo.org/community/brainstorm/view/dynamic_help_documentation/</link>
            <description><![CDATA[<p><strong>Summary:</strong> Creation and maintenance of help documentation for Maemo 5 devices, based on a wiki format, which is appended to downloadable applications via a system-level API, and stays in sync on the device in a similar fashion to the application via Application Manager Updates.<br /><br /><strong>Long Version:</strong> Here's the issue, documentation. No one likes to do it, and to create documentation on the device, is a secondary-side of pain for many developers. Therefore I recommend the creation of a a unified documentation point - the Maemo.org wiki - to which all of those who have Maemo 5/6 applications would append their program's help documentation within this wiki. And through the use of a system-level API (or additional dependency), the developer would be able to include this documentation onto the device as a part of the on-board Help feature. This would be linked through a Help or About menu in the respective application, and then also accessible from the general Help application on the device.<br /><br /><strong>Benefits:</strong> the documentation would be in one place - and updated as often as the application itself (if the developer does right). Users would not have to guess at where to find documentation towards their device, and what they find at Maemo.org would be equal to what is on their device.<br /><br /><strong>Note: </strong>This idea is not to mean that the entire wiki would be downloaded onto the device, only those entries which are attached (dependencies) to the application. In this way, a person would have just a snippet of the documentation as they need it.<br /><br /><strong>Downsides: </strong>Developers would have to write/maintain documentation in addition to their applications (positions for technical writers should open up here therefore). Documentation that is not up-to-date would reflect negatively on the developer's karma rating, which can seem unfair for a popular application that sees frequent downloading and positive comments.</p>
<p>Link to Talk thread: <a href="http://talk.maemo.org/showthread.php?p=386337">http://talk.maemo.org/showthread.php?p=386337</a></p>
<br /><br />0 solutions for this brainstorm.]]></description>
            <author>a.r.j.wright@gmail.com (Antoine RJ Wright)</author>
            <category>|Utilities|User Experience|System|Programming|maemo.org|</category>
            <pubDate>Sun, 22 Nov 2009 22:34:37 +0000</pubDate>
            <guid>http://maemo.org/midcom-permalink-377743a8d7b711dea8fb4f4331e9e3a7e3a7</guid>
        </item>
    </channel>
</rss>
