Lol, "Windows mentality". Not exactly as I'd describe it, and besides, that's an awfully black and white view of the world; "either one of the other"
Originally Posted by rwhitby
I think more of Internalz like FireFox. Firefox mainly is a web browser, but it can direct-view images just fine, as can it view text files. And if you have plugins or extensions in FireFox, it handle far more; multimedia, documents, etc.. And everything that FireFox can't handle, it passes off to the user's system to handle.
Internalz is the same way. I developed things like the text editor and image viewer in Internalz and the system couldn't handle those in a way I like. As for the Ipk Installer and Patchers, I began work on those around March/April, as some of my private beta testers can attest. At the time, Preware's stance on local ipk files was that they were a security risk and local installation wouldn't be coming. So I began work on the Internalz Ipk Installer and figured I could create a Patcher using similar code as in WOSQI. They weren't ready for release in time for my b-day (April 22nd, the release date of v1.0 of Internalz), so I held it off until v1.2, released over a month ago.
Personally, I don't subscribe to the black and white "window or linux" philosophy WebOS-Internals follows. I believe it depends on the situations. There is no text editor, so I built one. See a public need and provide it; filling in the empty spots in the operating system. That's what homebrew (and to a larger extent, all 3rd party applications) is all about.
And just like FireFox, Internalz is designed to operate in multiple, separate windows (in the case of webOS, cards), almost like separate sub-applications. Yes, you could think of that similar to Windows Explorer with Notepad, and Microsoft Picture Viewer, but in that similarity could be applied to Linux too, like Ubuntu as well, with Nautilus, Gedit, etc..
Anyway, back on topic. Functionality-wise, I believe Internalz is better for off-feed ipk intalls. From day 1, Internalz's Ipk Installer was meant for off-feed ipk files; to complement Preware, not replace it. Preware is great for managing packages, but when it comes to local files and their manipulation, Internalz is better, in my opinion. Despite implications that Internalz ipk install is unreliable or unproven; it uses the same .ipk install service as preware and the SDK, and even filecoaster (though I think myself and Rod can agree fileCoaster may not be a wise choice ).
Standards-wise, Internalz uses the same universal .ipk format as Palm and the rest of the webOS homebrew world. Ipk files installed in Internalz will be listd properly in Preware. So there really is no standards different between the two and users can feel confident with either choice.
Lastly, I feel I should point out there are a few minor visual/feature differences in Internalz, compared to Preware. Internalz displays package information: stuff like appid, version, developer, filepath, etc.. In addition, it shows users if the ipk has a postinst or prerm script. Not necessarily useful information, but I like it. As well, Internalz supports post-install/post-removal restart flags for advanced homebrew ipk files. I hope/expect Preware will eventually implement that in the future as it can be handy for ipk files that use it. Lastly, as of v1.3, Internalz supports the Copy to User Storage option, for files like email attachments, that aren't available in the usb mode area (see the
). This can be crucial for those like myself that like to store away off-feed ipk files (for various reasons, like backup).
Though when it come down to it, I'll always be biased to Internalz, and Rod will always be biased towards Preware. They're our creations and we want others to love and use them as much as we do.
And all feelings/opinions aside, they each have their pros and cons and it's up to the user to decide. Can't go wrong with either, really. And I think everyone can agree that it's great to have options; especially options that are interoperable, integrated, free and easy to use for the average user. Heh, I'd like to see Apple allow that.