Free portal pendidikan utusan software for mac

BioMed Lab Portal Server Package 0.80 is designed as a useful package containing a MacOS X Installer for a self-contained BioMed Laboratory Portal Server for intranet use for a biomedical research laboratory. It includes Apache web server with all the standard components (PHP, MySQL, Perl etc) from XAMPP, and XOOPS system with PubMedPDF module for managing thousands of PDF reprints from journals.

PubMedPDF integrates very nicely with the popular iPapers application, automatically indexing papers collected by iPapers and making them available via the Lab portal site for Mac and Windows alike. It also includes PHP-based PukiWiki system for managing notes and documentations for lab use. It is suitable for maintaining various lab notes and manuals, FAQs and instructions for daily activities of any lab. Modifying these web contents may be done via a standard browser, and simple changes can literally be done in a matter of seconds.

mojoPortal, is an open source web site framework and content management system written in C# that runs under Mono on Linux or Mac OS X or under ASP.NET on Windows.
You can think of mojoPortal as a Starter Kit for Advanced ASP.NET Portals and Web Sites.
Out of the box, mojoPortal provides dynamic database driven web site(s) with an XHTML compliant Content Management System and community features like Blogs, Forums, Image Galleries, etc.

Main features:
- Runs under Mac OS X, Windows/IIS or mono/Apache with most GNU/Linux distributions
- Works with MS SQL Server, MySQL, PostgreSQL, Firebird Sql, and SQLite databases
- Host multiple sites on 1 installation and db with host names
- XHTML Compliant Content Management with support for work flow and approval/publishing process
- Enter content with the FCKeditor , TinyMCE, or XStandard HTML WYSIWYG
- Blogs
- Forums
- Image Gallery
- RSS Feed Aggregator
- Event Calendar
- Contact Form
- File Manager - use with caution, provides direct access to the server file system.
- Shared Files module - looks and acts like the File Manager module but stores and manages files in a safe way on the server. Folders are really database items as are the friendly file names. Files are stored securely in a special folder and named using guid strings and a .config extension. This prevents them from being requested or served with a normal http request. Authorized users can download because the module serves them using Response.WriteFile. The module also supports versioning of files.
- User Profile Page - with easily customisable properties
- Member List Page
- Bread Crumbs
- Custom Skinning with support for user selectable skins and individual skins per page
- Flexible Menu system
- Localization - all labels and image alt text comes from a configuration file
- Configurable Whether to Encrypt Passwords
- Configurable Whether Registration requires e-mail confirmation
- Configure use of SSL for the whole Site or per Page
- Send Password Feature (when not using encryption)
- Url Re-writing for mapping friendly Urls to site pages
- Site Search with Role based filtering
- Error logging and optional debug logging
- Support for LDAP Authentication using Active Directory or OpenLDAP
- Support for Windows NTLM authentication
- Support for OpenID authentication
- Support for Windows Live ID authentication
- Personalization with WebParts
- Numerous attractive skins with Table-less CSS layouts
- Site Statistics and Who Is Online
- Poll Feature - currently only available using MS SQL or MySQL
- Survey Feature - currently only available using MS SQL or MySQL
- Newsletter

Enhancements
- Content Versioning
- The Html Content and Blog features now support keeping a history of every edit (like a wiki). You can compare any historical version of the content to the current version and you can restore any version to the editor so that you can restore it as it is by saving it or modify it further then save it. Versioning can be enabled at the feature instance level or it can be enforced site wide from Site Settings or it can be enforced from Web.config. Site administrators and content administrators can delete history but no other roles are allowed to delete the history. The ContentHistory is built into the core so that it does not have to be re-implemented for each feature. Each feature does implement its own UI to show or restore the previous versions, but they leverage common business classes to store and retrieve their history. In the future we will implement versioning for product and offer descriptions in the WebStore, developers may also leverage this in their own features to keep version history for their own feature data. This is one more thing to mark off our Road Map as complete. Next up is a general Content Tagging/Category system that can be re-used across features, and a Content Comment system that can be re-used across features.
- Web Chat using Windows Live Messenger
- See my previous post for more information about the new Chat feature. This was not even on the roadmap but when I saw how easy it was to implement I decided to work on it. It was fun and it only took a few days. One of the things I like best about my job is that I can just decide to work on something for a few days because its fun.
- New PlugNPay Payment Gateway in WebStore thanks to Voir Hillaire
- New Skin - dcarter-bluedesert, based on dcarter-ticktockpro but modified and contributed by Sami Isamil Hassan
- Various minor enhancements based on feedback and fixes for bugs reported in the forums since the last release.
- More progress moving away from ExtJs by implementing some .NET controls for YUI to replace the ones I previously built for ExtJs
- Some of you may have checked out my Site Office UI prototype in the past. Its a separate plug in system than the main content system designed more for a consistent application user interface rather than for creative design like we use for the public facing web site via our skins. You can see the Site Office layout on this site or the demo site if you login and click the "Site Office" link at the top of the page, or you can look at the origianl layout demo for ExtJs here. I still have not implemented any real features for Site Office, but the plug in system itself works and Ive even received emails from developers who have implemented their own plug features using it. I got kind of side tracked off of the Site Office idea partly because I had spent quite a bit of time implementing .NET wrapper cntrols around the ExtJs javascript to make it easy to use and then the ExtJs project changed their license to GPL which is not compatible with our CPL license, so I could no longer get upgrades of ExtJs and include them with mojoPortal. Since then weve been stuck on version 2.0.2 of ExtJs which was the last version they shipped under the LGPL (which was compatible). I had also used a little ExtJs in the Contact Form for the messaage list page. For a long time Ive been thinking I really need to build new .NET wrapper controls with similar functionality but using the YUI javascript instead of ExtJs.
- So again in the name of fun (because I like building .NET controls around javascript) I spent some time implementing some new controls with YUI to replace the ExtJs stuff Ive been using. I have now removed the dependency on ExtJs from the Contact Form feature and Ive got a good start on the layout framework to replace the current SiteOffice. I still have more work to do to finish, but the goal will be to eliminate all use of ExtJs in favor of YUI. The ExtJs javascript we include in mojoPortal is 6.36 MB, so it will reduce the size of our downloads once we no longer need to it. Anyway, you can see the work Ive done so far on the YUI layout here, its very similar as you can see to the current Site Office layout with ExtJs. Once I get some more of the YUI things wrapped up so they are easy to use, I might even change the site administration area so that it uses this kind of layout instead of the site skin.
- New Experimental CKEditor
- Some of you may have noticed that the FCKeditor project has shifted gears from the next upgrade of FCKeditor to their next generation version named CKEditor. I think they are basically taking the good parts from the FCKeditor implementation but doing a new redesign of the implementation using things they have learned and new techniques that have emerged to improve the architecture. The CKEditor does not yet have image upload or server browsing so I have disabled it by default, but anyone who really wants to check it out can un-comment it in the mojoEditor.config file in the root of the web. It really looks just like the FCKeditor but does not have all the functionality yet, I just figured it was good to get started with it so we can be ready as they make imporvements.

BolinOS is a modular publication and communication platform for Internet/Web development in order to enable simple management of complex portals.
BolinOS is based on a data structure compatible with Sqeleton, Internet/Web operating system, and uses standard open-source software: PHP, Apache, mySQL. BolinOS was developed in order to offer a simple and efficient platform that could take in account the quality and diversity of todays multimedia.
It is implemented and co-developed by Poinch.ch (www.poinch.ch - Swiss musical portal), the Radiology Department of Genevas University Hospitals (www.radiologie.hcuge.ch), Med-IA (www.med-ia.ch - medical multimedia portal), with a major actor that has permitted the start of everything: Wild, first Swiss web platform for the incubation of creators.
Many functionalities already exist. For example, an integrated agenda, email portal, groups and forums managemnt systen create a basic applicative set of easily integrated and publishable online tools.
There are also many more focused applications, such as multimedia albums, image collections, image manipulation applications or scientific poster making modules for online and paper publication. Many others are currently under development using the BolinOS framework.
Enhancements:
- New release that fix the security problem.

LibriBooks is a portal for selling rare, antique and out of print books, which has been programmed according to strict logic and technical outlines, to guarantee the easiest access to books and the most evidence from the search engines.

Libribooks defines clearly the bookshop contacts in the book form, leaving the buyer free to choose between a direct purchase or an online purchase without commission. Libribooks also offers a real time cataloguing of the subjects from the archive and provides the navigator with subject, author, title, and keyword search.

Weighted Companion Cube 0.1 is a neat application for Mac users. It is actually a free and animated Adium IM client dock icon pack featuring the Weighted Companion Cube from Valves game, Portal.

Requirements:

• Adium
• Mac OS X

Plone is a content management system for web publishing and the Zope application server.
The system provides pre-configured security and roles, a set of content types, and multi-lingual support, among other features. Plone is available under both GPL and commercial licenses.

Main features:
- Plone is flexible and powerful. It is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities.
- Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content.
- Plone is easy to install. You can install Plone with a click-and-run installer, and have a content management system running on your computer in just a few minutes.
- Plone is international. The Plone interface has more than 50 language translations, and tools for managing multilingual content.
- Plone is supported. There are close to a hundred developers in the Plone Development Team around the world, and hundreds of companies specializing in Plone development and support.
- Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3Cs AA rating for accessibility, in addition to using best-practice web standards like XHTML and CSS.
- Plone is Open Source. Plone is licensed under the GNU General Public License, the same license Linux uses. This gives you the right to use Plone without a license fee, and to improve upon the product.
- Plone is extensible. There are many add-on products for Plone that add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages.
- Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD.
- Plone is protected. The nonprofit Plone Foundation was formed in 2004 to promote the use of Plone around the world and protect the Plone IP and trademarks.

Enhancements
- This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.
- After Plone 3.2 (which focused on packaging/installer improvements), this is a minor release that adds some new features. It does not include any major changes: all products that work with Plone 3.0, 3.1 & 3.2 should also work in Plone 3.3. The upgrade from Plone 3.x is simple and non-invasive, ensuring a smooth upgrade experience.
Feature enhancements in this release:
Link type should automatically redirect when accessed directly:
- Links should be capable of doing automatic redirection.
Resource Registries Improvements:
- Allow Resource Registries to use conditional comments for CSS to bring the IEFixes.css into the registry and allow external references to resources for all registries.
Standardizing our use of INavigationRoot:
- Plone has the INavigationRoot marker interface which supports rooting your tabs, navigation, breadcrumbs, sitemaps and searches to a specific container inside of a portal which itself is a INavigationRoot. Some areas of this need to be cleaned up and standardized to follow a consistent convention.
Minor i18n upgrades:
- Include PloneLanguageTool 3.0 and PTS 1.5.
Disable inline editing by default:
- The current inline editing behaviour as introduced in Plone 3 was a mistake: it is a cool technology to show off, but in practice accidental clicks very frequently lead to unwanted edit-screens.
Adapterise the Extensible Indexable Object Wrapper:
- Make it easier to register ExtensibleIndexableObjectWrapper attributes with adapters
Improve locking configurability:
- This PLIP proposes to a) make it harder to accidentally leave content items in a locked state, and b) make it easier to adjust the lock timeout or disable locking entirely.
Clean up auto-sort, auto-order code:
- Clean up, i.e. remove all code related to auto-sorting / auto-ordering folder contents as this feature was implemented for Plone 2.1, but never got enabled. Basically this proposes to revert http://plone.org/products/atcontenttypes/roadmap/3
Replace workflow history viewlet with content history viewlet:
- Plone stores both workflow history and versioning history for objects. Only workflow history is shown in a viewlet in current Plone versions. I propose to show all history data.
View for rendering events as an iCalendar file:
- Make it possible to subscribe to Plone events in the standard iCalendar format.
Automate ZCML Loading for Plone Plug-ins:
- Enable automatic plugins for Plone with z3c.autoinclude