maps

I would like to share a track with you

Published with Blogger-droid v1.6.7

Sony Ericsson Xperia Neo is going to Australia with Telstra

Sony Ericsson Xperia Neo is going to Australia with Telstra: "

Australian mobile carrier Telstra will be bring the Sony Ericsson Xperia Neo down under, but unfortunately, we don’t have pricing or dates yet for official launch.

The Xperia Neo was one of a family of new Xperia devices launched at MWC. Here’s what it’s got inside its frame;

• 3.7 inch WVGA touchscreen


• HSPA and Wi-Fi


• 8 megapixel camera with HD recording


• 1GHz Qualcomm processor


• Android 2.3 Gingerbread

Visit TalkAndroid for android news, android guides, and much more!

Sony Ericsson Xperia Neo is going to Australia with Telstra

"

Samsung Galaxy S 4G will cost you $200 with T-Mobile

Samsung Galaxy S 4G will cost you $200 with T-Mobile: "

Well, it looks like even though you thought you could get a Samsung Galaxy S 4G at RadioShack for $149 on sale, you won’t be seeing that pricing from T-Mobile after all. They apparently…made a boo-boo with the pricing. It’ll cost $199.99 after a $50 mail-in rebate, and taxes n such of corse too. So, to grab one, you’ll actually need around $275.00 then have to fill out a rebate form at home for the extra $50 savings. Yeah…that sucks.

The Samsung Galaxy S 4G has;

• Cortex A8 Hummingbird 1GHz processor


• 4-inch Super AMOLED touch screen


• Android 2.2


• ST-Ericsson M5720 HSPA+ 4G modem capable of giving 21 Mbps


• Front-facing-camera


• 5MP camera with 720p HD video recording

Is the 4G version of the Samsung Galaxy S worth it?

Visit TalkAndroid for android news, android guides, and much more!

Samsung Galaxy S 4G will cost you $200 with T-Mobile

"

The Android 3.0 Fragments API

The Android 3.0 Fragments API: "

[This post is by Dianne Hackborn, a Software Engineer who sits very near the exact center of everything Android. — Tim Bray]

An important goal for Android 3.0 is to make it easier for developers to write applications that can scale across a variety of screen sizes, beyond the facilities already available in the platform:

• Since the beginning, Android’s UI framework has been designed around the use of layout managers, allowing UIs to be described in a way that will adjust to the space available. A common example is a ListView whose height changes depending on the size of the screen, which varies a bit between QVGA, HVGA, and WVGA aspect ratios.

• Android 1.6 introduced a new concept of screen densities, making it easy for apps to scale between different screen resolutions when the screen is about the same physical size. Developers immediately started using this facility when higher-resolution screens were introduced, first on Droid and then on other phones.

• Android 1.6 also made screen sizes accessible to developers, classifying them into buckets: “small” for QVGA aspect ratios, “normal” for HVGA and WVGA aspect ratios, and “large” for larger screens. Developers can use the resource system to select between different layouts based on the screen size.

The combination of layout managers and resource selection based on screen size goes a long way towards helping developers build scalable UIs for the variety of Android devices we want to enable. As a result, many existing handset applications Just Work under Honeycomb on full-size tablets, without special compatibility modes, with no changes required. However, as we move up into tablet-oriented UIs with 10-inch screens, many applications also benefit from a more radical UI adjustment than resources can easily provide by themselves.

Introducing the Fragment

Android 3.0 further helps applications adjust their interfaces with a new class called Fragment. A Fragment is a self-contained component with its own UI and lifecycle; it can be-reused in different parts of an application’s user interface depending on the desired UI flow for a particular device or screen.

In some ways you can think of a Fragment as a mini-Activity, though it can’t run independently but must be hosted within an actual Activity. In fact the introduction of the Fragment API gave us the opportunity to address many of the pain points we have seen developers hit with Activities, so in Android 3.0 the utility of Fragment extends far beyond just adjusting for different screens:

• Embedded Activities via ActivityGroup were a nice idea, but have always been difficult to deal with since Activity is designed to be an independent self-contained component instead of closely interacting with other activities. The Fragment API is a much better solution for this, and should be considered as a replacement for embedded activities.

• Retaining data across Activity instances could be accomplished through Activity.onRetainNonConfigurationInstance(), but this is fairly klunky and non-obvious. Fragment replaces that mechanism by allowing you to retain an entire Fragment instance just by setting a flag.

• A specialization of Fragment called DialogFragment makes it easy to show a Dialog that is managed as part of the Activity lifecycle. This replaces Activity’s “managed dialog” APIs.

• Another specialization of Fragment called ListFragment makes it easy to show a list of data. This is similar to the existing ListActivity (with a few more features), but should reduce the common question about how to show a list with some other data.

• The information about all fragments currently attached to an activity is saved for you by the framework in the activity’s saved instance state and restored for you when it restarts. This can greatly reduce the amount of state save and restore code you need to write yourself.

• The framework has built-in support for managing a back-stack of Fragment objects, making it easy to provide intra-activity Back button behavior that integrates the existing activity back stack. This state is also saved and restored for you automatically.

Getting started

To whet your appetite, here is a simple but complete example of implementing multiple UI flows using fragments. We first are going to design a landscape layout, containing a list of items on the left and details of the selected item on the right. This is the layout we want to achieve:

The code for this activity is not interesting; it just calls setContentView() with the given layout:

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
        android:orientation="horizontal"
        android:layout_width="match_parent"
        android:layout_height="match_parent">

    <fragment class="com.example.android.apis.app.TitlesFragment"
            android:id="@+id/titles" android:layout_weight="1"
            android:layout_width="0px"
            android:layout_height="match_parent" />

    <FrameLayout android:id="@+id/details" android:layout_weight="1"
            android:layout_width="0px"
            android:layout_height="match_parent" />
    
</LinearLayout>

You can see here our first new feature: the <fragment> tag allows you to automatically instantiate and install a Fragment subclass into your view hierarchy. The fragment being implemented here derives from ListFragment, displaying and managing a list of items the user can select. The implementation below takes care of displaying the details of an item either in-place or as a separate activity, depending on the UI layout. Note how changes to fragment state (the currently shown details fragment) are retained across configuration changes for you by the framework.

public static class TitlesFragment extends ListFragment {
    boolean mDualPane;
    int mCurCheckPosition = 0;

    @Override
    public void onActivityCreated(Bundle savedState) {
        super.onActivityCreated(savedState);

        // Populate list with our static array of titles.
        setListAdapter(new ArrayAdapter<String>(getActivity(),
                R.layout.simple_list_item_checkable_1,
                Shakespeare.TITLES));

        // Check to see if we have a frame in which to embed the details
        // fragment directly in the containing UI.
        View detailsFrame = getActivity().findViewById(R.id.details);
        mDualPane = detailsFrame != null
                && detailsFrame.getVisibility() == View.VISIBLE;

        if (savedState != null) {
            // Restore last state for checked position.
            mCurCheckPosition = savedState.getInt("curChoice", 0);
        }

        if (mDualPane) {
            // In dual-pane mode, list view highlights selected item.
            getListView().setChoiceMode(ListView.CHOICE_MODE_SINGLE);
            // Make sure our UI is in the correct state.
            showDetails(mCurCheckPosition);
        }
    }

    @Override
    public void onSaveInstanceState(Bundle outState) {
        super.onSaveInstanceState(outState);
        outState.putInt("curChoice", mCurCheckPosition);
    }

    @Override
    public void onListItemClick(ListView l, View v, int pos, long id) {
        showDetails(pos);
    }

    /**
     * Helper function to show the details of a selected item, either by
     * displaying a fragment in-place in the current UI, or starting a
     * whole new activity in which it is displayed.
     */
    void showDetails(int index) {
        mCurCheckPosition = index;

        if (mDualPane) {
            // We can display everything in-place with fragments.
            // Have the list highlight this item and show the data.
            getListView().setItemChecked(index, true);

            // Check what fragment is shown, replace if needed.
            DetailsFragment details = (DetailsFragment)
                    getFragmentManager().findFragmentById(R.id.details);
            if (details == null || details.getShownIndex() != index) {
                // Make new fragment to show this selection.
                details = DetailsFragment.newInstance(index);

                // Execute a transaction, replacing any existing
                // fragment with this one inside the frame.
                FragmentTransaction ft
                        = getFragmentManager().beginTransaction();
                ft.replace(R.id.details, details);
                ft.setTransition(
                        FragmentTransaction.TRANSIT_FRAGMENT_FADE);
                ft.commit();
            }

        } else {
            // Otherwise we need to launch a new activity to display
            // the dialog fragment with selected text.
            Intent intent = new Intent();
            intent.setClass(getActivity(), DetailsActivity.class);
            intent.putExtra("index", index);
            startActivity(intent);
        }
    }
}

For this first screen we need an implementation of DetailsFragment, which simply shows a TextView containing the text of the currently selected item.

public static class DetailsFragment extends Fragment {
    /**
     * Create a new instance of DetailsFragment, initialized to
     * show the text at 'index'.
     */
    public static DetailsFragment newInstance(int index) {
        DetailsFragment f = new DetailsFragment();

        // Supply index input as an argument.
        Bundle args = new Bundle();
        args.putInt('index', index);
        f.setArguments(args);

        return f;
    }

    public int getShownIndex() {
        return getArguments().getInt('index', 0);
    }
    
    @Override
    public View onCreateView(LayoutInflater inflater,
            ViewGroup container, Bundle savedInstanceState) {
        if (container == null) {
            // Currently in a layout without a container, so no
            // reason to create our view.
            return null;
        }

        ScrollView scroller = new ScrollView(getActivity());
        TextView text = new TextView(getActivity());
        int padding = (int)TypedValue.applyDimension(
                TypedValue.COMPLEX_UNIT_DIP,
                4, getActivity().getResources().getDisplayMetrics());
        text.setPadding(padding, padding, padding, padding);
        scroller.addView(text);
        text.setText(Shakespeare.DIALOGUE[getShownIndex()]);
        return scroller;
    }
}

It is now time to add another UI flow to our application. When in portrait orientation, there is not enough room to display the two fragments side-by-side, so instead we want to show only the list like this:

With the code shown so far, all we need to do here is introduce a new layout variation for portrait screens like so:

<FrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
        android:layout_width="match_parent"
        android:layout_height="match_parent">
    <fragment class="com.example.android.apis.app.TitlesFragment"
            android:id="@+id/titles"
            android:layout_width="match_parent"
            android:layout_height="match_parent" />
</FrameLayout>

The TitlesFragment will notice that it doesn’t have a container in which to show its details, so show only its list. When you tap on an item in the list we now need to go to a separate activity in which the details are shown.

With the DetailsFragment already implemented, the implementation of the new activity is very simple because it can reuse the same DetailsFragment from above:

public static class DetailsActivity extends FragmentActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);

        if (getResources().getConfiguration().orientation
                == Configuration.ORIENTATION_LANDSCAPE) {
            // If the screen is now in landscape mode, we can show the
            // dialog in-line so we don't need this activity.
            finish();
            return;
        }

        if (savedInstanceState == null) {
            // During initial setup, plug in the details fragment.
            DetailsFragment details = new DetailsFragment();
            details.setArguments(getIntent().getExtras());
            getSupportFragmentManager().beginTransaction().add(
                    android.R.id.content, details).commit();
        }
    }
}

Put that all together, and we have a complete working example of an application that fairly radically changes its UI flow based on the screen it is running on, and can even adjust it on demand as the screen configuration changes.

This illustrates just one way fragments can be used to adjust your UI. Depending on your application design, you may prefer other approaches. For example, you could put your entire application in one activity in which you change the fragment structure as its state changes; the fragment back stack can come in handy in this case.

More information on the Fragment and FragmentManager APIs can be found in the Android 3.0 SDK documentation. Also be sure to look at the ApiDemos app under the Resources tab, which has a variety of Fragment demos covering their use for alternative UI flow, dialogs, lists, populating menus, retaining across activity instances, the back stack, and more.

Fragmentation for all!

For developers starting work on tablet-oriented applications designed for Android 3.0, the new Fragment API is useful for many design situations that arise from the larger screen. Reasonable use of fragments should also make it easier to adjust the resulting application’s UI to new devices in the future as needed -- for phones, TVs, or wherever Android appears.

However, the immediate need for many developers today is probably to design applications that they can provide for existing phones while also presenting an improved user interface on tablets. With Fragment only being available in Android 3.0, their shorter-term utility is greatly diminished.

To address this, we plan to have the same fragment APIs (and the new LoaderManager as well) described here available as a static library for use with older versions of Android; we’re trying to go right back to 1.6. In fact, if you compare the code examples here to those in the Android 3.0 SDK, they are slightly different: this code is from an application using an early version of the static library fragment classes which is running, as you can see on the screenshots, on Android 2.3. Our goal is to make these APIs nearly identical, so you can start using them now and, at whatever point in the future you switch to Android 3.0 as your minimum version, move to the platform’s native implementation with few changes in your app.

We don’t have a firm date for when this library will be available, but it should be relatively soon. In the meantime, you can start developing with fragments on Android 3.0 to see how they work, and most of that effort should be transferable.

"

Introducing Renderscript

Introducing Renderscript: "

[This post is by R. Jason Sams, an Android engineer who specializes in graphics, performance tuning, and software architecture. —Tim Bray]

Renderscript is a key new Honeycomb feature which we haven’t yet discussed in much detail. I will address this in two parts. This post will be a quick overview of Renderscript. A more detailed technical post with a simple example will be provided later.

Renderscript is a new API targeted at high-performance 3D rendering and compute operations. The goal of Renderscript is to bring a lower level, higher performance API to Android developers. The target audience is the set of developers looking to maximize the performance of their applications and are comfortable working closer to the metal to achieve this. It provides the developer three primary tools: A simple 3D rendering API on top of hardware acceleration, a developer friendly compute API similar to CUDA, and a familiar language in C99.

Renderscript has been used in the creation of the new visually-rich YouTube and Books apps. It is the API used in the live wallpapers shipping with the first Honeycomb tablets.

The performance gain comes from executing native code on the device. However, unlike the existing NDK, this solution is cross-platform. The development language for Renderscript is C99 with extensions, which is compiled to a device-agnostic intermediate format during the development process and placed into the application package. When the app is run, the scripts are compiled to machine code and optimized on the device. This eliminates the problem of needing to target a specific machine architecture during the development process.

Renderscript is not intended to replace the existing high-level rendering APIs or languages on the platform. The target use is for performance-critical code segments where the needs exceed the abilities of the existing APIs.

It may seem interesting that nothing above talked about running code on CPUs vs. GPUs. The reason is that this decision is made on the device at runtime. Simple scripts will be able to run on the GPU as compute workloads when capable hardware is available. More complex scripts will run on the CPU(s). The CPU also serves as a fallback to ensure that scripts are always able to run even if a suitable GPU or other accelerator is not present. This is intended to be transparent to the developer. In general, simpler scripts will be able to run in more places in the future. For now we simply leverage the CPU resources and distribute the work across as many CPUs as are present in the device.

The video above, captured through an Android tablet’s HDMI out, is an example of Renderscript compute at work. (There’s a high-def version on YouTube.) In the video we show a simple brute force physics simulation of around 900 particles. The compute script runs each frame and automatically takes advantage of both cores. Once the physics simulation is done, a second graphics script does the rendering. In the video we push one of the larger balls to show the interaction. Then we tilt the tablet and let gravity do a little work. This shows the power of the dual A9s in the new Honeycomb tablet.

Renderscript Graphics provides a new runtime for continuously rendering scenes. This runtime sits on top of HW acceleration and uses the developers’ scripts to provide custom functionality to the controlling Dalvik code. This controlling code will send commands to it at a coarse level such as “turn the page” or “move the list”. The commands the two sides speak are determined by the scripts the developer provides. In this way it’s fully customizable. Early examples of Renderscript graphics were the live wallpapers and 3d application launcher that shipped with Eclair.

With Honeycomb, we have migrated from GL ES 1.1 to 2.0 as the renderer for Renderscript. With this, we have added programmable shader support, 3D model loading, and much more efficient allocation management. The new compiler, based on LLVM, is several times more efficient than acc was during the Eclair-through-Gingerbread time frame. The most important change is that the Renderscript API and tools are now public.

The screenshot above was taken from one of our internal test apps. The application implements a simple scene-graph which demonstrates recursive script to script calling. The Androids are loaded from an A3D file created in Maya and translated from a Collada file. A3D is an on device file format for storing Renderscript objects.

Later we will follow up with more technical information and sample code.

"

What you can get from MOBOSQUARE in new year?

What you can get from MOBOSQUARE in new year?: "

Not having heard of MoboSquare? We decided to look into it. What we found was actually pretty interesting. Having never been a fan of check-in services like Foursquare personally, MoboSquare is basically Foursquare… for apps and games.

MoboSquare lets you become the mayor of applications and games, earn badges and it works basically along the lines of Foursquare. You can also post short reviews, recommend apps and games to other people, and share them on social networks such as Facebook and Twitter but it also features a lot of those social networks features as well like badge privilages and followers/following.

That’s not the end of it though! MoboSquare also offers up Scoreloop and OpenFeint style features as well such as awards and achievements that can be unlocked and earned. Leaderboards for games and whatever else you can put a leaderboard on as well as challenges. Developers don’t even have to have MoboSquare integrated into their games or applications for people to become mayor of them either just like Foursquare and locations.

Overall this seems like a pretty complete package and we are confident that this will end up becoming popular, at least with the millions of check-in services users that are out there who love being the mayor of… well everything! Developers who are interested in integrating this into their applications or games can go check out the developer section of MoboSquare’s site and download the SDK.

You can download the official MoboSquare app (in beta form) off the Android Market for free as well.

"

ComScore: Android surpasses IOS in U.S. market share

ComScore: Android surpasses IOS in U.S. market share: "

ComScore has released its latest mobile report releasing that Android OS has surpassed Apple’s iOS in terms of U.S. smartphone subscriber share for the first time.

The data shows that up to 63.2 million people in the U.S. are using smartphones during period, up 60% from last year.

IRIM led the first place in the market share of smartphones, but declined a little from 37.3 in September to 31.6 in November. Google’s Android took second place with 28.7 percent market share of smartphones, which is up 7.3 percentage points versus September’s 21.4%. Apple accounted for 25 percent of smartphone subscribers (up 0.7 percentage points), followed by Microsoft with 8.4 percent and Palm with 3.7 percent.

Judging from the data above, we can see a promising future for Google’s Android!

"

Android 2.3.3 brings New NFC Capabilities

Android 2.3.3 brings New NFC Capabilities: "

As we mentioned back in December, Google revealed that new NFC capabilities would come with the new system. Yesterday Google has announced an update to Android 2.3 which enables more near-field communication (NFC) functionality for developers and future phones.

With this release, we can see some new features added in the 2.3.3 platform:

• A comprehensive NFC reader/writer API that lets apps read and write to almost any standard NFC tag in use today.


• Advanced Intent dispatching that gives apps more control over how/when they are launched when an NFC tag comes into range.


• Some limited support for peer-to-peer connection with other NFC devices.

In Android 2.3.3, Google has added a full-featured NFC read and write API, which will work with “almost any standard NFC tag in use today.” They’re also providing developers with better control over how their apps react when an NFC tag comes into range.

"

PHP for Android

PHP for Android: "

irontec mendevelop project android untuk php. Sehingga PHP dapat berjalan di platform android. PHP yang merupakan bahasa server web (web scripting). PHP yang di jalankan di android memiliki webserver sendiri dan editor tersendiri. Dengan adanya project ini Anda dapat mendevelop web php sederhana dari gadget android Anda.  Bermanfaat bukan ?

Berikut Adalah VIdeo penggunaan php di android.

PHPforAndroid.apk HOWTO install and test from irontec on Vimeo.

Anda dapat mendownload applikasi ini di http://phpforandroid.net . Yang di butuhkan android minimum Android 1.5. Dan aplikasi ini support untuk PHP 5.3.

"

App Inventor for Android Launched

App Inventor for Android Launched: "

Google have just announced App Inventor, a new tool in Google Labs that makes it easy for anyone – programmers and non-programmers, professionals and students – to create mobile applications for Android-powered devices.

App inventor will not only make Application development for Android easier, but it will even change the way people use their mobile phones. We have previously mentioned that Google Android is targeting developers, and today we are discovering that it’s trying to make application development easier even for non-programmers.

No other mobile platform will be able to compete with Google on this side. The only negative point for Android remain the differences/incompatibilities between versions, especially that we started already talking about Android 3 – Gingerbread.

From App inventor website :

To use App Inventor, you do not need to be a developer. App Inventor requires NO programming knowledge. This is because instead of writing code, you visually design the way the app looks and use blocks to specify the app’s behavior.

An online development environment will definitely make a revolution for the Android platform, even if you will say that applications will be limited in features compared to advanced programming capabilities.

With App Inventor you can create location-aware applications, for example to help you remember where you parked your car, an app that shows the location of your friends or colleagues at a concert or conference, or your own custom tour app of your school, workplace, or a museum. Or simply apps that use the phone features of an Android phone such texting, camera, sensors, … etc. But if you are more familiar with webservices you will be able even to interact with your favorite websites such Amazon and Twitter… etc.

App Inventor  gallery already include apps such :

DROIDMuni : displays schedules for the San Francisco transit system. After the user selects from one of the transits lines and choosing a direction and particular stop, the application will display the lines next arrival times. Once the user has retrieved the desired arrival times, they are able to set up to four favorites which are saved and stored based on their unique e-mail address. Using the DroidMuni remind feature, the user can set a reminder to be notified when a bus is a specified number of minutes away.

ParkIt : allows users to locate their car on their Android phone. After clicking the “Park It” button, the app stores the users car’s location until the “Find It” Button is clicked. The “Find It” button displays the user’s current location, and the user’s car’s location using latitude and longitude. When the user clicks “Show On Map”, GoogleMaps is activated, and the route to the car is displayed.

Drum Kit : allows the user to hit seven different parts of a full, labeled drum kit and hear each drum’s respective sound. This app allows the user not only to learn more about the drums (i.e. the names and sounds of the drums), but also to have fun and create their own beat.

Super Hero Game : a fantastic Quiz game that tests the users true Super Hero Knowledge. Each screen shows a different character from a superhero world and asks a question pertaining to that picture. The user types in the answer and clicks submit. The program responds with a RIGHT or WRONG and the user is prompted to go on to the next question. The question will change as well as the picture. If the user wants to quit at any time they can GIVE UP and the program closes.

Where’s Speedo : allows a user and a users friends or family find each other. The app detects the user’s location and sends it to the users friends or family using the app. The app allows the user to view the location of another user on a map. It also allows the user to set how often the app sends his/her location.

I think we should expect more amazing apps from this magical inventor ! Behind the app inventor a research work conducted in MIT including the Open Blocks Java library used by the blocks editor, Open Blocks visual programming which is closely related to the Scratch programming language, and Kawa Language Framework and Kawa’s dialect of the Scheme programming language used to translates the visual blocks language for implementation on Android.

App inventor is still invitation only, and you can complete this form to get an invitation when available.

source http://openhandsetmagazine.com/2010/07/app-inventor-for-android-launched/

"

Tutorial Membuat Icon Twitter Burung Terbang

Tutorial Membuat Icon Twitter Burung Terbang: "

Berikut ini adalah tutorial membuat icon twitter dengan animasi burung yang bisa terbang mengikuti arah gerakan seperti terbang naik-turun dan bisa bertengger pada setiap kotak yang ada pada blog/situs. Sebenarnya cara ini cukup mudah dan gampang, namun karena ada teman yang bertanya kepada saya maka kali ini saya buatkan tutorialnya secara singkat dan mudah.

Semoga tutorial berikut dapat membantu teman-teman sesama blogger maupun pengunjung blog saya. Oke, tanpa perlu panjang lebar, berikut adalah langkah-langkahnya:

1. Masuk (Login) ke Dashboard Blogger anda.
2. Pilih Tab Design, lalu Page Elelement.
3. Kemudian Tambahkan Gadged/Widget (Add a Gadged), pilih HTML/JavaScript. (Bebas diletakkan dimana saja).
4. Dari gadget/widget HTML/JavaScript tersebut, silahkan copy script 'JavaScript' dibawah: (tanpa title/judul/tanpa memasukkan nama untuk gadged/widgetnya).

Copy script berikut ini, agar tidak terjadi kesalahan kode jangan langsung di paste ke gadged/widget, tapi paste dulu ke notepad kemudian dari notepad copy lagi dan dimasukkan ke gadged/widget HTML/JavaScript sesuai petunjuk diatas.

source : http://www.imemovaz.com/2011/02/tutorial-membuat-icon-twitter-burung.html

"

Twitter Bans Popular Mobile Apps for Violating Policies

Twitter Bans Popular Mobile Apps for Violating Policies: "

Many users today are having issues logging into their Twitter accounts from mobile apps UberTwitter, Echofon, and Twitdroyd. According to Twitter itself, there's a really good reason for that. They've suspended the apps from the service for violation of Twitter's policies. The remedy? Twitter says you should use the official apps.

Twitter's official statement on the issue says the apps were kicked for a privacy issue involving Direct Messages over 140 characters, trademark violation, and for altering user tweets to make money. On the issue of trademark violation, apparently Twitter doesn't like the use of the term TweetUp by UberMedia (developer of UberTwitter and Twitdroyd). The full extent of issues in Echofon are not yet clear.

If you take Twitter's word for it, they've been telling the developers about these issues for months, and this is their last recourse. If so, the devs are to blame for not fixing the issues and leaving their paying users out in the cold. Since this is being called a suspension, not an outright ban, we assume these apps can find their way back to Twitter's good graces. In the meantime, it's an opportunity for competing apps to gain users.

"

Tap to Share Capability Coming to Android in Newest Update

Tap to Share Capability Coming to Android in Newest Update: "

HP made a point of showing off their tap to share capability at the announcement for the HP TouchPad and Pre3, but Google's newly minted version of Android enables a similar capability. It may have gotten lost in the shuffle, but by employing the new Near Field Communication (NFC) and Bluetooth APIs, Android users of the future will be able to enjoy some impressive feats of content sharing. The changes are coming in Android 2.3.3, and will require an NFC chip.

For the time being, only the Nexus S will be a candidate for this technology. It is the only phone with Gingerbread, and an NFC chip at this time. The new APIs will allow for seamless pairing over Bluetooth of two devices by tapping them together. No more awkward syncing up required. HP's version of tap to share was only demoed pushing URLs across devices, but the new Android update will allow any data to be sent across the Bluetooth link.

The 2.3.3 update has yet to go out, but Nexus S users should be seeing it soon. We'll be keeping an eye on this technology to see how developers use it. 

"

Photo Awesome #20: Name That Hardware!

Photo Awesome #20: Name That Hardware!: "

As you can no doubt imagine, sifting through products we've received from the past can be a hilarious experience. But every now and again we'll un-earth things that make us go, "wait, what?". So we decided to give you a quick geek quiz to round out your week. Have a look at the following four items, and see if you can tell us what they are, or more importantly, why they're hilarious. 

Hit up the comments with all your guesses, and stay tuned, 'cause on Tuesday, we'll reveal all the answers for you, as only Gordon Mah Ung could write them. Have a phenomenal weekend guys, we'll see you next week! 

 

We had to blur out the manufacturer on this one, otherwise, it'd just be too easy. 

 

 

Hit up the comments with all your guesses, and stay tuned, 'cause on Tuesday, we'll reveal all the answers for you, as only Gordon Mah Ung could write them. Have a phenomonal weekend guys, we'll see you next week! 

 

 

"

Coffee Table Meets Blackboard

Coffee Table Meets Blackboard: "
What will happen when coffee table meets blackboard? Strange as it may sound, but some designers can give us some incredible answers such as the following design concept.

Review The Codeigniter CMS : PyroCMS

Review The Codeigniter CMS : PyroCMS: "

The temptation of codeigniter project that hosted in http://www.codeigniter.com/ is rising within the time stamp. The claim of the best php framework can be seen through the further works from its fans. Codeigniter nowdays used to solve the fast development web project that allow the programmers initiate and inovate. And among side the object oriented concept that codeigniter compromised.

The magnificent CI form works is make it usable as the Content Management System (CMS). This aspect of market is target the users level of website management. You (programmer) like to said that it was the end user level of your development.

One of the focused today is about the PyroCMS. PyroCMS is the manifest of works that create the CMS it self. PyroCMS leads you to its fantastic feature. Security is number one that pyro perform in their website. They said that with Cross-Site Request Forgery protection, XSS filtering and very secure password encryption your website is safe with PyroCMS. PyroCMS is also said to be faster and yet fasted. Its can be achieve because they claim that they have surely done with performing javascript better and better, through network speed and the lightweight of pyro.

Another plus in this CMS is the facility to maintain user to divide them to any access level. You can also manage your file in specify public folder that can be filled with image, video, zipped file and many other. If you get cozy you’ll get help in built shop. This site enable the main currensy that can be set in administration setting.

Another feature of PyroCMS is about themes and add-ins. This CMS support the independence theme maker and support to giving out the plugins to the sites, just like wordpress did. You can also make your own theme by matching the structure in documentation. And you can add your own plugins like recaptcha, widget, feature article, social media, and many other. Last, you’ll get love to this is the integration capability to analytics. And filtering spam with akismet.

The Pyro CMS can be download by it hosted source at pyrocms.com or you can even download it through here.

---

The Preview

---

main administration page

Creating Article

Adding file and folder management in public area

User Management

Addins Management

Gallery Management

Themes Management

"

IM-ku BBM Indonesia Version

IM-ku BBM Indonesia Version: "

If the chat application may only be used by other brands of mobile phones or the same operator, according to PT Intouch Innovate Indonesia, it was the same as in the past where SMS service can not be cross-operator.

Therefore, inTouch bring innovation local chat homemade entitled IM me, or my Instant Messenger.

“The name was chosen according to its mission to develop a national chat service is useful for all stakeholders in the industry, including consumers, operators, and local vendor,” said Kendro Hendra, CEO of Innovate inTouch Indonesia, on the sidelines of the event ICS 2010, the Jakarta Convention Center, Friday July 16, 2010.

Not only BlackBerry users, users of Symbian OS and all Java-based mobile platform can use my IM applications, including local phone. Can all be enjoyed free of charge (excluding the cost of GPRS), although different brands of mobile phones and operators.

“It is time popular applications like chat can be used universally,” Kendro said. “We are confident, my IM can be absorbed quickly over the supported local vendors and operators,” he said.

So, what’s the difference with my IM application Messenger, MSN Messenger, Gtalk, or eBuddy? “This is the uniqueness of my IM. So using this application and sign up to the server via SMS, you can invite or invite friends from his cell phone only, “Kendro said.

Way, a user can send an SMS containing the URL address and then download it.

Similarly, in general IM, IM my avatar also comes with a feature, set the status, conferences, groups, chatbox, and smileys.

To get this application, users simply download it directly in the browser on your phone by typing the following URL address or by sending an SMS with the format IMKU to number 9800.

"

Blogging With Java, Why Not?

Blogging With Java, Why Not?: "

If you were long lasting your heart with java you might have know well these tools that help you build your blog ready to public. These list is the all know blogging engine built in java platform. So if you could running it on the web you need to fellow the host with tomcat ready on its server.

1. Snip Snap
   
   

   snipssnap logo

   
   

   SnipSnap is a free and easy to install weblog and wiki tool written in Java.



2. Blojsom
   
   

   blojsom logo

   
   

   A lightweight blog package written in Java that is inspired by blosxom. blojsom aims to retain the simplicity in design of its Perl-based “relative” while adding user flexibility in areas such as the flavors, templating, plugins, and the ability to run a multi-user blog with a single blojsom installation.



3. Thingamablog
   
   Thingamablog is a cross-platform, standalone blogging application that makes authoring and publishing your weblogs almost effortless. Thingamablog does NOT require a third-party blogging host, a cgi/php enabled web host, or a MySQL database. In fact, all you need to setup, and manage, a blog with Thingamablog is FTP, SFTP, or network access to a web server.
   
   

   thingamablog logo



4. DLOG 4J
   
   DLOG4J provides a full-featured, cross-platform, multi-database, wap-supported personal information portal, based on JSP/Servlet.Features:
   
   * WYSIWYG blog & comment editor
   
   * Insite Point to Point message transport
   
   * RSS aggregation
   
   * WAP support
   
   * Open and private blog category
   
   * Mail notification when commented
   
   * RDF, RSS, ATOM support
   
   * International support
   
   * Multi database (JDBC 2.0 compatibled) support


5. Blogunity
   
   

   blogunity logo

   
   

   * Community based blogging software
   
   * Uncomplex easy one minute installation routine
   
   * Easily deployable on any j2ee compliant application- and web servers
   
   * Provides support for 16 well known database-engines
   
   * Offers freely configurable number of individual/communtiy blogs per user
   
   * Simple but powerful editing of blog-articles using wiki-syntax
   
   * Flexible theme editing separate for each blog
   
   * Simple user management and blog administration via web interface



6. MapleBlog
   
   MapleBlog is a simple MVC Struts 1.1-based Web log that uses Hibernate as its model layer and Tiles/JSP for its View.


7. Blog-java
   
   Blog is an interface for managing a multi-topic blog (Web journal). Its easy interface allows users to quickly create journals with several topics, all of which are concurrently accessible.


8. JSP Blog
   
   JSP Blog is a Weblog written in pure JSP, built with Tomcat and MySQL.


9. The Roller Web Blogger
   
   A server-based weblogging software & a web application that is designed to support multiple simultaneous weblog users and visitors. Roller supports all of the latest-and-greatest weblogging features such as comments, WYSIWYG HTML editing, page templates, RSS syndication, trackback, blogroll management, and provides an XML-RPC interface for blogging clients such as w:bloggar and nntp//rss.


10. Peeble
    
    Pebble is a lightweight, open source, blogger that is written as a web application to run inside J2EE web containers using standards-based technologies such as JSP, servlets, filters, JSP custom tags, JSTL and JAXP. Running as a web application in any JSP 1.2/Servlet 2.3 compatible web container, Pebble maintains blog entries as XML files and serves up blog content dynamically. All maintenance of blog entries, blog properties, themes and so on is performed through your web browser, negating the need to telnet/ssh to the host and making Pebble ideal for anybody who is constantly on the move, or accesses the Internet through a firewall/proxy server.


11. Sprout
    
    Sprout is a simple blogger, but it’s also a HTTP & SQL base on top of which you can build any system: CMS, game server, campaign site; you name it! Sprout uses a node graph database structure, that allows you to store complex dynamic object hierarchies without altering the database table structure. You can still add normal tables with Memory for table like data structures. Sprout contains basic user handling in the main package because you will likely need that; while articles, comments and files are in a demo specific content package.

Resource : http://java-source.net/open-source/bloggers

"