Skip to content

Latest commit

 

History

History
45 lines (38 loc) · 3.03 KB

README.md

File metadata and controls

45 lines (38 loc) · 3.03 KB

PixelyVulpine-Layout

Powerful, modern and lightweight framework library for J2ME MIDlets

Objectives

To be beautiful

The framework shall follow modern's minimalist standards with some smooth animations

To be independent

No use of third-party libraries, unless they are open-source and accepts the MIT license (Code shall be merged, .jar must not be used)
I want it to be usable in J2ME SDK Mobile, so i can't use .jar libraries on this

To be universal

It should be compatible with QWERTY, Candybar and Touchscreen devices. Compatible with atleast 90% of MIDP 2.0+ CLDC 1.1 phones, from lower to higher end devices
The UIs shall also be automatically adjustable to the screen's resolution
It shall be cool to use on Android devices with J2ME Loader aswell like it were a native Android app

To be touch optimized

There's few J2ME apps that works great on touch, it should be well optimized for touch devices, but still, it needs to be 100% compatible with non-touchscreen devices

To be lightweight

It should cost few RAM and storage resource, main maximum should be 40Kb, but no more than 100Kb

To be customizable

The developer will be able to customize colors, textures, backgrounds and create it's own custom contents for this framework

To be easy

It should be easy to use on IDEs. Just some layout.addContent(Content) and you made a cool advanced design

Open-source

It shall be open-source and MIT license, so you can do your projects, including closed-source ones, without the need to reinventing the whell

To be fast

There'll be loading ofcourse, but they should not disturb much and take much long

Multilanguage

The developer should be able to make their MIDlet multilanguage with some XML file.

To be laggy... But not much

Miracles can't be done, ¿right? These phones were itself laggy. Target is from 10 to 24 FPS with some few cool effects. It may drop to 2 or 4 FPS, however, it is the developer's (and the phone's capabilities) responsability on this. But the framework needs to be sufficiently optimized to keep the framerate stable.
To keep the FPS stable, heavy effects like transparency will exist, but limited and not standardized, and will be manually and automatically configurable.

Legacy compatible (maybe)

It might be compatible with legacy LCDUI APIs

Example concept:

Actual look for now:

2021 08 31_23 15 31_2 2021 08 31_23 15 31_4 2021 08 31_23 18 55_1 2021 08 31_23 20 10_1